[Kernel-packages] [Bug 1829737] Re: Bluetooth: hci0: request failed to create LE connection: status 0x0c (Intel 9462/9560)
** Changed in: linux-firmware (Ubuntu) Importance: Undecided => Critical ** Changed in: linux-firmware (Ubuntu Bionic) Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1829737 Title: Bluetooth: hci0: request failed to create LE connection: status 0x0c (Intel 9462/9560) Status in HWE Next: New Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Bionic: In Progress Bug description: For kernel version >= 4.19, it fails to pair with BT4.0 HID devices and leave error messages in syslog: Bluetooth: hci0: request failed to create LE connection: status 0x0c Which can be detailed by btmon: < HCI Command: LE Extended Create Connection (0x08|0x0043) plen 26 #800 [hci0] 30.895622 Filter policy: White list is not used (0x00) Own address type: Public (0x00) Peer address type: Random (0x01) Peer address: DB:DD:51:2D:1C:CC (Static) Initiating PHYs: 0x01 Entry 0: LE 1M Scan interval: 60.000 msec (0x0060) Scan window: 60.000 msec (0x0060) Min connection interval: 30.00 msec (0x0018) Max connection interval: 50.00 msec (0x0028) Connection latency: 0 (0x) Supervision timeout: 420 msec (0x002a) Min connection length: 0.000 msec (0x) Max connection length: 0.000 msec (0x) > HCI Event: Command Status (0x0f) plen 4 #801 [hci0] 30.896453 LE Extended Create Connection (0x08|0x0043) ncmd 1 Status: Command Disallowed (0x0c) Indicating this is actually a firmware problem. Verified this has been fixed at least in upstream linux-firmware commit 29a536a02cadb75b84c6c0b5d7af22d34d278563, firmware release version 21.10.0.6. With that firmware blob placed under /lib/firmware/intel and a cold boot, dmesg gives updated revision and device pairing works as expected: Firmware revision 0.1 build 184 week 15 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1829737/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829725] Re: af_alg06 test from crypto test suite in LTP failed with kernel oops on B/C
https://lists.ubuntu.com/archives/kernel-team/2019-May/100831.html ** Description changed: - LTP: starting af_alg06 - BUG: unable to handle kernel paging request at 9cbe - IP: sha256_transform+0x28/0x1b20 - PGD 4d341067 P4D 4d341067 PUD 4d345067 PMD 4d346067 PTE 0 - Oops: [#1] SMP PTI - Modules linked in: authenc algif_aead xfrm_user xfrm_algo sha3_generic algif_hash salsa20_generic algif_skcipher af_alg kvm_intel kvm irqbypass joydev input_leds serio_raw mac_hid sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear cirrus ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops virtio_net psmouse virtio_blk drm i2c_piix4 pata_acpi floppy - CPU: 0 PID: 24368 Comm: af_alg06 Not tainted 4.15.0-50-generic #54-Ubuntu - Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014 - RIP: 0010:sha256_transform+0x28/0x1b20 - RSP: 0018:b58e8344baa0 EFLAGS: 00010283 - RAX: 0034 RBX: 9cbe000c RCX: - RDX: RSI: 9cbdffcc RDI: b58e8344bca8 - RBP: b58e8344bbd0 R08: 1b6c96f6 R09: b58e8344baa0 - R10: 7a9a01a1 R11: 1ecb7428 R12: 9cc0f332c00c - R13: b58e8344bca8 R14: 9cbff4d8d048 R15: 9cbff332c00c - FS: 7f9f2a44d580() GS:9cbfffc0() knlGS: - CS: 0010 DS: ES: CR0: 80050033 - CR2: 9cbe CR3: 7c1da000 CR4: 06f0 - DR0: DR1: DR2: - DR3: DR6: fffe0ff0 DR7: 0400 - Call Trace: - sha256_generic_block_fn+0x36/0x50 - crypto_sha256_finup+0xef/0x170 - crypto_shash_finup+0x25/0x30 - shash_digest_unaligned+0x47/0x60 - crypto_shash_digest+0x2e/0x40 - hmac_setkey+0x15a/0x210 - ? tty_insert_flip_string_fixed_flag+0x86/0xe0 - crypto_shash_setkey+0x35/0xc0 - ? pty_write+0x71/0x90 - shash_async_setkey+0x15/0x20 - crypto_ahash_setkey+0x38/0xb0 - crypto_authenc_setkey+0x68/0x100 [authenc] - crypto_aead_setkey+0x35/0xc0 - aead_setkey+0x15/0x20 [algif_aead] - alg_setsockopt+0x112/0x140 [af_alg] - SyS_setsockopt+0x86/0xf0 - do_syscall_64+0x73/0x130 - entry_SYSCALL_64_after_hwframe+0x3d/0xa2 - RIP: 0033:0x7f9f29f61e6a - RSP: 002b:7ffdd050ba38 EFLAGS: 0207 ORIG_RAX: 0036 - RAX: ffda RBX: 7f9f2a44d500 RCX: 7f9f29f61e6a - RDX: 0001 RSI: 0117 RDI: 0006 - RBP: 0006 R08: 0009 R09: 7ffdd050b960 - R10: 7ffdd050ba4f R11: 0207 R12: 0001 - R13: R14: R15: 56456d64d908 - Code: 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 57 41 56 41 55 41 54 53 48 81 ec 08 01 00 00 65 48 8b 04 25 28 00 00 00 48 89 45 d0 31 c0 <8b> 14 06 0f ca 89 94 05 d0 fe ff ff 48 83 c0 04 48 83 f8 40 75 - RIP: sha256_transform+0x28/0x1b20 RSP: b58e8344baa0 - CR2: 9cbe - ---[ end trace ac2d55c95d4eed9d ]--- + == Justification == + From the commit message: + Keys for "authenc" AEADs are formatted as an rtattr containing a 4-byte + 'enckeylen', followed by an authentication key and an encryption key. + crypto_authenc_extractkeys() parses the key to find the inner keys. + + However, it fails to consider the case where the rtattr's payload is + longer than 4 bytes but not 4-byte aligned, and where the key ends + before the next 4-byte aligned boundary. In this case, 'keylen -= + RTA_ALIGN(rta->rta_len);' underflows to a value near UINT_MAX. This + causes a buffer overread and crash during crypto_ahash_setkey(). + + This error can be reproduced easily with the af_alg06 test in LTP test + suite. (Basically it's the reproducer in the commit message) + + == Fix == + 8f9c4693 (crypto: authenc - fix parsing key with misaligned rta_len) + This patch can be cherry-picked into B/C, and it's already in X/D/E. + + == Test == + Test kernels could be found here: + https://people.canonical.com/~phlin/kernel/lp-1829725-afalg06/ + + Both verified on a KVM node, this issue will no longer exist. + + == Regression potential == + Low, this patch just improves the checking for rtattr payload size to make sure it's the expected size. Also It has been upstream since 2018 Dec. and applied in some of our kernels. No subsequent bug report was filed against it. + + + LTP: starting af_alg06 + BUG: unable to handle kernel paging request at 9cbe + IP: sha256_transform+0x28/0x1b20 + PGD 4d341067 P4D 4d341067 PUD 4d345067 PMD 4d346067 PTE 0 + Oops: [#1] SMP PTI + Modules linked in: authenc algif_aead xfrm_user xfrm_algo sha3_generic algif_hash salsa20_generic algif_skcipher af_alg
[Kernel-packages] [Bug 1826461] Re: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection.
It should be safe. Let's see if it's already fixed upstream, before bisecting between two older kernel versions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826461 Title: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection. Status in linux package in Ubuntu: Confirmed Bug description: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection. Ubuntu 18.04, Thinkpad X240, Sierra modem Reproduced on 4.15 and 4.18 kernel. The bug is triggered only when there is no WiFi connection. After waking laptop from suspend ModemManager stops working and after that I cannot suspend anymore. When it happens mmcli -L gives: Found 1 modems: /org/freedesktop/ModemManager1/Modem/9 [Sierra] MBIM [1199:A001] And mmcli -m 9: Status | lock: 'none' | unlock retries: 'sim-pin (3)' | state: 'registered' |power state: 'on' |access tech: 'gprs, lte' | signal quality: '0' (cached) After a few attempts to restart ModemManager and suspend it starts working. But only for one suspend. After one suspend I need to do the whole procedure again. Similar to: https://askubuntu.com/questions/1084698/ubuntu-18-04-em7455-works-only-after-suspend https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950?comments=all https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743 On Ubuntu 16.04 suspend and ModemManager used to work flawlessly. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jan2384 F pulseaudio /dev/snd/controlC1: jan2384 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=2e1ab569-7004-4df3-b9f0-445fd74a1998 InstallationDate: Installed on 2016-10-22 (915 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20ALA0ARHH Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=88a770a0-dfd0-42f5-91bb-960353d1f1f6 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-18-generic N/A linux-backports-modules-4.18.0-18-generic N/A linux-firmware 1.173.5 Tags: bionic Uname: Linux 4.18.0-18-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-14 (254 days ago) UserGroups: adm audio cdrom dip input lp lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GIET94WW (2.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ALA0ARHH dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGIET94WW(2.44):bd09/20/2018:svnLENOVO:pn20ALA0ARHH:pvrThinkPadX240:rvnLENOVO:rn20ALA0ARHH:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X240 dmi.product.name: 20ALA0ARHH dmi.product.sku: LENOVO_MT_20AL_BU_Think_FM_ThinkPad X240 dmi.product.version: ThinkPad X240 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830029] Re: nouveau driver for nvidia is sluggish on GTX970M to the point of unusability
Yes I am aware of the stale bug problem and have been on both ends. But as the number of open bugs decreases (at least in some components), the problem should happen less: https://docs.google.com/spreadsheets/d/e/2PACX- 1vRDHPxGBHqM6XkT_S8ggtYfD0xchKSUD_z9PopNVE3G1rU05fVSnxDGcDsEstl7gu7N- tzCU6mLUp2V/pubchart?oid=254968654=interactive -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830029 Title: nouveau driver for nvidia is sluggish on GTX970M to the point of unusability Status in linux package in Ubuntu: Incomplete Bug description: I am trying to use the nouveau drivers on a recent (today) install of 18.04 on a 2.5yo laptop. Unfortunately the nvidia drivers don't work at all. What I am finding is that the sluggishness of the display is comparable to the case when nouveau drivers are disabled. The only real difference is in the amount of noise coming from the fan because of a slightly reduced CPU load due to Xorg. I don't even know where to start looking into this intelligently, but I would have expected that the drivers would have gotten to a usable state in the past 2 1/2 years since I last tried them on this machine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 22 21:05:40 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6540] NVIDIA Corporation GM204M [GeForce GTX 970M] [10de:13d8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 970M] [1558:6540] InstallationDate: Installed on 2019-05-22 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 5986:066d Acer, Inc Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook P65_P67RGRERA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic root=UUID=d6da27fa-5d91-4240-b3c9-c7de06124a36 ro nomodeset quiet nosplash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: P65_P67RGRERA dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.13:bd01/27/2016:svnNotebook:pnP65_P67RGRERA:pvrNotApplicable:rvnNotebook:rnP65_P67RGRERA:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P65_P67RGRERA dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 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/1830029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828134] Re: Wifi not working after suspend/resume cycle
** Also affects: network-manager (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/1828134 Title: Wifi not working after suspend/resume cycle Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: About 75% of the time for the past few weeks (I don't have a time where this started), my wifi is not working after resume from suspend. I'm happy to provide more debugging info if needed. I have tried an rmmod/modprobe on on the iwlwifi,iwlmvm modules just to see after the resume, and didn't re-enable the card. The symptoms are, the wlp4so interface is DOWN, I can't bring it up. gnome-network-manager widget turning the interface off/on doesn't work. I don't see anything glaring in dmesg. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-generic 5.0.0.14.15 ProcVersionSignature: Ubuntu 5.0.0-14.15-generic 5.0.6 Uname: Linux 5.0.0-14-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dpb4587 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue May 7 18:49:01 2019 InstallationDate: Installed on 2018-06-18 (323 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20HRCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-14-generic root=UUID=fa64d67d-26bf-4c42-a12f-c45b6ea5117c ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-14-generic N/A linux-backports-modules-5.0.0-14-generic N/A linux-firmware1.178 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-03-15 (53 days ago) dmi.bios.date: 02/14/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET52W(1.37) dmi.board.asset.tag: Not Available dmi.board.name: 20HRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1MET52W(1.37):bd02/14/2019:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 5th dmi.product.name: 20HRCTO1WW dmi.product.sku: LENOVO_MT_20HR_BU_Think_FM_ThinkPad X1 Carbon 5th dmi.product.version: ThinkPad X1 Carbon 5th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828134/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829679] Re: Resolution stuck at 1024x768
Please confirm the issue doesn't happen on previous kernel versions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829679 Title: Resolution stuck at 1024x768 Status in linux package in Ubuntu: Confirmed Bug description: I installed ubuntu 18.04 than upgraded to 19.04 and everything was fine(resolution 1920x1080 on a samsung TV) for a few weeks than suddenly it dropped to 1024x768. I'm running a AMD HD7670 video card with a display port to HDMI cable to the tv --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hlm1881 F pulseaudio /dev/snd/controlC1: hlm1881 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-05-19 (1 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: enp0s25 no wireless extensions. lono wireless extensions. enp3s0no wireless extensions. MachineType: Dell Inc. OptiPlex 755 Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 RfKill: Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-19 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 06/11/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A22 dmi.board.name: 0PU052 dmi.board.vendor: Dell Inc. dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA22:bd06/11/2012:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 755 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829679/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830000] Re: NVIDIA driver (390) does not allow progress to login screen
Laptops are almost always wired with only the Intel GPU connected to the LCD. If there is an Nvidia GPU then it is not connected to the screen; it only shares rendered frames with the Intel GPU via system memory. This allows the Nvidia GPU to be completely turned off without losing the screen or needing to change drivers. And the Intel driver absolutely requires modesetting to work (hence no 'nomodeset'), because that is the only mode of operation supported by the Intel driver (unless you want 1024x768 and software rendering). Yes, I think Escape is edge triggered only. It's not a modifier key like Shift is. But also yes I only use UEFI so maybe legacy BIOS modes still support Shift. -- 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/183 Title: NVIDIA driver (390) does not allow progress to login screen Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Bug description: Installing the nvidia-driver-390 package and disabling (or not) the nouveau drivers results in a system that superficially appears to busy hang before reaching the login screen, leaving only the fsck "/dev/sda1: clean,..." message on the screen. The machine is alive, and logging in remotely gives a hint at what is happening. The output of top shows that init and systemd are struggling with something: ``` top - 17:24:00 up 1 min, 1 user, load average: 2.76, 1.00, 0.36 Tasks: 188 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 17.0 us, 15.2 sy, 0.0 ni, 67.6 id, 0.0 wa, 0.0 hi, 0.1 si, 0.0 st KiB Mem : 16238012 total, 15513832 free, 242248 used, 481932 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15716900 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 225600 9312 6672 S 60.4 0.1 0:51.63 /sbin/init nosplash 797 root 20 0 71656 7180 5296 S 26.8 0.0 0:14.92 /lib/systemd/systemd-logind 1133 root 20 0 46368 3584 1976 R 13.9 0.0 0:12.01 /lib/systemd/systemd-udevd 795 root 20 0 1773200 30772 12548 S 13.2 0.2 0:11.71 /usr/lib/snapd/snapd 784 message+ 20 0 51464 6036 3988 S 12.9 0.0 0:11.15 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --s+ 308 root 19 -1 249904 120460 114260 S 10.7 0.7 0:10.60 /lib/systemd/systemd-journald 1132 root 20 0 46368 3584 1976 S 10.0 0.0 0:08.71 /lib/systemd/systemd-udevd 1134 root 20 0 46368 3260 1656 S 10.0 0.0 0:08.61 /lib/systemd/systemd-udevd 333 root 20 0 46368 4684 3084 S 5.0 0.0 0:04.25 /lib/systemd/systemd-udevd ``` Eventually, Xorg does manage to get a word in, but falls over, to try again repeatedly. ``` top - 16:52:36 up 2 min, 1 user, load average: 1.69, 1.04, 0.43 Tasks: 187 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 9.5 us, 3.7 sy, 0.0 ni, 85.6 id, 0.0 wa, 0.0 hi, 1.2 si, 0.0 st KiB Mem : 16238012 total, 15457080 free, 278152 used, 502780 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15680684 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1821 root 20 0 312908 61228 20584 R 65.2 0.4 0:01.97 /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -b+ 806 root 20 0 71656 7200 5320 S 18.5 0.0 0:24.83 /lib/systemd/systemd-logind ``` A further hint comes from syslog which is spammed with systemd trying to start nvidia-persistenced, which is then killed. This happens hundreds of times while the machine is up. This except shows one instance. ``` May 22 16:34:52 cube systemd[1]: Starting NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Verbose syslog connection opened May 22 16:34:52 cube nvidia-persistenced: Now running with user ID 123 and group ID 127 May 22 16:34:52 cube systemd[1]: Started NVIDIA Persistence Daemon. May 22 16:34:52 cube nvidia-persistenced: Started (31927) May 22 16:34:52 cube nvidia-persistenced: device :01:00.0 - registered May 22 16:34:52 cube nvidia-persistenced: Local RPC service initialized May 22 16:34:52 cube nvidia-persistenced:
[Kernel-packages] [Bug 1830029] Re: nouveau driver for nvidia is sluggish on GTX970M to the point of unusability
The reason I ask this is that launchpad has an unfortunate approach to issue management (these two that you have been communicating in are a welcome change - thanks) where bugs go stale for years or are dropped due to lack of engagement from maintainers. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830029 Title: nouveau driver for nvidia is sluggish on GTX970M to the point of unusability Status in linux package in Ubuntu: Incomplete Bug description: I am trying to use the nouveau drivers on a recent (today) install of 18.04 on a 2.5yo laptop. Unfortunately the nvidia drivers don't work at all. What I am finding is that the sluggishness of the display is comparable to the case when nouveau drivers are disabled. The only real difference is in the amount of noise coming from the fan because of a slightly reduced CPU load due to Xorg. I don't even know where to start looking into this intelligently, but I would have expected that the drivers would have gotten to a usable state in the past 2 1/2 years since I last tried them on this machine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 22 21:05:40 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6540] NVIDIA Corporation GM204M [GeForce GTX 970M] [10de:13d8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 970M] [1558:6540] InstallationDate: Installed on 2019-05-22 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 5986:066d Acer, Inc Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook P65_P67RGRERA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic root=UUID=d6da27fa-5d91-4240-b3c9-c7de06124a36 ro nomodeset quiet nosplash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: P65_P67RGRERA dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.13:bd01/27/2016:svnNotebook:pnP65_P67RGRERA:pvrNotApplicable:rvnNotebook:rnP65_P67RGRERA:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P65_P67RGRERA dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 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/1830029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830090] Re: Cannot reach 1300Mbps using DW1830 (BCM943602BAED) with linux-firmware
Does the actually network speed affected by this bug? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1830090 Title: Cannot reach 1300Mbps using DW1830 (BCM943602BAED) with linux-firmware Status in linux-firmware package in Ubuntu: New Bug description: I cannot reach 1300Mbps using DW1830 (BCM943602BAED) with linux-firmware, only 985Mbps maximum. It works fine under win10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1830090/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818797] Re: Xenial update: 4.4.172 upstream stable release
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1818797
Title:
Xenial update: 4.4.172 upstream stable release
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
4.4.172 upstream stable release
from git://git.kernel.org/
Linux 4.4.172
ipmi:ssif: Fix handling of multi-part return messages
net: speed up skb_rbtree_purge()
mm, proc: be more verbose about unstable VMA flags in /proc//smaps
mm/page-writeback.c: don't break integrity writeback on ->writepage() error
ocfs2: fix panic due to unrecovered local alloc
scsi: megaraid: fix out-of-bound array accesses
sysfs: Disable lockdep for driver bind/unbind files
ALSA: bebob: fix model-id of unit for Apogee Ensemble
dm snapshot: Fix excessive memory usage and workqueue stalls
dm kcopyd: Fix bug causing workqueue stalls
perf parse-events: Fix unchecked usage of strncpy()
perf svghelper: Fix unchecked usage of strncpy()
perf intel-pt: Fix error with config term "pt=0"
mmc: atmel-mci: do not assume idle after atmci_request_end
kconfig: fix memory leak when EOF is encountered in quotation
kconfig: fix file name and line number of warn_ignored_character()
clk: imx6q: reset exclusive gates on init
scsi: target: use consistent left-aligned ASCII INQUIRY data
net: call sk_dst_reset when set SO_DONTROUTE
media: firewire: Fix app_info parameter type in avc_ca{,_app}_info
powerpc/pseries/cpuidle: Fix preempt warning
pstore/ram: Do not treat empty buffers as valid
jffs2: Fix use of uninitialized delayed_work, lockdep breakage
arm64: perf: set suppress_bind_attrs flag to true
MIPS: SiByte: Enable swiotlb for SWARM, LittleSur and BigSur
writeback: don't decrement wb->refcnt if !wb->bdi
e1000e: allow non-monotonic SYSTIM readings
platform/x86: asus-wmi: Tell the EC the OS will handle the display off hotkey
xfs: don't fail when converting shortform attr to long form during
ATTR_REPLACE
ipv6: Take rcu_read_lock in __inet6_bind for mapped addresses
ipv6: Consider sk_bound_dev_if when binding a socket to a v4 mapped address
r8169: Add support for new Realtek Ethernet
media: vb2: be sure to unlock mutex on errors
drm/fb-helper: Ignore the value of fb_var_screeninfo.pixclock
loop: Fix double mutex_unlock(_ctl_mutex) in loop_control_ioctl()
loop: Get rid of loop_index_mutex
loop: Fold __loop_release into loop_release
block/loop: Use global lock for ioctl() operation.
tipc: fix uninit-value in tipc_nl_compat_doit
tipc: fix uninit-value in tipc_nl_compat_name_table_dump
tipc: fix uninit-value in tipc_nl_compat_link_set
tipc: fix uninit-value in tipc_nl_compat_bearer_enable
tipc: fix uninit-value in tipc_nl_compat_link_reset_stats
sctp: allocate sctp_sockaddr_entry with kzalloc
selinux: fix GPF on invalid policy
sunrpc: handle ENOMEM in rpcb_getport_async
media: vb2: vb2_mmap: move lock up
LSM: Check for NULL cred-security on free
media: vivid: set min width/height to a value > 0
media: vivid: fix error handling of kthread_run
omap2fb: Fix stack memory disclosure
Disable MSI also when pcie-octeon.pcie_disable on
mfd: tps6586x: Handle interrupts on suspend
mips: fix n32 compat_ipc_parse_version
scsi: sd: Fix cache_type_store()
Yama: Check for pid death before checking ancestry
btrfs: wait on ordered extents on abort cleanup
crypto: authenc - fix parsing key with misaligned rta_len
crypto: authencesn - Avoid twice completion call in decrypt path
ip: on queued skb use skb_header_pointer instead of pskb_may_pull
packet: Do not leak dev refcounts on error exit
net: bridge: fix a bug on using a neighbour cache entry without checking its
state
ipv6: fix kernel-infoleak in ipv6_local_error()
arm64: Don't trap host pointer auth use to EL2
arm64/kvm: consistently handle host HCR_EL2 flags
proc: Remove empty line in /proc/self/status
media: em28xx: Fix misplaced reset of dev->v4l::field_count
f2fs: fix validation of the block count in sanity_check_raw_super
f2fs: fix missing up_read
f2fs: fix invalid memory access
f2fs: fix to do sanity check with cp_pack_start_sum
f2fs: fix to do sanity check with block address in main area v2
f2fs: fix to do sanity check with block address in main area
f2fs: fix to do
[Kernel-packages] [Bug 1830000] Re: NVIDIA driver (390) does not allow progress to login screen
re:nomodeset: That's odd unless the drivers on the live usb media are old; nomodeset is definitely needed to not lock up from the live usb on this machine. re:grubmenu: I'm not using UEFI, so AFAIU, shift should be the key (though I tried both). Is it edge triggered? If not, I've had the key held down from the moment the boot process is started at the boot medium option screen of my BIOS. -- 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/183 Title: NVIDIA driver (390) does not allow progress to login screen Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Bug description: Installing the nvidia-driver-390 package and disabling (or not) the nouveau drivers results in a system that superficially appears to busy hang before reaching the login screen, leaving only the fsck "/dev/sda1: clean,..." message on the screen. The machine is alive, and logging in remotely gives a hint at what is happening. The output of top shows that init and systemd are struggling with something: ``` top - 17:24:00 up 1 min, 1 user, load average: 2.76, 1.00, 0.36 Tasks: 188 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 17.0 us, 15.2 sy, 0.0 ni, 67.6 id, 0.0 wa, 0.0 hi, 0.1 si, 0.0 st KiB Mem : 16238012 total, 15513832 free, 242248 used, 481932 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15716900 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 225600 9312 6672 S 60.4 0.1 0:51.63 /sbin/init nosplash 797 root 20 0 71656 7180 5296 S 26.8 0.0 0:14.92 /lib/systemd/systemd-logind 1133 root 20 0 46368 3584 1976 R 13.9 0.0 0:12.01 /lib/systemd/systemd-udevd 795 root 20 0 1773200 30772 12548 S 13.2 0.2 0:11.71 /usr/lib/snapd/snapd 784 message+ 20 0 51464 6036 3988 S 12.9 0.0 0:11.15 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --s+ 308 root 19 -1 249904 120460 114260 S 10.7 0.7 0:10.60 /lib/systemd/systemd-journald 1132 root 20 0 46368 3584 1976 S 10.0 0.0 0:08.71 /lib/systemd/systemd-udevd 1134 root 20 0 46368 3260 1656 S 10.0 0.0 0:08.61 /lib/systemd/systemd-udevd 333 root 20 0 46368 4684 3084 S 5.0 0.0 0:04.25 /lib/systemd/systemd-udevd ``` Eventually, Xorg does manage to get a word in, but falls over, to try again repeatedly. ``` top - 16:52:36 up 2 min, 1 user, load average: 1.69, 1.04, 0.43 Tasks: 187 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 9.5 us, 3.7 sy, 0.0 ni, 85.6 id, 0.0 wa, 0.0 hi, 1.2 si, 0.0 st KiB Mem : 16238012 total, 15457080 free, 278152 used, 502780 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15680684 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1821 root 20 0 312908 61228 20584 R 65.2 0.4 0:01.97 /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -b+ 806 root 20 0 71656 7200 5320 S 18.5 0.0 0:24.83 /lib/systemd/systemd-logind ``` A further hint comes from syslog which is spammed with systemd trying to start nvidia-persistenced, which is then killed. This happens hundreds of times while the machine is up. This except shows one instance. ``` May 22 16:34:52 cube systemd[1]: Starting NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Verbose syslog connection opened May 22 16:34:52 cube nvidia-persistenced: Now running with user ID 123 and group ID 127 May 22 16:34:52 cube systemd[1]: Started NVIDIA Persistence Daemon. May 22 16:34:52 cube nvidia-persistenced: Started (31927) May 22 16:34:52 cube nvidia-persistenced: device :01:00.0 - registered May 22 16:34:52 cube nvidia-persistenced: Local RPC service initialized May 22 16:34:52 cube nvidia-persistenced: Received signal 15 May 22 16:34:52 cube systemd[1]: Stopping NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Socket closed. May 22 16:34:52 cube nvidia-persistenced: PID file unlocked. May 22 16:34:52 cube nvidia-persistenced: PID file closed. May 22 16:34:52 cube
[Kernel-packages] [Bug 1827822] Re: kernel null pointer dereference
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827822 Title: kernel null pointer dereference Status in linux package in Ubuntu: Confirmed Bug description: System started freezing up a couple days ago. After the latest one, I looked at the syslog file and found what appears to be a kernel bug report. May 5 18:06:03 corbin-goul kernel: [ 4650.769677] BUG: unable to handle kernel NULL pointer dereference at 0008 May 5 18:06:03 corbin-goul kernel: [ 4650.769694] IP: rm_hole+0x19/0x70 [drm] May 5 18:06:03 corbin-goul kernel: [ 4650.769696] PGD 0 P4D 0 May 5 18:06:03 corbin-goul kernel: [ 4650.769698] Oops: 0002 [#1] SMP PTI May 5 18:06:03 corbin-goul kernel: [ 4650.769700] Modules linked in: nls_iso8859_1 snd_hda_codec_realtek snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_codec_generic snd_hda_intel snd _hda_codec kvm snd_hda_core snd_hwdep snd_pcm irqbypass mei_me intel_cstate mei intel_rapl_perf snd_seq_midi input_leds snd_seq_midi_event serio_raw snd_rawmidi snd_seq snd_seq_device snd_timer lpc_ich snd shpchp soundcore mac_hid s ch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq a sync_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear raid1 hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 May 5 18:06:03 corbin-goul kernel: [ 4650.769733] aesni_intel i2c_algo_bit aes_x86_64 crypto_simd drm_kms_helper glue_helper cryptd syscopyarea sysfillrect sysimgblt r8169 fb_sys_fops ahci mii drm libahci sata_inic162x video May 5 18:06:03 corbin-goul kernel: [ 4650.769743] CPU: 0 PID: 8713 Comm: kworker/0:0 Not tainted 4.15.0-48-generic #51-Ubuntu May 5 18:06:03 corbin-goul kernel: [ 4650.769744] Hardware name: Gigabyte Technology Co., Ltd. H87M-D3H/H87M-D3H, BIOS F3 04/24/2013 May 5 18:06:03 corbin-goul kernel: [ 4650.769770] Workqueue: events __i915_gem_free_work [i915] May 5 18:06:03 corbin-goul kernel: [ 4650.769778] RIP: 0010:rm_hole+0x19/0x70 [drm] May 5 18:06:03 corbin-goul kernel: [ 4650.769779] RSP: 0018:95fb81f2bd20 EFLAGS: 00010202 May 5 18:06:03 corbin-goul kernel: [ 4650.769780] RAX: RBX: 89d51f1382c0 RCX: May 5 18:06:03 corbin-goul kernel: [ 4650.769781] RDX: RSI: 89d765cf8b40 RDI: 89d51f138318 May 5 18:06:03 corbin-goul kernel: [ 4650.769782] RBP: 95fb81f2bd28 R08: 89d5e7b71bc0 R09: May 5 18:06:03 corbin-goul kernel: [ 4650.769783] R10: 95fb81f2bde0 R11: 0001 R12: 89d765cf8b00 May 5 18:06:03 corbin-goul kernel: [ 4650.769784] R13: R14: 89d51f1382e0 R15: 89d75f6c37c8 May 5 18:06:03 corbin-goul kernel: [ 4650.769786] FS: () GS:89d77e20() knlGS: May 5 18:06:03 corbin-goul kernel: [ 4650.769787] CS: 0010 DS: ES: CR0: 80050033 May 5 18:06:03 corbin-goul kernel: [ 4650.769788] CR2: 0008 CR3: 0002eac0a002 CR4: 001606f0 May 5 18:06:03 corbin-goul kernel: [ 4650.769789] Call Trace: May 5 18:06:03 corbin-goul kernel: [ 4650.769797] drm_mm_remove_node+0x29d/0x360 [drm] May 5 18:06:03 corbin-goul kernel: [ 4650.769801] ? __internal_add_timer+0x1f/0x60 May 5 18:06:03 corbin-goul kernel: [ 4650.769816] i915_vma_remove+0x3a/0x100 [i915] May 5 18:06:03 corbin-goul kernel: [ 4650.769830] i915_vma_unbind+0x1cd/0x370 [i915] May 5 18:06:03 corbin-goul kernel: [ 4650.769843] i915_vma_close+0x7d/0xa0 [i915] May 5 18:06:03 corbin-goul kernel: [ 4650.769856] __i915_gem_free_objects+0xa3/0x2c0 [i915] May 5 18:06:03 corbin-goul kernel: [ 4650.769867] __i915_gem_free_work+0x60/0x90 [i915] May 5 18:06:03 corbin-goul kernel: [ 4650.769870] process_one_work+0x1de/0x410 May 5 18:06:03 corbin-goul kernel: [ 4650.769872] worker_thread+0x32/0x410 May 5 18:06:03 corbin-goul kernel: [ 4650.769874] kthread+0x121/0x140 May 5 18:06:03 corbin-goul kernel: [ 4650.769876] ? process_one_work+0x410/0x410 May 5 18:06:03 corbin-goul kernel: [ 4650.769878] ? kthread_create_worker_on_cpu+0x70/0x70 May 5 18:06:03 corbin-goul kernel: [ 4650.769881] ret_from_fork+0x35/0x40 May 5 18:06:03 corbin-goul kernel: [ 4650.769882] Code: 00 00 00 45 31 d2 eb bb 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 48 8b 57 30 48 8b 47 38 48 89 fb 48 8d 7f 58 <48> 89 42 08 48 89 10 48 b8 00 01 00 00 00 00 ad de 48 89 47 d8 May 5 18:06:03 corbin-goul kernel: [ 4650.769909] RIP: rm_hole+0x19/0x70 [drm]
[Kernel-packages] [Bug 1825780] Re: Kprobe event string type argument failed in ftrace from ubuntu_kernel_selftests on B/C i386
Passed with Cosmic i386 with proposed kernel. ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic ** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825780 Title: Kprobe event string type argument failed in ftrace from ubuntu_kernel_selftests on B/C i386 Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: == Justification == When running the ftrace in ubunut_kernel_selftests, the "Kprobe event string type argument" test will fail on Bionic / Cosmic i386: [22] Kprobe event string type argument [FAIL] This is because the test was trying to probe a notrace function. # grep create_trace_kprobe /sys/kernel/debug/tracing/available_filter_functions == Fix == 6fc7c411 (selftests/ftrace: Fix kprobe string testcase to not probe notrace function) This will change the event to trace in the test, from create_trace_kprobe to tracefs_create_dir Patch can be cherry-picked for Cosmic. For Bionic and Xenial, it can be cherry-picked after the commit 9855c462 for bug 1812809. Although we don't run this ftrace test in Xenial, it will still be a plus to fix this. It's already been applied in D. This patch belongs to a patchset [1], in which further limits kprobe- events probing on notrace function. To address this issue for the testing tool this one will be suffice. [1] https://lkml.org/lkml/2018/7/30/257 == Test == Patch tested with Bionic / Cosmic i386. Test passed as expected: [22] Kprobe event string type argument [PASS] == Regression potential == None. This patch is just for the kernel testing tool. == Original bug report == Failure spotted on Bionic / Cosmic i386 (node fozzie) [22] Kprobe event string type argument [FAIL] selftests: ftrace: ftracetest === Ftrace unit tests === [1] Basic trace file check [PASS] [2] Basic test for tracers [PASS] [3] Basic trace clock test [PASS] [4] Basic event tracing check[PASS] [5] Snapshot and tracing setting [PASS] [6] event tracing - enable/disable with event level files[PASS] [7] event tracing - restricts events based on pid[PASS] [8] event tracing - enable/disable with subsystem level files[PASS] [9] event tracing - enable/disable with top level files [PASS] [10] ftrace - function graph filters with stack tracer [PASS] [11] ftrace - function graph filters [PASS] [12] ftrace - function pid filters [PASS] [13] ftrace - test for function event triggers [PASS] [14] ftrace - function profiler with function tracing[PASS] [15] ftrace - test reading of set_ftrace_filter [PASS] [16] ftrace - test for function traceon/off triggers [PASS] [17] Test creation and deletion of trace instances while setting an event [PASS] [18] Test creation and deletion of trace instances [PASS] [19] Kprobe dynamic event - adding and removing [PASS] [20] Kprobe dynamic event - busy event check [PASS] [21] Kprobe dynamic event with arguments [PASS] [22] Kprobe event string type argument [FAIL] [23] Kprobe event argument syntax[PASS] [24] Kprobes event arguments with types [PASS] [25] Kprobe event auto/manual naming [PASS] [26] Kprobe dynamic event with function tracer [PASS] [27] Kretprobe dynamic event with arguments [PASS] [28] Kretprobe dynamic event with maxactive [PASS] [29] Register/unregister many kprobe events [PASS] [30] event trigger - test extended error support [PASS] [31] event trigger - test field variable support [PASS] [32] event trigger - test multiple actions on hist trigger [PASS] [33] event trigger - test inter-event histogram trigger onmatch action [PASS] [34] event trigger - test inter-event histogram trigger onmatch-onmax action [PASS] [35] event trigger - test inter-event histogram trigger onmax action [PASS] [36] event trigger - test synthetic_events syntax parser [PASS] [37] event trigger - test event enable/disable trigger [PASS] [38] event trigger - test trigger filter [PASS] [39] event trigger - test histogram modifiers[PASS] [40] event trigger - test multiple histogram triggers[PASS] [41] event trigger - test snapshot-trigger [PASS] [42] event trigger - test stacktrace-trigger [PASS] [43] trace_marker trigger - test snapshot trigger[PASS] [44] trace_marker trigger - test histogram with synthetic event against
[Kernel-packages] [Bug 1830029] Re: nouveau driver for nvidia is sluggish on GTX970M to the point of unusability
I think it's appropriate to stay Incomplete because this is essentially just a kernel bug, in the nouveau driver. Option (b) above isn't directly relevant, but might be a workaround, even permanently. Any proper solution to this bug requires testing of option (a) in comment #4. So still 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/1830029 Title: nouveau driver for nvidia is sluggish on GTX970M to the point of unusability Status in linux package in Ubuntu: Incomplete Bug description: I am trying to use the nouveau drivers on a recent (today) install of 18.04 on a 2.5yo laptop. Unfortunately the nvidia drivers don't work at all. What I am finding is that the sluggishness of the display is comparable to the case when nouveau drivers are disabled. The only real difference is in the amount of noise coming from the fan because of a slightly reduced CPU load due to Xorg. I don't even know where to start looking into this intelligently, but I would have expected that the drivers would have gotten to a usable state in the past 2 1/2 years since I last tried them on this machine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 22 21:05:40 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6540] NVIDIA Corporation GM204M [GeForce GTX 970M] [10de:13d8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 970M] [1558:6540] InstallationDate: Installed on 2019-05-22 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 5986:066d Acer, Inc Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook P65_P67RGRERA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic root=UUID=d6da27fa-5d91-4240-b3c9-c7de06124a36 ro nomodeset quiet nosplash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: P65_P67RGRERA dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.13:bd01/27/2016:svnNotebook:pnP65_P67RGRERA:pvrNotApplicable:rvnNotebook:rnP65_P67RGRERA:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P65_P67RGRERA dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 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/1830029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830029] Re: nouveau driver for nvidia is sluggish on GTX970M to the point of unusability
Please undo the incomplete. The action that was asked for was performed in the comment #2. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830029 Title: nouveau driver for nvidia is sluggish on GTX970M to the point of unusability Status in linux package in Ubuntu: Incomplete Bug description: I am trying to use the nouveau drivers on a recent (today) install of 18.04 on a 2.5yo laptop. Unfortunately the nvidia drivers don't work at all. What I am finding is that the sluggishness of the display is comparable to the case when nouveau drivers are disabled. The only real difference is in the amount of noise coming from the fan because of a slightly reduced CPU load due to Xorg. I don't even know where to start looking into this intelligently, but I would have expected that the drivers would have gotten to a usable state in the past 2 1/2 years since I last tried them on this machine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 22 21:05:40 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6540] NVIDIA Corporation GM204M [GeForce GTX 970M] [10de:13d8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 970M] [1558:6540] InstallationDate: Installed on 2019-05-22 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 5986:066d Acer, Inc Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook P65_P67RGRERA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic root=UUID=d6da27fa-5d91-4240-b3c9-c7de06124a36 ro nomodeset quiet nosplash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: P65_P67RGRERA dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.13:bd01/27/2016:svnNotebook:pnP65_P67RGRERA:pvrNotApplicable:rvnNotebook:rnP65_P67RGRERA:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P65_P67RGRERA dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 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/1830029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830000] Re: NVIDIA driver (390) does not allow progress to login screen
Your Intel GPU, which usually is the only GPU wired directly to the laptop screen, requires modesetting to be enabled. I recall old versions of the Nvidia driver did not like that, but current versions do. I think "current" includes Ubuntu 18.04. As for the grub menu, yes it might have become harder to trigger in recent years but I am pretty sure Escape still works. You just have to be very fast... -- 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/183 Title: NVIDIA driver (390) does not allow progress to login screen Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Bug description: Installing the nvidia-driver-390 package and disabling (or not) the nouveau drivers results in a system that superficially appears to busy hang before reaching the login screen, leaving only the fsck "/dev/sda1: clean,..." message on the screen. The machine is alive, and logging in remotely gives a hint at what is happening. The output of top shows that init and systemd are struggling with something: ``` top - 17:24:00 up 1 min, 1 user, load average: 2.76, 1.00, 0.36 Tasks: 188 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 17.0 us, 15.2 sy, 0.0 ni, 67.6 id, 0.0 wa, 0.0 hi, 0.1 si, 0.0 st KiB Mem : 16238012 total, 15513832 free, 242248 used, 481932 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15716900 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 225600 9312 6672 S 60.4 0.1 0:51.63 /sbin/init nosplash 797 root 20 0 71656 7180 5296 S 26.8 0.0 0:14.92 /lib/systemd/systemd-logind 1133 root 20 0 46368 3584 1976 R 13.9 0.0 0:12.01 /lib/systemd/systemd-udevd 795 root 20 0 1773200 30772 12548 S 13.2 0.2 0:11.71 /usr/lib/snapd/snapd 784 message+ 20 0 51464 6036 3988 S 12.9 0.0 0:11.15 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --s+ 308 root 19 -1 249904 120460 114260 S 10.7 0.7 0:10.60 /lib/systemd/systemd-journald 1132 root 20 0 46368 3584 1976 S 10.0 0.0 0:08.71 /lib/systemd/systemd-udevd 1134 root 20 0 46368 3260 1656 S 10.0 0.0 0:08.61 /lib/systemd/systemd-udevd 333 root 20 0 46368 4684 3084 S 5.0 0.0 0:04.25 /lib/systemd/systemd-udevd ``` Eventually, Xorg does manage to get a word in, but falls over, to try again repeatedly. ``` top - 16:52:36 up 2 min, 1 user, load average: 1.69, 1.04, 0.43 Tasks: 187 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 9.5 us, 3.7 sy, 0.0 ni, 85.6 id, 0.0 wa, 0.0 hi, 1.2 si, 0.0 st KiB Mem : 16238012 total, 15457080 free, 278152 used, 502780 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15680684 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1821 root 20 0 312908 61228 20584 R 65.2 0.4 0:01.97 /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -b+ 806 root 20 0 71656 7200 5320 S 18.5 0.0 0:24.83 /lib/systemd/systemd-logind ``` A further hint comes from syslog which is spammed with systemd trying to start nvidia-persistenced, which is then killed. This happens hundreds of times while the machine is up. This except shows one instance. ``` May 22 16:34:52 cube systemd[1]: Starting NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Verbose syslog connection opened May 22 16:34:52 cube nvidia-persistenced: Now running with user ID 123 and group ID 127 May 22 16:34:52 cube systemd[1]: Started NVIDIA Persistence Daemon. May 22 16:34:52 cube nvidia-persistenced: Started (31927) May 22 16:34:52 cube nvidia-persistenced: device :01:00.0 - registered May 22 16:34:52 cube nvidia-persistenced: Local RPC service initialized May 22 16:34:52 cube nvidia-persistenced: Received signal 15 May 22 16:34:52 cube systemd[1]: Stopping NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Socket closed. May 22 16:34:52 cube nvidia-persistenced: PID file unlocked. May 22 16:34:52 cube nvidia-persistenced: PID file closed. May 22 16:34:52
[Kernel-packages] [Bug 1830000] Re: NVIDIA driver (390) does not allow progress to login screen
I will give that a go. The nomodeset option was set during istall, presumably because the live usb install media doesn't boot without it. I vaguely recall altering that option at the grub menu, but it was a long day yesterday, so I am not sure (as an aside, why does the grub menu not come up with shift or esc any more - I needed to alter the grub files to make it possible to see the menu at all, which is pretty unfriendly). -- 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/183 Title: NVIDIA driver (390) does not allow progress to login screen Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Bug description: Installing the nvidia-driver-390 package and disabling (or not) the nouveau drivers results in a system that superficially appears to busy hang before reaching the login screen, leaving only the fsck "/dev/sda1: clean,..." message on the screen. The machine is alive, and logging in remotely gives a hint at what is happening. The output of top shows that init and systemd are struggling with something: ``` top - 17:24:00 up 1 min, 1 user, load average: 2.76, 1.00, 0.36 Tasks: 188 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 17.0 us, 15.2 sy, 0.0 ni, 67.6 id, 0.0 wa, 0.0 hi, 0.1 si, 0.0 st KiB Mem : 16238012 total, 15513832 free, 242248 used, 481932 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15716900 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 225600 9312 6672 S 60.4 0.1 0:51.63 /sbin/init nosplash 797 root 20 0 71656 7180 5296 S 26.8 0.0 0:14.92 /lib/systemd/systemd-logind 1133 root 20 0 46368 3584 1976 R 13.9 0.0 0:12.01 /lib/systemd/systemd-udevd 795 root 20 0 1773200 30772 12548 S 13.2 0.2 0:11.71 /usr/lib/snapd/snapd 784 message+ 20 0 51464 6036 3988 S 12.9 0.0 0:11.15 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --s+ 308 root 19 -1 249904 120460 114260 S 10.7 0.7 0:10.60 /lib/systemd/systemd-journald 1132 root 20 0 46368 3584 1976 S 10.0 0.0 0:08.71 /lib/systemd/systemd-udevd 1134 root 20 0 46368 3260 1656 S 10.0 0.0 0:08.61 /lib/systemd/systemd-udevd 333 root 20 0 46368 4684 3084 S 5.0 0.0 0:04.25 /lib/systemd/systemd-udevd ``` Eventually, Xorg does manage to get a word in, but falls over, to try again repeatedly. ``` top - 16:52:36 up 2 min, 1 user, load average: 1.69, 1.04, 0.43 Tasks: 187 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 9.5 us, 3.7 sy, 0.0 ni, 85.6 id, 0.0 wa, 0.0 hi, 1.2 si, 0.0 st KiB Mem : 16238012 total, 15457080 free, 278152 used, 502780 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15680684 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1821 root 20 0 312908 61228 20584 R 65.2 0.4 0:01.97 /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -b+ 806 root 20 0 71656 7200 5320 S 18.5 0.0 0:24.83 /lib/systemd/systemd-logind ``` A further hint comes from syslog which is spammed with systemd trying to start nvidia-persistenced, which is then killed. This happens hundreds of times while the machine is up. This except shows one instance. ``` May 22 16:34:52 cube systemd[1]: Starting NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Verbose syslog connection opened May 22 16:34:52 cube nvidia-persistenced: Now running with user ID 123 and group ID 127 May 22 16:34:52 cube systemd[1]: Started NVIDIA Persistence Daemon. May 22 16:34:52 cube nvidia-persistenced: Started (31927) May 22 16:34:52 cube nvidia-persistenced: device :01:00.0 - registered May 22 16:34:52 cube nvidia-persistenced: Local RPC service initialized May 22 16:34:52 cube nvidia-persistenced: Received signal 15 May 22 16:34:52 cube systemd[1]: Stopping NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Socket closed. May 22 16:34:52 cube nvidia-persistenced: PID file unlocked. May 22 16:34:52 cube nvidia-persistenced: PID file
[Kernel-packages] [Bug 1779756] Re: Intel XL710 - i40e driver does not work with kernel 4.15 (Ubuntu 18.04)
** Tags added: sts -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1779756 Title: Intel XL710 - i40e driver does not work with kernel 4.15 (Ubuntu 18.04) Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Bug description: [Impact] The i40e driver can get stalled on tx timeouts. This can happen when DCB is enabled on the connected switch. This can also trigger a second situation when a tx timeout occurs before the recovery of a previous timeout has completed due to CPU load, which is not handled correctly. This leads to networking delays, drops and application timeouts and hangs. Note that the first tx timeout cause is just one of the ways to end up in the second situation. This issue was seen on a heavily loaded Kafka broker node running the 4.15.0-38-generic kernel on Xenial. Symptoms include messages in the kernel log of the form: --- [4733544.982116] i40e :18:00.1 eno2: tx_timeout: VSI_seid: 390, Q 6, NTC: 0x1a0, HWB: 0x66, NTU: 0x66, TAIL: 0x66, INT: 0x0 [4733544.982119] i40e :18:00.1 eno2: tx_timeout recovery level 1, hung_queue 6 With the test kernel provided in this LP bug which had these two commits compiled in, the problem has not been seen again, and has been running successfully for several months: "i40e: Fix for Tx timeouts when interface is brought up if DCB is enabled" Commit: fa38e30ac73fbb01d7e5d0fd1b12d412fa3ac3ee "i40e: prevent overlapping tx_timeout recover" Commit: d5585b7b6846a6d0f9517afe57be3843150719da * The first commit is already in Disco, Cosmic * The second commit is already in Disco * Bionic needs both patches and Cosmic needs the second [Test Case] * We are considering the case of both issues above occurring. * Seen by reporter on a Kafka broker node with heavy traffic. * Not easy to reproduce as it requires something like the following example environment and heavy load: Kernel: 4.15.0-38-generic Network driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 NIC: Intel 40Gb XL710 DCB enabled [Regression Potential] Low, as the first only impacts i40e DCB environment, and has been running for several months in production-load testing successfully. --- Original Description Today Ubuntu 16.04 LTS Enablement Stacks has moved from the Kernel 4.13 to the Kernel 4.15.0-24-generic. On a "Dell PowerEdge R330" server with a network adapter "Intel Ethernet Converged Network Adapter X710-DA2" (driver i40e) the network card no longer works and permanently displays these three lines : [ 98.012098] i40e :01:00.0 enp1s0f0: tx_timeout: VSI_seid: 388, Q 8, NTC: 0x0, HWB: 0x0, NTU: 0x1, TAIL: 0x1, INT: 0x1 [ 98.012119] i40e :01:00.0 enp1s0f0: tx_timeout recovery level 11, hung_queue 8 [ 98.012125] i40e :01:00.0 enp1s0f0: tx_timeout recovery unsuccessful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779756/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814095] Re: bnxt_en_po: TX timed out triggering Netdev Watchdog Timer
** Tags added: sts -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814095 Title: bnxt_en_po: TX timed out triggering Netdev Watchdog Timer Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Released Bug description: [Impact] The bnxt_en_bpo driver experienced tx timeouts causing the system to experience network stalls and fail to send data and heartbeat packets. The following 25Gb Broadcom NIC error was seen on Xenial running the 4.4.0-141-generic kernel on an amd64 host seeing moderate-heavy network traffic (just once): * The bnxt_en_po driver froze on a "TX timed out" error and triggered the Netdev Watchdog timer under load. * From kernel log: "NETDEV WATCHDOG: eno2d1 (bnxt_en_bpo): transmit queue 0 timed out" See attached kern.log excerpt file for full excerpt of error log. * Release = Xenial Kernel = 4.4.0-141-generic #167 eno2d1 = Product Name: Broadcom Adv. Dual 25Gb Ethernet * This caused the driver to reset in order to recover: "bnxt_en_bpo :19:00.1 eno2d1: TX timeout detected, starting reset task!" driver: bnxt_en_bpo version: 1.8.1 source: ubuntu/bnxt/bnxt.c: bnxt_tx_timeout() * The loss of connectivity and softirq stall caused other failures on the system. * The bnxt_en_po driver is the imported Broadcom driver pulled in to support newer Broadcom HW (specific boards) while the bnx_en module continues to support the older HW. The current Linux upstream driver does not compile easily with the 4.4 kernel (too many changes). * This upstream and bnxt_en driver fix is a likely solution: "bnxt_en: Fix TX timeout during netpoll" commit: 73f21c653f930f438d53eed29b5e4c65c8a0f906 This fix has not been applied to the bnxt_en_po driver version, but review of the code indicates that it is susceptible to the bug, and the fix would be reasonable. [Test Case] * Unfortunately, this is not easy to reproduce. Also, it is only seen on 4.4 kernels with newer Broadcom NICs supported by the bnxt_en_bpo driver. [Regression Potential] * The patch is restricted to the bpo driver, with very constrained scope - just the newest Broadcom NICs being used by the Xenial 4.4 kernel (as opposed to the hwe 4.15 etc. kernels, which would have the in-tree fixed driver). * The patch is very small and backport is fairly minimal and simple. * The fix has been running on the in-tree driver in upstream mainline as well as the Ubuntu Linux in-tree driver, although the Broadcom driver has a lot of lower level code that is different, this piece is still the same. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814095/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820948] Re: i40e xps management broken when > 64 queues/cpus
** Tags added: sts ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic verification-done-cosmic ** Tags removed: verification-done-cosmic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820948 Title: i40e xps management broken when > 64 queues/cpus Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: [Impact] Transmit packet steering (xps) settings don't work when the number of queues (cpus) is higher than 64. This is currently still an issue on the 4.15 kernel (Xenial -hwe and Bionic kernels). It was fixed in Intel's i40e driver version 2.7.11 and in 4.16-rc1 mainline Linux (i.e. Cosmic, Disco have fix). Fix - The following commit fixes this issue (as identified by Lihong Yang in discussion with Intel i40e team): "i40e: Fix the number of queues available to be mapped for use" Commit: bc6d33c8d93f520e97a8c6330b8910053d4f It requires the following commit as well: i40e: Do not allow use more TC queue pairs than MSI-X vectors exist Commit: 1563f2d2e01242f05dd523ffd56fe104bc1afd58 [Test Case] 1. Kernel version: Bionic/Xenial -hwe: any 4.15 kernel i40e driver version: 2.1.14-k Any system with > 64 CPUs 2. For any queue 0 - 63, you can read/set tx xps: echo > /sys/class/net/eth2/queues/tx-63/xps_cpus echo $? 0 cat /sys/class/net/eth2/queues/tx-63/xps_cpus 00,, But for any queue number > 63, we see this error: echo > /sys/class/net/eth2/queues/tx-64/xps_cpus echo: write error: Invalid argument cat /sys/class/net/eth2/queues/tx-64/xps_cpus cat: /sys/class/net/eth2/queues/tx-64/xps_cpus: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1794232] Re: Geneve tunnels don't work when ipv6 is disabled
** Tags added: sts -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1794232 Title: Geneve tunnels don't work when ipv6 is disabled Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Released Bug description: SRU Justification Impact: Cannot create geneve tunnels if ipv6 is disabled dynamically. Fix: Fixed by upstream commit in v5.0: Commit: cf1c9ccba7308e48a68fa77f476287d9d614e4c7 "geneve: correctly handle ipv6.disable module parameter" Hence available in Disco and later; required in X,B,C. Testcase: 1. Boot with "ipv6.disable=1" 2. Then try and create a geneve tunnel using: # ovs-vsctl add-br br1 # ovs-vsctl add-port br1 geneve1 -- set interface geneve1 type=geneve options:remote_ip=192.168.x.z // ip of the other host Regression Potential: Low, only geneve tunnels when ipv6 dynamically disabled, current status is it doesn't work at all. Other Info: * Mainline commit msg includes reference to a fix for non-metadata tunnels (infrastructure is not yet in our tree prior to Disco), hence not being included at this time under this case. At this time, all geneve tunnels created as above are metadata-enabled. --- [Impact] When attempting to create a geneve tunnel on Ubuntu 16.04 Xenial, in an OS environment with open vswitch, where ipv6 has been disabled, the create fails with the error : “ovs-vsctl: Error detected while setting up 'geneve0': could not add network device geneve0 to ofproto (Address family not supported by protocol)." [Fix] There is an upstream commit for this in v5.0 mainline (and in Disco and later Ubuntu kernels). "geneve: correctly handle ipv6.disable module parameter" Commit: cf1c9ccba7308e48a68fa77f476287d9d614e4c7 This fix is needed on all our series prior to Disco and the v5.0 kernel: X, C, B. It is identical to the fix we implemented and tested internally with, but had not pushed upstream yet. [Test Case] (Best to do this on a kvm guest VM so as not to interfere with your system's networking) 1. On any Ubuntu Xenial kernel, disable ipv6. This example is shown with the 4.15.0-23-generic kernel (which differs slightly from 4.4.x in symptoms): - Edit /etc/default/grub to add the line: GRUB_CMDLINE_LINUX="ipv6.disable=1" - # update-grub - Reboot 2. Install OVS # apt install openvswitch-switch 3. Create a Geneve tunnel # ovs-vsctl add-br br1 # ovs-vsctl add-port br1 geneve1 -- set interface geneve1 type=geneve options:remote_ip=192.168.x.z (where remote_ip is the IP of the other host) You will see the following error message: "ovs-vsctl: Error detected while setting up 'geneve1'. See ovs-vswitchd log for details." From /var/log/openvswitch/ovs-vswitchd.log you will see: "2018-07-02T16:48:13.295Z|00026|dpif|WARN|system@ovs-system: failed to add geneve1 as port: Address family not supported by protocol" You will notice from the "ifconfig" output that the device genev_sys_6081 is not created. If you do not disable IPv6 (remove ipv6.disable=1 from /etc/default/grub + update-grub + reboot), the same 'ovs-vsctl add-port' command completes successfully. You can see that it is working properly by adding an IP to the br1 and pinging each host. On kernel 4.4 (4.4.0-128-generic), the error message doesn't happen using the 'ovs-vsctl add-port' command, no warning is shown in ovs-vswitchd.log, but the device genev_sys_6081 is also not created and ping test won't work. With the fixed test kernel, the interfaces and tunnel is created successfully. [Regression Potential] * Low -- affects the geneve driver only, and when ipv6 is disabled, and since it doesn't work in that case at all, this fix gets the tunnel up and running for the common case. [Other Info] * Analysis Geneve tunnels should work with either IPv4 or IPv6 environments as a design and support principle. Currently, however, what's in the implementation requires support for ipv6 for metadata-based tunnels which geneve is: rather than: a) ipv4 + metadata // whether ipv6 compiled or dynamically disabled b) ipv4 + metadata + ipv6 What enforces this in the current 4.4.0-x code when opening a Geneve tunnel is the following in geneve_open() : bool ipv6 = geneve->remote.sa.sa_family == AF_INET6; bool metadata = geneve->collect_md; ... #if IS_ENABLED(CONFIG_IPV6) geneve->sock6 = NULL; if (ipv6 || metadata) ret = geneve_sock_add(geneve, true); #endif if (!ret && (!ipv6 || metadata))
[Kernel-packages] [Bug 1829912] Re: [Lenovo ideapad 330-15IKB] Sound very low, and quality of audio very bad.
Please test this dkms under 5.0 kernel, if the sound changes better? To install this deb: sudo dpkg -i oem-audio-xxx.deb reboot check your sound To remove this deb: sudo dpkg -P oem-audio-hda-daily-dkms reboot ** Attachment added: "oem-audio-hda-daily-dkms_0.1_all.deb" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829912/+attachment/5265837/+files/oem-audio-hda-daily-dkms_0.1_all.deb -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829912 Title: [Lenovo ideapad 330-15IKB] Sound very low, and quality of audio very bad. Status in linux package in Ubuntu: Incomplete Bug description: I am on a Lenovo Ideapad 330. I've switched to Ubuntu from Windows. The audio quality in Ubuntu is horrible to say the least, It is very low, and in case I use VLC or enable overamplification, the quality of sound output becomes worse. I have ensured that the volume on alsamixer is 100. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: phaneesh 1605 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue May 21 23:41:49 2019 InstallationDate: Installed on 2019-05-17 (4 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8TCN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15IKB dmi.modalias: dmi:bvnLENOVO:bvr8TCN44WW:bd06/13/2018:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB: dmi.product.family: ideapad 330-15IKB dmi.product.name: 81DE dmi.product.sku: LENOVO_MT_81DE_BU_idea_FM_ideapad 330-15IKB dmi.product.version: Lenovo ideapad 330-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829912/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830000] Re: NVIDIA driver (390) does not allow progress to login screen
** Package changed: gdm3 (Ubuntu) => nvidia-graphics-drivers-390 (Ubuntu) ** Tags added: nvidia -- 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/183 Title: NVIDIA driver (390) does not allow progress to login screen Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Bug description: Installing the nvidia-driver-390 package and disabling (or not) the nouveau drivers results in a system that superficially appears to busy hang before reaching the login screen, leaving only the fsck "/dev/sda1: clean,..." message on the screen. The machine is alive, and logging in remotely gives a hint at what is happening. The output of top shows that init and systemd are struggling with something: ``` top - 17:24:00 up 1 min, 1 user, load average: 2.76, 1.00, 0.36 Tasks: 188 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 17.0 us, 15.2 sy, 0.0 ni, 67.6 id, 0.0 wa, 0.0 hi, 0.1 si, 0.0 st KiB Mem : 16238012 total, 15513832 free, 242248 used, 481932 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15716900 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 225600 9312 6672 S 60.4 0.1 0:51.63 /sbin/init nosplash 797 root 20 0 71656 7180 5296 S 26.8 0.0 0:14.92 /lib/systemd/systemd-logind 1133 root 20 0 46368 3584 1976 R 13.9 0.0 0:12.01 /lib/systemd/systemd-udevd 795 root 20 0 1773200 30772 12548 S 13.2 0.2 0:11.71 /usr/lib/snapd/snapd 784 message+ 20 0 51464 6036 3988 S 12.9 0.0 0:11.15 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --s+ 308 root 19 -1 249904 120460 114260 S 10.7 0.7 0:10.60 /lib/systemd/systemd-journald 1132 root 20 0 46368 3584 1976 S 10.0 0.0 0:08.71 /lib/systemd/systemd-udevd 1134 root 20 0 46368 3260 1656 S 10.0 0.0 0:08.61 /lib/systemd/systemd-udevd 333 root 20 0 46368 4684 3084 S 5.0 0.0 0:04.25 /lib/systemd/systemd-udevd ``` Eventually, Xorg does manage to get a word in, but falls over, to try again repeatedly. ``` top - 16:52:36 up 2 min, 1 user, load average: 1.69, 1.04, 0.43 Tasks: 187 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 9.5 us, 3.7 sy, 0.0 ni, 85.6 id, 0.0 wa, 0.0 hi, 1.2 si, 0.0 st KiB Mem : 16238012 total, 15457080 free, 278152 used, 502780 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15680684 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1821 root 20 0 312908 61228 20584 R 65.2 0.4 0:01.97 /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -b+ 806 root 20 0 71656 7200 5320 S 18.5 0.0 0:24.83 /lib/systemd/systemd-logind ``` A further hint comes from syslog which is spammed with systemd trying to start nvidia-persistenced, which is then killed. This happens hundreds of times while the machine is up. This except shows one instance. ``` May 22 16:34:52 cube systemd[1]: Starting NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Verbose syslog connection opened May 22 16:34:52 cube nvidia-persistenced: Now running with user ID 123 and group ID 127 May 22 16:34:52 cube systemd[1]: Started NVIDIA Persistence Daemon. May 22 16:34:52 cube nvidia-persistenced: Started (31927) May 22 16:34:52 cube nvidia-persistenced: device :01:00.0 - registered May 22 16:34:52 cube nvidia-persistenced: Local RPC service initialized May 22 16:34:52 cube nvidia-persistenced: Received signal 15 May 22 16:34:52 cube systemd[1]: Stopping NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Socket closed. May 22 16:34:52 cube nvidia-persistenced: PID file unlocked. May 22 16:34:52 cube nvidia-persistenced: PID file closed. May 22 16:34:52 cube nvidia-persistenced: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced May 22 16:34:52 cube nvidia-persistenced: Shutdown (31927) May 22 16:34:52 cube systemd[1]: Stopped NVIDIA Persistence Daemon. ``` This is a fresh install of 18.04.2
[Kernel-packages] [Bug 1830029] Re: nouveau driver for nvidia is sluggish on GTX970M to the point of unusability
Your kernel log in comment #2 is showing a lot of crashes in the nouveau kernel driver. The best and only remedies for that are: (a) Install a newer kernel or just install a newer version of Ubuntu. Ubuntu 19.04: http://releases.ubuntu.com/19.04/ or kernel packages: https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D or (b) Continue trying to get the Nvidia proprietary driver working, per bug 183. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830029 Title: nouveau driver for nvidia is sluggish on GTX970M to the point of unusability Status in linux package in Ubuntu: Incomplete Bug description: I am trying to use the nouveau drivers on a recent (today) install of 18.04 on a 2.5yo laptop. Unfortunately the nvidia drivers don't work at all. What I am finding is that the sluggishness of the display is comparable to the case when nouveau drivers are disabled. The only real difference is in the amount of noise coming from the fan because of a slightly reduced CPU load due to Xorg. I don't even know where to start looking into this intelligently, but I would have expected that the drivers would have gotten to a usable state in the past 2 1/2 years since I last tried them on this machine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 22 21:05:40 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6540] NVIDIA Corporation GM204M [GeForce GTX 970M] [10de:13d8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 970M] [1558:6540] InstallationDate: Installed on 2019-05-22 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 5986:066d Acer, Inc Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook P65_P67RGRERA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic root=UUID=d6da27fa-5d91-4240-b3c9-c7de06124a36 ro nomodeset quiet nosplash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: P65_P67RGRERA dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.13:bd01/27/2016:svnNotebook:pnP65_P67RGRERA:pvrNotApplicable:rvnNotebook:rnP65_P67RGRERA:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P65_P67RGRERA dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 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/1830029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829657] Re: Ubuntu 16.04 with kernel 4.4.0-148 hangs on boot on a ThinkPad L460 while 4.4.0-145 doesnt
The same on Lenovo desktop, had to downgrade to 4.4.0-146. Kernel driver in use: i915 -- 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/1829657 Title: Ubuntu 16.04 with kernel 4.4.0-148 hangs on boot on a ThinkPad L460 while 4.4.0-145 doesnt Status in linux-signed package in Ubuntu: Confirmed Bug description: After the automatic update from 4.4.0-145 to 4.4.0-148 on a Thinkpad L460 the boot process hangs before any visible output and doesnt proceed from there. Changing back to 4.4.0-145 in the grub menu makes the boot proceed normally. > lspci -knn | grep -A3 VGA 00:02.0 VGA compatible controller [0300]: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) Subsystem: Lenovo Skylake Integrated Graphics [17aa:5051] Kernel driver in use: i915_bpo Kernel modules: i915_bpo ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-145-generic 4.4.0-145.171 ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176 Uname: Linux 4.4.0-145-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Sun May 19 16:36:06 2019 InstallationDate: Installed on 2016-11-04 (925 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1829657/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830029] Re: nouveau driver for nvidia is sluggish on GTX970M to the point of unusability
You appear to be using a kernel parameter ('nomodeset') which will
definitely break the nouveau driver and prevent it from working. To fix
this, please:
1. Edit /etc/default/grub and remove 'nomodeset'.
2. Run: sudo update-grub
3. Reboot
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** 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/1830029
Title:
nouveau driver for nvidia is sluggish on GTX970M to the point of
unusability
Status in linux package in Ubuntu:
Incomplete
Bug description:
I am trying to use the nouveau drivers on a recent (today) install of
18.04 on a 2.5yo laptop. Unfortunately the nvidia drivers don't work
at all.
What I am finding is that the sluggishness of the display is
comparable to the case when nouveau drivers are disabled. The only
real difference is in the amount of noise coming from the fan because
of a slightly reduced CPU load due to Xorg.
I don't even know where to start looking into this intelligently, but
I would have expected that the drivers would have gotten to a usable
state in the past 2 1/2 years since I last tried them on this machine.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed May 22 21:05:40 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA
controller])
Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6540]
NVIDIA Corporation GM204M [GeForce GTX 970M] [10de:13d8] (rev a1) (prog-if
00 [VGA controller])
Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 970M] [1558:6540]
InstallationDate: Installed on 2019-05-22 (0 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 5986:066d Acer, Inc
Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc.
Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Notebook P65_P67RGRERA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic
root=UUID=d6da27fa-5d91-4240-b3c9-c7de06124a36 ro nomodeset quiet nosplash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/27/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.13
dmi.board.asset.tag: Tag 12345
dmi.board.name: P65_P67RGRERA
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1.05.13:bd01/27/2016:svnNotebook:pnP65_P67RGRERA:pvrNotApplicable:rvnNotebook:rnP65_P67RGRERA:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: P65_P67RGRERA
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
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/1830029/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830000] [NEW] NVIDIA driver (390) does not allow progress to login screen
You have been subscribed to a public bug: Installing the nvidia-driver-390 package and disabling (or not) the nouveau drivers results in a system that superficially appears to busy hang before reaching the login screen, leaving only the fsck "/dev/sda1: clean,..." message on the screen. The machine is alive, and logging in remotely gives a hint at what is happening. The output of top shows that init and systemd are struggling with something: ``` top - 17:24:00 up 1 min, 1 user, load average: 2.76, 1.00, 0.36 Tasks: 188 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 17.0 us, 15.2 sy, 0.0 ni, 67.6 id, 0.0 wa, 0.0 hi, 0.1 si, 0.0 st KiB Mem : 16238012 total, 15513832 free, 242248 used, 481932 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15716900 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 225600 9312 6672 S 60.4 0.1 0:51.63 /sbin/init nosplash 797 root 20 0 71656 7180 5296 S 26.8 0.0 0:14.92 /lib/systemd/systemd-logind 1133 root 20 0 46368 3584 1976 R 13.9 0.0 0:12.01 /lib/systemd/systemd-udevd 795 root 20 0 1773200 30772 12548 S 13.2 0.2 0:11.71 /usr/lib/snapd/snapd 784 message+ 20 0 51464 6036 3988 S 12.9 0.0 0:11.15 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --s+ 308 root 19 -1 249904 120460 114260 S 10.7 0.7 0:10.60 /lib/systemd/systemd-journald 1132 root 20 0 46368 3584 1976 S 10.0 0.0 0:08.71 /lib/systemd/systemd-udevd 1134 root 20 0 46368 3260 1656 S 10.0 0.0 0:08.61 /lib/systemd/systemd-udevd 333 root 20 0 46368 4684 3084 S 5.0 0.0 0:04.25 /lib/systemd/systemd-udevd ``` Eventually, Xorg does manage to get a word in, but falls over, to try again repeatedly. ``` top - 16:52:36 up 2 min, 1 user, load average: 1.69, 1.04, 0.43 Tasks: 187 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 9.5 us, 3.7 sy, 0.0 ni, 85.6 id, 0.0 wa, 0.0 hi, 1.2 si, 0.0 st KiB Mem : 16238012 total, 15457080 free, 278152 used, 502780 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15680684 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1821 root 20 0 312908 61228 20584 R 65.2 0.4 0:01.97 /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -b+ 806 root 20 0 71656 7200 5320 S 18.5 0.0 0:24.83 /lib/systemd/systemd-logind ``` A further hint comes from syslog which is spammed with systemd trying to start nvidia-persistenced, which is then killed. This happens hundreds of times while the machine is up. This except shows one instance. ``` May 22 16:34:52 cube systemd[1]: Starting NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Verbose syslog connection opened May 22 16:34:52 cube nvidia-persistenced: Now running with user ID 123 and group ID 127 May 22 16:34:52 cube systemd[1]: Started NVIDIA Persistence Daemon. May 22 16:34:52 cube nvidia-persistenced: Started (31927) May 22 16:34:52 cube nvidia-persistenced: device :01:00.0 - registered May 22 16:34:52 cube nvidia-persistenced: Local RPC service initialized May 22 16:34:52 cube nvidia-persistenced: Received signal 15 May 22 16:34:52 cube systemd[1]: Stopping NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Socket closed. May 22 16:34:52 cube nvidia-persistenced: PID file unlocked. May 22 16:34:52 cube nvidia-persistenced: PID file closed. May 22 16:34:52 cube nvidia-persistenced: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced May 22 16:34:52 cube nvidia-persistenced: Shutdown (31927) May 22 16:34:52 cube systemd[1]: Stopped NVIDIA Persistence Daemon. ``` This is a fresh install of 18.04.2 (less than an hour old). If apport has not collected all the necessary details I'll post them after this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-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:
[Kernel-packages] [Bug 1830008] Re: [HP ProBook 450 G0] Camera is not detected
It is likely this bug has already been fixed in a newer version of Ubuntu. Please try live booting these from USB to see if they have the same problem (open the 'Cheese' app to test the camera): * 18.04 LTS: http://releases.ubuntu.com/18.04.2/ * 19.04: http://releases.ubuntu.com/19.04/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830008 Title: [HP ProBook 450 G0] Camera is not detected Status in linux package in Ubuntu: Incomplete Bug description: Camera is not detecting in my laptop hp450 Ubuntu 16.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177 Uname: Linux 4.4.0-148-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed May 22 15:01:31 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:194d] Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8670A/8670M/8750M] [1002:6600] (rev ff) (prog-if ff) InstallationDate: Installed on 2014-07-17 (1769 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP ProBook 450 G0 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic root=UUID=b777ded0-d5eb-4304-b538-a5179211a701 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IRF Ver. F.21 dmi.board.name: 1949 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 90.0C dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IRFVer.F.21:bd09/18/2013:svnHewlett-Packard:pnHPProBook450G0:pvrA2019CD200:rvnHewlett-Packard:rn1949:rvrKBCVersion90.0C:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 450 G0 dmi.product.version: A2019CD200 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed May 22 14:49:06 2019 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1116 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830008] Re: Camera is not detected
Thanks. It appears the kernel doesn't detect/support your camera, so I am reassigning this bug to the kernel. ** Summary changed: - Getting raedon error when booting + Camera is not detected ** Summary changed: - Camera is not detected + [HP ProBook 450 G0] Camera is not detected ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830008 Title: [HP ProBook 450 G0] Camera is not detected Status in linux package in Ubuntu: Incomplete Bug description: Camera is not detecting in my laptop hp450 Ubuntu 16.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177 Uname: Linux 4.4.0-148-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed May 22 15:01:31 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:194d] Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8670A/8670M/8750M] [1002:6600] (rev ff) (prog-if ff) InstallationDate: Installed on 2014-07-17 (1769 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP ProBook 450 G0 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic root=UUID=b777ded0-d5eb-4304-b538-a5179211a701 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IRF Ver. F.21 dmi.board.name: 1949 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 90.0C dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IRFVer.F.21:bd09/18/2013:svnHewlett-Packard:pnHPProBook450G0:pvrA2019CD200:rvnHewlett-Packard:rn1949:rvrKBCVersion90.0C:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 450 G0 dmi.product.version: A2019CD200 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed May 22 14:49:06 2019 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1116 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830029] [NEW] nouveau driver for nvidia is sluggish on GTX970M to the point of unusability
You have been subscribed to a public bug: I am trying to use the nouveau drivers on a recent (today) install of 18.04 on a 2.5yo laptop. Unfortunately the nvidia drivers don't work at all. What I am finding is that the sluggishness of the display is comparable to the case when nouveau drivers are disabled. The only real difference is in the amount of noise coming from the fan because of a slightly reduced CPU load due to Xorg. I don't even know where to start looking into this intelligently, but I would have expected that the drivers would have gotten to a usable state in the past 2 1/2 years since I last tried them on this machine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 22 21:05:40 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6540] NVIDIA Corporation GM204M [GeForce GTX 970M] [10de:13d8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 970M] [1558:6540] InstallationDate: Installed on 2019-05-22 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 5986:066d Acer, Inc Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook P65_P67RGRERA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic root=UUID=d6da27fa-5d91-4240-b3c9-c7de06124a36 ro nomodeset quiet nosplash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: P65_P67RGRERA dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.13:bd01/27/2016:svnNotebook:pnP65_P67RGRERA:pvrNotApplicable:rvnNotebook:rnP65_P67RGRERA:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P65_P67RGRERA dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 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: Incomplete ** Tags: amd64 apport-bug bionic performance ubuntu -- nouveau driver for nvidia is sluggish on GTX970M to the point of unusability https://bugs.launchpad.net/bugs/1830029 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 1830008] [NEW] [HP ProBook 450 G0] Camera is not detected
You have been subscribed to a public bug: Camera is not detecting in my laptop hp450 Ubuntu 16.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177 Uname: Linux 4.4.0-148-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed May 22 15:01:31 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:194d] Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8670A/8670M/8750M] [1002:6600] (rev ff) (prog-if ff) InstallationDate: Installed on 2014-07-17 (1769 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP ProBook 450 G0 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic root=UUID=b777ded0-d5eb-4304-b538-a5179211a701 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IRF Ver. F.21 dmi.board.name: 1949 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 90.0C dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IRFVer.F.21:bd09/18/2013:svnHewlett-Packard:pnHPProBook450G0:pvrA2019CD200:rvnHewlett-Packard:rn1949:rvrKBCVersion90.0C:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 450 G0 dmi.product.version: A2019CD200 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed May 22 14:49:06 2019 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1116 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.8 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu xenial -- [HP ProBook 450 G0] Camera is not detected https://bugs.launchpad.net/bugs/1830008 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 1825499] Re: Touchpad vertical sensitivity is much higher than horizontal sensitivity [HP Pavilion g6]
Ubuntu 18.10 (which does not have the bug) uses kernel version 4.18 so please start testing versions around there. If you find 4.18 fixes the bug then next please find a version roughly halfway between 4.18 and 5.0.0 ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825499 Title: Touchpad vertical sensitivity is much higher than horizontal sensitivity [HP Pavilion g6] Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: After installing Kubuntu 19.04, I found that vertical sensitivity is much higher than horizontal sensitivity. Installing xserver-xorg-input-synaptics improved the situation a bit and enabled KDE touchpad setting that were disabled. It's very annoying. Laptop: HP Pavilion g6. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-input-synaptics 1.9.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CurrentDesktop: KDE Date: Fri Apr 19 12:00:02 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=UUID=e1903286-a666-49b1-8177-cf31dc5c8e9f ro quiet splash vt.handoff=1 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.25 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 183E dmi.board.vendor: Hewlett-Packard dmi.board.version: 56.32 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088512005D160:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: D4Z91EA#ABV dmi.product.version: 088512005D160 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1825499/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829652] Re: Kernel panic upon resetting ixgbe SR-IOV VFIO virtual function using 5.0 kernel
Patch submitted upstream: https://www.spinics.net/lists/netdev/msg571753.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829652 Title: Kernel panic upon resetting ixgbe SR-IOV VFIO virtual function using 5.0 kernel Status in linux package in Ubuntu: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: In Progress Bug description: Hi, I've recently upgraded my system to ubuntu 19.04, and kernel consistently panics when I boot a virtual machine using an SR-IOV VFIO virtual function. Could reproduce with 5.0.0-13-generic and 5.0.0-15-generic, doesn't happen with 4.18.0-20-generic. I'm using libvirt and VM is using KVM, XML snippet to delegate virtual function to VM is: As soon as I start the VM using "virsh start vm", kernel panics. I'm using X550T intel NIC (lspci output: Ethernet controller: Intel Corporation Ethernet Controller 10G X550T (rev 01)) on a Supermicro X11SSH-CTF motherboard, with up to date bios and 4 virtual functions (class/net/em1/device/sriov_numvfs = 4). Given panic stack trace (see attachment), I've narrowed down the bug to ixgbe_ipsec_vf_clear function in upstream ixgbe driver: https://github.com/torvalds/linux/blob/72cf0b07418a9c8349aa9137194b1ccba6e54a9d/drivers/net/ethernet/intel/ixgbe/ixgbe_ipsec.c#L840 When I comment its usage (https://github.com/torvalds/linux/blob/72cf0b07418a9c8349aa9137194b1ccba6e54a9d/drivers/net/ethernet/intel/ixgbe/ixgbe_sriov.c#L734), everything works as expected (I'm not using any ipsec feature). Didn't try to fix the ixgbe_ipsec_vf_clear function though. Please find attached a stack trace collected using IPMI serial-over- lan. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829652/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824259] Re: Headphone jack switch sense is inverted: plugging in headphones disables headphone output
With chance of regression quite low, we will not remove this particular fix prior to release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: [Impact] On the LattePanda board, the headphone detection signal is not correct, it is inverted: plugging in headphones disables headphone output [Fix] In the codec driver, there already is a fixup, just set the inv_jd1_1 to true. [Test Case] It is tested by the bug reporter, please refer to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824259/comments/23 [Regression Risk] Low. This fix is specific to a board which is defined by DMI strings. My machine is a LattePanda board, which uses a "chtrt5645" device as a sound card. It has a single headphone output jack, which I think is a TRRS jack, with a mic input, such as is normally used on phones. When I don't have headphones plugged in, the system thinks headphones *are* plugged in. Gnome Control Center shows my audio device as being headphones. If I insert a headphone connector partway into the jack, I can even get sound in the headphones. But if I plug the headphones all the way in, the system decided that I have *un*plugged the headphones, and switches output over to "Speaker". The system doesn't actually have a speaker, only a headphone jack. And when the system switches over to "Speaker", I get no sound out of the headphones, even if I open "pavucontrol" and swap over to "Headphones (unplugged)" on the "Output Devices" tab. This is what "pacmd"'s "list-cards" command says with my headphones *unplugged*: 2 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "1" alsa.card_name = "Intel HDMI/DP LPE Audio" alsa.long_card_name = "Intel HDMI/DP LPE Audio" alsa.driver_name = "snd_hdmi_lpe_audio" device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio" sysfs.path = "/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "22b0" device.product.name = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" device.string = "1" device.description = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: no) output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 800, available: no) output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (priority 800, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no) off: Off (priority 0, available: unknown) active profile: ports: hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" index: 1 name: driver: owner module: 8 properties: alsa.card = "0" alsa.card_name = "chtrt5645" alsa.long_card_name = "AMICorporation-Defaultstring-Defaultstring-CherryTrailCR" alsa.driver_name = "snd_soc_sst_cht_bsw_rt5645" device.bus_path = "platform-cht-bsw-rt5645" sysfs.path = "/devices/pci:00/808622A8:00/cht-bsw-rt5645/sound/card0" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card" profiles: HiFi: Default (priority 8000, available: unknown) off: Off (priority 0, available:
[Kernel-packages] [Bug 1828134] Re: Wifi not working after suspend/resume cycle
Hello David, any new information on this 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/1828134 Title: Wifi not working after suspend/resume cycle Status in linux package in Ubuntu: Confirmed Bug description: About 75% of the time for the past few weeks (I don't have a time where this started), my wifi is not working after resume from suspend. I'm happy to provide more debugging info if needed. I have tried an rmmod/modprobe on on the iwlwifi,iwlmvm modules just to see after the resume, and didn't re-enable the card. The symptoms are, the wlp4so interface is DOWN, I can't bring it up. gnome-network-manager widget turning the interface off/on doesn't work. I don't see anything glaring in dmesg. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-generic 5.0.0.14.15 ProcVersionSignature: Ubuntu 5.0.0-14.15-generic 5.0.6 Uname: Linux 5.0.0-14-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dpb4587 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue May 7 18:49:01 2019 InstallationDate: Installed on 2018-06-18 (323 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20HRCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-14-generic root=UUID=fa64d67d-26bf-4c42-a12f-c45b6ea5117c ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-14-generic N/A linux-backports-modules-5.0.0-14-generic N/A linux-firmware1.178 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-03-15 (53 days ago) dmi.bios.date: 02/14/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET52W(1.37) dmi.board.asset.tag: Not Available dmi.board.name: 20HRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1MET52W(1.37):bd02/14/2019:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 5th dmi.product.name: 20HRCTO1WW dmi.product.sku: LENOVO_MT_20HR_BU_Think_FM_ThinkPad X1 Carbon 5th dmi.product.version: ThinkPad X1 Carbon 5th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828134/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1824259] Re: Headphone jack switch sense is inverted: plugging in headphones disables headphone output
Do I have to downgrade my system from Dingo to Cosmic in order to test this in Cosmic, to keep my bug from being closed? May 20, 2019 7:02 AM, "Ubuntu Kernel Bot" wrote: > This bug is awaiting verification that the kernel in -proposed solves > the problem. Please test the kernel and update this bug with the > results. If the problem is solved, change the tag 'verification-needed- > cosmic' to 'verification-done-cosmic'. If the problem still exists, > change the tag 'verification-needed-cosmic' to 'verification-failed- > cosmic'. > > If verification is not done by 5 working days from today, this fix will > be dropped from the source code, and this bug will be closed. > > See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how > to enable and use -proposed. Thank you! > > ** Tags added: verification-needed-cosmic > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1824259 > > Title: > Headphone jack switch sense is inverted: plugging in headphones > disables headphone output > > Status in linux package in Ubuntu: > Fix Committed > Status in linux source package in Bionic: > Fix Committed > Status in linux source package in Cosmic: > Fix Committed > Status in linux source package in Disco: > Fix Committed > > Bug description: > [Impact] > On the LattePanda board, the headphone detection signal is not correct, it is > inverted: plugging in headphones disables headphone output > > [Fix] > In the codec driver, there already is a fixup, just set the inv_jd1_1 to true. > > [Test Case] > It is tested by the bug reporter, please refer to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824259/comments/23 > > [Regression Risk] > Low. This fix is specific to a board which is defined by DMI strings. > > My machine is a LattePanda board, which uses a "chtrt5645" device as a sound > card. It has a single > headphone output jack, which I think is a TRRS jack, with a mic input, such > as is normally used on > phones. > > When I don't have headphones plugged in, the system thinks headphones > *are* plugged in. Gnome Control Center shows my audio device as being > headphones. If I insert a headphone connector partway into the jack, I > can even get sound in the headphones. > > But if I plug the headphones all the way in, the system decided that I > have *un*plugged the headphones, and switches output over to > "Speaker". The system doesn't actually have a speaker, only a > headphone jack. And when the system switches over to "Speaker", I get > no sound out of the headphones, even if I open "pavucontrol" and swap > over to "Headphones (unplugged)" on the "Output Devices" tab. > > This is what "pacmd"'s "list-cards" command says with my headphones > *unplugged*: > > 2 card(s) available. > index: 0 > name: > driver: > owner module: 7 > properties: > alsa.card = "1" > alsa.card_name = "Intel HDMI/DP LPE Audio" > alsa.long_card_name = "Intel HDMI/DP LPE Audio" > alsa.driver_name = "snd_hdmi_lpe_audio" > device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio" > sysfs.path = "/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1" > device.bus = "pci" > device.vendor.id = "8086" > device.vendor.name = "Intel Corporation" > device.product.id = "22b0" > device.product.name = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx > Series PCI Configuration > Registers" > device.string = "1" > device.description = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx > Series PCI Configuration > Registers" > module-udev-detect.discovered = "1" > device.icon_name = "audio-card-pci" > profiles: > output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: > no) > output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 800, > available: no) > output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (priority 800, > available: no) > output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, > available: no) > output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority > 600, available: no) > output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority > 600, available: no) > output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, > available: no) > output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority > 600, available: no) > output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority > 600, available: no) > off: Off (priority 0, available: unknown) > active profile: > ports: > hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, > available: no) > properties: > device.icon_name = "video-display" > hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, > available: no) > properties: > device.icon_name = "video-display" > hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, > available: no) > properties: >
[Kernel-packages] [Bug 1826461] Re: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection.
Hi Kai-Heng Feng, thanks for your time. I would like to help but I have never installed mainline kernel before. Is it safe? Is it necessary since we know that this bug appeared after upgrade from Ubuntu 16.04 to 18.04 (so it didn't affect kernels before 4.15)? This is my only laptop and it is indispensable for me to work. Can I do it with ukuu or do I have to do it manually? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826461 Title: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection. Status in linux package in Ubuntu: Confirmed Bug description: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection. Ubuntu 18.04, Thinkpad X240, Sierra modem Reproduced on 4.15 and 4.18 kernel. The bug is triggered only when there is no WiFi connection. After waking laptop from suspend ModemManager stops working and after that I cannot suspend anymore. When it happens mmcli -L gives: Found 1 modems: /org/freedesktop/ModemManager1/Modem/9 [Sierra] MBIM [1199:A001] And mmcli -m 9: Status | lock: 'none' | unlock retries: 'sim-pin (3)' | state: 'registered' |power state: 'on' |access tech: 'gprs, lte' | signal quality: '0' (cached) After a few attempts to restart ModemManager and suspend it starts working. But only for one suspend. After one suspend I need to do the whole procedure again. Similar to: https://askubuntu.com/questions/1084698/ubuntu-18-04-em7455-works-only-after-suspend https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950?comments=all https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743 On Ubuntu 16.04 suspend and ModemManager used to work flawlessly. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jan2384 F pulseaudio /dev/snd/controlC1: jan2384 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=2e1ab569-7004-4df3-b9f0-445fd74a1998 InstallationDate: Installed on 2016-10-22 (915 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20ALA0ARHH Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=88a770a0-dfd0-42f5-91bb-960353d1f1f6 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-18-generic N/A linux-backports-modules-4.18.0-18-generic N/A linux-firmware 1.173.5 Tags: bionic Uname: Linux 4.18.0-18-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-14 (254 days ago) UserGroups: adm audio cdrom dip input lp lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GIET94WW (2.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ALA0ARHH dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGIET94WW(2.44):bd09/20/2018:svnLENOVO:pn20ALA0ARHH:pvrThinkPadX240:rvnLENOVO:rn20ALA0ARHH:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X240 dmi.product.name: 20ALA0ARHH dmi.product.sku: LENOVO_MT_20AL_BU_Think_FM_ThinkPad X240 dmi.product.version: ThinkPad X240 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security
Chris, thanks for confirming which processor is in use. To force downgrade the microcode package on bionic, do: sudo apt install intel-microcode=3.20180312.0~ubuntu18.04.1 For other releases, you will need to replace the version with what version(s) are available for your release; you can use apt-cache policy to see what is available. In the worst case, if the version you want to downgrade to is not available in the archive any more (e.g. for xenial or trusty), you can navigate to that release's information page for that package (e.g. https://launchpad.net/ubuntu/xenial/+source/intel-microcode), navigate to the specific version you desire, and manually download the appropriate binary deb for your system, and install it via 'sudo dpkg -i intel_microcode-VERSION_ARCH.deb'. One downside to using older versions is that, unless you use dpkg pinning to keep them in place, unattended-upgrades or some other update process will upgrade them to the current version available for that release, putting you right back to where you started. An alternative approach would be to add IUCODE_TOOL_INITRAMFS=no to /etc/default/intel-microcode and then re-running 'update-initramfs -u' to remove the microcode bits from the initramfs image. NOTE: you will want to remember that you did this so that you can re-enable microcode updates once this issue has been resolved. 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/1829620 Title: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: Description: - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of booting, after grub) - does not even show the enter cryptsetup passphrase - affected kernels: # apt list --installed |grep linux-signed WARNING: apt does not have a stable CLI interface. Use with caution in scripts. linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 [installed] linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 4.18.0.20.70 amd64 [installed] linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 5.0.0.15.71 amd64 [installed] - the setup is not new, has been working perfectly before (about 7 days since my last restart?) System: - HW: ASUS Zenbook 14 UX433FN - Ubuntu 18.04, runing latest HWE, fully updated - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup), Suspected/possible cause?: - recent intel-microcode package update - recent kernel package updates Steps taken: - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding nosplash, noplymouth) - completely removed nvidia drivers (apt purge *nvidia*) - completely purged and reinstalled grub (grup-pc) - completely purged and reinstalled all kernels (headers, modules, image, ..) - toggle BIOS "fastboot" (now using OFF) - toggle UEFI SecureBoot (now using ON) - remove plymouth (apt remove *plymouth* , but the workaround is working with plymouth installed) Workaround: - so far, I'm only able to boot with non-Ubuntu kernel! (linux-image-liquorix-amd64) - which needs "splash" option ON - reinstall cryptsetup & update-grub (as suggested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620/comments/10 ) I am not sure how to get you more debug info, as this setup has been working before, and it's a very eary boot-process bug, so I can't even access dmesg etc. EDIT: Hypothesis: Only affects ASUS with i7-8565U Whiskey Lake Intel CPU Upstream Bug Report: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1 WORKAROUND 1: disable intel microcode updates during boot From this bug: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920 1/ add the boot parameter: dis_ucode_ldr to /etc/default/grub 2/ update-grub WORKAROUND 2: downgrade (and hold) intel-microcode to older version from bionic/main apt install --reinstall intel-microcode=3.20180312.0~ubuntu18.04.1 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2337 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge (not installed) Tags: bionic wayland-session Uname: Linux 5.0.0-17.1-liquorix-amd64 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo vboxusers video
[Kernel-packages] [Bug 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security
^^^ sorry this cpuinfo was off a ux433fn booted on an affected kernel with dis_ucode_ldr -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829620 Title: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: Description: - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of booting, after grub) - does not even show the enter cryptsetup passphrase - affected kernels: # apt list --installed |grep linux-signed WARNING: apt does not have a stable CLI interface. Use with caution in scripts. linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 [installed] linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 4.18.0.20.70 amd64 [installed] linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 5.0.0.15.71 amd64 [installed] - the setup is not new, has been working perfectly before (about 7 days since my last restart?) System: - HW: ASUS Zenbook 14 UX433FN - Ubuntu 18.04, runing latest HWE, fully updated - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup), Suspected/possible cause?: - recent intel-microcode package update - recent kernel package updates Steps taken: - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding nosplash, noplymouth) - completely removed nvidia drivers (apt purge *nvidia*) - completely purged and reinstalled grub (grup-pc) - completely purged and reinstalled all kernels (headers, modules, image, ..) - toggle BIOS "fastboot" (now using OFF) - toggle UEFI SecureBoot (now using ON) - remove plymouth (apt remove *plymouth* , but the workaround is working with plymouth installed) Workaround: - so far, I'm only able to boot with non-Ubuntu kernel! (linux-image-liquorix-amd64) - which needs "splash" option ON - reinstall cryptsetup & update-grub (as suggested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620/comments/10 ) I am not sure how to get you more debug info, as this setup has been working before, and it's a very eary boot-process bug, so I can't even access dmesg etc. EDIT: Hypothesis: Only affects ASUS with i7-8565U Whiskey Lake Intel CPU Upstream Bug Report: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1 WORKAROUND 1: disable intel microcode updates during boot From this bug: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920 1/ add the boot parameter: dis_ucode_ldr to /etc/default/grub 2/ update-grub WORKAROUND 2: downgrade (and hold) intel-microcode to older version from bionic/main apt install --reinstall intel-microcode=3.20180312.0~ubuntu18.04.1 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2337 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge (not installed) Tags: bionic wayland-session Uname: Linux 5.0.0-17.1-liquorix-amd64 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo vboxusers video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2339 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6 Tags: third-party-packages bionic wayland-session Uname: Linux 5.0.0-15-generic x86_64 UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1829620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security
Steve, Mark, I've had bios version 302 installed since the 5th of April and was booting fine until the apt-get upgrade run on the 21st of May note in my proc/cpuinfo the microcode version is listed as 0x98 also how do you force a downgrade of the microcode package? ** Attachment added: "cpuinfo" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620/+attachment/5265823/+files/proc-cpuinfo.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/1829620 Title: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: Description: - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of booting, after grub) - does not even show the enter cryptsetup passphrase - affected kernels: # apt list --installed |grep linux-signed WARNING: apt does not have a stable CLI interface. Use with caution in scripts. linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 [installed] linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 4.18.0.20.70 amd64 [installed] linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 5.0.0.15.71 amd64 [installed] - the setup is not new, has been working perfectly before (about 7 days since my last restart?) System: - HW: ASUS Zenbook 14 UX433FN - Ubuntu 18.04, runing latest HWE, fully updated - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup), Suspected/possible cause?: - recent intel-microcode package update - recent kernel package updates Steps taken: - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding nosplash, noplymouth) - completely removed nvidia drivers (apt purge *nvidia*) - completely purged and reinstalled grub (grup-pc) - completely purged and reinstalled all kernels (headers, modules, image, ..) - toggle BIOS "fastboot" (now using OFF) - toggle UEFI SecureBoot (now using ON) - remove plymouth (apt remove *plymouth* , but the workaround is working with plymouth installed) Workaround: - so far, I'm only able to boot with non-Ubuntu kernel! (linux-image-liquorix-amd64) - which needs "splash" option ON - reinstall cryptsetup & update-grub (as suggested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620/comments/10 ) I am not sure how to get you more debug info, as this setup has been working before, and it's a very eary boot-process bug, so I can't even access dmesg etc. EDIT: Hypothesis: Only affects ASUS with i7-8565U Whiskey Lake Intel CPU Upstream Bug Report: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1 WORKAROUND 1: disable intel microcode updates during boot From this bug: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920 1/ add the boot parameter: dis_ucode_ldr to /etc/default/grub 2/ update-grub WORKAROUND 2: downgrade (and hold) intel-microcode to older version from bionic/main apt install --reinstall intel-microcode=3.20180312.0~ubuntu18.04.1 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2337 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge (not installed) Tags: bionic wayland-session Uname: Linux 5.0.0-17.1-liquorix-amd64 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo vboxusers video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2339 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6 Tags: third-party-packages bionic wayland-session Uname: Linux 5.0.0-15-generic x86_64 UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1829620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post
[Kernel-packages] [Bug 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security
Intel microcode update definitely created same issue for me on Asus Zenbook 14 (UX433F) on 18.04.2 LTS. Can also confirm the instructions above "add dis_ucode_ldr to the kernel command line (from GRUB if you cannot boot)" worked perfectly for temporary workaround. This is my fourth Asus, and I've been using Linux since 1997, but I can't remember struggling as much with any other machine/distro combo as with this UX433F on 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/1829620 Title: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: Description: - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of booting, after grub) - does not even show the enter cryptsetup passphrase - affected kernels: # apt list --installed |grep linux-signed WARNING: apt does not have a stable CLI interface. Use with caution in scripts. linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 [installed] linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 4.18.0.20.70 amd64 [installed] linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 5.0.0.15.71 amd64 [installed] - the setup is not new, has been working perfectly before (about 7 days since my last restart?) System: - HW: ASUS Zenbook 14 UX433FN - Ubuntu 18.04, runing latest HWE, fully updated - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup), Suspected/possible cause?: - recent intel-microcode package update - recent kernel package updates Steps taken: - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding nosplash, noplymouth) - completely removed nvidia drivers (apt purge *nvidia*) - completely purged and reinstalled grub (grup-pc) - completely purged and reinstalled all kernels (headers, modules, image, ..) - toggle BIOS "fastboot" (now using OFF) - toggle UEFI SecureBoot (now using ON) - remove plymouth (apt remove *plymouth* , but the workaround is working with plymouth installed) Workaround: - so far, I'm only able to boot with non-Ubuntu kernel! (linux-image-liquorix-amd64) - which needs "splash" option ON - reinstall cryptsetup & update-grub (as suggested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620/comments/10 ) I am not sure how to get you more debug info, as this setup has been working before, and it's a very eary boot-process bug, so I can't even access dmesg etc. EDIT: Hypothesis: Only affects ASUS with i7-8565U Whiskey Lake Intel CPU Upstream Bug Report: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1 WORKAROUND 1: disable intel microcode updates during boot From this bug: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920 1/ add the boot parameter: dis_ucode_ldr to /etc/default/grub 2/ update-grub WORKAROUND 2: downgrade (and hold) intel-microcode to older version from bionic/main apt install --reinstall intel-microcode=3.20180312.0~ubuntu18.04.1 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2337 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge (not installed) Tags: bionic wayland-session Uname: Linux 5.0.0-17.1-liquorix-amd64 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo vboxusers video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2339 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6 Tags: third-party-packages bionic wayland-session Uname: Linux 5.0.0-15-generic x86_64 UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1829620/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1830116] 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 1830116 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/1830116 Title: linux-generic: missing module intel_pmc_core Status in linux package in Ubuntu: Incomplete Bug description: Description: linux-5.0.0-15-generic has missing module named 'intel_pmc_core' for device: 00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-LP PMC [8086:9d21] (rev 21) Similar bug #1730770 ? Release: 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830116/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830116] Re: linux-generic: missing module intel_pmc_core
** Package changed: linux-meta (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/1830116 Title: linux-generic: missing module intel_pmc_core Status in linux package in Ubuntu: New Bug description: Description: linux-5.0.0-15-generic has missing module named 'intel_pmc_core' for device: 00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-LP PMC [8086:9d21] (rev 21) Similar bug #1730770 ? Release: 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830116/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830116] [NEW] linux-generic: missing module intel_pmc_core
Public bug reported: Description: linux-5.0.0-15-generic has missing module named 'intel_pmc_core' for device: 00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-LP PMC [8086:9d21] (rev 21) Similar bug #1730770 ? Release: 19.04 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: disco ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/1830116/+attachment/5265818/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1830116 Title: linux-generic: missing module intel_pmc_core Status in linux package in Ubuntu: New Bug description: Description: linux-5.0.0-15-generic has missing module named 'intel_pmc_core' for device: 00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-LP PMC [8086:9d21] (rev 21) Similar bug #1730770 ? Release: 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830116/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823516] Re: Nvidia driver installed but X apps are using software rendering (LLVMpipe) in Wayland sessions
Couldn't find a bug, but it's described as a known issue here: https://blogs.gnome.org/uraeus/2019/04/03/preparing-for-fedora- workstation-30/ Given the description above it seems to be waiting on a new nvidia driver - still an issue on 430.14. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1823516 Title: Nvidia driver installed but X apps are using software rendering (LLVMpipe) in Wayland sessions Status in mesa package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in nvidia-graphics-drivers-418 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Triaged Bug description: Nvidia driver installed but X apps are using software rendering (LLVMpipe) in Wayland sessions. I am using kernel parameter nvidia-drm.modeset=1, which is required to get the "Ubuntu on Wayland" option. But after logging in I see: $ glxinfo | grep OpenGL OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 8.0, 256 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 19.0.1 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.1 Mesa 19.0.1 OpenGL shading language version string: 1.40 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 19.0.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: $ es2_info | grep ^GL GL_VERSION: OpenGL ES 3.0 Mesa 19.0.1 GL_RENDERER: llvmpipe (LLVM 8.0, 256 bits) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nvidia-driver-418 418.56-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu25 Architecture: amd64 Date: Sun Apr 7 17:26:07 2019 InstallationDate: Installed on 2018-12-04 (124 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) SourcePackage: nvidia-graphics-drivers-418 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1823516/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826125]
In https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826125/comments/53 it is mentioned that the same laptop with PCLinuxOS with 5.0.2 doesn't flicker. Is it worth it getting some data from there perhaps? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826125 Title: Dell XPS 13 9380 flickering (Whiskey Lake) Status in Linux: Incomplete Status in linux package in Ubuntu: Confirmed Bug description: A brand new Dell XPS 13 9380 preinstalled with Ubuntu 18.04 flickers to the point of being totally unusable. I have upgraded since to 18.10 and 19.04 with no changes. I have tried several combinations of the i915 parameters fastboot, enable_rc6 and enable_fbc to no avail. Examples of flickering are here: https://photos.app.goo.gl/1PkL2HrjMBP41aML9 https://photos.app.goo.gl/CMzmMwrCPH5wh8aw6 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1430 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-20180608-47+italia-whl+X31 DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-13 (10 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 9380 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1035-oem root=UUID=252898e9-6e96-4705-a709-2db930b7c4c7 ro quiet splash i915.fastboot=1 i915.enable_rc6=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1035.40-oem 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-1035-oem N/A linux-backports-modules-4.15.0-1035-oem N/A linux-firmware 1.178 Tags: disco Uname: Linux 4.15.0-1035-oem x86_64 UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 02/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/14/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1826125/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826125]
(In reply to Paulo J. Matos from comment #11) > Created attachment 144319 [details] > rc5+ kernel with enable_psr=0 The log was cut off so couldn't see that PSR was in fact disabled. You can fix that by passing eg. log_buf_len=2M to the kernel cmdline. Anyways, after a second glance at the logs I see the sink does sometimes indicate that the receiver port was not synchronized. Not sure why the failure manifests at that level with the link otherwise being reported as stable. Looks like we could try to reduce the link rate a bit and still have enough bandwidth for the 4k@60 mode. I'll attach something to that effect. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826125 Title: Dell XPS 13 9380 flickering (Whiskey Lake) Status in Linux: Incomplete Status in linux package in Ubuntu: Confirmed Bug description: A brand new Dell XPS 13 9380 preinstalled with Ubuntu 18.04 flickers to the point of being totally unusable. I have upgraded since to 18.10 and 19.04 with no changes. I have tried several combinations of the i915 parameters fastboot, enable_rc6 and enable_fbc to no avail. Examples of flickering are here: https://photos.app.goo.gl/1PkL2HrjMBP41aML9 https://photos.app.goo.gl/CMzmMwrCPH5wh8aw6 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1430 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-20180608-47+italia-whl+X31 DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-13 (10 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 9380 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1035-oem root=UUID=252898e9-6e96-4705-a709-2db930b7c4c7 ro quiet splash i915.fastboot=1 i915.enable_rc6=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1035.40-oem 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-1035-oem N/A linux-backports-modules-4.15.0-1035-oem N/A linux-firmware 1.178 Tags: disco Uname: Linux 4.15.0-1035-oem x86_64 UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 02/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/14/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1826125/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826125]
Hmm, yes 4.32 is what the BIOS uses, so this might even help:
[1.391106] [drm:intel_dump_pipe_config [i915]] port clock: 432000, pipe src
size: 3840x2160, pixel rate 533299
Hmm. That probably means this is a victim of commit f11cb1c19ad0
("drm/i915/dp: revert back to max link rate and lane count on eDP"),
which I think would have picked the lower link rate for us.
Yes, eDP revision seems to be 1.4a:
[1.385017] [drm:intel_dp_init_connector [i915]] eDP DPCD: 04 92 a5
so I believe that is indeed what would have happened.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1826125
Title:
Dell XPS 13 9380 flickering (Whiskey Lake)
Status in Linux:
Incomplete
Status in linux package in Ubuntu:
Confirmed
Bug description:
A brand new Dell XPS 13 9380 preinstalled with Ubuntu 18.04 flickers
to the point of being totally unusable.
I have upgraded since to 18.10 and 19.04 with no changes. I have tried
several combinations of the i915 parameters fastboot, enable_rc6 and
enable_fbc to no avail.
Examples of flickering are here:
https://photos.app.goo.gl/1PkL2HrjMBP41aML9
https://photos.app.goo.gl/CMzmMwrCPH5wh8aw6
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm1430 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-20180608-47+italia-whl+X31
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2019-04-13 (10 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary
20180608-09:38
MachineType: Dell Inc. XPS 13 9380
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1035-oem
root=UUID=252898e9-6e96-4705-a709-2db930b7c4c7 ro quiet splash i915.fastboot=1
i915.enable_rc6=0 vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-1035.40-oem 4.15.18
PulseList:
Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not
accessible: Permission denied
No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-4.15.0-1035-oem N/A
linux-backports-modules-4.15.0-1035-oem N/A
linux-firmware 1.178
Tags: disco
Uname: Linux 4.15.0-1035-oem x86_64
UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 02/14/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.1
dmi.board.name: 0KTW76
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.2.1:bd02/14/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9380
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1826125/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826125]
Timo, I have attached the dmesg with rc5+ kernel you asked me to test. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826125 Title: Dell XPS 13 9380 flickering (Whiskey Lake) Status in Linux: Incomplete Status in linux package in Ubuntu: Confirmed Bug description: A brand new Dell XPS 13 9380 preinstalled with Ubuntu 18.04 flickers to the point of being totally unusable. I have upgraded since to 18.10 and 19.04 with no changes. I have tried several combinations of the i915 parameters fastboot, enable_rc6 and enable_fbc to no avail. Examples of flickering are here: https://photos.app.goo.gl/1PkL2HrjMBP41aML9 https://photos.app.goo.gl/CMzmMwrCPH5wh8aw6 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1430 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-20180608-47+italia-whl+X31 DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-13 (10 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 9380 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1035-oem root=UUID=252898e9-6e96-4705-a709-2db930b7c4c7 ro quiet splash i915.fastboot=1 i915.enable_rc6=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1035.40-oem 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-1035-oem N/A linux-backports-modules-4.15.0-1035-oem N/A linux-firmware 1.178 Tags: disco Uname: Linux 4.15.0-1035-oem x86_64 UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 02/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/14/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1826125/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826125]
Created attachment 144325 [PATCH] hack: Disable 5.4ghz link rate for skl This should drop the link rate to 4.32ghz, which is the lowest we can go with this panel. Please test. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826125 Title: Dell XPS 13 9380 flickering (Whiskey Lake) Status in Linux: Incomplete Status in linux package in Ubuntu: Confirmed Bug description: A brand new Dell XPS 13 9380 preinstalled with Ubuntu 18.04 flickers to the point of being totally unusable. I have upgraded since to 18.10 and 19.04 with no changes. I have tried several combinations of the i915 parameters fastboot, enable_rc6 and enable_fbc to no avail. Examples of flickering are here: https://photos.app.goo.gl/1PkL2HrjMBP41aML9 https://photos.app.goo.gl/CMzmMwrCPH5wh8aw6 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1430 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-20180608-47+italia-whl+X31 DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-13 (10 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 9380 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1035-oem root=UUID=252898e9-6e96-4705-a709-2db930b7c4c7 ro quiet splash i915.fastboot=1 i915.enable_rc6=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1035.40-oem 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-1035-oem N/A linux-backports-modules-4.15.0-1035-oem N/A linux-firmware 1.178 Tags: disco Uname: Linux 4.15.0-1035-oem x86_64 UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 02/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/14/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1826125/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826125]
Created attachment 144319 rc5+ kernel with enable_psr=0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826125 Title: Dell XPS 13 9380 flickering (Whiskey Lake) Status in Linux: Incomplete Status in linux package in Ubuntu: Confirmed Bug description: A brand new Dell XPS 13 9380 preinstalled with Ubuntu 18.04 flickers to the point of being totally unusable. I have upgraded since to 18.10 and 19.04 with no changes. I have tried several combinations of the i915 parameters fastboot, enable_rc6 and enable_fbc to no avail. Examples of flickering are here: https://photos.app.goo.gl/1PkL2HrjMBP41aML9 https://photos.app.goo.gl/CMzmMwrCPH5wh8aw6 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1430 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-20180608-47+italia-whl+X31 DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-13 (10 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 9380 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1035-oem root=UUID=252898e9-6e96-4705-a709-2db930b7c4c7 ro quiet splash i915.fastboot=1 i915.enable_rc6=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1035.40-oem 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-1035-oem N/A linux-backports-modules-4.15.0-1035-oem N/A linux-firmware 1.178 Tags: disco Uname: Linux 4.15.0-1035-oem x86_64 UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 02/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/14/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1826125/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826125]
(In reply to Ville Syrjala from comment #9) > [4.550517] [drm:intel_dp_hpd_pulse [i915]] ESI: 41 00 00 00 00 00 00 00 > 00 00 00 00 81 01 > > According to that the sink thinks everything is fine, so no idea why > generates short hpds. > > Could be some kind of PSR fail. Please try passing i915.enable_psr=0 to the > kernel cmdline. enable_psr=0 does not help. Posting dmesg with enable_psr=0. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826125 Title: Dell XPS 13 9380 flickering (Whiskey Lake) Status in Linux: Incomplete Status in linux package in Ubuntu: Confirmed Bug description: A brand new Dell XPS 13 9380 preinstalled with Ubuntu 18.04 flickers to the point of being totally unusable. I have upgraded since to 18.10 and 19.04 with no changes. I have tried several combinations of the i915 parameters fastboot, enable_rc6 and enable_fbc to no avail. Examples of flickering are here: https://photos.app.goo.gl/1PkL2HrjMBP41aML9 https://photos.app.goo.gl/CMzmMwrCPH5wh8aw6 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1430 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-20180608-47+italia-whl+X31 DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-13 (10 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 9380 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1035-oem root=UUID=252898e9-6e96-4705-a709-2db930b7c4c7 ro quiet splash i915.fastboot=1 i915.enable_rc6=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1035.40-oem 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-1035-oem N/A linux-backports-modules-4.15.0-1035-oem N/A linux-firmware 1.178 Tags: disco Uname: Linux 4.15.0-1035-oem x86_64 UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 02/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/14/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1826125/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826125]
[4.550517] [drm:intel_dp_hpd_pulse [i915]] ESI: 41 00 00 00 00 00 00 00 00 00 00 00 81 01 According to that the sink thinks everything is fine, so no idea why generates short hpds. Could be some kind of PSR fail. Please try passing i915.enable_psr=0 to the kernel cmdline. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826125 Title: Dell XPS 13 9380 flickering (Whiskey Lake) Status in Linux: Incomplete Status in linux package in Ubuntu: Confirmed Bug description: A brand new Dell XPS 13 9380 preinstalled with Ubuntu 18.04 flickers to the point of being totally unusable. I have upgraded since to 18.10 and 19.04 with no changes. I have tried several combinations of the i915 parameters fastboot, enable_rc6 and enable_fbc to no avail. Examples of flickering are here: https://photos.app.goo.gl/1PkL2HrjMBP41aML9 https://photos.app.goo.gl/CMzmMwrCPH5wh8aw6 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1430 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-20180608-47+italia-whl+X31 DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-13 (10 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 9380 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1035-oem root=UUID=252898e9-6e96-4705-a709-2db930b7c4c7 ro quiet splash i915.fastboot=1 i915.enable_rc6=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1035.40-oem 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-1035-oem N/A linux-backports-modules-4.15.0-1035-oem N/A linux-firmware 1.178 Tags: disco Uname: Linux 4.15.0-1035-oem x86_64 UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 02/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/14/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1826125/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826125]
Created attachment 144318 Timo rc5+ kernel 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/1826125 Title: Dell XPS 13 9380 flickering (Whiskey Lake) Status in Linux: Incomplete Status in linux package in Ubuntu: Confirmed Bug description: A brand new Dell XPS 13 9380 preinstalled with Ubuntu 18.04 flickers to the point of being totally unusable. I have upgraded since to 18.10 and 19.04 with no changes. I have tried several combinations of the i915 parameters fastboot, enable_rc6 and enable_fbc to no avail. Examples of flickering are here: https://photos.app.goo.gl/1PkL2HrjMBP41aML9 https://photos.app.goo.gl/CMzmMwrCPH5wh8aw6 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1430 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-20180608-47+italia-whl+X31 DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-13 (10 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 9380 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1035-oem root=UUID=252898e9-6e96-4705-a709-2db930b7c4c7 ro quiet splash i915.fastboot=1 i915.enable_rc6=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1035.40-oem 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-1035-oem N/A linux-backports-modules-4.15.0-1035-oem N/A linux-firmware 1.178 Tags: disco Uname: Linux 4.15.0-1035-oem x86_64 UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 02/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/14/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1826125/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829652] Re: Kernel panic upon resetting ixgbe SR-IOV VFIO virtual function using 5.0 kernel
** Changed in: linux (Ubuntu) Assignee: (unassigned) => dann frazier (dannf) ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Assignee: dann frazier (dannf) Status: Confirmed ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Disco) Status: New => In Progress ** Changed in: linux (Ubuntu Eoan) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829652 Title: Kernel panic upon resetting ixgbe SR-IOV VFIO virtual function using 5.0 kernel Status in linux package in Ubuntu: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: In Progress Bug description: Hi, I've recently upgraded my system to ubuntu 19.04, and kernel consistently panics when I boot a virtual machine using an SR-IOV VFIO virtual function. Could reproduce with 5.0.0-13-generic and 5.0.0-15-generic, doesn't happen with 4.18.0-20-generic. I'm using libvirt and VM is using KVM, XML snippet to delegate virtual function to VM is: As soon as I start the VM using "virsh start vm", kernel panics. I'm using X550T intel NIC (lspci output: Ethernet controller: Intel Corporation Ethernet Controller 10G X550T (rev 01)) on a Supermicro X11SSH-CTF motherboard, with up to date bios and 4 virtual functions (class/net/em1/device/sriov_numvfs = 4). Given panic stack trace (see attachment), I've narrowed down the bug to ixgbe_ipsec_vf_clear function in upstream ixgbe driver: https://github.com/torvalds/linux/blob/72cf0b07418a9c8349aa9137194b1ccba6e54a9d/drivers/net/ethernet/intel/ixgbe/ixgbe_ipsec.c#L840 When I comment its usage (https://github.com/torvalds/linux/blob/72cf0b07418a9c8349aa9137194b1ccba6e54a9d/drivers/net/ethernet/intel/ixgbe/ixgbe_sriov.c#L734), everything works as expected (I'm not using any ipsec feature). Didn't try to fix the ixgbe_ipsec_vf_clear function though. Please find attached a stack trace collected using IPMI serial-over- lan. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829652/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829187] Re: linux-raspi2: 4.15.0-1037.39 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-certification-testing Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1829219 phase: Testing phase-changed: Tuesday, 21. May 2019 17:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-beta: 'Pending -- snap pi-kernel not in expected channel(s): arch=armhf:channel=18-cm3/beta:rev=34 - arch=armhf:channel=18-pi2/beta:rev=34' - snap-release-to-edge: 'Pending -- snap pi-kernel not in expected channel(s): arch=armhf:channel=18-cm3/edge:rev=34 - arch=armhf:channel=18-pi2/edge:rev=34' + snap-certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress -- 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/1829187 Title: linux-raspi2: 4.15.0-1037.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Confirmed Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1829219 phase: Testing phase-changed: Tuesday, 21. May 2019 17:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829187/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828187] Re: ibm, dynamic-memory property not found while loading kexec kernel (4.18.0-18-generic)
The attachment "kexec-tools_2.0.16-1ubuntu3.1.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1828187 Title: ibm,dynamic-memory property not found while loading kexec kernel (4.18.0-18-generic) Status in The Ubuntu-power-systems project: In Progress Status in kexec-tools package in Ubuntu: In Progress Bug description: For SRU: [Impact] * The ibm,dynamic-memory-v2 device tree property replaced the original ibm,dynamic-memory property. Since kexec-tools doesn't know to look for the "-v2" property yet, it fails to successfully parse the node using the new "-v2" property. * These changes enable the new "-v2" property to be successfully parsed from the node. [Test Case] * Load panic kernel or regular kernel with kexec command: kdump-config unload; kdump-config load OR kexec -l --append="`cat /proc/cmdline`" --initrd=/boot/initrd.img-`uname -r` /boot/vmlinux-`uname -r` * Expected result: kexec loads without any warning/error messages [Testing] These changes were tested by Hari with a positive result on a 4.18 kernel for ppc64el. [Regression Potential] * Low. * These changes exist in 'kexec-tools' for disco and onwards (these kernels are all >= 4.16 where the -v2 property was enabled). * The Bionic edge and Cosmic kernels have support for the -v2 property since they are also >= 4.16. * The regular 4.15 Bionic kernel is the more interesting of the bunch in terms of regression potential since 4.15 is too early to have the -v2 property enabled. The changes introduced by this patch appear to only attempt "-v2" parsing if it was unable to parse the "-v1" node. The absence of the v1 node implies that the device tree is using the "v2" property. Since the "-v2" option is not enabled for the 4.15 kernel, if the "-v1" parsing fails, then the "-v2" parsing will certainly fail, and the code throws the same error condition is it did before the patch was applied anyway. Original bug description below. --- == Comment: #0 - Hari Krishna Bathini - 2019-05-07 13:37:51 == ---Problem Description--- On 4.18.0-18-generic kernel, kexec load command throws below traces: --- Regular kexec load: root@ubuntu:~# kexec -l --append="`cat /proc/cmdline`" --initrd=/boot/initrd.img-`uname -r` /boot/vmlinux-`uname -r` /proc/device-tree/ibm,dynamic-reconfiguration-memory/ibm,dynamic-memory: No such file or directory Modified cmdline:BOOT_IMAGE=/boot/vmlinux-4.18.0-18-generic root=UUID=1aa9458c-3974-4cb4-9ab3-9ee03c0f4e5e ro crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M root@ubuntu:~# --- KDump kernel load: root@ubuntu:~# kdump-config unload * unloaded kdump kernel root@ubuntu:~# kdump-config load * Creating symlink /var/lib/kdump/vmlinuz * Creating symlink /var/lib/kdump/initrd.img /proc/device-tree/ibm,dynamic-reconfiguration-memory/ibm,dynamic-memory: No such file or directory /proc/device-tree/ibm,dynamic-reconfiguration-memory/ibm,dynamic-memory: No such file or directory Modified cmdline:BOOT_IMAGE=/boot/vmlinux-4.18.0-18-generic root=UUID=1aa9458c-3974-4cb4-9ab3-9ee03c0f4e5e ro maxcpus=1 systemd.unit=kdump-tools-dump.service irqpoll noirqdistrib nousb elfcorehdr=158912K * loaded kdump kernel root@ubuntu:~# --- Contact Information = hbath...@in.ibm.com ---uname output--- Linux ubuntu 4.18.0-18-generic #19~18.04.1-Ubuntu SMP Fri Apr 5 10:21:11 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux ---Additional Hardware Info--- na Machine Type = na ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Load panic kernel or regular kernel with kexec command: kdump-config unload; kdump-config load OR kexec -l --append="`cat /proc/cmdline`" --initrd=/boot/initrd.img-`uname -r` /boot/vmlinux-`uname -r` Actual Result: DT files are not found while loading the kernel Expected result: kexec loads without any warning/error messages Userspace tool common name: kexec-tools The userspace tool has the following bit modes: 64-bit Userspace rpm: kexec-tools Userspace tool obtained from project website: na *Additional Instructions for hbath...@in.ibm.com: -Attach ltrace and strace of userspace application. == Comment: #1 - Hari Krishna Bathini - 2019-05-07 13:44:25 == Since v4.16 kernel, ibm,dynamic-memory-v2 Device
[Kernel-packages] [Bug 1829177] Re: linux-aws: 4.18.0-1017.19 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829176 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1829186 phase: Testing phase-changed: Friday, 17. May 2019 18:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress - regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- 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/1829177 Title: linux-aws: 4.18.0-1017.19 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829176 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1829186 phase: Testing phase-changed: Friday, 17. May 2019 18:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829177] Re: linux-aws: 4.18.0-1017.19 -proposed tracker
kernel bugs: amd64 ubuntu_kvm_unit_tests: (1821390): apic-split will fail in kvm_units_tests, (1821394): vmx tests fail in kvm_unit_tests, (1822308) vmx_hlt_with_rvi_test in kvm_unit_tests fails ubuntu_ltp_syscalls: (1819116): sync_file_range02 in ubuntu_ltp_syscalls fails C/D arm64 ubuntu_ltp_syscalls: (1819116): sync_file_range02 in ubuntu_ltp_syscalls fails C/D ubuntu_kernel_selftests:(1830016): run_netsocktests from net in ubuntu_kernel_selftests failed with Socket type not supported ** Tags added: regression-testing-passed -- 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/1829177 Title: linux-aws: 4.18.0-1017.19 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829176 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1829186 phase: Testing phase-changed: Friday, 17. May 2019 18:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
You might be experiencing an issue caused by the way Windows handles powering off the sound card. Restarting from Windows yields a non- functioning sound card in Linux. A full shutdown from Windows and subsequent power-on will allow sound to work in Linux. This bug report is for the UX391UA and has been confirmed as fixed - please open a new report specific to your issue if required. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821152] Re: lxc-test-no-new-privs failed with Temporary failure resolving 'archive.ubuntu.com'
** Also affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-aws (Ubuntu) -- 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/1821152 Title: lxc-test-no-new-privs failed with Temporary failure resolving 'archive.ubuntu.com' Status in ubuntu-kernel-tests: New Status in linux-azure package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Bug description: It seems this failure only exist in KVM instances. FAIL: lxc-tests: lxc-test-no-new-privs (37s) --- + DONE=0 + trap cleanup EXIT SIGHUP SIGINT SIGTERM + mkdir -p /etc/lxc/ + cat + ARCH=i386 + type dpkg ++ dpkg --print-architecture + ARCH=amd64 + lxc-create -t download -n c1 -- -d ubuntu -r xenial -a amd64 Setting up the GPG keyring Downloading the image index Downloading the rootfs Downloading the metadata The image cache is now ready Unpacking the rootfs --- You just created an Ubuntu xenial amd64 (20190320_07:42) container. To enable SSH, run: apt install openssh-server No default root or user password are set by LXC. + echo 'lxc.no_new_privs = 1' + lxc-start -n c1 ++ lxc-info -n c1 -p -H + p1=8818 + '[' 8818 '!=' -1 ']' + sleep 5s + lxc-attach -n c1 --clear-env -- apt update -y WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Err:1 http://archive.ubuntu.com/ubuntu xenial InRelease Temporary failure resolving 'archive.ubuntu.com' Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease Temporary failure resolving 'security.ubuntu.com' Err:3 http://archive.ubuntu.com/ubuntu xenial-updates InRelease Temporary failure resolving 'archive.ubuntu.com' Reading package lists... Building dependency tree... Reading state information... All packages are up to date. W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial/InRelease Temporary failure resolving 'archive.ubuntu.com' W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease Temporary failure resolving 'archive.ubuntu.com' W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease Temporary failure resolving 'security.ubuntu.com' W: Some index files failed to download. They have been ignored, or old ones used instead. + lxc-attach -n c1 --clear-env -- apt install -y gcc make WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Reading package lists... Building dependency tree... Reading state information... The following additional packages will be installed: binutils cpp cpp-5 gcc-5 libasan2 libatomic1 libc-dev-bin libc6-dev libcc1-0 libcilkrts5 libgcc-5-dev libgomp1 libisl15 libitm1 liblsan0 libmpc3 libmpfr4 libmpx0 libquadmath0 libtsan0 libubsan0 linux-libc-dev manpages manpages-dev Suggested packages: binutils-doc cpp-doc gcc-5-locales gcc-multilib autoconf automake libtool flex bison gdb gcc-doc gcc-5-multilib gcc-5-doc libgcc1-dbg libgomp1-dbg libitm1-dbg libatomic1-dbg libasan2-dbg liblsan0-dbg libtsan0-dbg libubsan0-dbg libcilkrts5-dbg libmpx0-dbg libquadmath0-dbg glibc-doc make-doc man-browser The following NEW packages will be installed: binutils cpp cpp-5 gcc gcc-5 libasan2 libatomic1 libc-dev-bin libc6-dev libcc1-0 libcilkrts5 libgcc-5-dev libgomp1 libisl15 libitm1 liblsan0 libmpc3 libmpfr4 libmpx0 libquadmath0 libtsan0 libubsan0 linux-libc-dev make manpages manpages-dev 0 upgraded, 26 newly installed, 0 to remove and 0 not upgraded. Need to get 28.7 MB of archives. After this operation, 102 MB of additional disk space will be used. Err:1 http://archive.ubuntu.com/ubuntu xenial/main amd64 libmpfr4 amd64 3.1.4-1 Temporary failure resolving 'archive.ubuntu.com' Err:2 http://archive.ubuntu.com/ubuntu xenial/main amd64 libmpc3 amd64 1.0.3-1 Temporary failure resolving 'archive.ubuntu.com' Err:3 http://archive.ubuntu.com/ubuntu xenial/main amd64 manpages all 4.04-2 Temporary failure resolving 'archive.ubuntu.com' Err:4 http://security.ubuntu.com/ubuntu xenial-security/main amd64 binutils amd64 2.26.1-1ubuntu1~16.04.8 Temporary failure resolving 'archive.ubuntu.com' Err:5 http://archive.ubuntu.com/ubuntu xenial/main amd64 libisl15 amd64 0.16.1-1 Temporary failure resolving 'archive.ubuntu.com' It's a bit weird that if I run the command manually, it looks OK lxc-create -t download -n c1 -- -d ubuntu -r xenial -a amd64 lxc-start -n c1 lxc-attach -n c1 --clear-env -- apt update -y Hit:1 http://archive.ubuntu.com/ubuntu xenial InRelease Get:2 http://archive.ubuntu.com/ubuntu xenial-updates
[Kernel-packages] [Bug 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security
Also, I'm still able to boot any kernel (with no extra boot params) when I force-downgrade the intel-microcode to 2018 version (from bionic/main) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829620 Title: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: Description: - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of booting, after grub) - does not even show the enter cryptsetup passphrase - affected kernels: # apt list --installed |grep linux-signed WARNING: apt does not have a stable CLI interface. Use with caution in scripts. linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 [installed] linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 4.18.0.20.70 amd64 [installed] linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 5.0.0.15.71 amd64 [installed] - the setup is not new, has been working perfectly before (about 7 days since my last restart?) System: - HW: ASUS Zenbook 14 UX433FN - Ubuntu 18.04, runing latest HWE, fully updated - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup), Suspected/possible cause?: - recent intel-microcode package update - recent kernel package updates Steps taken: - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding nosplash, noplymouth) - completely removed nvidia drivers (apt purge *nvidia*) - completely purged and reinstalled grub (grup-pc) - completely purged and reinstalled all kernels (headers, modules, image, ..) - toggle BIOS "fastboot" (now using OFF) - toggle UEFI SecureBoot (now using ON) - remove plymouth (apt remove *plymouth* , but the workaround is working with plymouth installed) Workaround: - so far, I'm only able to boot with non-Ubuntu kernel! (linux-image-liquorix-amd64) - which needs "splash" option ON - reinstall cryptsetup & update-grub (as suggested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620/comments/10 ) I am not sure how to get you more debug info, as this setup has been working before, and it's a very eary boot-process bug, so I can't even access dmesg etc. EDIT: Hypothesis: Only affects ASUS with i7-8565U Whiskey Lake Intel CPU Upstream Bug Report: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1 WORKAROUND 1: disable intel microcode updates during boot From this bug: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920 1/ add the boot parameter: dis_ucode_ldr to /etc/default/grub 2/ update-grub WORKAROUND 2: downgrade (and hold) intel-microcode to older version from bionic/main apt install --reinstall intel-microcode=3.20180312.0~ubuntu18.04.1 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2337 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge (not installed) Tags: bionic wayland-session Uname: Linux 5.0.0-17.1-liquorix-amd64 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo vboxusers video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2339 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6 Tags: third-party-packages bionic wayland-session Uname: Linux 5.0.0-15-generic x86_64 UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1829620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security
> https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0.17/ so I have tested with a kernel from this PPA and it did not help. Tyler, there's one strange thing I'd like to ask: the boot process behaves stateful(?!), ie. I can get into a previous "clean"/"dirty" state (and at least liquorix) kernel then boots differently. 1. make the kernel get stuck, eg. run ubuntu 4.15 (-dis_ucode_ldr) -> "dirty". reboot (I have to hard power off). 2. Boot liquorix kernel (-dis_ucode_ldr, +mds=off) -> stuck! 3. make kernel pass once successfully. eg boot liquorix (+dis_ucode_ldr) -> i get to cryptsetup asking for passwd in intrd (it's not enough to reboot at this stage), need to fill in and boot to desktop. -> "clean". Reboot. 4. now repeat step 2, and I get to boot?! How is 2 vs. 4 possible? Where is the info stored? 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/1829620 Title: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: Description: - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of booting, after grub) - does not even show the enter cryptsetup passphrase - affected kernels: # apt list --installed |grep linux-signed WARNING: apt does not have a stable CLI interface. Use with caution in scripts. linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 [installed] linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 4.18.0.20.70 amd64 [installed] linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 5.0.0.15.71 amd64 [installed] - the setup is not new, has been working perfectly before (about 7 days since my last restart?) System: - HW: ASUS Zenbook 14 UX433FN - Ubuntu 18.04, runing latest HWE, fully updated - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup), Suspected/possible cause?: - recent intel-microcode package update - recent kernel package updates Steps taken: - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding nosplash, noplymouth) - completely removed nvidia drivers (apt purge *nvidia*) - completely purged and reinstalled grub (grup-pc) - completely purged and reinstalled all kernels (headers, modules, image, ..) - toggle BIOS "fastboot" (now using OFF) - toggle UEFI SecureBoot (now using ON) - remove plymouth (apt remove *plymouth* , but the workaround is working with plymouth installed) Workaround: - so far, I'm only able to boot with non-Ubuntu kernel! (linux-image-liquorix-amd64) - which needs "splash" option ON - reinstall cryptsetup & update-grub (as suggested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620/comments/10 ) I am not sure how to get you more debug info, as this setup has been working before, and it's a very eary boot-process bug, so I can't even access dmesg etc. EDIT: Hypothesis: Only affects ASUS with i7-8565U Whiskey Lake Intel CPU Upstream Bug Report: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1 WORKAROUND 1: disable intel microcode updates during boot From this bug: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920 1/ add the boot parameter: dis_ucode_ldr to /etc/default/grub 2/ update-grub WORKAROUND 2: downgrade (and hold) intel-microcode to older version from bionic/main apt install --reinstall intel-microcode=3.20180312.0~ubuntu18.04.1 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2337 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge (not installed) Tags: bionic wayland-session Uname: Linux 5.0.0-17.1-liquorix-amd64 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo vboxusers video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2339 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6 Tags: third-party-packages bionic wayland-session Uname: Linux 5.0.0-15-generic x86_64 UnreportableReason: Toto není
[Kernel-packages] [Bug 1830016] Re: run_netsocktests from net in ubuntu_kernel_selftests failed with Socket type not supported
affects cosmic, AWS cloud, 4.18.0-1017.19-aws ** Also affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-aws (Ubuntu Cosmic) Status: New => Incomplete ** Changed in: linux-aws (Ubuntu) Status: New => Confirmed ** Changed in: linux-aws (Ubuntu Cosmic) Status: Incomplete => Confirmed ** Tags added: arm64 ** Tags added: aws -- 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/1830016 Title: run_netsocktests from net in ubuntu_kernel_selftests failed with Socket type not supported Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Status in linux-aws source package in Cosmic: Confirmed Bug description: After fixing 1825777, the run_netsocktests is failing correctly, it's failing with: running socket test socket(44, 0, 0) expected err (Address family not supported by protocol) got (Socket type not supported) [FAIL] ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-20-generic 4.18.0-20.21 ProcVersionSignature: User Name 4.18.0-20.21-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 09:45 seq crw-rw 1 root audio 116, 33 May 22 09:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.3 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 May 22 10:31:17 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro RelatedPackageVersions: linux-restricted-modules-4.18.0-20-generic N/A linux-backports-modules-4.18.0-20-generic N/A linux-firmware 1.175.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1830016/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829166] Re: linux-azure: 5.0.0-1007.7 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1829173 phase: Testing phase-changed: Monday, 20. May 2019 11:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress - regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- 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/1829166 Title: linux-azure: 5.0.0-1007.7 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1829173 phase: Testing phase-changed: Monday, 20. May 2019 11:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827944] Re: Kernel 5.1 is unsupported (and nvidia-418.56 error) [error: initialization of `vm_fault_t (*)(struct vm_fault *)' {aka `unsigned int (*)(struct vm_fault *)'} from i
Side note: the issue is fixed in nvidia-430.14
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1827944
Title:
Kernel 5.1 is unsupported (and nvidia-418.56 error) [error:
initialization of `vm_fault_t (*)(struct vm_fault *)' {aka `unsigned
int (*)(struct vm_fault *)'} from incompatible pointer type `int
(*)(struct vm_fault *)']
Status in dkms package in Ubuntu:
Opinion
Status in nvidia-graphics-drivers-418 package in Ubuntu:
Confirmed
Bug description:
Installing mainline v5.1 from https://kernel.ubuntu.com/~kernel-
ppa/mainline/v5.1/ , I get this error:
ERROR (dkms apport): kernel package linux-
headers-5.1.0-050100-generic is not supported
Also, building nvidia modules fail; I'm not sure it's
related/critical.
See attached file for both logs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1827944/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829166] Re: linux-azure: 5.0.0-1007.7 -proposed tracker
Testing Results: monotonic_time: (1774959): clock test in monotonic_time will fail on Azure Instances ubuntu_kernel_selftests: (1829812): ubuntu_kernel_selftests [net] ubuntu_bpf test case fails to build on disco, (1830084) :ubuntu_kernel_tests ftrace fails on disco, linux-azure ubuntu_kvm_unittests:1821394 : vmx tests fail in kvm_unit_tests ubuntu_ltp_syscalls:1819116: sync_file_range02 in ubuntu_ltp_syscalls fails C/D ubuntu_lxc:1821152:lxc-test-no-new-privs failed with Temporary failure resolving 'archive.ubuntu.com' ** Tags added: regression-testing-passed -- 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/1829166 Title: linux-azure: 5.0.0-1007.7 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1829173 phase: Testing phase-changed: Monday, 20. May 2019 11:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1063038] Re: Broadcom BCM57780 Cannot Connect at Gigabit Speed using tg3 module.
As per upstream in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063038/comments/27 the device is rate limited in firmware intentionally. Hence, while it is technically possible to override this from a firmware perspective (i.e. Acer+Broadcom would release a firmware update), from a linux project perspective, investigating and, if viable, implementing an override of said firmware rate limiting as it stands today would need to be done upstream. ** Changed in: linux (Ubuntu) Importance: Undecided => Wishlist ** Changed in: linux (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1063038 Title: Broadcom BCM57780 Cannot Connect at Gigabit Speed using tg3 module. Status in linux package in Ubuntu: Won't Fix Bug description: I've got a device with a Broadcom 57780 ethernet NIC. It uses the tg3.ko driver module. The problem is that this NIC cannot connect at gigabit (1000MBps) speed. In all cases connection works well at 100MBps. Following are the tests I've completed: - Cables tested with cable tester - Cables tested to work at gigabit speed with Realtek and Intel gigabit NICs. - All unmanaged switch ports tested at ggigabit speed with other NICs. - Tried to connect with NetworkManager enabled and disabled. - Tried both dhcp and static connections. - Tried to renegotiate connection with `ethtool -r` both with TSO enabled and disabled. - Tried 3.2.0-23-generic 3.5.0-15-generic3.5.0-17-generic 3.6.0-999-generic kernels from main, xorg-edgers and mainline repos. - Used 'tg3_debug=1' kernel option in grub with the following output: [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic root=UUID=eccabacd-efb2-45b4-b7a6-2f530d50afd3 ro rootflags=subvol=@ tg3_debug=1 i915_enable_rc6=7 i915_enable_fbc=1 lvds_downclock=1 [0.00] Kernel command line: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic root=UUID=eccabacd-efb2-45b4-b7a6-2f530d50afd3 ro rootflags=subvol=@ tg3_debug=1 i915_enable_rc6=7 i915_enable_fbc=1 lvds_downclock=1 [5.963136] tg3.c:v3.123 (March 21, 2012) [5.995781] tg3 mdio bus: probed [6.005583] tg3 :01:00.0: >eth0: Tigon3 [partno(BCM57780) rev 57780001] (PCI Express) MAC address dc:0e:a1:ac:38:d5 [6.005687] tg3 :01:00.0: >eth0: attached PHY driver [Broadcom BCM57780] (mii_bus:phy_addr=100:01) [6.005790] tg3 :01:00.0: >eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1] [6.005887] tg3 :01:00.0: >eth0: dma_rwctrl[7618] dma_mask[64-bit] [ 294.987653] tg3 :01:00.0: >irq 44 for MSI/MSI-X [ 295.893224] tg3 :01:00.0: >eth0: Link is down [ 309.887879] tg3 :01:00.0: >eth0: Link is up at 100 Mbps, full duplex [ 309.887886] tg3 :01:00.0: >eth0: Flow control is on for TX and on for RX Other distros' forums suggest loading broadcom.ko first; however, this module is no present. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lzane 2139 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd440 irq 43' Mixer name : 'Realtek ALC272X' Components : 'HDA:10ec0272,10250601,0011' Controls : 22 Simple ctrls : 11 DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=e3645816-84f7-43fe-91a8-28638a230826 InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120424) Lsusb: Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 04f2:b209 Chicony Electronics Co., Ltd MachineType: Acer Aspire 5733 Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic root=UUID=eccabacd-efb2-45b4-b7a6-2f530d50afd3 ro rootflags=subvol=@ tg3_debug=1 i915_enable_rc6=7 i915_enable_fbc=1 lvds_downclock=1 ProcVersionSignature: Ubuntu 3.5.0-17.26-generic 3.5.5 RelatedPackageVersions:
[Kernel-packages] [Bug 1063038] Re: Broadcom BCM57780 Cannot Connect at Gigabit Speed using tg3 module.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1063038 Title: Broadcom BCM57780 Cannot Connect at Gigabit Speed using tg3 module. Status in linux package in Ubuntu: Won't Fix Bug description: I've got a device with a Broadcom 57780 ethernet NIC. It uses the tg3.ko driver module. The problem is that this NIC cannot connect at gigabit (1000MBps) speed. In all cases connection works well at 100MBps. Following are the tests I've completed: - Cables tested with cable tester - Cables tested to work at gigabit speed with Realtek and Intel gigabit NICs. - All unmanaged switch ports tested at ggigabit speed with other NICs. - Tried to connect with NetworkManager enabled and disabled. - Tried both dhcp and static connections. - Tried to renegotiate connection with `ethtool -r` both with TSO enabled and disabled. - Tried 3.2.0-23-generic 3.5.0-15-generic3.5.0-17-generic 3.6.0-999-generic kernels from main, xorg-edgers and mainline repos. - Used 'tg3_debug=1' kernel option in grub with the following output: [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic root=UUID=eccabacd-efb2-45b4-b7a6-2f530d50afd3 ro rootflags=subvol=@ tg3_debug=1 i915_enable_rc6=7 i915_enable_fbc=1 lvds_downclock=1 [0.00] Kernel command line: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic root=UUID=eccabacd-efb2-45b4-b7a6-2f530d50afd3 ro rootflags=subvol=@ tg3_debug=1 i915_enable_rc6=7 i915_enable_fbc=1 lvds_downclock=1 [5.963136] tg3.c:v3.123 (March 21, 2012) [5.995781] tg3 mdio bus: probed [6.005583] tg3 :01:00.0: >eth0: Tigon3 [partno(BCM57780) rev 57780001] (PCI Express) MAC address dc:0e:a1:ac:38:d5 [6.005687] tg3 :01:00.0: >eth0: attached PHY driver [Broadcom BCM57780] (mii_bus:phy_addr=100:01) [6.005790] tg3 :01:00.0: >eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1] [6.005887] tg3 :01:00.0: >eth0: dma_rwctrl[7618] dma_mask[64-bit] [ 294.987653] tg3 :01:00.0: >irq 44 for MSI/MSI-X [ 295.893224] tg3 :01:00.0: >eth0: Link is down [ 309.887879] tg3 :01:00.0: >eth0: Link is up at 100 Mbps, full duplex [ 309.887886] tg3 :01:00.0: >eth0: Flow control is on for TX and on for RX Other distros' forums suggest loading broadcom.ko first; however, this module is no present. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lzane 2139 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd440 irq 43' Mixer name : 'Realtek ALC272X' Components : 'HDA:10ec0272,10250601,0011' Controls : 22 Simple ctrls : 11 DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=e3645816-84f7-43fe-91a8-28638a230826 InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120424) Lsusb: Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 04f2:b209 Chicony Electronics Co., Ltd MachineType: Acer Aspire 5733 Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic root=UUID=eccabacd-efb2-45b4-b7a6-2f530d50afd3 ro rootflags=subvol=@ tg3_debug=1 i915_enable_rc6=7 i915_enable_fbc=1 lvds_downclock=1 ProcVersionSignature: Ubuntu 3.5.0-17.26-generic 3.5.5 RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware1.94 Tags: precise Uname: Linux 3.5.0-17-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo dmi.bios.date:
[Kernel-packages] [Bug 1063038] Re: Broadcom BCM57780 Cannot Connect at Gigabit Speed using tg3 module.
** No longer affects: 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/1063038 Title: Broadcom BCM57780 Cannot Connect at Gigabit Speed using tg3 module. Status in linux package in Ubuntu: Won't Fix Bug description: I've got a device with a Broadcom 57780 ethernet NIC. It uses the tg3.ko driver module. The problem is that this NIC cannot connect at gigabit (1000MBps) speed. In all cases connection works well at 100MBps. Following are the tests I've completed: - Cables tested with cable tester - Cables tested to work at gigabit speed with Realtek and Intel gigabit NICs. - All unmanaged switch ports tested at ggigabit speed with other NICs. - Tried to connect with NetworkManager enabled and disabled. - Tried both dhcp and static connections. - Tried to renegotiate connection with `ethtool -r` both with TSO enabled and disabled. - Tried 3.2.0-23-generic 3.5.0-15-generic3.5.0-17-generic 3.6.0-999-generic kernels from main, xorg-edgers and mainline repos. - Used 'tg3_debug=1' kernel option in grub with the following output: [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic root=UUID=eccabacd-efb2-45b4-b7a6-2f530d50afd3 ro rootflags=subvol=@ tg3_debug=1 i915_enable_rc6=7 i915_enable_fbc=1 lvds_downclock=1 [0.00] Kernel command line: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic root=UUID=eccabacd-efb2-45b4-b7a6-2f530d50afd3 ro rootflags=subvol=@ tg3_debug=1 i915_enable_rc6=7 i915_enable_fbc=1 lvds_downclock=1 [5.963136] tg3.c:v3.123 (March 21, 2012) [5.995781] tg3 mdio bus: probed [6.005583] tg3 :01:00.0: >eth0: Tigon3 [partno(BCM57780) rev 57780001] (PCI Express) MAC address dc:0e:a1:ac:38:d5 [6.005687] tg3 :01:00.0: >eth0: attached PHY driver [Broadcom BCM57780] (mii_bus:phy_addr=100:01) [6.005790] tg3 :01:00.0: >eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1] [6.005887] tg3 :01:00.0: >eth0: dma_rwctrl[7618] dma_mask[64-bit] [ 294.987653] tg3 :01:00.0: >irq 44 for MSI/MSI-X [ 295.893224] tg3 :01:00.0: >eth0: Link is down [ 309.887879] tg3 :01:00.0: >eth0: Link is up at 100 Mbps, full duplex [ 309.887886] tg3 :01:00.0: >eth0: Flow control is on for TX and on for RX Other distros' forums suggest loading broadcom.ko first; however, this module is no present. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lzane 2139 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd440 irq 43' Mixer name : 'Realtek ALC272X' Components : 'HDA:10ec0272,10250601,0011' Controls : 22 Simple ctrls : 11 DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=e3645816-84f7-43fe-91a8-28638a230826 InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120424) Lsusb: Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 04f2:b209 Chicony Electronics Co., Ltd MachineType: Acer Aspire 5733 Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic root=UUID=eccabacd-efb2-45b4-b7a6-2f530d50afd3 ro rootflags=subvol=@ tg3_debug=1 i915_enable_rc6=7 i915_enable_fbc=1 lvds_downclock=1 ProcVersionSignature: Ubuntu 3.5.0-17.26-generic 3.5.5 RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware1.94 Tags: precise Uname: Linux 3.5.0-17-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo dmi.bios.date: 11/07/2011 dmi.bios.vendor: Acer dmi.bios.version: V1.07 dmi.board.asset.tag: Base Board
[Kernel-packages] [Bug 1063038] Re: Broadcom BCM57780 Cannot Connect at Gigabit Speed using tg3 module.
** Project changed: linux => linux (Ubuntu) ** Changed in: linux (Ubuntu) Remote watch: Email to netdev@vger # => None -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1063038 Title: Broadcom BCM57780 Cannot Connect at Gigabit Speed using tg3 module. Status in linux package in Ubuntu: Won't Fix Bug description: I've got a device with a Broadcom 57780 ethernet NIC. It uses the tg3.ko driver module. The problem is that this NIC cannot connect at gigabit (1000MBps) speed. In all cases connection works well at 100MBps. Following are the tests I've completed: - Cables tested with cable tester - Cables tested to work at gigabit speed with Realtek and Intel gigabit NICs. - All unmanaged switch ports tested at ggigabit speed with other NICs. - Tried to connect with NetworkManager enabled and disabled. - Tried both dhcp and static connections. - Tried to renegotiate connection with `ethtool -r` both with TSO enabled and disabled. - Tried 3.2.0-23-generic 3.5.0-15-generic3.5.0-17-generic 3.6.0-999-generic kernels from main, xorg-edgers and mainline repos. - Used 'tg3_debug=1' kernel option in grub with the following output: [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic root=UUID=eccabacd-efb2-45b4-b7a6-2f530d50afd3 ro rootflags=subvol=@ tg3_debug=1 i915_enable_rc6=7 i915_enable_fbc=1 lvds_downclock=1 [0.00] Kernel command line: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic root=UUID=eccabacd-efb2-45b4-b7a6-2f530d50afd3 ro rootflags=subvol=@ tg3_debug=1 i915_enable_rc6=7 i915_enable_fbc=1 lvds_downclock=1 [5.963136] tg3.c:v3.123 (March 21, 2012) [5.995781] tg3 mdio bus: probed [6.005583] tg3 :01:00.0: >eth0: Tigon3 [partno(BCM57780) rev 57780001] (PCI Express) MAC address dc:0e:a1:ac:38:d5 [6.005687] tg3 :01:00.0: >eth0: attached PHY driver [Broadcom BCM57780] (mii_bus:phy_addr=100:01) [6.005790] tg3 :01:00.0: >eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1] [6.005887] tg3 :01:00.0: >eth0: dma_rwctrl[7618] dma_mask[64-bit] [ 294.987653] tg3 :01:00.0: >irq 44 for MSI/MSI-X [ 295.893224] tg3 :01:00.0: >eth0: Link is down [ 309.887879] tg3 :01:00.0: >eth0: Link is up at 100 Mbps, full duplex [ 309.887886] tg3 :01:00.0: >eth0: Flow control is on for TX and on for RX Other distros' forums suggest loading broadcom.ko first; however, this module is no present. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lzane 2139 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd440 irq 43' Mixer name : 'Realtek ALC272X' Components : 'HDA:10ec0272,10250601,0011' Controls : 22 Simple ctrls : 11 DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=e3645816-84f7-43fe-91a8-28638a230826 InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120424) Lsusb: Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 04f2:b209 Chicony Electronics Co., Ltd MachineType: Acer Aspire 5733 Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic root=UUID=eccabacd-efb2-45b4-b7a6-2f530d50afd3 ro rootflags=subvol=@ tg3_debug=1 i915_enable_rc6=7 i915_enable_fbc=1 lvds_downclock=1 ProcVersionSignature: Ubuntu 3.5.0-17.26-generic 3.5.5 RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware1.94 Tags: precise Uname: Linux 3.5.0-17-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo dmi.bios.date: 11/07/2011
[Kernel-packages] [Bug 1821152] Re: lxc-test-no-new-privs failed with Temporary failure resolving 'archive.ubuntu.com'
affects linux-azure 5.0.0-1007.7 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1821152 Title: lxc-test-no-new-privs failed with Temporary failure resolving 'archive.ubuntu.com' Status in ubuntu-kernel-tests: New Status in linux-azure package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Bug description: It seems this failure only exist in KVM instances. FAIL: lxc-tests: lxc-test-no-new-privs (37s) --- + DONE=0 + trap cleanup EXIT SIGHUP SIGINT SIGTERM + mkdir -p /etc/lxc/ + cat + ARCH=i386 + type dpkg ++ dpkg --print-architecture + ARCH=amd64 + lxc-create -t download -n c1 -- -d ubuntu -r xenial -a amd64 Setting up the GPG keyring Downloading the image index Downloading the rootfs Downloading the metadata The image cache is now ready Unpacking the rootfs --- You just created an Ubuntu xenial amd64 (20190320_07:42) container. To enable SSH, run: apt install openssh-server No default root or user password are set by LXC. + echo 'lxc.no_new_privs = 1' + lxc-start -n c1 ++ lxc-info -n c1 -p -H + p1=8818 + '[' 8818 '!=' -1 ']' + sleep 5s + lxc-attach -n c1 --clear-env -- apt update -y WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Err:1 http://archive.ubuntu.com/ubuntu xenial InRelease Temporary failure resolving 'archive.ubuntu.com' Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease Temporary failure resolving 'security.ubuntu.com' Err:3 http://archive.ubuntu.com/ubuntu xenial-updates InRelease Temporary failure resolving 'archive.ubuntu.com' Reading package lists... Building dependency tree... Reading state information... All packages are up to date. W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial/InRelease Temporary failure resolving 'archive.ubuntu.com' W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease Temporary failure resolving 'archive.ubuntu.com' W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease Temporary failure resolving 'security.ubuntu.com' W: Some index files failed to download. They have been ignored, or old ones used instead. + lxc-attach -n c1 --clear-env -- apt install -y gcc make WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Reading package lists... Building dependency tree... Reading state information... The following additional packages will be installed: binutils cpp cpp-5 gcc-5 libasan2 libatomic1 libc-dev-bin libc6-dev libcc1-0 libcilkrts5 libgcc-5-dev libgomp1 libisl15 libitm1 liblsan0 libmpc3 libmpfr4 libmpx0 libquadmath0 libtsan0 libubsan0 linux-libc-dev manpages manpages-dev Suggested packages: binutils-doc cpp-doc gcc-5-locales gcc-multilib autoconf automake libtool flex bison gdb gcc-doc gcc-5-multilib gcc-5-doc libgcc1-dbg libgomp1-dbg libitm1-dbg libatomic1-dbg libasan2-dbg liblsan0-dbg libtsan0-dbg libubsan0-dbg libcilkrts5-dbg libmpx0-dbg libquadmath0-dbg glibc-doc make-doc man-browser The following NEW packages will be installed: binutils cpp cpp-5 gcc gcc-5 libasan2 libatomic1 libc-dev-bin libc6-dev libcc1-0 libcilkrts5 libgcc-5-dev libgomp1 libisl15 libitm1 liblsan0 libmpc3 libmpfr4 libmpx0 libquadmath0 libtsan0 libubsan0 linux-libc-dev make manpages manpages-dev 0 upgraded, 26 newly installed, 0 to remove and 0 not upgraded. Need to get 28.7 MB of archives. After this operation, 102 MB of additional disk space will be used. Err:1 http://archive.ubuntu.com/ubuntu xenial/main amd64 libmpfr4 amd64 3.1.4-1 Temporary failure resolving 'archive.ubuntu.com' Err:2 http://archive.ubuntu.com/ubuntu xenial/main amd64 libmpc3 amd64 1.0.3-1 Temporary failure resolving 'archive.ubuntu.com' Err:3 http://archive.ubuntu.com/ubuntu xenial/main amd64 manpages all 4.04-2 Temporary failure resolving 'archive.ubuntu.com' Err:4 http://security.ubuntu.com/ubuntu xenial-security/main amd64 binutils amd64 2.26.1-1ubuntu1~16.04.8 Temporary failure resolving 'archive.ubuntu.com' Err:5 http://archive.ubuntu.com/ubuntu xenial/main amd64 libisl15 amd64 0.16.1-1 Temporary failure resolving 'archive.ubuntu.com' It's a bit weird that if I run the command manually, it looks OK lxc-create -t download -n c1 -- -d ubuntu -r xenial -a amd64 lxc-start -n c1 lxc-attach -n c1 --clear-env -- apt update -y Hit:1 http://archive.ubuntu.com/ubuntu xenial InRelease Get:2 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [109 kB] Get:3 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
[Kernel-packages] [Bug 1063038] [NEW] Broadcom BCM57780 Cannot Connect at Gigabit Speed using tg3 module.
You have been subscribed to a public bug: I've got a device with a Broadcom 57780 ethernet NIC. It uses the tg3.ko driver module. The problem is that this NIC cannot connect at gigabit (1000MBps) speed. In all cases connection works well at 100MBps. Following are the tests I've completed: - Cables tested with cable tester - Cables tested to work at gigabit speed with Realtek and Intel gigabit NICs. - All unmanaged switch ports tested at ggigabit speed with other NICs. - Tried to connect with NetworkManager enabled and disabled. - Tried both dhcp and static connections. - Tried to renegotiate connection with `ethtool -r` both with TSO enabled and disabled. - Tried 3.2.0-23-generic 3.5.0-15-generic3.5.0-17-generic 3.6.0-999-generic kernels from main, xorg-edgers and mainline repos. - Used 'tg3_debug=1' kernel option in grub with the following output: [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic root=UUID=eccabacd-efb2-45b4-b7a6-2f530d50afd3 ro rootflags=subvol=@ tg3_debug=1 i915_enable_rc6=7 i915_enable_fbc=1 lvds_downclock=1 [0.00] Kernel command line: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic root=UUID=eccabacd-efb2-45b4-b7a6-2f530d50afd3 ro rootflags=subvol=@ tg3_debug=1 i915_enable_rc6=7 i915_enable_fbc=1 lvds_downclock=1 [5.963136] tg3.c:v3.123 (March 21, 2012) [5.995781] tg3 mdio bus: probed [6.005583] tg3 :01:00.0: >eth0: Tigon3 [partno(BCM57780) rev 57780001] (PCI Express) MAC address dc:0e:a1:ac:38:d5 [6.005687] tg3 :01:00.0: >eth0: attached PHY driver [Broadcom BCM57780] (mii_bus:phy_addr=100:01) [6.005790] tg3 :01:00.0: >eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1] [6.005887] tg3 :01:00.0: >eth0: dma_rwctrl[7618] dma_mask[64-bit] [ 294.987653] tg3 :01:00.0: >irq 44 for MSI/MSI-X [ 295.893224] tg3 :01:00.0: >eth0: Link is down [ 309.887879] tg3 :01:00.0: >eth0: Link is up at 100 Mbps, full duplex [ 309.887886] tg3 :01:00.0: >eth0: Flow control is on for TX and on for RX Other distros' forums suggest loading broadcom.ko first; however, this module is no present. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lzane 2139 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd440 irq 43' Mixer name : 'Realtek ALC272X' Components : 'HDA:10ec0272,10250601,0011' Controls : 22 Simple ctrls : 11 DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=e3645816-84f7-43fe-91a8-28638a230826 InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120424) Lsusb: Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 04f2:b209 Chicony Electronics Co., Ltd MachineType: Acer Aspire 5733 Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic root=UUID=eccabacd-efb2-45b4-b7a6-2f530d50afd3 ro rootflags=subvol=@ tg3_debug=1 i915_enable_rc6=7 i915_enable_fbc=1 lvds_downclock=1 ProcVersionSignature: Ubuntu 3.5.0-17.26-generic 3.5.5 RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware1.94 Tags: precise Uname: Linux 3.5.0-17-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo dmi.bios.date: 11/07/2011 dmi.bios.vendor: Acer dmi.bios.version: V1.07 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Aspire 5733 dmi.board.vendor: Acer dmi.board.version: V1.07 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.07 dmi.modalias: dmi:bvnAcer:bvrV1.07:bd11/07/2011:svnAcer:pnAspire5733:pvrV1.07:rvnAcer:rnAspire5733:rvrV1.07:cvnAcer:ct10:cvrV1.07: dmi.product.name: Aspire 5733 dmi.product.version: V1.07 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags:
[Kernel-packages] [Bug 1824981] Re: cifs set_oplock buffer overflow in strcat
** Tags added: sts -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824981 Title: cifs set_oplock buffer overflow in strcat Status in linux package in Ubuntu: Fix Released Bug description: Ubuntu 18.04.2 LTS Linux SRV013 4.15.0-47-generic #50-Ubuntu SMP Wed Mar 13 10:44:52 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux DELL R740, 2 CPU (40 Cores, 80 Threads), 384 GiB RAM top - 12:39:53 up 3:41, 4 users, load average: 66.19, 64.06, 76.90 Tasks: 1076 total, 1 running, 675 sleeping, 12 stopped, 1 zombie %Cpu(s): 28.2 us, 0.3 sy, 0.0 ni, 71.5 id, 0.0 wa, 0.0 hi, 0.1 si, 0.0 st KiB Mem : 39483801+total, 24077185+free, 57428284 used, 96637872 buff/cache KiB Swap: 999420 total, 999420 free,0 used. 33477683+avail Mem We've seen the following bug many times since we introduced new machines running Ubuntu 18. Wasn't an issue older machines running Ubuntu 16. Three different machines are affected, so it's rather not a hardware issue. | detected buffer overflow in strcat | [ cut here ] | kernel BUG at /build/linux-6ZmFRN/linux-4.15.0/lib/string.c:1052! | invalid opcode: [#1] SMP PTI | Modules linked in: [...] | Hardware name: Dell Inc. PowerEdge R740/0923K0, BIOS 1.6.11 11/20/2018 | RIP: 0010:fortify_panic+0x13/0x22 | [...] | Call Trace: | smb21_set_oplock_level+0x147/0x1a0 [cifs] | smb3_set_oplock_level+0x22/0x90 [cifs] | smb2_set_fid+0x76/0xb0 [cifs] | cifs_new_fileinfo+0x259/0x390 [cifs] | ? smb2_get_lease_key+0x40/0x40 [cifs] | ? cifs_new_fileinfo+0x259/0x390 [cifs] | cifs_open+0x3db/0x8d0 [cifs] | [...] (Full dmesg output attached) After hitting this bug there are many cifs related dmesg entries, processes lock up and eventually the systems freezes. The share is mounted using: //server/share /mnt/server/ cifs defaults,auto,iocharset=utf8,noperm,file_mode=0777,dir_mode=0777,credentials=/root/passwords/share,domain=myDomain,uid=myUser,gid=10513,mfsymlinks Currently we're testing the cifs mount options "cache=none" as the bug seems to be oplock related. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824981/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security
> or you've recently installed a BIOS update which contains the latest microcode revision and the kernel microcode loader didn't do anything. Asus published BIOS version 302 for your laptop on 2019-04-02 (https://www.asus.com/Laptops/ASUS-ZenBook-14-UX433FN/HelpDesk_BIOS/). I really have updated to BIOS v302 from Asus website. It is roughly around the time the problems started, but I *think* I have been able to boot with the new BIOS before. So probably some change in kernel/microcode in addition to that? > To summarize, maybe you've installed a BIOS update that includes the new microcode and that's allowing you to boot the liquorix kernel because it isn't doing a microcode load because of A) and/or B) above? yes. Both cases: (updated BIOS + liquorix kernel) or (dis_ucode_ldr + ubuntu kernel) work 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/1829620 Title: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: Description: - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of booting, after grub) - does not even show the enter cryptsetup passphrase - affected kernels: # apt list --installed |grep linux-signed WARNING: apt does not have a stable CLI interface. Use with caution in scripts. linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 [installed] linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 4.18.0.20.70 amd64 [installed] linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 5.0.0.15.71 amd64 [installed] - the setup is not new, has been working perfectly before (about 7 days since my last restart?) System: - HW: ASUS Zenbook 14 UX433FN - Ubuntu 18.04, runing latest HWE, fully updated - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup), Suspected/possible cause?: - recent intel-microcode package update - recent kernel package updates Steps taken: - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding nosplash, noplymouth) - completely removed nvidia drivers (apt purge *nvidia*) - completely purged and reinstalled grub (grup-pc) - completely purged and reinstalled all kernels (headers, modules, image, ..) - toggle BIOS "fastboot" (now using OFF) - toggle UEFI SecureBoot (now using ON) - remove plymouth (apt remove *plymouth* , but the workaround is working with plymouth installed) Workaround: - so far, I'm only able to boot with non-Ubuntu kernel! (linux-image-liquorix-amd64) - which needs "splash" option ON - reinstall cryptsetup & update-grub (as suggested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620/comments/10 ) I am not sure how to get you more debug info, as this setup has been working before, and it's a very eary boot-process bug, so I can't even access dmesg etc. EDIT: Hypothesis: Only affects ASUS with i7-8565U Whiskey Lake Intel CPU Upstream Bug Report: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1 WORKAROUND 1: disable intel microcode updates during boot From this bug: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920 1/ add the boot parameter: dis_ucode_ldr to /etc/default/grub 2/ update-grub WORKAROUND 2: downgrade (and hold) intel-microcode to older version from bionic/main apt install --reinstall intel-microcode=3.20180312.0~ubuntu18.04.1 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2337 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge (not installed) Tags: bionic wayland-session Uname: Linux 5.0.0-17.1-liquorix-amd64 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo vboxusers video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2339 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6 Tags: third-party-packages bionic wayland-session Uname: Linux 5.0.0-15-generic x86_64 UnreportableReason: Toto není oficiální KDE
[Kernel-packages] [Bug 1813936] Re: kernel BUG at /build/linux-A9GvNk/linux-4.15.0/lib/string.c:1052!
*** This bug is a duplicate of bug 1824981 *** https://bugs.launchpad.net/bugs/1824981 ** This bug is no longer a duplicate of bug 1813928 kernel BUG at /build/linux-A9GvNk/linux-4.15.0/lib/string.c:1052! ** This bug has been marked a duplicate of bug 1824981 cifs set_oplock buffer overflow in strcat -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813936 Title: kernel BUG at /build/linux-A9GvNk/linux-4.15.0/lib/string.c:1052! Status in linux package in Ubuntu: Confirmed Bug description: happend during normal operation in the background ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-39-generic 4.15.0-39.42 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: hnl1417 F...m pulseaudio /dev/snd/controlC0: hnl1417 F pulseaudio Date: Wed Jan 30 21:56:47 2019 Failure: oops HibernationDevice: RESUME=UUID=5835e245-0f6b-49d1-8d73-f7d80ed579cb InstallationDate: Installed on 2018-11-14 (76 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 23252F0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: kernel BUG at /build/linux-A9GvNk/linux-4.15.0/lib/string.c:1052! UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/25/2017 dmi.bios.vendor: LENOVO dmi.bios.version: G2ETB0WW (2.70 ) dmi.board.asset.tag: Not Available dmi.board.name: 23252F0 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: 100010263594 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ETB0WW(2.70):bd09/25/2017:svnLENOVO:pn23252F0:pvrThinkPadX230:rvnLENOVO:rn23252F0:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 23252F0 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813928] Re: kernel BUG at /build/linux-A9GvNk/linux-4.15.0/lib/string.c:1052!
*** This bug is a duplicate of bug 1824981 *** https://bugs.launchpad.net/bugs/1824981 This LP is a duplicate for #1824981 - I'll mark it as dup. Thanks, Guilherme ** Tags added: sts ** This bug has been marked a duplicate of bug 1824981 cifs set_oplock buffer overflow in strcat -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813928 Title: kernel BUG at /build/linux-A9GvNk/linux-4.15.0/lib/string.c:1052! Status in linux package in Ubuntu: Confirmed Bug description: just happened in the background ... no idea about the direct cause ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-39-generic 4.15.0-39.42 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: hnl1417 F...m pulseaudio /dev/snd/controlC0: hnl1417 F pulseaudio Date: Wed Jan 30 20:57:49 2019 Failure: oops HibernationDevice: RESUME=UUID=5835e245-0f6b-49d1-8d73-f7d80ed579cb InstallationDate: Installed on 2018-11-14 (76 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 23252F0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: kernel BUG at /build/linux-A9GvNk/linux-4.15.0/lib/string.c:1052! UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/25/2017 dmi.bios.vendor: LENOVO dmi.bios.version: G2ETB0WW (2.70 ) dmi.board.asset.tag: Not Available dmi.board.name: 23252F0 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: 100010263594 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ETB0WW(2.70):bd09/25/2017:svnLENOVO:pn23252F0:pvrThinkPadX230:rvnLENOVO:rn23252F0:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 23252F0 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813928/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security
On 2019-05-22 17:13:02, Mark wrote: > > This may be a bug in how the kernel is loading the microcode > > can you review the liquorix patches? Their kernel boots with said > microcode. I compared the arch/x86/ source code directories in the liquorix and Ubuntu kernels. While there are a large amount of differences, I didn't see anything that would cause a microcode loading behavior change. This has me wondering about a few things regarding your being able to boot the liquorix kernel in comment #41. A) 'dmesg | grep microcode' showed no output. This is confusing because the microcode loader should print information when it loads microcode unless it is disabled. Your /proc/cmdline doesn't show the dis_ucode_ldr kernel parameter being in use but the use of that option would prevent anything from being printed by the microcode loader. B) You have the latest microcode revision (0xb8) loaded according to /sys/devices/system/cpu/cpu0/microcode/version. That means that either the kernel microcode loader did load microcode or you've recently installed a BIOS update which contains the latest microcode revision and the kernel microcode loader didn't do anything. Asus published BIOS version 302 for your laptop on 2019-04-02 (https://www.asus.com/Laptops/ASUS-ZenBook-14-UX433FN/HelpDesk_BIOS/). It is has no release notes that I can find. The release date on the BIOS update comes after the date stamped in the microcode file (2019-03-30). That would be quite the turnaround time but it is technically possible that it contains revision 0xb8. To summarize, maybe you've installed a BIOS update that includes the new microcode and that's allowing you to boot the liquorix kernel because it isn't doing a microcode load because of A) and/or B) above? The upstream bug report has mentions of Arch, Fedora, Ubuntu, and upstream kernels all being affected by this bug. I'm skeptical that the liquorix kernel is doing microcode loading correctly, when nobody else is, which is why I'm trying to double check everything in comment #41. > Is there a PPA with vanilla kernel I should try? We have a mainline vanilla kernel builds of 5.0.17 here: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0.17/ Unfortunately, the 5.0.18 build, which would more closely resemble the liquorix kernel, isn't available yet. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829620 Title: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: Description: - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of booting, after grub) - does not even show the enter cryptsetup passphrase - affected kernels: # apt list --installed |grep linux-signed WARNING: apt does not have a stable CLI interface. Use with caution in scripts. linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 [installed] linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 4.18.0.20.70 amd64 [installed] linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 5.0.0.15.71 amd64 [installed] - the setup is not new, has been working perfectly before (about 7 days since my last restart?) System: - HW: ASUS Zenbook 14 UX433FN - Ubuntu 18.04, runing latest HWE, fully updated - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup), Suspected/possible cause?: - recent intel-microcode package update - recent kernel package updates Steps taken: - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding nosplash, noplymouth) - completely removed nvidia drivers (apt purge *nvidia*) - completely purged and reinstalled grub (grup-pc) - completely purged and reinstalled all kernels (headers, modules, image, ..) - toggle BIOS "fastboot" (now using OFF) - toggle UEFI SecureBoot (now using ON) - remove plymouth (apt remove *plymouth* , but the workaround is working with plymouth installed) Workaround: - so far, I'm only able to boot with non-Ubuntu kernel! (linux-image-liquorix-amd64) - which needs "splash" option ON - reinstall cryptsetup & update-grub (as suggested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620/comments/10 ) I am not sure how to get you more debug info, as this setup has been working before, and it's a very eary boot-process bug, so I can't even access dmesg etc. EDIT: Hypothesis: Only affects ASUS with i7-8565U Whiskey Lake Intel CPU Upstream Bug Report: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1
[Kernel-packages] [Bug 1063038] Re: Broadcom BCM57780 Cannot Connect at Gigabit Speed using tg3 module.
Please close. Does not reproduce on 19.04 ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1063038 Title: Broadcom BCM57780 Cannot Connect at Gigabit Speed using tg3 module. Status in Linux: New Status in linux package in Ubuntu: Invalid Bug description: I've got a device with a Broadcom 57780 ethernet NIC. It uses the tg3.ko driver module. The problem is that this NIC cannot connect at gigabit (1000MBps) speed. In all cases connection works well at 100MBps. Following are the tests I've completed: - Cables tested with cable tester - Cables tested to work at gigabit speed with Realtek and Intel gigabit NICs. - All unmanaged switch ports tested at ggigabit speed with other NICs. - Tried to connect with NetworkManager enabled and disabled. - Tried both dhcp and static connections. - Tried to renegotiate connection with `ethtool -r` both with TSO enabled and disabled. - Tried 3.2.0-23-generic 3.5.0-15-generic3.5.0-17-generic 3.6.0-999-generic kernels from main, xorg-edgers and mainline repos. - Used 'tg3_debug=1' kernel option in grub with the following output: [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic root=UUID=eccabacd-efb2-45b4-b7a6-2f530d50afd3 ro rootflags=subvol=@ tg3_debug=1 i915_enable_rc6=7 i915_enable_fbc=1 lvds_downclock=1 [0.00] Kernel command line: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic root=UUID=eccabacd-efb2-45b4-b7a6-2f530d50afd3 ro rootflags=subvol=@ tg3_debug=1 i915_enable_rc6=7 i915_enable_fbc=1 lvds_downclock=1 [5.963136] tg3.c:v3.123 (March 21, 2012) [5.995781] tg3 mdio bus: probed [6.005583] tg3 :01:00.0: >eth0: Tigon3 [partno(BCM57780) rev 57780001] (PCI Express) MAC address dc:0e:a1:ac:38:d5 [6.005687] tg3 :01:00.0: >eth0: attached PHY driver [Broadcom BCM57780] (mii_bus:phy_addr=100:01) [6.005790] tg3 :01:00.0: >eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1] [6.005887] tg3 :01:00.0: >eth0: dma_rwctrl[7618] dma_mask[64-bit] [ 294.987653] tg3 :01:00.0: >irq 44 for MSI/MSI-X [ 295.893224] tg3 :01:00.0: >eth0: Link is down [ 309.887879] tg3 :01:00.0: >eth0: Link is up at 100 Mbps, full duplex [ 309.887886] tg3 :01:00.0: >eth0: Flow control is on for TX and on for RX Other distros' forums suggest loading broadcom.ko first; however, this module is no present. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lzane 2139 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd440 irq 43' Mixer name : 'Realtek ALC272X' Components : 'HDA:10ec0272,10250601,0011' Controls : 22 Simple ctrls : 11 DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=e3645816-84f7-43fe-91a8-28638a230826 InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120424) Lsusb: Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 04f2:b209 Chicony Electronics Co., Ltd MachineType: Acer Aspire 5733 Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic root=UUID=eccabacd-efb2-45b4-b7a6-2f530d50afd3 ro rootflags=subvol=@ tg3_debug=1 i915_enable_rc6=7 i915_enable_fbc=1 lvds_downclock=1 ProcVersionSignature: Ubuntu 3.5.0-17.26-generic 3.5.5 RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware1.94 Tags: precise Uname: Linux 3.5.0-17-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo dmi.bios.date:
[Kernel-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
Update: the sound problem on UX430U is intermittent. Sometimes it works, sometimes it is gone. I haven't been able to see a clear pattern so far. This is definitely not a hardware problem since everything works rock solid under Windows (I have a dual boot). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
I have the same problem on Asus Zenbook UX430U. Upgrading to kernel 4.20.16 using ukuu did not fully solve the problem. It worked after the first boot, but no longer works after restarting. Should I open a separate 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827755] Re: nx842 - CRB request time out (-110) when uninstall NX modules and initiate NX request
Patch submitted for SRU: https://lists.ubuntu.com/archives/kernel-team/2019-May/100825.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827755 Title: nx842 - CRB request time out (-110) when uninstall NX modules and initiate NX request Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Bug description: [Impact] PowerPC 842 hardware compression support is currently broken, this effects workloads like zswap and others that exploit 842 hardware compression on Power. [Test] - Install nx-compress and nx-842-powernv modules - Initiate NX request - Uninstall these modules - Initiate NX request again and we get CRB timeout with error -110 Test kernel available in the PPA, please see comment #4 and please see comment #5 that verifies the PPA kernel works as expected. [Fix] IBM has identified that the following upstream patch fixes the issue: 656ecc16e8fc crypto/nx: Initialize 842 high and normal RxFIFO control registers [Regression Potential] The patch only impacts the nx-842 modules, only available on PowerPC architecture and does not have any impact on other architectures or generic code. Risk of regression is very low. [Other Info] ---Problem Description--- Normally nx-compress and nx-842-powernv modules are loaded when selects 842-nx compressor if not loaded and execute forever during system execution. So we will not see this bug in normal case. But we are seeing NX CRB request timeout when uninstall these modules and load them or select 842-nx compressor. ---uname output--- 18.04 Machine Type = P9 system ---Steps to Reproduce--- - Install nx-compress and nx-842-powernv modules - Initiate NX request - Uninstall these modules - Initiate NX request again and we get CRB timeout with error -110 Patches are included in 4.19-rc1 6e708000ec2c93c2bde6a46aa2d6c3e80d4eaeb9 - powerpc/powernv: Export opal_check_token symbol 656ecc16e8fc2ab44b3d70e3fcc197a7020d0ca5 - crypto/nx: Initialize 842 high and normal RxFIFO control registers > Looks like the first commit was included in a recent 18.04 update > (4.15.0-48.51), see > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819989 > > but I don't see the second one there yet. > > If this is still needed, I would suggest getting this bug mirrored to LP to > put on Canonical's radar. We need second commit (656ecc16e8fc2ab44b3d70e3fcc197a7020d0ca) to fix this actual issue. But no use of having the first commit without second one. The first one just exports opal_check_token symbol which is used in the second commit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1827755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829211] Re: linux-fips: 4.15.0-1008.9 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1829219 - phase: Holding before Promote to Proposed - phase-changed: Wednesday, 22. May 2019 13:42 UTC + phase: Ready for Promote to Proposed + phase-changed: Wednesday, 22. May 2019 17:07 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa main:building,signed:building,meta:failed + promote-to-proposed: Pending -- ready for review -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829211 Title: linux-fips: 4.15.0-1008.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1829219 phase: Ready for Promote to Proposed phase-changed: Wednesday, 22. May 2019 17:07 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829211/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security
> To avoid confusion, we need to be clear that the i7-8565U is a Whiskey Lake processor (*not* a Kaby Lake) yep, sorry, I got confused in the intel naming scheme, it's whiskey I'm having problems with ;) > This may be a bug in how the kernel is loading the microcode can you review the liquorix patches? Their kernel boots with said microcode. Is there a PPA with vanilla kernel I should try? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829620 Title: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: Description: - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of booting, after grub) - does not even show the enter cryptsetup passphrase - affected kernels: # apt list --installed |grep linux-signed WARNING: apt does not have a stable CLI interface. Use with caution in scripts. linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 [installed] linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 4.18.0.20.70 amd64 [installed] linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 5.0.0.15.71 amd64 [installed] - the setup is not new, has been working perfectly before (about 7 days since my last restart?) System: - HW: ASUS Zenbook 14 UX433FN - Ubuntu 18.04, runing latest HWE, fully updated - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup), Suspected/possible cause?: - recent intel-microcode package update - recent kernel package updates Steps taken: - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding nosplash, noplymouth) - completely removed nvidia drivers (apt purge *nvidia*) - completely purged and reinstalled grub (grup-pc) - completely purged and reinstalled all kernels (headers, modules, image, ..) - toggle BIOS "fastboot" (now using OFF) - toggle UEFI SecureBoot (now using ON) - remove plymouth (apt remove *plymouth* , but the workaround is working with plymouth installed) Workaround: - so far, I'm only able to boot with non-Ubuntu kernel! (linux-image-liquorix-amd64) - which needs "splash" option ON - reinstall cryptsetup & update-grub (as suggested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620/comments/10 ) I am not sure how to get you more debug info, as this setup has been working before, and it's a very eary boot-process bug, so I can't even access dmesg etc. EDIT: Hypothesis: Only affects ASUS with i7-8565U Whiskey Lake Intel CPU Upstream Bug Report: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1 WORKAROUND 1: disable intel microcode updates during boot From this bug: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920 1/ add the boot parameter: dis_ucode_ldr to /etc/default/grub 2/ update-grub WORKAROUND 2: downgrade (and hold) intel-microcode to older version from bionic/main apt install --reinstall intel-microcode=3.20180312.0~ubuntu18.04.1 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2337 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge (not installed) Tags: bionic wayland-session Uname: Linux 5.0.0-17.1-liquorix-amd64 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo vboxusers video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2339 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6 Tags: third-party-packages bionic wayland-session Uname: Linux 5.0.0-15-generic x86_64 UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1829620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1830090] Re: Cannot reach 1300Mbps using DW1830 (BCM943602BAED) with linux-firmware
Mai 22 15:01:29 kevin335200 kernel: brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43602-pcie.bin for chip 0x00aa52(43602) rev 0x01 Mai 22 15:01:29 kevin335200 kernel: brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt failed with error -2 Mai 22 15:01:31 kevin335200 kernel: brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Nov 10 2015 06:38:10 version 7.35.177.61 (r598657) FWID 01-ea662a8c Maybe the firmware version is too old? ** Description changed: I cannot reach 1300Mbps using DW1830 (BCM943602BAED) with linux-firmware, only 985Mbps maximum. - It works under win10. + It works fine under win10. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1830090 Title: Cannot reach 1300Mbps using DW1830 (BCM943602BAED) with linux-firmware Status in linux-firmware package in Ubuntu: New Bug description: I cannot reach 1300Mbps using DW1830 (BCM943602BAED) with linux-firmware, only 985Mbps maximum. It works fine under win10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1830090/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828187] Re: ibm, dynamic-memory property not found while loading kexec kernel (4.18.0-18-generic)
.debdiff attached to this comment for sponsorship consideration to Bionic. ** Patch added: "kexec-tools_2.0.16-1ubuntu1.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1828187/+attachment/5265778/+files/kexec-tools_2.0.16-1ubuntu1.1.debdiff ** Description changed: + For SRU: + + [Impact] + + * The ibm,dynamic-memory-v2 device tree property replaced the original + ibm,dynamic-memory property. Since kexec-tools doesn't know to look for + the "-v2" property yet, it fails to successfully parse the node using + the new "-v2" property. + + * These changes enable the new "-v2" property to be successfully parsed + from the node. + + [Test Case] + + * Load panic kernel or regular kernel with kexec command: + + kdump-config unload; kdump-config load + + OR + + kexec -l --append="`cat /proc/cmdline`" --initrd=/boot/initrd.img-`uname + -r` /boot/vmlinux-`uname -r` + + * Expected result: kexec loads without any warning/error messages + + [Testing] + + These changes were tested by Hari with a positive result on a 4.18 + kernel for ppc64el. + + [Regression Potential] + + * Low. + * These changes exist in 'kexec-tools' for disco and onwards (these kernels are all >= 4.16 where the -v2 property was enabled). + * The Bionic edge and Cosmic kernels have support for the -v2 property since they are also >= 4.16. + * The regular 4.15 Bionic kernel is the more interesting of the bunch in terms of regression potential since 4.15 is too early to have the -v2 property enabled. The changes introduced by this patch appear to only attempt "-v2" parsing if it was unable to parse the "-v1" node. The absence of the v1 node implies that the device tree is using the "v2" property. Since the "-v2" option is not enabled for the 4.15 kernel, if the "-v1" parsing fails, then the "-v2" parsing will certainly fail, and the code throws the same error condition is it did before the patch was applied anyway. + + Original bug description below. + --- + == Comment: #0 - Hari Krishna Bathini - 2019-05-07 13:37:51 == ---Problem Description--- On 4.18.0-18-generic kernel, kexec load command throws below traces: --- Regular kexec load: root@ubuntu:~# kexec -l --append="`cat /proc/cmdline`" --initrd=/boot/initrd.img-`uname -r` /boot/vmlinux-`uname -r` /proc/device-tree/ibm,dynamic-reconfiguration-memory/ibm,dynamic-memory: No such file or directory - Modified cmdline:BOOT_IMAGE=/boot/vmlinux-4.18.0-18-generic root=UUID=1aa9458c-3974-4cb4-9ab3-9ee03c0f4e5e ro crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M - root@ubuntu:~# + Modified cmdline:BOOT_IMAGE=/boot/vmlinux-4.18.0-18-generic root=UUID=1aa9458c-3974-4cb4-9ab3-9ee03c0f4e5e ro crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M + root@ubuntu:~# --- KDump kernel load: root@ubuntu:~# kdump-config unload - * unloaded kdump kernel + * unloaded kdump kernel root@ubuntu:~# kdump-config load - * Creating symlink /var/lib/kdump/vmlinuz - * Creating symlink /var/lib/kdump/initrd.img + * Creating symlink /var/lib/kdump/vmlinuz + * Creating symlink /var/lib/kdump/initrd.img /proc/device-tree/ibm,dynamic-reconfiguration-memory/ibm,dynamic-memory: No such file or directory /proc/device-tree/ibm,dynamic-reconfiguration-memory/ibm,dynamic-memory: No such file or directory - Modified cmdline:BOOT_IMAGE=/boot/vmlinux-4.18.0-18-generic root=UUID=1aa9458c-3974-4cb4-9ab3-9ee03c0f4e5e ro maxcpus=1 systemd.unit=kdump-tools-dump.service irqpoll noirqdistrib nousb elfcorehdr=158912K - * loaded kdump kernel - root@ubuntu:~# + Modified cmdline:BOOT_IMAGE=/boot/vmlinux-4.18.0-18-generic root=UUID=1aa9458c-3974-4cb4-9ab3-9ee03c0f4e5e ro maxcpus=1 systemd.unit=kdump-tools-dump.service irqpoll noirqdistrib nousb elfcorehdr=158912K + * loaded kdump kernel + root@ubuntu:~# --- - - Contact Information = hbath...@in.ibm.com - + + Contact Information = hbath...@in.ibm.com + ---uname output--- Linux ubuntu 4.18.0-18-generic #19~18.04.1-Ubuntu SMP Fri Apr 5 10:21:11 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux - + ---Additional Hardware Info--- - na + na - - Machine Type = na - + Machine Type = na + ---Debugger--- A debugger is not configured - + ---Steps to Reproduce--- - Load panic kernel or regular kernel with kexec command: + Load panic kernel or regular kernel with kexec command: kdump-config unload; kdump-config load OR kexec -l --append="`cat /proc/cmdline`" --initrd=/boot/initrd.img-`uname -r` /boot/vmlinux-`uname -r` Actual Result: DT files are not found while loading the kernel Expected result: kexec loads without any warning/error messages - - Userspace tool common name: kexec-tools - - The userspace tool has the following bit modes: 64-bit + + Userspace tool common name: kexec-tools + + The userspace tool has the following bit modes: 64-bit Userspace rpm:
[Kernel-packages] [Bug 1828187] Re: ibm, dynamic-memory property not found while loading kexec kernel (4.18.0-18-generic)
.debdiff attached to this comment for sponsorship consideration to Cosmic, adding SRU paperwork to original bug description. ** Patch added: "kexec-tools_2.0.16-1ubuntu3.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1828187/+attachment/5265777/+files/kexec-tools_2.0.16-1ubuntu3.1.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1828187 Title: ibm,dynamic-memory property not found while loading kexec kernel (4.18.0-18-generic) Status in The Ubuntu-power-systems project: In Progress Status in kexec-tools package in Ubuntu: In Progress Bug description: For SRU: [Impact] * The ibm,dynamic-memory-v2 device tree property replaced the original ibm,dynamic-memory property. Since kexec-tools doesn't know to look for the "-v2" property yet, it fails to successfully parse the node using the new "-v2" property. * These changes enable the new "-v2" property to be successfully parsed from the node. [Test Case] * Load panic kernel or regular kernel with kexec command: kdump-config unload; kdump-config load OR kexec -l --append="`cat /proc/cmdline`" --initrd=/boot/initrd.img-`uname -r` /boot/vmlinux-`uname -r` * Expected result: kexec loads without any warning/error messages [Testing] These changes were tested by Hari with a positive result on a 4.18 kernel for ppc64el. [Regression Potential] * Low. * These changes exist in 'kexec-tools' for disco and onwards (these kernels are all >= 4.16 where the -v2 property was enabled). * The Bionic edge and Cosmic kernels have support for the -v2 property since they are also >= 4.16. * The regular 4.15 Bionic kernel is the more interesting of the bunch in terms of regression potential since 4.15 is too early to have the -v2 property enabled. The changes introduced by this patch appear to only attempt "-v2" parsing if it was unable to parse the "-v1" node. The absence of the v1 node implies that the device tree is using the "v2" property. Since the "-v2" option is not enabled for the 4.15 kernel, if the "-v1" parsing fails, then the "-v2" parsing will certainly fail, and the code throws the same error condition is it did before the patch was applied anyway. Original bug description below. --- == Comment: #0 - Hari Krishna Bathini - 2019-05-07 13:37:51 == ---Problem Description--- On 4.18.0-18-generic kernel, kexec load command throws below traces: --- Regular kexec load: root@ubuntu:~# kexec -l --append="`cat /proc/cmdline`" --initrd=/boot/initrd.img-`uname -r` /boot/vmlinux-`uname -r` /proc/device-tree/ibm,dynamic-reconfiguration-memory/ibm,dynamic-memory: No such file or directory Modified cmdline:BOOT_IMAGE=/boot/vmlinux-4.18.0-18-generic root=UUID=1aa9458c-3974-4cb4-9ab3-9ee03c0f4e5e ro crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M root@ubuntu:~# --- KDump kernel load: root@ubuntu:~# kdump-config unload * unloaded kdump kernel root@ubuntu:~# kdump-config load * Creating symlink /var/lib/kdump/vmlinuz * Creating symlink /var/lib/kdump/initrd.img /proc/device-tree/ibm,dynamic-reconfiguration-memory/ibm,dynamic-memory: No such file or directory /proc/device-tree/ibm,dynamic-reconfiguration-memory/ibm,dynamic-memory: No such file or directory Modified cmdline:BOOT_IMAGE=/boot/vmlinux-4.18.0-18-generic root=UUID=1aa9458c-3974-4cb4-9ab3-9ee03c0f4e5e ro maxcpus=1 systemd.unit=kdump-tools-dump.service irqpoll noirqdistrib nousb elfcorehdr=158912K * loaded kdump kernel root@ubuntu:~# --- Contact Information = hbath...@in.ibm.com ---uname output--- Linux ubuntu 4.18.0-18-generic #19~18.04.1-Ubuntu SMP Fri Apr 5 10:21:11 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux ---Additional Hardware Info--- na Machine Type = na ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Load panic kernel or regular kernel with kexec command: kdump-config unload; kdump-config load OR kexec -l --append="`cat /proc/cmdline`" --initrd=/boot/initrd.img-`uname -r` /boot/vmlinux-`uname -r` Actual Result: DT files are not found while loading the kernel Expected result: kexec loads without any warning/error messages Userspace tool common name: kexec-tools The userspace tool has the following bit modes: 64-bit Userspace rpm: kexec-tools Userspace tool obtained from project website: na *Additional Instructions for hbath...@in.ibm.com: -Attach ltrace and strace of userspace application. == Comment: #1 - Hari Krishna Bathini - 2019-05-07 13:44:25 == Since v4.16 kernel, ibm,dynamic-memory-v2 Device Tree Property is supported in the kernel. This leaves kexec-tools on ppc64le broken without the below fix patches:
[Kernel-packages] [Bug 1827755] Re: nx842 - CRB request time out (-110) when uninstall NX modules and initiate NX request
** Description changed: + [Impact] + PowerPC 842 hardware compression support is currently broken, this effects workloads like zswap and others that exploit 842 hardware compression on Power. + + [Test] + - Install nx-compress and nx-842-powernv modules + - Initiate NX request + - Uninstall these modules + - Initiate NX request again and we get CRB timeout with error -110 + Test kernel available in the PPA, please see comment #4 and please see comment #5 that verifies the PPA kernel works as expected. + + [Fix] + IBM has identified that the following upstream patch fixes the issue: + 656ecc16e8fc crypto/nx: Initialize 842 high and normal RxFIFO control registers + + [Regression Potential] + The patch only impacts the nx-842 modules, only available on PowerPC architecture and does not have any impact on other architectures or generic code. Risk of regression is very low. + + [Other Info] ---Problem Description--- - Normally nx-compress and nx-842-powernv modules are loaded when selects 842-nx compressor if not loaded and execute forever during system execution. So we will not see this bug in normal case. + Normally nx-compress and nx-842-powernv modules are loaded when selects 842-nx compressor if not loaded and execute forever during system execution. So we will not see this bug in normal case. - But we are seeing NX CRB request timeout when uninstall these modules and load them or select 842-nx compressor. - + But we are seeing NX CRB request timeout when uninstall these modules + and load them or select 842-nx compressor. + ---uname output--- 18.04 - - Machine Type = P9 system - + + Machine Type = P9 system + ---Steps to Reproduce--- - Install nx-compress and nx-842-powernv modules - Initiate NX request - Uninstall these modules - Initiate NX request again and we get CRB timeout with error -110 Patches are included in 4.19-rc1 6e708000ec2c93c2bde6a46aa2d6c3e80d4eaeb9 - powerpc/powernv: Export opal_check_token symbol 656ecc16e8fc2ab44b3d70e3fcc197a7020d0ca5 - crypto/nx: Initialize 842 high and normal RxFIFO control registers > Looks like the first commit was included in a recent 18.04 update > (4.15.0-48.51), see > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819989 - > + > > but I don't see the second one there yet. - > + > > If this is still needed, I would suggest getting this bug mirrored to LP to > put on Canonical's radar. We need second commit (656ecc16e8fc2ab44b3d70e3fcc197a7020d0ca) to fix this actual issue. But no use of having the first commit without second one. The first one just exports opal_check_token symbol which is used in the second commit. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827755 Title: nx842 - CRB request time out (-110) when uninstall NX modules and initiate NX request Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Bug description: [Impact] PowerPC 842 hardware compression support is currently broken, this effects workloads like zswap and others that exploit 842 hardware compression on Power. [Test] - Install nx-compress and nx-842-powernv modules - Initiate NX request - Uninstall these modules - Initiate NX request again and we get CRB timeout with error -110 Test kernel available in the PPA, please see comment #4 and please see comment #5 that verifies the PPA kernel works as expected. [Fix] IBM has identified that the following upstream patch fixes the issue: 656ecc16e8fc crypto/nx: Initialize 842 high and normal RxFIFO control registers [Regression Potential] The patch only impacts the nx-842 modules, only available on PowerPC architecture and does not have any impact on other architectures or generic code. Risk of regression is very low. [Other Info] ---Problem Description--- Normally nx-compress and nx-842-powernv modules are loaded when selects 842-nx compressor if not loaded and execute forever during system execution. So we will not see this bug in normal case. But we are seeing NX CRB request timeout when uninstall these modules and load them or select 842-nx compressor. ---uname output--- 18.04 Machine Type = P9 system ---Steps to Reproduce--- - Install nx-compress and nx-842-powernv modules - Initiate NX request - Uninstall these modules - Initiate NX request again and we get CRB timeout with error -110 Patches are included in 4.19-rc1 6e708000ec2c93c2bde6a46aa2d6c3e80d4eaeb9 - powerpc/powernv: Export opal_check_token symbol 656ecc16e8fc2ab44b3d70e3fcc197a7020d0ca5 - crypto/nx: Initialize 842 high and normal RxFIFO control registers > Looks like the first commit was included in a recent 18.04 update > (4.15.0-48.51), see > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819989 > > but
[Kernel-packages] [Bug 1830090] [NEW] Cannot reach 1300Mbps using DW1830 (BCM943602BAED) with linux-firmware
Public bug reported: I cannot reach 1300Mbps using DW1830 (BCM943602BAED) with linux-firmware, only 985Mbps maximum. It works under win10. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Description changed: - I cannot reach 1300Mbps using DW1830 (BCM943602BAED) with linux-firmware, only maximal 985Mbps. + I cannot reach 1300Mbps using DW1830 (BCM943602BAED) with linux-firmware, only 985Mbps maximum. It works under win10. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1830090 Title: Cannot reach 1300Mbps using DW1830 (BCM943602BAED) with linux-firmware Status in linux-firmware package in Ubuntu: New Bug description: I cannot reach 1300Mbps using DW1830 (BCM943602BAED) with linux-firmware, only 985Mbps maximum. It works under win10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1830090/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1823753] Re: arm64: cma_alloc errors at boot
On Wed, May 22, 2019 at 8:41 AM Paolo Pisati <1823...@bugs.launchpad.net> wrote:
>
> I realize this is just a workaround (and the above 31M cma memory
> fragmentation is ugly), but we should definitely bump CMA allocation
> space: definitely 32M (since that's what upstream default to) but if 64M
> solves a problem you have at the moment (until we sort out the driver
> issue), i'm not opposing to such a change -
Unfortunately, without other mitigations, we blow past 64M as well.
Ignoring fragmentation, we're using ~108M of CMA (summing up the
totals in comment #11). I think including the dma-contiguous patches
are key. They would alleviate the pain of the single page allocations
(~46M), and unblock driver optimizations from doing the same (hisi_sas
driver could move 33M of allocs out of CMA). Those would impact archs
that have CONFIG_DMA_CMA, which are arm64 and armhf-generic:
debian.master/config/annotations:CONFIG_DMA_CMA
policy<{'amd64': 'n', 'arm64': 'y', 'armhf-generic': 'y',
'armhf-generic-lpae': 'n', 'i386': 'n', 's390x': 'n'}>
I don't have any real armhf-generic hw anymore - if I prepared PPA
kernels, would you happen to have kit for regression testing?
> after all, you are the main
> consumer of generic/arm64 (all other boards are either armhf or have
> their own topic kernel) so if there's a workaround we can apply to make
> your life easier, i don't see why we shouldn't do it.
My biggest concern w/ bumping up CMA is that we do appear to have
users of the arm64/generic kernel on platforms I don't have. For
instance, the reason we got into this CMA issue at all was by turning
on DMA_CMA on arm64 for the RPi3 (bug 1803206) - so I'd at least like
to get some regression testing on that platform. And, obviously such
relatively lowmem platforms make me want to be rather conservative
about bumping up CMA sizes.
-dann
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1823753
Title:
arm64: cma_alloc errors at boot
Status in linux package in Ubuntu:
Confirmed
Bug description:
On some arm64 systems[*] we are seeing a spew of messages on the
console:
[ 19.534097] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
[ 19.534109] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
[ 19.534113] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
[ 19.534126] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
[ 19.534130] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
[ 19.534142] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
[ 19.534146] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
[ 19.534157] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
[ 19.534161] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
[ 19.534173] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
[ 19.534177] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
This appears to be non-fatal - impacted systems all eventually boot.
But, at least in the case of the HP m400, it slows down boot enough
that MAAS' default timeout will expire before completing deployment.
[*] Observed on a HiSilicon D06 w/ SMMU disabled in the BIOS, as well
as an HP m400 (APM X-Gene) cartridge - although, not on another one
that - in theory - should be identical.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823753/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819116] Re: sync_file_range02 in ubuntu_ltp_syscalls fails C/D
affects disco, 5.0.0-1007.7 linux-azure ** Also affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Attachment added: "ltp_syscalls-azure-disco" https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1819116/+attachment/5265775/+files/ltp_syscalls-azure-disco -- 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/1819116 Title: sync_file_range02 in ubuntu_ltp_syscalls fails C/D Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-aws source package in Bionic: New Status in linux-azure source package in Bionic: New Status in linux source package in Cosmic: New Status in linux-aws source package in Cosmic: New Status in linux-azure source package in Cosmic: New Status in linux source package in Disco: Incomplete Status in linux-aws source package in Disco: New Status in linux-azure source package in Disco: New Bug description: syslog output attached as attachment. <<>> incrementing stop tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop2' tst_supported_fs_types.c:72: INFO: Kernel supports ext2 tst_supported_fs_types.c:56: INFO: mkfs.ext2 does exist tst_supported_fs_types.c:72: INFO: Kernel supports ext3 tst_supported_fs_types.c:56: INFO: mkfs.ext3 does exist tst_supported_fs_types.c:72: INFO: Kernel supports ext4 tst_supported_fs_types.c:56: INFO: mkfs.ext4 does exist tst_supported_fs_types.c:72: INFO: Kernel supports xfs tst_supported_fs_types.c:56: INFO: mkfs.xfs does exist tst_supported_fs_types.c:72: INFO: Kernel supports btrfs tst_supported_fs_types.c:56: INFO: mkfs.btrfs does exist tst_supported_fs_types.c:72: INFO: Kernel supports vfat tst_supported_fs_types.c:56: INFO: mkfs.vfat does exist tst_supported_fs_types.c:95: INFO: Filesystem exfat is not supported tst_supported_fs_types.c:72: INFO: Kernel supports ntfs tst_supported_fs_types.c:56: INFO: mkfs.ntfs does exist tst_test.c:1157: INFO: Testing on ext2 tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext2 opts='' extra opts='' mke2fs 1.44.6 (5-Mar-2019) tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:54: PASS: Test file range synced to device tst_test.c:1157: INFO: Testing on ext3 tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext3 opts='' extra opts='' mke2fs 1.44.6 (5-Mar-2019) tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:54: PASS: Test file range synced to device tst_test.c:1157: INFO: Testing on ext4 tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext4 opts='' extra opts='' mke2fs 1.44.6 (5-Mar-2019) tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:54: PASS: Test file range synced to device tst_test.c:1157: INFO: Testing on xfs tst_mkfs.c:90: INFO: Formatting /dev/loop2 with xfs opts='' extra opts='' tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:54: PASS: Test file range synced to device tst_test.c:1157: INFO: Testing on btrfs tst_mkfs.c:90: INFO: Formatting /dev/loop2 with btrfs opts='' extra opts='' tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:54: PASS: Test file range synced to device tst_test.c:1157: INFO: Testing on vfat tst_mkfs.c:90: INFO: Formatting /dev/loop2 with vfat opts='' extra opts='' tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:54: PASS: Test file range synced to device tst_test.c:1157: INFO: Testing on ntfs tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ntfs opts='' extra opts='' The partition start sector was not specified for /dev/loop2 and it could not be obtained automatically. It has been set to 0. The number of sectors per track was not specified for /dev/loop2 and it could not be obtained automatically. It has been set to 0. The number of heads was not specified for /dev/loop2 and it could not be obtained automatically. It has been set to 0. To boot from a device, Windows needs the 'partition start sector', the 'sectors per track' and the 'number of heads' to be set. Windows will not be able to boot from this device. safe_macros.c:739: INFO: Trying FUSE... tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:56: FAIL: Synced 0, expected 33554432 Summary: passed 6 failed 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=11 termination_type=exited termination_id=1 corefile=no cutime=10 cstime=157 <<>> INFO: ltp-pan reported some tests FAIL LTP Version: 20190115 ### Done executing testcases. LTP Version: 20190115
[Kernel-packages] [Bug 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security
I was able to speak with folks at Intel about this and got some good info from them: * To avoid confusion, we need to be clear that the i7-8565U is a Whiskey Lake processor (*not* a Kaby Lake) - https://ark.intel.com/content/www/us/en/ark/products/149091/intel-core-i7-8565u-processor-8m-cache-up-to-4-60-ghz.html * There is an upstream intel-microcode bug report that is already tracking this issue - https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1 * The upstream bug report suggests that the problem is seen with both the 20190312 and 20190514 microcode releases * This may be a bug in how the kernel is loading the microcode ** Bug watch added: github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues #1 https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1 ** Description changed: Description: - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of booting, after grub) - does not even show the enter cryptsetup passphrase - affected kernels: # apt list --installed |grep linux-signed WARNING: apt does not have a stable CLI interface. Use with caution in scripts. linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 [installed] linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 4.18.0.20.70 amd64 [installed] linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 5.0.0.15.71 amd64 [installed] - the setup is not new, has been working perfectly before (about 7 days since my last restart?) System: - HW: ASUS Zenbook 14 UX433FN - Ubuntu 18.04, runing latest HWE, fully updated - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup), Suspected/possible cause?: - recent intel-microcode package update - recent kernel package updates Steps taken: - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding nosplash, noplymouth) - completely removed nvidia drivers (apt purge *nvidia*) - completely purged and reinstalled grub (grup-pc) - completely purged and reinstalled all kernels (headers, modules, image, ..) - toggle BIOS "fastboot" (now using OFF) - toggle UEFI SecureBoot (now using ON) - remove plymouth (apt remove *plymouth* , but the workaround is working with plymouth installed) Workaround: - so far, I'm only able to boot with non-Ubuntu kernel! (linux-image-liquorix-amd64) - which needs "splash" option ON - reinstall cryptsetup & update-grub (as suggested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620/comments/10 ) I am not sure how to get you more debug info, as this setup has been working before, and it's a very eary boot-process bug, so I can't even access dmesg etc. EDIT: Hypothesis: - Only affects ASUS with newer (Kaby lake) Intel CPU, intel-microcode + Only affects ASUS with i7-8565U Whiskey Lake Intel CPU + Upstream Bug Report: + https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1 WORKAROUND 1: disable intel microcode updates during boot From this bug: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920 1/ add the boot parameter: dis_ucode_ldr to /etc/default/grub 2/ update-grub WORKAROUND 2: downgrade (and hold) intel-microcode to older version from bionic/main apt install --reinstall intel-microcode=3.20180312.0~ubuntu18.04.1 - --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2337 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge (not installed) Tags: bionic wayland-session Uname: Linux 5.0.0-17.1-liquorix-amd64 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo vboxusers video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2339 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6 Tags: third-party-packages bionic wayland-session Uname: Linux 5.0.0-15-generic x86_64 UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo video _MarkForUpload: True -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.
Re: [Kernel-packages] [Bug 1829912] Re: [Lenovo ideapad 330-15IKB] Sound very low, and quality of audio very bad.
Hi, I have upgraded to Ubuntu 19.04 and Kernel 5.0, The sound is still the same with overamplification disabled. Is the fix for the audio driver uploaded ?? Regards, Phaneesh On Wed, May 22, 2019 at 7:45 AM Hui Wang wrote: > @Phaneesh, > > Could you please install the ubuntu 5.0 kernel, then I will upload a > audio driver (dkms) for 5.0 kernel to test. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1829912 > > Title: > [Lenovo ideapad 330-15IKB] Sound very low, and quality of audio very > bad. > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > I am on a Lenovo Ideapad 330. I've switched to Ubuntu from Windows. The > audio quality in Ubuntu is horrible to say the least, It is very low, and > in case I use VLC or enable overamplification, the quality of sound output > becomes worse. > I have ensured that the volume on alsamixer is 100. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: pulseaudio 1:11.1-1ubuntu7.2 > ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 > Uname: Linux 4.18.0-20-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > ApportVersion: 2.20.9-0ubuntu7.6 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: phaneesh 1605 F pulseaudio > CurrentDesktop: ubuntu:GNOME > Date: Tue May 21 23:41:49 2019 > InstallationDate: Installed on 2019-05-17 (4 days ago) > InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 > (20190210) > ProcEnviron: >LANGUAGE=en_IN:en >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_IN >SHELL=/bin/bash > SourcePackage: pulseaudio > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 06/13/2018 > dmi.bios.vendor: LENOVO > dmi.bios.version: 8TCN44WW > dmi.board.asset.tag: NO Asset Tag > dmi.board.name: LNVNB161216 > dmi.board.vendor: LENOVO > dmi.board.version: NO DPK > dmi.chassis.asset.tag: NO Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: LENOVO > dmi.chassis.version: Lenovo ideapad 330-15IKB > dmi.modalias: > dmi:bvnLENOVO:bvr8TCN44WW:bd06/13/2018:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB: > dmi.product.family: ideapad 330-15IKB > dmi.product.name: 81DE > dmi.product.sku: LENOVO_MT_81DE_BU_idea_FM_ideapad 330-15IKB > dmi.product.version: Lenovo ideapad 330-15IKB > dmi.sys.vendor: LENOVO > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829912/+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/1829912 Title: [Lenovo ideapad 330-15IKB] Sound very low, and quality of audio very bad. Status in linux package in Ubuntu: Incomplete Bug description: I am on a Lenovo Ideapad 330. I've switched to Ubuntu from Windows. The audio quality in Ubuntu is horrible to say the least, It is very low, and in case I use VLC or enable overamplification, the quality of sound output becomes worse. I have ensured that the volume on alsamixer is 100. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: phaneesh 1605 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue May 21 23:41:49 2019 InstallationDate: Installed on 2019-05-17 (4 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8TCN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15IKB dmi.modalias: dmi:bvnLENOVO:bvr8TCN44WW:bd06/13/2018:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB: dmi.product.family: ideapad 330-15IKB dmi.product.name: 81DE dmi.product.sku: LENOVO_MT_81DE_BU_idea_FM_ideapad 330-15IKB dmi.product.version: Lenovo ideapad 330-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829912/+subscriptions
[Kernel-packages] [Bug 1817321] Re: installer does not support iSCSI iBFT
The attachment "bionic_d-i.debdiff" seems to be a debdiff. The ubuntu- sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: 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/1817321 Title: installer does not support iSCSI iBFT Status in debian-installer package in Ubuntu: Confirmed Status in hw-detect package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in partman-iscsi package in Ubuntu: Confirmed Status in debian-installer source package in Bionic: Confirmed Status in hw-detect source package in Bionic: Confirmed Status in linux source package in Bionic: Fix Released Status in partman-iscsi source package in Bionic: Confirmed Status in debian-installer source package in Cosmic: Confirmed Status in hw-detect source package in Cosmic: Confirmed Status in linux source package in Cosmic: Fix Released Status in partman-iscsi source package in Cosmic: Confirmed Status in debian-installer source package in Disco: Confirmed Status in hw-detect source package in Disco: Confirmed Status in linux source package in Disco: Fix Released Status in partman-iscsi source package in Disco: Confirmed Status in debian-installer source package in Eoan: Confirmed Status in hw-detect source package in Eoan: Confirmed Status in linux source package in Eoan: Fix Released Status in partman-iscsi source package in Eoan: Confirmed Bug description: [Impact] * It's not possible to access iBFT (iSCSI Boot Firmware Table) information (settings for network interface, initiator, and target) in the installer because the 'iscsi_ibft' module is not present in udeb packages. * Even if it was, the installer does not handle iBFT information at all, thus any settings are ignored, and iSCSI-related configuration has to be done manually or with workarounds. * This impacts user-experience and automatic installation on systems and deployments which actually do provide the iBFT feature and information, but cannot use it practically. * With proper iBFT support in the installer (kernel module in udeb package and automatic iSCSI-related configuration) users will be able to rely on iBFT to install/deploy Ubuntu on their servers and datacenters. * These fixes add the 'iscsi_ibft' kernel module in the scsi-modules udeb, and configure network/iSCSI according to iBFT information in disk-detect. This is done in disk-detect so that the iSCSI LUNs are detected as disks (useful in case of no other disks in the system so the installer doesn't complain nor wait too long) and that any partman-related preseed options are not required and may be still available for the user. [Test Case] * linux package / kernel module in udeb: $ dpkg-deb -c scsi-modules_*.udeb | grep iscsi_ibft.ko Check the module loads in the installer environment. See comment with example for disco. * d-i/hw-detect/partman-iscsi package: See comments 11, 12, 13. [Regression Potential] * linux package: low, the kernel module is not loaded by default, and only checks whether iBFT information is present in firmware, then exposes that in sysfs in read-only mode. * d-i/hw-detect/partman-iscsi: - d-i: kernel version update to include iscsi_ibft module, based on kernel released to -updates plus one week monitoring bug reports -- it should be OK. Tested on amd64/i386/arm64/ppc64el on QEMU, plus amd64 on baremetal -- see comment 11. - hw-detect: low, the changes are enabled by a preseed option. see comment 12. - partman-iscsi: low, simple changes, plus one fix that has been tested in detail, and falls back to previous behavior if it fails. see comment 13. [Other Info] * This has been verified both by the developer with a simple iSCSI iBFT environment (2 VMs: iSCSI target & initiator with UEFI+iPXE) and by an user with system/firmware that supports iBFT for iSCSI. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1817321/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826125] Re: Dell XPS 13 9380 flickering (Whiskey Lake)
@agiani, are you using in PCLinuxOS any kernel options? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826125 Title: Dell XPS 13 9380 flickering (Whiskey Lake) Status in Linux: Incomplete Status in linux package in Ubuntu: Confirmed Bug description: A brand new Dell XPS 13 9380 preinstalled with Ubuntu 18.04 flickers to the point of being totally unusable. I have upgraded since to 18.10 and 19.04 with no changes. I have tried several combinations of the i915 parameters fastboot, enable_rc6 and enable_fbc to no avail. Examples of flickering are here: https://photos.app.goo.gl/1PkL2HrjMBP41aML9 https://photos.app.goo.gl/CMzmMwrCPH5wh8aw6 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1430 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-20180608-47+italia-whl+X31 DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-13 (10 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 9380 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1035-oem root=UUID=252898e9-6e96-4705-a709-2db930b7c4c7 ro quiet splash i915.fastboot=1 i915.enable_rc6=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1035.40-oem 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-1035-oem N/A linux-backports-modules-4.15.0-1035-oem N/A linux-firmware 1.178 Tags: disco Uname: Linux 4.15.0-1035-oem x86_64 UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 02/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/14/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1826125/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821394] Re: vmx tests fail in kvm_unit_tests
affects , linux-azure 5.0.0-1007.7 ** Tags added: 5.0.0 -- 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/1821394 Title: vmx tests fail in kvm_unit_tests Status in ubuntu-kernel-tests: Confirmed Status in linux-aws package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Bug description: Reproducible: Yes, every time. Series: cosmic Kernel: "linux-aws 4.18.0-1012.14" Steps: 1.) apt-get install --yes --allow build-essential cpu-checker qemu-kvm git gcc-multilib 2.) git clone --depth=1 https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git 3.) cd kvm-unit-tests; ./configure; make 4.) TESTNAME=vmx TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu host,+vmx -append "-exit_monitor_from_l2_test -ept_access* -vmx_smp* -vmx_vmcs_shadow_test" PASS: Enable-EPT enabled; EPT memory type 6: vmlaunch succeeds FAIL: Enable-EPT enabled; EPT memory type 7: vmlaunch fails FAIL: Enable-EPT enabled; EPT page walk length 0: vmlaunch fails FAIL: Enable-EPT enabled; EPT page walk length 8: vmlaunch fails FAIL: Enable-EPT enabled; EPT page walk length 16: vmlaunch fails PASS: Enable-EPT enabled; EPT page walk length 24: vmlaunch succeeds FAIL: Enable-EPT enabled; EPT page walk length 32: vmlaunch fails FAIL: Enable-EPT enabled; EPT page walk length 40: vmlaunch fails FAIL: Enable-EPT enabled; EPT page walk length 48: vmlaunch fails FAIL: Enable-EPT enabled; EPT page walk length 56: vmlaunch fails INFO: Processor supports accessed and dirty flag PASS: Enable-EPT enabled; EPT accessed and dirty flag 0: vmlaunch succeeds PASS: Enable-EPT enabled; EPT accessed and dirty flag 1: vmlaunch succeeds PASS: Enable-EPT enabled; reserved bits [11:7] 0: vmlaunch succeeds FAIL: Enable-EPT enabled; reserved bits [11:7] 1: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 2: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 3: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 4: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 5: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 6: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 7: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 8: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 9: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 10: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 11: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 12: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 13: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 14: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 15: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 16: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 17: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 18: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 19: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 20: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 21: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 22: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 23: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 24: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 25: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 26: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 27: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 28: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 29: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 30: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 31: vmlaunch fails PASS: Enable-EPT enabled; reserved bits [63:N] 0: vmlaunch succeeds FAIL: Enable-EPT enabled; reserved bits [63:N] 1: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 2: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 4: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 8: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 16: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 32: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 64: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 128: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 256: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 512: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 1024: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 2048: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 4096: vmlaunch fails FAIL: Enable-EPT enabled;
[Kernel-packages] [Bug 1829211] Re: linux-fips: 4.15.0-1008.9 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1829219 phase: Holding before Promote to Proposed phase-changed: Wednesday, 22. May 2019 13:42 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa meta:failed,main:building,signed:building + promote-to-proposed: Pending -- builds not complete in ppa main:building,signed:building,meta:failed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829211 Title: linux-fips: 4.15.0-1008.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1829219 phase: Holding before Promote to Proposed phase-changed: Wednesday, 22. May 2019 13:42 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa main:building,signed:building,meta:failed To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829211/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829812] Re: Regression for ubuntu_bpf test case fails to build on disco
Affects: Disco, 5.0.0-1007.7 linux-azure
** Summary changed:
- Regression for ubuntu_bpf test case fails to build on disco
+ Regression for ubuntu_kernel_selftests [net] ubuntu_bpf test case fails to
build on disco
--
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/1829812
Title:
Regression for ubuntu_kernel_selftests [net] ubuntu_bpf test case
fails to build on disco
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux-aws package in Ubuntu:
New
Status in linux-azure package in Ubuntu:
New
Status in linux source package in Disco:
New
Status in linux-aws source package in Disco:
New
Status in linux-azure source package in Disco:
New
Bug description:
This test will failed to build on 5.0.0-16 Disco.
5.0.0-16 Disco + 5.0.0-15 source code - build OK
5.0.0-16 Disco + 5.0.0-16 source code - Failed
Bisect shows this one e38969c9 (selftests/bpf: skip verifier tests for
unsupported program types) in our tree is the cause (upstream commit:
8184d44c)
Which uses a "recently introduced bpf_probe_prog_type()" to skip test.
And we don't have it implemented.
make[1]: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf'
gcc -o
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/urandom_read
-static urandom_read.c -Wl,--build-id
make -C ../../../lib/bpf
OUTPUT=/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/
make[2]: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/lib/bpf'
Auto-detecting system features:
...libelf: [ on ]
... bpf: [ on ]
HOSTCC
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/fixdep.o
HOSTLD
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/fixdep-in.o
LINK
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/fixdep
CC
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/libbpf.o
CC
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/bpf.o
CC
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/nlattr.o
CC
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/btf.o
CC
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/libbpf_errno.o
CC
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/str_error.o
CC
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/netlink.o
CC
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/bpf_prog_linfo.o
LD
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/libbpf-in.o
LINK
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/libbpf.a
LINK
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/libbpf.so
LINK
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/test_libbpf
make[2]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/lib/bpf'
gcc -Wall -O2 -I../../../include/uapi -I../../../lib -I../../../lib/bpf
-I../../../../include/generated -I../../../includetest_verifier.c
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/libbpf.a
-lcap -lelf -lrt -lpthread -o
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/test_verifier
make[1]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf'
make: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests'
stderr:
Warning: Kernel ABI header at 'tools/include/uapi/linux/if_link.h' differs
from latest version at 'include/uapi/linux/if_link.h'
test_verifier.c: In function ‘do_test_single’:
test_verifier.c:15951:22: warning: implicit declaration of function
‘bpf_probe_prog_type’; did you mean ‘bpf_program__set_type’?
[-Wimplicit-function-declaration]
if (fd_prog < 0 && !bpf_probe_prog_type(prog_type, 0)) {
^~~
bpf_program__set_type
/usr/bin/ld: /tmp/ccRNIovw.o: in function `do_test_single':
test_verifier.c:(.text+0xf41): undefined reference to `bpf_probe_prog_type'
collect2: error: ld returned 1 exit status
make[1]: *** [../lib.mk:152:
[Kernel-packages] [Bug 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security
Here's my /proc/cpuinfo ** Attachment added: "cpuinfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620/+attachment/5265773/+files/cpuinfo.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/1829620 Title: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: Description: - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of booting, after grub) - does not even show the enter cryptsetup passphrase - affected kernels: # apt list --installed |grep linux-signed WARNING: apt does not have a stable CLI interface. Use with caution in scripts. linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 [installed] linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 4.18.0.20.70 amd64 [installed] linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 5.0.0.15.71 amd64 [installed] - the setup is not new, has been working perfectly before (about 7 days since my last restart?) System: - HW: ASUS Zenbook 14 UX433FN - Ubuntu 18.04, runing latest HWE, fully updated - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup), Suspected/possible cause?: - recent intel-microcode package update - recent kernel package updates Steps taken: - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding nosplash, noplymouth) - completely removed nvidia drivers (apt purge *nvidia*) - completely purged and reinstalled grub (grup-pc) - completely purged and reinstalled all kernels (headers, modules, image, ..) - toggle BIOS "fastboot" (now using OFF) - toggle UEFI SecureBoot (now using ON) - remove plymouth (apt remove *plymouth* , but the workaround is working with plymouth installed) Workaround: - so far, I'm only able to boot with non-Ubuntu kernel! (linux-image-liquorix-amd64) - which needs "splash" option ON - reinstall cryptsetup & update-grub (as suggested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620/comments/10 ) I am not sure how to get you more debug info, as this setup has been working before, and it's a very eary boot-process bug, so I can't even access dmesg etc. EDIT: Hypothesis: Only affects ASUS with newer (Kaby lake) Intel CPU, intel-microcode WORKAROUND 1: disable intel microcode updates during boot From this bug: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920 1/ add the boot parameter: dis_ucode_ldr to /etc/default/grub 2/ update-grub WORKAROUND 2: downgrade (and hold) intel-microcode to older version from bionic/main apt install --reinstall intel-microcode=3.20180312.0~ubuntu18.04.1 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2337 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge (not installed) Tags: bionic wayland-session Uname: Linux 5.0.0-17.1-liquorix-amd64 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo vboxusers video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2339 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6 Tags: third-party-packages bionic wayland-session Uname: Linux 5.0.0-15-generic x86_64 UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1829620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829812] Re: Regression for ubuntu_bpf test case fails to build on disco
This is coming up on the azure kernel as well. Various instance flavor
types:
05/20 14:12:08 DEBUG| utils:0153| [stdout] make[2]: Leaving directory
'/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/lib/bpf'
05/20 14:12:08 DEBUG| utils:0153| [stdout] gcc -Wall -O2
-I../../../include/uapi -I../../../lib -I../../../lib/bpf
-I../../../../include/generated -I../../../includetest_verifier.c
/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/libbpf.a
-lcap -lelf -lrt -lpthread -o
/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/test_verifier
05/20 14:12:09 ERROR| utils:0153| [stderr] test_verifier.c: In function
‘do_test_single’:
05/20 14:12:09 ERROR| utils:0153| [stderr] test_verifier.c:15951:22:
warning: implicit declaration of function ‘bpf_probe_prog_type’; did you
mean ‘bpf_program__set_type’? [-Wimplicit-function-declaration]
05/20 14:12:09 ERROR| utils:0153| [stderr] if (fd_prog < 0 &&
!bpf_probe_prog_type(prog_type, 0)) {
05/20 14:12:09 ERROR| utils:0153| [stderr]
^~~
05/20 14:12:09 ERROR| utils:0153| [stderr]
bpf_program__set_type
05/20 14:12:09 ERROR| utils:0153| [stderr] /usr/bin/ld: /tmp/ccUGUMFc.o: in
function `do_test_single':
05/20 14:12:09 ERROR| utils:0153| [stderr] test_verifier.c:(.text+0xf41):
undefined reference to `bpf_probe_prog_type'
05/20 14:12:10 ERROR| utils:0153| [stderr] collect2: error: ld returned 1
exit status
05/20 14:12:10 ERROR| utils:0153| [stderr] make[1]: *** [../lib.mk:152:
/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/test_verifier]
Error 1
05/20 14:12:10 DEBUG| utils:0153| [stdout] make[1]: Leaving directory
'/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf'
05/20 14:12:10 DEBUG| utils:0153| [stdout] make: Leaving directory
'/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
05/20 14:12:10 ERROR| utils:0153| [stderr] make: *** [Makefile:90: all]
Error 2
05/20 14:12:10 ERROR| test:0414| Exception escaping from test:
Traceback (most recent call last):
File "/home/azure/autotest/client/shared/test.py", line 411, in _exec
_call_test_function(self.execute, *p_args, **p_dargs)
File "/home/azure/autotest/client/shared/test.py", line 823, in
_call_test_function
return func(*args, **dargs)
File "/home/azure/autotest/client/shared/test.py", line 291, in execute
postprocess_profiled_run, args, dargs)
File "/home/azure/autotest/client/shared/test.py", line 212, in _call_run_once
self.run_once(*args, **dargs)
File
"/home/azure/autotest/client/tests/ubuntu_kernel_selftests/ubuntu_kernel_selftests.py",
line 144, in run_once
utils.system(cmd)
File "/home/azure/autotest/client/shared/utils.py", line 1232, in system
verbose=verbose).exit_status
File "/home/azure/autotest/client/shared/utils.py", line 918, in run
"Command returned non-zero exit status")
CmdError: Command failed,
rc=2, Command returned non-zero exit status
* Command:
make -C linux/tools/testing/selftests TARGETS=bpf
Exit status: 2
Duration: 5.6805369854
** Also affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
** Tags added: aws azure
--
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/1829812
Title:
Regression for ubuntu_kernel_selftests [net] ubuntu_bpf test case
fails to build on disco
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux-aws package in Ubuntu:
New
Status in linux-azure package in Ubuntu:
New
Status in linux source package in Disco:
New
Status in linux-aws source package in Disco:
New
Status in linux-azure source package in Disco:
New
Bug description:
This test will failed to build on 5.0.0-16 Disco.
5.0.0-16 Disco + 5.0.0-15 source code - build OK
5.0.0-16 Disco + 5.0.0-16 source code - Failed
Bisect shows this one e38969c9 (selftests/bpf: skip verifier tests for
unsupported program types) in our tree is the cause (upstream commit:
8184d44c)
Which uses a "recently introduced bpf_probe_prog_type()" to skip test.
And we don't have it implemented.
make[1]: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf'
gcc -o
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/urandom_read
-static urandom_read.c -Wl,--build-id
make -C ../../../lib/bpf
OUTPUT=/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/
make[2]: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/lib/bpf'
