[Kernel-packages] [Bug 1813244] Re: systemd cause kernel trace "BUG: unable to handle kernel paging request at 6db23a14" on Cosmic i386
New patch after the review from the LKML. ** Patch added: "openvswitch: fix flow actions reallocation - v2" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813244/+attachment/5250007/+files/0001-openvswitch-fix-flow-actions-reallocation.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/1813244 Title: systemd cause kernel trace "BUG: unable to handle kernel paging request at 6db23a14" on Cosmic i386 Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: This issue was found after leaving a SUT to run overnight (was testing the ubuntu_cts_kernel test 13 hours ago before this happens). Can't tell if this is a regression, as I haven't find a way to reproduce it. But I do see similar reports on the Internet [1] After checking the systemd service timers, it looks like this is caused by the logrotate.service: $ sudo systemctl list-timers --all NEXT LEFT LAST PASSEDUNIT ACTIVATES Fri 2019-01-25 06:18:58 UTC 1h 40min left Thu 2019-01-24 06:34:15 UTC 22h ago apt-daily-upgrade.timer apt-daily-upgrade.service Fri 2019-01-25 09:15:54 UTC 4h 37min left Fri 2019-01-25 03:43:24 UTC 55min ago apt-daily.timer apt-daily.service Fri 2019-01-25 17:02:47 UTC 12h left Fri 2019-01-25 04:20:17 UTC 18min ago motd-news.timer motd-news.service Sat 2019-01-26 00:00:00 UTC 19h left Fri 2019-01-25 00:00:37 UTC 4h 38min ago logrotate.timer logrotate.service Sat 2019-01-26 04:02:38 UTC 23h left Fri 2019-01-25 04:02:38 UTC 36min ago systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.serv Mon 2019-01-28 00:00:00 UTC 2 days left Wed 2019-01-23 10:44:18 UTC 1 day 17h ago fstrim.timer fstrim.service n/a n/a n/a n/a snapd.snap-repair.timer snapd.snap-repair.service 7 timers listed. After this happens, you won't be able to reboot it with the command. $ sudo reboot sudo: unable to resolve host onza: Resource temporarily unavailable Killed Here is the error message, please refer to the attachment for a complete syslog: Jan 25 00:00:37 onza systemd[1]: Starting Rotate log files... Jan 25 00:00:37 onza kernel: [45282.956634] BUG: unable to handle kernel paging request at 6db23a14 Jan 25 00:00:37 onza kernel: [45282.962902] *pdpt = 33fa1001 *pde = Jan 25 00:00:37 onza kernel: [45282.968650] Oops: [#1] SMP Jan 25 00:00:37 onza kernel: [45282.971796] CPU: 0 PID: 407 Comm: systemd-journal Not tainted 4.18.0-14-generic #15-Ubuntu Jan 25 00:00:37 onza kernel: [45282.980330] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 Jan 25 00:00:37 onza kernel: [45282.988127] EIP: __kmalloc+0xc9/0x240 Jan 25 00:00:37 onza kernel: [45282.991785] Code: 4d e0 8d 4a 01 31 c6 8b 45 f0 89 75 dc 31 f3 8b 37 64 0f c7 0e 0f 94 c0 84 c0 74 b9 8b 75 e4 8b 45 dc 39 45 e0 74 0e 03 5f 14 <33> 1b 33 9f b4 00 00 00 0f 18 03 f7 45 ec 00 80 00 00 0f 85 3f 01 Jan 25 00:00:37 onza kernel: [45283.011254] EAX: 9e20b374 EBX: 6db23a14 ECX: 350d EDX: 350c Jan 25 00:00:37 onza kernel: [45283.017769] ESI: eac03a00 EDI: eac03a00 EBP: f461fd9c ESP: f461fd74 Jan 25 00:00:37 onza kernel: [45283.024304] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00010206 Jan 25 00:00:37 onza kernel: [45283.031245] CR0: 80050033 CR2: 6db23a14 CR3: 29d304a0 CR4: 06f0 Jan 25 00:00:37 onza kernel: [45283.037770] Call Trace: Jan 25 00:00:37 onza kernel: [45283.040395] ? ext4_htree_store_dirent+0x2e/0x120 Jan 25 00:00:37 onza kernel: [45283.045255] ext4_htree_store_dirent+0x2e/0x120 Jan 25 00:00:37 onza kernel: [45283.049951] htree_dirblock_to_tree+0xd2/0x230 Jan 25 00:00:37 onza kernel: [45283.054562] ext4_htree_fill_tree+0x7f/0x2c0 Jan 25 00:00:37 onza kernel: [45283.058991] ? kmem_cache_alloc_trace+0x167/0x1e0 Jan 25 00:00:37 onza kernel: [45283.063849] ? ext4_readdir+0x9d4/0xb10 Jan 25 00:00:37 onza kernel: [45283.067854] ext4_readdir+0x6aa/0xb10 Jan 25 00:00:37 onza kernel: [45283.071687] ? _copy_to_user+0x21/0x30 Jan 25 00:00:37 onza kernel: [45283.075597] ? do_statfs64+0x34/0x60 Jan 25 00:00:37 onza kernel: [45283.079334] ? security_file_permission+0x7c/0xb0 Jan 25 00:00:37 onza kernel: [45283.084306] iterate_dir+0x15c/0x1a0 Jan 25 00:00:37 onza kernel: [45283.087883] ksys_getdents64+0x6f/0x110 Jan 25 00:00:37 onza kernel: [45283.091853] ? iterate_dir+0x1a0/0x1a0 Jan 25 00:00:37 onza kernel: [45283.095771] sys_getdents64+0x16/0x20 Jan 25 00:00:37 onza kernel: [45283.099595] do_fast_syscall_32+0x7f/0x1e0 Jan 25 00:00:37 onza kernel: [4528
[Kernel-packages] [Bug 1819691] Re: linux-raspi2: 4.15.0-1033.35 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Confirmed -- 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/1819691 Title: linux-raspi2: 4.15.0-1033.35 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released 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: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed 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: 1819716 phase: Testing phase-changed: Thursday, 21. March 2019 19:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: 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/1819691/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819691] Re: linux-raspi2: 4.15.0-1033.35 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Fix Released => New -- 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/1819691 Title: linux-raspi2: 4.15.0-1033.35 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released 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: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed 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: 1819716 phase: Testing phase-changed: Thursday, 21. March 2019 19:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: 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/1819691/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822032] Re: perf_event_open02 in ubuntu_ltp_syscalls failed on Cosmic s390x
Related commit in LTP: https://github.com/linux-test-project/ltp/commit/8032a1ae42afd024bd3e74984108020e7fa756e5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822032 Title: perf_event_open02 in ubuntu_ltp_syscalls failed on Cosmic s390x Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Cosmic: Incomplete Bug description: Failed on Cosmic s390x KVM, zVM, LPAR: startup='Wed Mar 20 10:06:36 2019' perf_event_open02 1 TBROK : perf_event_open02.c:275: perf_event_open failed: errno=ENOENT(2): No such file or directory perf_event_open02 2 TBROK : perf_event_open02.c:275: Remaining cases broken tag=perf_event_open02 stime=1553076396 dur=0 exit=exited stat=2 core=no cu=0 cs=0 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-17-generic 4.18.0-17.18 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic s390x NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.2 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Thu Mar 28 04:34:19 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=86fb6fff-dc2f-4ffd-9ea8-a15d77ae3eaa crashkernel=196M RelatedPackageVersions: linux-restricted-modules-4.18.0-17-generic N/A linux-backports-modules-4.18.0-17-generic N/A linux-firmware 1.175.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1822032/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818294] Re: HiSilicon HNS ethernet broken in 4.15.0-45
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818294 Title: HiSilicon HNS ethernet broken in 4.15.0-45 Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Released Bug description: [Impact] The 1G NICs on the Huawei XR320 system do not detect link on initial boot, resulting in broken networking. This is a regression caused by: 308c6cafde01 ("net: hns: All ports can not work when insmod hns ko after rmmod.") While that fixed an issue with phys after reloading the driver, it caused an issue with some phys on initial load. [Test Case] dmesg | grep "hns-nic HISI00C2:02 enahisic2i2: link up" (With enahisic2i2 properly wired up) [Fix] This was addressed by upstream commit c77804be53369 ("net: hns: Fix WARNING when hns modules installed"). While the commit message suggests this was for a separate issue that we are not seeing (a WARNING message), it also resolves this issue. [Regression Risk] Restricted to the hns driver, which is only used by certain HiSilicon SOCs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818294/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic
** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: === SRU Justification === [Impact] Realtek 8723be's ant_sel parameter stops working since 4.15.0-33.36. [Fix] The commit that causes the regression works in mainline, so there are some functional dependencies are not in 4.15. Finding those dependencies can be hard since I don't have the hardware to test with, also pulling new commits may cause new regression. So the safest way to deal with this bug is to simply revert the regression commit. [Test] User confirmed reverting the commit can fix the issue. [Regression Potential] Low. Realtek 8723be works without this commit. === Original Bug Report === When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1234 F pulseaudio /dev/snd/controlC0: al 1234 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Notebook Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8137 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.02 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802480] Re: Crash when using IPsec VTI interfaces on 4.15 and 4.18.
The commit is already in upstream stable tree, so it will be included to future Ubuntu kernel 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/1802480 Title: Crash when using IPsec VTI interfaces on 4.15 and 4.18. Status in linux package in Ubuntu: Confirmed Bug description: Hey! After upgrading a few VPN to 4.15.0-38.41 (either Xenial or Bionic), we get random crashes. This also happens with the 4.18 in bionic- proposed. These crashes didn't happen with 4.4 from Xenial. Here is a stack trace: [ 31.154360] BUG: unable to handle kernel NULL pointer dereference at 0038 [ 31.162233] PGD 0 P4D 0 [ 31.164786] Oops: [#1] SMP PTI [ 31.168291] CPU: 5 PID: 42 Comm: ksoftirqd/5 Not tainted 4.18.0-11-generic #12~18.04.1-Ubuntu [ 31.176854] Hardware name: Supermicro Super Server/X10SDV-4C-7TP4F, BIOS 1.0b 11/21/2016 [ 31.184980] RIP: 0010:vti_rcv_cb+0xb9/0x1a0 [ip_vti] [ 31.189962] Code: 8b 44 24 70 0f c8 89 87 b4 00 00 00 48 8b 86 20 05 00 00 8b 80 f8 14 00 00 85 c0 75 05 48 85 d2 74 0e 48 8b 43 58 48 83 e0 fe 40 38 04 74 7d 44 89 b3 b4 00 00 00 49 8b 44 24 20 48 39 86 20 [ 31.208916] RSP: 0018:bc61832e3920 EFLAGS: 00010246 [ 31.214160] RAX: RBX: 9a3504964a00 RCX: 0002 [ 31.221328] RDX: 9a351add4080 RSI: 9a351aa08000 RDI: 9a3504964a00 [ 31.228485] RBP: bc61832e3940 R08: 0004 R09: c0aa612b [ 31.235643] R10: 0008f09b99881884 R11: 1884bd4e2d6b1fac R12: 9a3507b31900 [ 31.242803] R13: 9a3507b31000 R14: R15: 9a3504964a00 [ 31.249964] FS: () GS:9a35bfd4() knlGS: [ 31.258077] CS: 0010 DS: ES: CR0: 80050033 [ 31.263848] CR2: 0038 CR3: 00041a40a003 CR4: 003606e0 [ 31.271004] DR0: DR1: DR2: [ 31.278163] DR3: DR6: fffe0ff0 DR7: 0400 [ 31.285320] Call Trace: [ 31.287789] xfrm4_rcv_cb+0x4a/0x70 [ 31.291297] xfrm_input+0x58f/0x8f0 [ 31.294807] vti_input+0xaa/0x110 [ip_vti] [ 31.298926] vti_rcv+0x33/0x3c [ip_vti] [ 31.302783] xfrm4_esp_rcv+0x39/0x50 [ 31.306375] ip_local_deliver_finish+0x62/0x200 [ 31.310923] ip_local_deliver+0xdf/0xf0 [ 31.314775] ? ip_rcv_finish+0x420/0x420 [ 31.318718] ip_rcv_finish+0x126/0x420 [ 31.322486] ip_rcv+0x28f/0x360 [ 31.325655] ? inet_del_offload+0x40/0x40 [ 31.329686] __netif_receive_skb_core+0x48c/0xb70 [ 31.334413] ? kmem_cache_alloc+0xb4/0x1d0 [ 31.338532] ? __build_skb+0x2b/0xf0 [ 31.342128] __netif_receive_skb+0x18/0x60 [ 31.346244] ? __netif_receive_skb+0x18/0x60 [ 31.350536] netif_receive_skb_internal+0x45/0xe0 [ 31.355263] napi_gro_receive+0xc5/0xf0 [ 31.359141] mlx5e_handle_rx_cqe+0x1b2/0x5d0 [mlx5_core] [ 31.364476] ? skb_release_all+0x24/0x30 [ 31.368430] mlx5e_poll_rx_cq+0xd3/0x990 [mlx5_core] [ 31.373432] mlx5e_napi_poll+0x9b/0xc60 [mlx5_core] [ 31.378333] ? __switch_to_asm+0x34/0x70 [ 31.382270] ? __switch_to_asm+0x40/0x70 [ 31.386214] ? __switch_to_asm+0x34/0x70 [ 31.391056] ? __switch_to_asm+0x40/0x70 [ 31.395905] ? __switch_to_asm+0x34/0x70 [ 31.400743] net_rx_action+0x140/0x3a0 [ 31.405379] ? __switch_to+0xad/0x500 [ 31.409887] __do_softirq+0xe4/0x2bb [ 31.414448] run_ksoftirqd+0x2b/0x40 [ 31.418862] smpboot_thread_fn+0xfc/0x170 [ 31.423700] kthread+0x121/0x140 [ 31.427701] ? sort_range+0x30/0x30 [ 31.432040] ? kthread_create_worker_on_cpu+0x70/0x70 [ 31.437816] ret_from_fork+0x35/0x40 [ 31.442219] Modules linked in: esp6 authenc echainiv xfrm6_mode_tunnel xfrm4_mode_tunnel xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key xfrm_algo ip_vti ip_tunnel ip6_vti ip6_tunnel tunnel6 8021q garp mrp stp llc bonding ipt_REJECT nf_reject_ipv4 nfnetlink_log n fnetlink xt_NFLOG xt_hl xt_limit xt_nat xt_TCPMSS xt_HL xt_comment xt_tcpudp xt_multiport xt_conntrack iptable_filter iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat xt_connmark xt_mark iptable_mangle xt_CT nf_conntrack xt_addrtype iptable_raw bpfilter ipmi_ssif gpio_ ich intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass intel_cstate intel_rapl_perf input_leds joydev mei_me intel_pch_thermal ioatdma mei lpc_ich ipmi_si ipmi_devintf ipmi_msghandler acpi_pad mac_hid sch_fq_codel [ 31.519488] ib_iser rdma_cm iw_cm ib_cm 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 raid0 multipath linear mlx5_ib ib_uverbs ib
[Kernel-packages] [Bug 1820366] Re: network install of xenial 16.04 fails with linux-generic package error
*** This bug is a duplicate of bug 1820755 *** https://bugs.launchpad.net/bugs/1820755 This is affecting us too in network installation, while deploying base from build during base installation it's throwing error 'Debootstrap failed with source code' -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820366 Title: network install of xenial 16.04 fails with linux-generic package error Status in linux package in Ubuntu: Confirmed Bug description: network installing xenial ubuntu is failing for myself and other people (as seen on the #ubuntu irc channel). I had this issue both with and without preseed. I am using the latest netboot kernel and initrd files from http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/installer- amd64/current/images/netboot/ ( I re-downloaded and checked the file digest). The latest version available from the above URL is 4.4.0-142 and the installer fails while installing 4.4.0-143. The following error messages seen during installation: Mar 16 01:20:12 in-target: Setting up linux-image-4.4.0-143-generic (4.4.0-143.169) ... Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: 50: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: Mar 16 01:20:12 in-target: linux-update-symlinks: not found Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dpkg: error processing package linux-image-4.4.0-143-generic (--configure): Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: subprocess installed post-installation script returned error exit status 127 Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dpkg: dependency problems prevent configuration of linux-modules-extra-4.4.0-143-generic: Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: linux-modules-extra-4.4.0-143-generic depends on linux-image-4.4.0-143-generic | linux-image-unsigned-4.4.0-143-generic; however: Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Package linux-image-4.4.0-143-generic is not configured yet. Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Package linux-image-unsigned-4.4.0-143-generic is not installed. Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dpkg: error processing package linux-modules-extra-4.4.0-143-generic (--configure): Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dependency problems - leaving unconfigured Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Setting up intel-microcode (3.20180807a.0ubuntu0.16.04.1) ... Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: update-initramfs: deferring update (trigger activated) Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: intel-microcode: microcode will be updated at next boot Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Setting up amd64-microcode (3.20180524.1~ubuntu0.16.04.2) ...^M Mar 16 01:20:12 in-target: update-initramfs: deferring update (trigger activated) Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: amd64-microcode: microcode will be updated at next boot Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dpkg: dependency problems prevent configuration of linux-image-generic: Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: linux-image-generic depends on linux-image-4.4.0-143-generic | linux-image-unsigned-4.4.0-143-generic; however: Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Package linux-image-4.4.0-143-generic is not configured yet. Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Package linux-image-unsigned-4.4.0-143-generic is not installed. Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: linux-image-generic depends on linux-modules-extra-4.4.0-143-generic; however: Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Package linux-modules-extra-4.4.0-143-generic is not configured yet. Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dpkg: error processing package linux-image-generic (--configure): Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dependency problems - leaving unconfigured Mar 16 01:20:12 in-target: ^M After having these issue with a preseed file, I started a PXE install without any preseed ( therefore answering the standard installer questions manually) but I still had the same error. I was told in the #ubuntu irc channel to set : d-i base-installer/kernel/image string linux-image-4.4.0-142-generic in my preseed file. This worked and the installer completed correctly without any failures. Previously my preseed file container: d-i base-installer/kernel/image string linux-generic but as I said above, even without a prese
[Kernel-packages] [Bug 1814069] Re: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814069 Title: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2 Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: === SRU Justification === [Impact] NULL pointer dereference in netvsc_probe(). Module hv_netvsc is included in initramfs, so this blocks the boot process. For Hyper-V only supports single channel, rndis_filter_device_add() bails early and jump to tag "out". Subsequent code calls rndis_filter_device_remove() and returns ERR_PTR(ret), where ret is 0 (sucess). Because of that, it passes IS_ERR(nvdev) check in netvsc_probe() and cause a NULL pointer dereference, as nvdev now is 0: ... if (nvdev->num_chn > 1) schedule_work(&nvdev->subchan_work); [Fix] Correctly return net_device at the end of rndis_filter_device_add(). [Test] Users report positive result. [Regression Potenial] Low. Trivial change, patches are in upstream sometime. === Original Bug Report === Ubuntu stuck on booting on HyperV Server 2008R2. I saw kernel messages, seems to load ram image the boot is stuck. Seems to be a problem with hyperv drivers propably harddrive. Reverted back to the previous kernel. Description:Ubuntu 18.04.1 LTS Release:18.04Description:Ubuntu 18.04.1 LTS Release:18.04 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 31 08:52 seq crw-rw 1 root audio 116, 33 Jan 31 08:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=86036ccb-bc11-11e8-93c9-00155dfd7535 ro maybe-ubiquity ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090004 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 8531-7125-9206-2460-7819-2663-90 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090004:bd03/19/2009:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: dmi.product.name: Virtual Machine dmi.product.version: 7.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819486] Re: Crash from :i915 module with 4.15.0-46-generic using multi-display
** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819486 Title: Crash from :i915 module with 4.15.0-46-generic using multi-display Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: === SRU Justification === [Impact] 4.15.0-46 breaks once worked external display over docking. [Fix] Revert the commit that causes regression. [Test] User confirms reverting the commit solves the regression. [Regression Potential] Low. Docking can works without this commit on Bionic kernel. While previously working using 4.15.0-45-generic, booting my thinkpad T480 on a dock with additional screen connected and "kernel 4.15.0-46-generic" lead to a crash of the system. === Original Bug Report === Laptop is running Ubuntu 18.04.2 LTS. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: user 3449 F...m pulseaudio /dev/snd/controlC1: user 3449 F pulseaudio /dev/snd/pcmC0D0p: user 3449 F...m pulseaudio /dev/snd/controlC0: user 3449 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7 InstallationDate: Installed on 2018-06-28 (256 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20L5000AFR Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin netdev plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET37W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5000AFR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L5000AFR:pvrThinkPadT480:rvnLENOVO:rn20L5000AFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5000AFR dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819486/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820153] Re: [SRU][B/C/OEM]IOMMU: add kernel dma protection
** Changed in: linux-oem (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1820153 Title: [SRU][B/C/OEM]IOMMU: add kernel dma protection Status in HWE Next: In Progress Status in linux package in Ubuntu: Invalid Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Bionic: New Status in linux-oem source package in Bionic: Fix Committed Status in linux source package in Cosmic: New Status in linux-oem source package in Cosmic: New Bug description: SRU justification: [Impact] OS can use IOMMU to defend against DMA attacks from a PCI device like thunderbolt one. Intel adds DMA_CTRL_PLATFORM_OPT_IN_FLAG flag in DMAR ACPI table. Use this flag to enable IOMMU and use _DSD to identify untrusted PCI devices. [Fix] Enable IOMMU when BIOS supports DMA opt in flag and ExternalFacingPort in _DSD. Disable ATS on the untrusted PCI device. [Test] Tested on 2 Intel platforms that supports DMA opt in flag with a thunderbolt dock station. iommu enabled as expected with this fix. [Regression Potential] Upstream fix, Verified on supported platforms, no affection on not supported platforms. Backported changes are fairly minimal. These patches are included in 5.0 kernel, disco is good. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1820153/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819921] Re: [SRU] [B/OEM] Fix ACPI bug that causes boot failure
** Also affects: linux-oem (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: linux-oem (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1819921 Title: [SRU] [B/OEM] Fix ACPI bug that causes boot failure Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Committed Bug description: [Impact] Some lenovo laptops failed to boot at a very early stage, only blackscreen shown. [Fix] Some system BIOS set definition in if statement, it would be deferred to be loaded. Some devices would not work properly and cause a system lockup. add a quirk for these laptops to execute all acpi tables and make system work properly. [Test] Tested on several laptops, the laptop that failed to boot boots well. Other laptops still works fine. [Regression Potential] SAUCE patch.Low, specific changes depends on hardware. Upstream fix: commit 5a8361f7ecceaed64b4064000d16cb703462be49 Author: Schmauss, Erik Date: Thu Feb 15 13:09:30 2018 -0800 ACPICA: Integrate package handling with module-level code Due to the lots of changes in this commit and other regressions concern So made a sauce patch in Bionic kernel with the specific BIOS series. Verified on several laptops. Fix boot failure and no regression found. The upstream fix is in 4.17-rc1, so only Bionic/OEM 4.15 kernels need it. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1819921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822036] [NEW] Add devicetree overlay to support the SLB9670 TPM module for RPi
Public bug reported: [Impact] * Currently it is not possible to use the SLB9670 TPM module with Ubuntu Core since we do not ship the required devicetree overlay to enable it https://github.com/raspberrypi/linux/commit/c28ac2dc08bd73963f953a757a3362c64b5524ed and there is no way for snaps to easily add their own devicetree overlay. Finally it is not practical to expect Ubuntu Core users to have to build and maintain their own kernels just to support a particular hardware device. For background discussion, refer to this thread on the snapcraft forums - https://forum.snapcraft.io/t/guidance-on-snap-interface-to-load-a -device-tree-overlay-on-rpi-core18/10106/11 * Once this overlay is added, then users simply need to modify the boot config.txt to enable the overlay to be loaded automatically. In the future, snapd might also enable support so this can be managed by snapd via snap system configuration. [Test Case] * Boot a RPi with a SLB9670 connected, modify /boot/config.txt to specify dtoverlay=tpm-slb9670, then load the tpm_tis_spi module and /dev/tpm0 should the be available. [Regression Potential] * Almost zero chance of regression potential since this is simply adding a new overlay to the kernel. This is not loaded automatically so there is no real chance of regression. [Other Info] * All that is required for this SRU is to merge https://github.com/raspberrypi/linux/commit/c28ac2dc08bd73963f953a757a3362c64b5524ed to the current bionic raspi kernel branch. ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New -- 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/1822036 Title: Add devicetree overlay to support the SLB9670 TPM module for RPi Status in linux-raspi2 package in Ubuntu: New Bug description: [Impact] * Currently it is not possible to use the SLB9670 TPM module with Ubuntu Core since we do not ship the required devicetree overlay to enable it https://github.com/raspberrypi/linux/commit/c28ac2dc08bd73963f953a757a3362c64b5524ed and there is no way for snaps to easily add their own devicetree overlay. Finally it is not practical to expect Ubuntu Core users to have to build and maintain their own kernels just to support a particular hardware device. For background discussion, refer to this thread on the snapcraft forums - https://forum.snapcraft.io/t/guidance-on-snap-interface-to- load-a-device-tree-overlay-on-rpi-core18/10106/11 * Once this overlay is added, then users simply need to modify the boot config.txt to enable the overlay to be loaded automatically. In the future, snapd might also enable support so this can be managed by snapd via snap system configuration. [Test Case] * Boot a RPi with a SLB9670 connected, modify /boot/config.txt to specify dtoverlay=tpm-slb9670, then load the tpm_tis_spi module and /dev/tpm0 should the be available. [Regression Potential] * Almost zero chance of regression potential since this is simply adding a new overlay to the kernel. This is not loaded automatically so there is no real chance of regression. [Other Info] * All that is required for this SRU is to merge https://github.com/raspberrypi/linux/commit/c28ac2dc08bd73963f953a757a3362c64b5524ed to the current bionic raspi kernel branch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1822036/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811815] Re: Lenovo ideapad 330-15ICH Wifi rfkill hard blocked
** Also affects: linux (Ubuntu Disco) Importance: Undecided Assignee: TJ (tj) Status: Fix Committed ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Cosmic) Status: New => Fix Committed ** Changed in: linux (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811815 Title: Lenovo ideapad 330-15ICH Wifi rfkill hard blocked 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: === SRU Justification === [Impact] Lenovo ideapad 330-15ICH Wifi rfkill hard blocked [Fix] The platform in question doesn't have hardware RF switch, so quirk it off. [Test] User confirm it fixes the issue. [Regression Potential] Minimal. This fix is limited to one specific platform. === Original Bug Report === The issue here is that the drivers/platform/x86/ideapad_laptop.c module assumes the Lenovo Ideapad 330-15ICH has a hardware RF-kill switch, reads the I/O port for its state, gets a zero, and therefore reports to the kernel that RFkill is hard-blocked. The current workaround is to blacklist the module to stop it being loaded. I've attached a simple patch for the module that teaches it that this model does not have a hardware RF kill switch. Original Report - Ubuntu 18.10 does not detect the Intel Dual Band Wireless-AC 3165 card, specifically on a Lenovo ideapad 330 laptop. A current workaround: - Blacklist the "ideapad-laptop" module. - Edit/create a file in "/etc/modprobe.d/" and name it "blacklist.conf" or something similar (if it does not already exist), and append "blacklist ideapad-laptop" to the file. Save and reboot. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dustin 1948 F pulseaudio /dev/snd/pcmC0D0p: dustin 1948 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 15 04:08:20 2019 InstallationDate: Installed on 2019-01-15 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:210e Acer, Inc Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 3938:1047 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81FK ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=fa5d161c-779c-4cf7-aa07-6da06d655747 ro acpi_osi=! "acpi_osi=Windows 2012" quiet splash nouveau.modeset=0 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7ZCN28WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15ICH dmi.modalias: dmi:bvnLENOVO:bvr7ZCN28WW:bd07/17/2018:svnLENOVO:pn81FK:pvrLenovoideapad330-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15ICH: dmi.product.family: ideapad 330-15ICH dmi.product.name: 81FK dmi.product.sku: LENOVO_MT_81FK_BU_idea_FM_ideapad 330-15ICH dmi.product.version: Lenovo ideapad 330-15ICH dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818204] Re: Qualcomm Atheros QCA9377 wireless does not work
** Also affects: network-manager (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: network-manager (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818204 Title: Qualcomm Atheros QCA9377 wireless does not work Status in linux package in Ubuntu: Fix Committed Status in network-manager package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in network-manager source package in Bionic: New Status in linux source package in Cosmic: Fix Committed Status in network-manager source package in Cosmic: New Bug description: === SRU Justification === [Impact] Lenovo ideapad 530S-14ARR Wifi rfkill hard blocked [Fix] The platform in question doesn't have hardware RF switch, so quirk it off. [Test] User confirm it fixes the issue. [Regression Potential] Minimal. This fix is limited to one specific platform. === Original Bug Report === I have Lenovo 530s laptop with Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31). The menu shows that wireless is off. Turning on the wireless from the menu does not do anything. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 1 11:42:34 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-02-20 (8 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IpRoute: default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100 130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 130.232.69.176 metric 100 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 ada277fe-966d-33ff-aba2-8ba32d6ce5a9 ethernet 155143 pe 1. maaliskuuta 2019 11.42.13 yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes enx00e04c704f68 activated /org/freedesktop/NetworkManager/ActiveConnection/11 -- virbr0 dc46fe89-5b22-438a-85d5-37be48a077ea bridge 155143 pe 1. maaliskuuta 2019 11.42.13 no 0 no/org/freedesktop/NetworkManager/Settings/2 yes virbr0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled disabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sami 1315 F pulseaudio /dev/snd/controlC0: sami 1315 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-02-20 (11 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IpRoute: default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100 130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 130.232.69.176 metric 100 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown MachineType: LENOVO 81H1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.6-2ubuntu1.1 PackageArchitecture: amd64 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: B
[Kernel-packages] [Bug 1821395] Re: fscache: jobs might hang when fscache disk is full
** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821395 Title: fscache: jobs might hang when fscache disk is full Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: [Impact] * fscache issue where jobs get hung when fscache disk is full. * trivial upstream fix; already applied in X/D, required in B/C: commit c5a94f434c82 ("fscache: fix race between enablement and dropping of object"). [Test Case] * Test kernel verified / regression-tested by reporter. * Apparently there's no simple test case, but these are the conditions to hit the problem: 1) The active dataset size is equal to the cache disk size. The application reads the data over and over again. 2) Disk is near full (90%+) 3) cachefilesd in userspace is trying to cull the old objects while new objects are being looked up. 4) new cachefiles are created and some fail with no disk space. 5) race in dropping object state machine and deferred lookup state machine causes the hang. 6) HUNG in fscache_wait_for_deferred_lookup for clear bit FSCACHE_COOKIE_LOOKING_UP cookie->flags. [Regression Potential] * Low; contained in fscache; no further fixes applied upstream. * This patch is applied in a stable tree (linux-4.4.y). [Original Description] An user reported an fscache issue where jobs get hung when the fscache disk is full. After investigation, it's been found to be an issue already reported/fixed upstream, by commit c5a94f434c82 ("fscache: fix race between enablement and dropping of object"). This patch is required in Bionic and Cosmic, and it's applied in Xenial (via stable) and Disco. Apparently there's no simple test case, but these are the conditions to hit the problem: 1) The active dataset size is equal to the cache disk size. The application reads the data over and over again. 2) Disk is near full (90%+) 3) cachefilesd in userspace is trying to cull the old objects while new objects are being looked up. 4) new cachefiles are created and some fail with no disk space. 5) race in dropping object state machine and deferred lookup state machine causes the hang. 6) HUNG in fscache_wait_for_deferred_lookup for clear bit FSCACHE_COOKIE_LOOKING_UP cookie->flags. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821395/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822032] 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 1822032 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 ** Changed in: linux (Ubuntu Cosmic) 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/1822032 Title: perf_event_open02 in ubuntu_ltp_syscalls failed on Cosmic s390x Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Cosmic: Incomplete Bug description: Failed on Cosmic s390x KVM, zVM, LPAR: startup='Wed Mar 20 10:06:36 2019' perf_event_open02 1 TBROK : perf_event_open02.c:275: perf_event_open failed: errno=ENOENT(2): No such file or directory perf_event_open02 2 TBROK : perf_event_open02.c:275: Remaining cases broken tag=perf_event_open02 stime=1553076396 dur=0 exit=exited stat=2 core=no cu=0 cs=0 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-17-generic 4.18.0-17.18 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic s390x NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.2 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Thu Mar 28 04:34:19 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=86fb6fff-dc2f-4ffd-9ea8-a15d77ae3eaa crashkernel=196M RelatedPackageVersions: linux-restricted-modules-4.18.0-17-generic N/A linux-backports-modules-4.18.0-17-generic N/A linux-firmware 1.175.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1822032/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822032] [NEW] perf_event_open02 in ubuntu_ltp_syscalls failed on Cosmic s390x
Public bug reported: Failed on Cosmic s390x KVM, zVM, LPAR: startup='Wed Mar 20 10:06:36 2019' perf_event_open02 1 TBROK : perf_event_open02.c:275: perf_event_open failed: errno=ENOENT(2): No such file or directory perf_event_open02 2 TBROK : perf_event_open02.c:275: Remaining cases broken tag=perf_event_open02 stime=1553076396 dur=0 exit=exited stat=2 core=no cu=0 cs=0 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-17-generic 4.18.0-17.18 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic s390x NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.2 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Thu Mar 28 04:34:19 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=86fb6fff-dc2f-4ffd-9ea8-a15d77ae3eaa crashkernel=196M RelatedPackageVersions: linux-restricted-modules-4.18.0-17-generic N/A linux-backports-modules-4.18.0-17-generic N/A linux-firmware 1.175.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Tags: apport-bug cosmic package-from-proposed s390x ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: ubuntu-kernel-tests 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/1822032 Title: perf_event_open02 in ubuntu_ltp_syscalls failed on Cosmic s390x Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Cosmic: New Bug description: Failed on Cosmic s390x KVM, zVM, LPAR: startup='Wed Mar 20 10:06:36 2019' perf_event_open02 1 TBROK : perf_event_open02.c:275: perf_event_open failed: errno=ENOENT(2): No such file or directory perf_event_open02 2 TBROK : perf_event_open02.c:275: Remaining cases broken tag=perf_event_open02 stime=1553076396 dur=0 exit=exited stat=2 core=no cu=0 cs=0 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-17-generic 4.18.0-17.18 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic s390x NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.2 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Thu Mar 28 04:34:19 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=86fb6fff-dc2f-4ffd-9ea8-a15d77ae3eaa crashkernel=196M RelatedPackageVersions: linux-restricted-modules-4.18.0-17-generic N/A linux-backports-modules-4.18.0-17-generic N/A linux-firmware 1.175.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1822032/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775784] Re: inotify08 in LTP syscall test failed with X/X-LTS/X-HWE/A/B kernel
Didn't see this on C P8/P9 anymore. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775784 Title: inotify08 in LTP syscall test failed with X/X-LTS/X-HWE/A/B kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: Triaged Bug description: <<>> tag=inotify08 stime=1527762360 cmdline="inotify08" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s inotify08.c:201: INFO: ovl/test_file ino=27918358, dev=8:1 inotify08.c:212: INFO: ovl/test_file ino=27918363, dev=8:1 inotify08.c:150: FAIL: didn't get event: mask=4 inotify08.c:150: FAIL: didn't get event: mask=20 inotify08.c:150: FAIL: didn't get event: mask=8 Summary: passed 0 failed 3 skipped 0 warnings 0 <<>> initiation_status="ok" duration=1 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24~16.04.1 ProcVersionSignature: User Name 4.15.0-22.24~16.04.1-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri Jun 8 08:08:27 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1775784/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1778705] Re: skey in ubuntu-kvm-unit-test failed on Xenial zVM
Out-of-scope, set priority to low. ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Summary changed: - skey in ubuntu-kvm-unit-test failed on Xenial zVM + skey in ubuntu-kvm-unit-test failed on X/C zVM ** Changed in: linux (Ubuntu) Importance: Medium => Low ** Changed in: linux (Ubuntu Xenial) Importance: Medium => Low ** Changed in: linux (Ubuntu Cosmic) Importance: Undecided => Low ** Changed in: ubuntu-kernel-tests Importance: Undecided => Low -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1778705 Title: skey in ubuntu-kvm-unit-test failed on X/C zVM Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Cosmic: New Bug description: TESTNAME=skey TIMEOUT=90s ACCEL= ./s390x/run s390x/skey.elf -smp 1 FAIL skey (2 tests) This is the only failure in this test suite on Xenial zVM, need to run it manually to see what's going on. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-130-generic 4.4.0-130.156 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: [ 3288.479241] audit_printk_skb: 153 callbacks suppressed [ 3288.479246] audit: type=1400 audit(1530011067.825:63): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/snapd/snap-confine" pid=6480 comm="apparmor_parser" [ 3288.510095] audit: type=1400 audit(1530011067.865:64): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" pid=6480 comm="apparmor_parser" Date: Tue Jun 26 07:05:34 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=44b0b919-a1a4-4849-9425-e71d4ac87d85 crashkernel=196M nobp=1 BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-130-generic N/A linux-backports-modules-4.4.0-130-generic N/A linux-firmware 1.157.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1778705/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812988] Re: ff76b0565523319d7c1c0b51d5a5a8915d33efab in ubuntu_btrfs_kernel_fixes generate kernel traces on Cosmic
Found on Cosmic i386 node pepe ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Tags added: i386 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812988 Title: ff76b0565523319d7c1c0b51d5a5a8915d33efab in ubuntu_btrfs_kernel_fixes generate kernel traces on Cosmic Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Cosmic: New Bug description: This issue can only be reproduced on certain HW, node "daedalus" (AMD64), "modoc" P8 And this can only be reproduced when running the whole test suite, it will be fine if you just run this test: Invoking test ff76b0565523319d7c1c0b51d5a5a8915d33efab fix ff76b0565523319d7c1c0b51d5a5a8915d33efab Btrfs: Don't allocate inode that is already in use Due to an off-by-one error, it is possible to reproduce a bug when the inode cache is used. The same inode number is assigned twice, the second time this leads to an EEXIST in btrfs_insert_empty_items(). Create subvolume '/tmp/mnt-ff76b0565523319d7c1c0b51d5a5a8915d33efab/s1' Create a snapshot of '/tmp/mnt-ff76b0565523319d7c1c0b51d5a5a8915d33efab/s1' in '/tmp/mnt-ff76b0565523319d7c1c0b51d5a5a8915d33efab/s2' Create a snapshot of '/tmp/mnt-ff76b0565523319d7c1c0b51d5a5a8915d33efab/s2' in '/tmp/mnt-ff76b0565523319d7c1c0b51d5a5a8915d33efab/s3' Found kernel issue: [ 2713.591492] WARNING: CPU: 18 PID: 61234 at fs/btrfs/inode.c:9256 btrfs_destroy_inode+0x1d7/0x210 [btrfs] [ 2713.591494] Modules linked in: btrfs zstd_compress nls_iso8859_1 ipmi_ssif intel_rapl skx_edac nfit x86_pkg_temp_thermal intel_powerclamp joydev input_leds coretemp kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel intel_cstate intel_rapl_perf mei_me mei ioatdma ipmi_si dca ipmi_devintf ipmi_msghandler acpi_pad acpi_power_meter 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 raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ast i2c_algo_bit ttm hid_generic drm_kms_helper aesni_intel aes_x86_64 syscopyarea usbhid sysfillrect crypto_simd hid sysimgblt cryptd fb_sys_fops ahci glue_helper i40e drm lpc_ich libahci wmi [last unloaded: zstd_compress] [ 2713.591577] CPU: 18 PID: 61234 Comm: umount Tainted: GW 4.18.0-14-generic #15-Ubuntu [ 2713.591579] Hardware name: Intel Corporation S2600WFD/S2600WFD, BIOS SE5C620.86B.01.00.0412.020920172159 02/09/2017 [ 2713.591611] RIP: 0010:btrfs_destroy_inode+0x1d7/0x210 [btrfs] [ 2713.591612] Code: d0 31 d2 48 89 83 e0 fe ff ff 49 8b 85 e0 03 00 00 48 85 c0 0f 94 c2 e9 4c ff ff ff 0f 0b e9 60 fe ff ff 0f 0b e9 67 fe ff ff <0f> 0b e9 6e fe ff ff 0f 0b e9 75 fe ff ff 0f 0b e9 7c fe ff ff 0f [ 2713.591666] RSP: 0018:a966b0bbfc48 EFLAGS: 00010206 [ 2713.591669] RAX: 90c5bf3e6800 RBX: 90c5e06bbc30 RCX: [ 2713.591671] RDX: RSI: RDI: 90c5e06bbc30 [ 2713.591673] RBP: a966b0bbfc78 R08: 0001 R09: c08fe101 [ 2713.591674] R10: 90c58aac2510 R11: 0001 R12: 90c5e06bbcb8 [ 2713.591676] R13: c0972940 R14: 90c5e06bbd88 R15: a966b0bbfd48 [ 2713.591679] FS: 7f31837e8080() GS:90c61fa8() knlGS: [ 2713.591681] CS: 0010 DS: ES: CR0: 80050033 [ 2713.591682] CR2: 7f3183b70308 CR3: 00080167a002 CR4: 007606e0 [ 2713.591685] DR0: DR1: DR2: [ 2713.591686] DR3: DR6: fffe0ff0 DR7: 0400 [ 2713.591688] PKRU: 5554 [ 2713.591689] Call Trace: [ 2713.591702] destroy_inode+0x3e/0x60 [ 2713.591707] evict+0x139/0x1a0 [ 2713.591711] iput+0x148/0x210 [ 2713.591739] free_fs_root+0x1b/0xc0 [btrfs] [ 2713.591766] btrfs_drop_and_free_fs_root+0x7c/0xf0 [btrfs] [ 2713.591793] btrfs_free_fs_roots+0xdc/0x170 [btrfs] [ 2713.591824] ? __btrfs_sysfs_remove_fsid+0x68/0x70 [btrfs] [ 2713.591852] close_ctree+0x10c/0x2d0 [btrfs] [ 2713.591872] btrfs_put_super+0x15/0x20 [btrfs] [ 2713.591878] generic_shutdown_super+0x72/0x110 [ 2713.591882] kill_anon_super+0x12/0x20 [ 2713.591904] btrfs_kill_super+0x18/0x110 [btrfs] [ 2713.591906] deactivate_locked_super+0x3a/0x80 [ 2713.591907] deactivate_super+0x51/0x60 [ 2713.591909] cleanup_mnt+0x3f/0x70 [ 2713.591910] __cleanup_mnt+0x12/0x20 [ 2713.591915] task_work_run+0x9d/0xc0 [ 2713.591920] exit_to_usermode_loop+0xed/0xf0 [ 2713.591922] do_syscall_64+0x
[Kernel-packages] [Bug 1821390] 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 1821390 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 ** Changed in: linux (Ubuntu Bionic) Status: New => Incomplete ** Changed in: linux (Ubuntu Cosmic) 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/1821390 Title: apic-split will fail in kvm_units_tests on aws i3.metal Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-aws source package in Bionic: New Status in linux source package in Cosmic: Incomplete Status in linux-aws source package in Cosmic: 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=apic-split TIMEOUT=90s ACCEL= ./x86/run x86/apic.flat -smp 2 -cpu qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split root@ip-172-31-5-254:/home/ubuntu/kvm-unit-tests# TESTNAME=apic-split TIMEOUT=90s ACCEL= ./x86/run x86/apic.flat -smp 2 -cpu qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/apic.flat -smp 2 -cpu qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split # -initrd /tmp/tmp.ZHQwPUOuLD qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.8001H:ECX.svm [bit 2] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.8001H:ECX.svm [bit 2] enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 459000 cr4 = 20 apic version: 1050014 PASS: apic existence PASS: xapic id matches cpuid PASS: writeable xapic id PASS: non-writeable x2apic id PASS: sane x2apic id PASS: x2apic id matches cpuid PASS: correct xapic id after reset PASS: apic_disable: Local apic disabled PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is clear PASS: apic_disable: *0xfee00030: PASS: apic_disable: CR8: 0 PASS: apic_disable: CR8: f PASS: apic_disable: *0xfee00080: PASS: apic_disable: Local apic enabled in xAPIC mode PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set PASS: apic_disable: *0xfee00030: 1050014 PASS: apic_disable: *0xfee00080: 0 PASS: apic_disable: *0xfee00080: f0 PASS: apic_disable: Local apic enabled in x2APIC mode PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set PASS: apic_disable: *0xfee00030: PASS: apic_disable: CR8: 0 PASS: apic_disable: CR8: f PASS: apic_disable: *0xfee00080: x2apic enabled PASS: x2apic enabled to invalid state PASS: x2apic enabled to apic enabled PASS: x2apic enabled to disabled state PASS: disabled to invalid state PASS: disabled to x2apic enabled PASS: apic enabled to invalid state PASS: apicbase: relocate apic PASS: apicbase: reserved physaddr bits PASS: apicbase: reserved low bits PASS: self ipi starting broadcast (x2apic) PASS: APIC physical broadcast address PASS: APIC physical broadcast shorthand FAIL: PV IPIs testing PASS: nmi-after-sti PASS: multiple nmi PASS: APIC LVT timer one shot starting apic change mode PASS: TMICT value reset PASS: TMCCT should have a non-zero value PASS: TMCCT should have reached 0 PASS: TMCCT should have a non-zero value PASS: TMCCT should not be reset to TMICT value PASS: TMCCT should be reset to the initial-count PASS: TMCCT should not be reset to init PASS: TMCCT should have reach zero PASS: TMCCT should stay at zero PASS: tsc deadline timer PASS: tsc deadline timer clearing SUMMARY: 51 tests, 1 unexpected failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1821390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821903] Re: svm in ubuntu_kvm_unit_test failed on 3.13 / 4.4
** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux-signed-lts-xenial (Ubuntu Cosmic) Importance: Undecided Status: New ** No longer affects: linux-signed-lts-xenial (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/1821903 Title: svm in ubuntu_kvm_unit_test failed on 3.13 / 4.4 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Trusty: Incomplete Status in linux-signed-lts-xenial source package in Trusty: New Status in linux source package in Xenial: Incomplete Status in linux-signed-lts-xenial source package in Xenial: New Status in linux source package in Cosmic: New Status in linux-signed-lts-xenial source package in Cosmic: New Bug description: This svm test timeouted on T-3.13 failed on T-4.4 with: root@gonzo:/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests# TESTNAME=svm TIMEOUT=90s ACCEL= ./x86/run x86/svm.flat -smp 2 -cpu qemu64,+svm timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/svm.flat -smp 2 -cpu qemu64,+svm # -initrd /tmp/tmp.PDi0UKyCcl enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 466000 cr4 = 20 PASS: null PASS: vmrun PASS: ioio PASS: vmrun intercept check PASS: cr3 read intercept PASS: cr3 read nointercept PASS: cr3 read intercept emulate PASS: dr intercept check PASS: msr intercept check PASS: mode_switch PASS: asid_zero PASS: sel_cr0_bug FAIL: tsc_adjust Latency VMRUN : max: 80562 min: 19763 avg: 20374 Latency VMEXIT: max: 83146 min: 20193 avg: 20834 PASS: latency_run_exit Latency VMLOAD: max: 38298 min: 4619 avg: 4838 Latency VMSAVE: max: 32870 min: 4637 avg: 4809 Latency STGI: max: 55478 min: 3846 avg: 3923 Latency CLGI: max: 67473 min: 3379 avg: 3437 PASS: latency_svm_insn SUMMARY: 15 tests, 1 unexpected failures ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.4.0-143-generic 4.4.0-143.169~14.04.2 ProcVersionSignature: User Name 4.4.0-143.169~14.04.2-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 Date: Wed Mar 27 11:00:42 2019 SourcePackage: linux-signed-lts-xenial UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1821903/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748103] Re: apic test in kvm-unit-test failed on E4v3 azure node with 4.13/4.14 kernel
** Tags added: cosmic ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux-azure-edge (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New -- 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/1748103 Title: apic test in kvm-unit-test failed on E4v3 azure node with 4.13/4.14 kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: New Status in linux-azure-edge package in Ubuntu: New Status in linux source package in Xenial: New Status in linux-azure source package in Xenial: New Status in linux-azure-edge source package in Xenial: New Status in linux source package in Cosmic: New Status in linux-azure source package in Cosmic: New Status in linux-azure-edge source package in Cosmic: New Bug description: With Joshua's comment in bug 1719524: "Nested KVM can only be tried on instance sizes with nested Hypervisor support: Ev3 and Dv3.", although the instance name is E4v3 here but I can start a KVM on it. Test apic will timeout on it. Steps: 1. git clone --depth=1 https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git 2. cd kvm-unit-tests; ./configure; make 3. Run the apic test as root: # TESTNAME=apic TIMEOUT=30 ACCEL= ./x86/run x86/apic.flat -smp 2 -cpu qemu64,+x2apic,+tsc-deadline timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/apic.flat -smp 2 -cpu qemu64,+x2apic,+tsc-deadline # -initrd /tmp/tmp.onXtr5JVp7 enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 459000 cr4 = 20 apic version: 1050014 PASS: apic existence PASS: xapic id matches cpuid PASS: writeable xapic id PASS: non-writeable x2apic id PASS: sane x2apic id FAIL: x2apic id matches cpuid PASS: correct xapic id after reset PASS: apic_disable: Local apic enabled PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set PASS: apic_disable: Local apic disabled PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is clear PASS: apic_disable: Local apic enabled PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set x2apic enabled PASS: x2apic enabled to invalid state PASS: x2apic enabled to apic enabled PASS: disabled to invalid state PASS: disabled to x2apic enabled PASS: apic enabled to invalid state PASS: apicbase: relocate apic PASS: apicbase: reserved physaddr bits PASS: apicbase: reserved low bits PASS: self ipi starting broadcast (x2apic) PASS: APIC physical broadcast address PASS: APIC physical broadcast shorthand PASS: nmi-after-sti qemu-system-x86_64: terminating on signal 15 from pid 7246 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.14.0-1004-azure-edge 4.14.0-1004.4 ProcVersionSignature: User Name 4.14.0-1004.4-username-edge 4.14.14 Uname: Linux 4.14.0-1004-azure-edge x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Thu Feb 8 06:00:55 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-azure-edge UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 DistroRelease: Ubuntu 16.04 Package: linux-azure-edge PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: User Name 4.13.0-1009.12-username 4.13.13 Tags: xenial uec-images Uname: Linux 4.13.0-1009-azure x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy libvirtd lxd netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1748103/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821064] Re: hns3: fix oops in hns3_clean_rx_ring()
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821064 Title: hns3: fix oops in hns3_clean_rx_ring() Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: [Impact] kernel oops [Test Case] Run netperf between two hosts. Doesn't 100% cause a crash, but works as a regression test. [Fix] d394d33bee224 net: hns3: add dma_rmb() for rx description [Regression Risk] Restricted to a driver specific to the hi1620 SoC. Since this adds a new read barrier, there is a potential performance regression risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821064/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821390] Re: apic-split will fail in kvm_units_tests on aws i3.metal
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821390 Title: apic-split will fail in kvm_units_tests on aws i3.metal Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux-aws package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-aws source package in Bionic: New Status in linux source package in Cosmic: New Status in linux-aws source package in Cosmic: 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=apic-split TIMEOUT=90s ACCEL= ./x86/run x86/apic.flat -smp 2 -cpu qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split root@ip-172-31-5-254:/home/ubuntu/kvm-unit-tests# TESTNAME=apic-split TIMEOUT=90s ACCEL= ./x86/run x86/apic.flat -smp 2 -cpu qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/apic.flat -smp 2 -cpu qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split # -initrd /tmp/tmp.ZHQwPUOuLD qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.8001H:ECX.svm [bit 2] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.8001H:ECX.svm [bit 2] enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 459000 cr4 = 20 apic version: 1050014 PASS: apic existence PASS: xapic id matches cpuid PASS: writeable xapic id PASS: non-writeable x2apic id PASS: sane x2apic id PASS: x2apic id matches cpuid PASS: correct xapic id after reset PASS: apic_disable: Local apic disabled PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is clear PASS: apic_disable: *0xfee00030: PASS: apic_disable: CR8: 0 PASS: apic_disable: CR8: f PASS: apic_disable: *0xfee00080: PASS: apic_disable: Local apic enabled in xAPIC mode PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set PASS: apic_disable: *0xfee00030: 1050014 PASS: apic_disable: *0xfee00080: 0 PASS: apic_disable: *0xfee00080: f0 PASS: apic_disable: Local apic enabled in x2APIC mode PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set PASS: apic_disable: *0xfee00030: PASS: apic_disable: CR8: 0 PASS: apic_disable: CR8: f PASS: apic_disable: *0xfee00080: x2apic enabled PASS: x2apic enabled to invalid state PASS: x2apic enabled to apic enabled PASS: x2apic enabled to disabled state PASS: disabled to invalid state PASS: disabled to x2apic enabled PASS: apic enabled to invalid state PASS: apicbase: relocate apic PASS: apicbase: reserved physaddr bits PASS: apicbase: reserved low bits PASS: self ipi starting broadcast (x2apic) PASS: APIC physical broadcast address PASS: APIC physical broadcast shorthand FAIL: PV IPIs testing PASS: nmi-after-sti PASS: multiple nmi PASS: APIC LVT timer one shot starting apic change mode PASS: TMICT value reset PASS: TMCCT should have a non-zero value PASS: TMCCT should have reached 0 PASS: TMCCT should have a non-zero value PASS: TMCCT should not be reset to TMICT value PASS: TMCCT should be reset to the initial-count PASS: TMCCT should not be reset to init PASS: TMCCT should have reach zero PASS: TMCCT should stay at zero PASS: tsc deadline timer PASS: tsc deadline timer clearing SUMMARY: 51 tests, 1 unexpected failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1821390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821961] Re: Fix for dual Intel NVMes
** Tags added: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821961 Title: Fix for dual Intel NVMes Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: In Progress Bug description: [Impact] SRU for LP: #1811755 doesn't really fix the issue. Only one of the two NVMe can be correctly enumerated. [Fix] There are two separate entries for the Intel NVMe device. Fix that. [Test] User confirms it works. [Regression Potential] The fix limits to Intel 760p/Pro 7600p SSD, and the fix has been verified by the bug reporter. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821961] Re: Fix for dual Intel NVMes
** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821961 Title: Fix for dual Intel NVMes Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: In Progress Bug description: [Impact] SRU for LP: #1811755 doesn't really fix the issue. Only one of the two NVMe can be correctly enumerated. [Fix] There are two separate entries for the Intel NVMe device. Fix that. [Test] User confirms it works. [Regression Potential] The fix limits to Intel 760p/Pro 7600p SSD, and the fix has been verified by the bug reporter. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821936] Re: ALC274 unsupported
If the problem is the kernel version then please try to find the closest two versions where one works and the other does not, from this list: https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821936 Title: ALC274 unsupported Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1821936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821936] Re: ALC274 unsupported
Derek, are you saying kernel 4.18 (or earlier) does not have the bug? ** Changed in: alsa-driver (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/1821936 Title: ALC274 unsupported Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1821936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821929] Re: Bluetooth mouse is not able to connect
I think we should work on releasing the gnome-bluetooth fix for bug 1773897 before assessing whether or not this is a different issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1821929 Title: Bluetooth mouse is not able to connect Status in bluez package in Ubuntu: New Bug description: I recently bought not expensive wireless mouse with bluetooth support: https://www.aliexpress.com/item/Wireless-Mouse-Bluetooth-Mouse-Silent-Computer-Mouse-PC-Mause-Wireless-Rechargeable-Ergonomic-Optical-USB-Mice-2/32879862474.html?spm=a2g0s.12269583.0.0.36ab310dUGrVZS I works in MacOS X and Windows but doesn't work in Linux. I suppose I can debug that mouse under Windows to collect more information if I have proper instructions. I collected some information about that mouse: # uname -a Linux asus-N752VX 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux # lsb_release -a Distributor ID:Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename:bionic # lsusb Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 0bda:8763 Realtek Semiconductor Corp. (BT usb) Bus 001 Device 002: ID 0bda:57f6 Realtek Semiconductor Corp. (Web cam) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub # usb-devices T: Bus=01 Lev=01 Prnt=01 Port=08 Cnt=04 Dev#= 6 Spd=12 MxCh= 0 D: Ver= 2.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=0bda ProdID=8763 Rev=02.00 S: Manufacturer=Realtek S: Product=Bluetooth Radio S: SerialNumber=00e04c01 C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=500mA I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb # bluetoothctl --version bluetoothctl: 5.48 # hciconfig -a hci0:Type: Primary Bus: USB BD Address: 94:E9:79:1A:89:1D ACL MTU: 820:8 SCO MTU: 255:16 UP RUNNING PSCAN RX bytes:1604 acl:0 sco:0 events:170 errors:0 TX bytes:28036 acl:0 sco:0 commands:166 errors:0 Features: 0xff 0xff 0xff 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT Name: 'asus-N752VX' Class: 0x1c010c Service Classes: Rendering, Capturing, Object Transfer Device Class: Computer, Laptop HCI Version: 4.0 (0x6) Revision: 0xe3e LMP Version: 4.0 (0x6) Subversion: 0x4380 Manufacturer: Realtek Semiconductor Corporation (93) # bluetoothctl [NEW] Controller 94:E9:79:1A:89:1D asus-N752VX [default] [NEW] Device 5A:4B:3C:0E:07:B2 Bluetooth Mouse 4.0 # show Controller 94:E9:79:1A:89:1D (public) Name: asus-N752VX Alias: asus-N752VX Class: 0x001c010c Powered: yes Discoverable: no Pairable: yes UUID: Headset AG(1112--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: OBEX Object Push (1105--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: IrMC Sync (1104--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: Vendor specific (5005--1000-8000-0002ee01) UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb) UUID: Phonebook Access Server (112f--1000-8000-00805f9b34fb) UUID: Message Access Server (1132--1000-8000-00805f9b34fb) UUID: Headset (1108--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0530 Discovering: no # devices Device 5A:4B:3C:0E:07:B2 Bluetooth Mouse 4.0 # info 5A:4B:3C:0E:07:B2 Device 5A:4B:3C:0E:07:B2 (public) Name: Bluetooth Mouse 4.0 Alias: Bluetooth Mouse 4.0 Class: 0x2580 Icon: input-mouse Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) Modalias: usb:v0A5Cp0001d0129 # paired-
[Kernel-packages] [Bug 1820755] Re: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found
I just found https://bugs.launchpad.net/ubuntu/xenial/+source/linux/+bug/1820419 - seems like the same root cause and linux-image-4.4.0-145-generic mentioned there (in -proposed) worked as I had hoped above (it has a version check on the Depends: linux-base, which pulls in the needed script from xenial-updates -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1820755 Title: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found Status in Blue Linux: New Status in linux package in Ubuntu: Confirmed Status in linux-base package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Status in linux-base source package in Xenial: Fix Released Bug description: Using a netboot install of Ubuntu 16.04 LTS server, the install fails when configuring the kernel. The failure will not let you move on. This seems to have happened after the release of https://lists.ubuntu.com/archives/ubuntu-security-announce/2019-March/004803.html The error logs Mar 18 17:09:50 in-target: Setting up linux-modules-4.4.0-143-generic (4.4.0-143.169) ... Mar 18 17:09:50 in-target: ^M Mar 18 17:09:51 in-target: Setting up linux-image-4.4.0-143-generic (4.4.0-143.169) ... Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: 50: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: Mar 18 17:09:51 in-target: linux-update-symlinks: not found Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: dpkg: error processing package linux-image-4.4.0-143-generic (--configure): Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: subprocess installed post-installation script returned error exit status 127 Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: dpkg: dependency problems prevent configuration of linux-modules-extra-4.4.0-143-generic: Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: linux-modules-extra-4.4.0-143-generic depends on linux-image-4.4.0-143-generic | linux-image-unsigned-4.4.0-143-generic; however: Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: Package linux-image-4.4.0-143-generic is not configured yet. Mar 18 17:09:51 in-target: ^M Mar To manage notifications about this bug go to: https://bugs.launchpad.net/bluelinux/+bug/1820755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821713] Re: linux-raspi2: 4.4.0-1106.114 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) => Taihsiang Ho (taihsiangho) -- 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/1821713 Title: linux-raspi2: 4.4.0-1106.114 -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: In Progress 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 Xenial: Confirmed 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: 1821724 phase: Testing phase-changed: Wednesday, 27. March 2019 14:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress 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/1821713/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821724] Re: linux: 4.4.0-145.171 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) => Taihsiang Ho (taihsiangho) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821724 Title: linux: 4.4.0-145.171 -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: In Progress 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: Confirmed 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 package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed 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 1819658 (trusty/linux-aws), bug 1819659 (trusty/linux-lts-xenial) derivatives: bug 1819654 (linux-euclid), bug 1820326 (linux-fips), bug 1821712 (linux-kvm), bug 1821713 (linux-raspi2), bug 1821723 (linux-snapdragon), bug 1821726 (linux-aws) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Wednesday, 27. March 2019 12:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-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/1821724/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820419] Re: linux-generic should depend on linux-base >=4.1
I'm not the original reporter, but I hit (and analyzed) what seems to be the same failure in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820755 I just switched our packer template over to -proposed to test this: i.e. changed it to use http://archive.ubuntu.com/ubuntu/dists/xenial- proposed/main/installer- amd64/20101020ubuntu451.28/images/netboot/mini.iso, added apt- setup/proposed=true to the kernel command-line) and I can confirm that this runs to completion (whereas xenial- updates/current/images/netboot/mini.iso errors out. debootstrap still initially installs the original xenial version of linux-base (but that's expected, since debootstrap is unable to look at multiple repositories), but it eventually gets upgraded debootstrap: Preparing to unpack .../linux-base_4.0ubuntu1_all.deb ... debootstrap: Unpacking linux-base (4.0ubuntu1) ... ... debootstrap: Setting up linux-base (4.0ubuntu1) ... ... but later on (once base-installer is doing the kernel using the real in-target apt-get) it picks up the new kernel from xednial-proposed, and that prods it to pick up the new linux-base from xenial-updates ... in-target: The following additional packages will be installed: in-target: linux-base linux-headers-4.4.0-145 linux-headers-4.4.0-145-generic in-target: linux-headers-generic linux-headers-virtual linux-image-4.4.0-145-generic in-target: linux-image-virtual linux-modules-4.4.0-145-generic in-target: Suggested packages: in-target: fdutils linux-doc-4.4.0 | linux-source-4.4.0 linux-tools in-target: Recommended packages: in-target: grub-pc | grub-efi-amd64 | grub-efi-ia32 | grub | lilo in-target: The following NEW packages will be installed: in-target: linux-headers-4.4.0-145 linux-headers-4.4.0-145-generic in-target: linux-headers-generic linux-headers-virtual linux-image-4.4.0-145-generic in-target: linux-image-virtual linux-modules-4.4.0-145-generic linux-virtual in-target: The following packages will be upgraded: in-target: linux-base in-target: 1 upgraded, 8 newly installed, 0 to remove and 98 not upgraded. in-target: Need to get 29.8 MB of archives. in-target: After this operation, 146 MB of additional disk space will be used. in-target: Get:1 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 linux-base all 4.5ubuntu1~16.04.1 [18.1 kB] in-target: Get:2 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 linux-headers-4.4.0-145 all 4.4.0-145.171 [10.0 MB] in-target: Get:3 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 linux-headers-4.4.0-145-generic amd64 4.4.0-145.171 [820 kB] in-target: Get:4 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 linux-headers-generic amd64 4.4.0.145.153 [2,568 B] in-target: Get:5 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 linux-headers-virtual amd64 4.4.0.145.153 [1,760 B] in-target: Get:6 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 linux-modules-4.4.0-145-generic amd64 4.4.0-145.171 [12.0 MB] in-target: Get:7 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 linux-image-4.4.0-145-generic amd64 4.4.0-145.171 [6,919 kB] in-target: Get:8 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 linux-image-virtual amd64 4.4.0.145.153 [2,694 B] in-target: Get:9 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 linux-virtual amd64 4.4.0.145.153 [1,778 B] ... and it unpacks that first ... in-target: Preparing to unpack .../linux-base_4.5ubuntu1~16.04.1_all.deb ... in-target: in-target: Unpacking linux-base (4.5ubuntu1~16.04.1) over (4.0ubuntu1) ... ... in-target: Setting up linux-base (4.5ubuntu1~16.04.1) ... ...and the symlinks in postinst work ... in-target: Setting up linux-image-4.4.0-145-generic (4.4.0-145.171) ...^M in-target: I: /vmlinuz.old is now a symlink to boot/vmlinuz-4.4.0-145-generic^M in-target: I: /initrd.img.old is now a symlink to boot/initrd.img-4.4.0-145-generic^M in-target: I: /vmlinuz is now a symlink to boot/vmlinuz-4.4.0-145-generic^M in-target: I: /initrd.img is now a symlink to boot/initrd.img-4.4.0-145-generic^M in-target: Setting up linux-image-virtual (4.4.0.145.153) ...^M in-target: Setting up linux-virtual (4.4.0.145.153) ...^M So... I don't know if you need verification from the original reporter too, but it looks good to 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/1820419 Title: linux-generic should depend on linux-base >=4.1 Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Bug description: [ SRU Justification ] == Impact == Due to unversioned dependencies to linux-base, minimal installations will not pull in the latest requirements. == Fix == Depend on linux-base (>= 4.5ubuntu1~16.04.1) specifically == Testcase == See below (but also can be checked on dependencies). == Risk of Regression == Low, no actual
[Kernel-packages] [Bug 1813244] Re: systemd cause kernel trace "BUG: unable to handle kernel paging request at 6db23a14" on Cosmic i386
** 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/1813244 Title: systemd cause kernel trace "BUG: unable to handle kernel paging request at 6db23a14" on Cosmic i386 Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: This issue was found after leaving a SUT to run overnight (was testing the ubuntu_cts_kernel test 13 hours ago before this happens). Can't tell if this is a regression, as I haven't find a way to reproduce it. But I do see similar reports on the Internet [1] After checking the systemd service timers, it looks like this is caused by the logrotate.service: $ sudo systemctl list-timers --all NEXT LEFT LAST PASSEDUNIT ACTIVATES Fri 2019-01-25 06:18:58 UTC 1h 40min left Thu 2019-01-24 06:34:15 UTC 22h ago apt-daily-upgrade.timer apt-daily-upgrade.service Fri 2019-01-25 09:15:54 UTC 4h 37min left Fri 2019-01-25 03:43:24 UTC 55min ago apt-daily.timer apt-daily.service Fri 2019-01-25 17:02:47 UTC 12h left Fri 2019-01-25 04:20:17 UTC 18min ago motd-news.timer motd-news.service Sat 2019-01-26 00:00:00 UTC 19h left Fri 2019-01-25 00:00:37 UTC 4h 38min ago logrotate.timer logrotate.service Sat 2019-01-26 04:02:38 UTC 23h left Fri 2019-01-25 04:02:38 UTC 36min ago systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.serv Mon 2019-01-28 00:00:00 UTC 2 days left Wed 2019-01-23 10:44:18 UTC 1 day 17h ago fstrim.timer fstrim.service n/a n/a n/a n/a snapd.snap-repair.timer snapd.snap-repair.service 7 timers listed. After this happens, you won't be able to reboot it with the command. $ sudo reboot sudo: unable to resolve host onza: Resource temporarily unavailable Killed Here is the error message, please refer to the attachment for a complete syslog: Jan 25 00:00:37 onza systemd[1]: Starting Rotate log files... Jan 25 00:00:37 onza kernel: [45282.956634] BUG: unable to handle kernel paging request at 6db23a14 Jan 25 00:00:37 onza kernel: [45282.962902] *pdpt = 33fa1001 *pde = Jan 25 00:00:37 onza kernel: [45282.968650] Oops: [#1] SMP Jan 25 00:00:37 onza kernel: [45282.971796] CPU: 0 PID: 407 Comm: systemd-journal Not tainted 4.18.0-14-generic #15-Ubuntu Jan 25 00:00:37 onza kernel: [45282.980330] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 Jan 25 00:00:37 onza kernel: [45282.988127] EIP: __kmalloc+0xc9/0x240 Jan 25 00:00:37 onza kernel: [45282.991785] Code: 4d e0 8d 4a 01 31 c6 8b 45 f0 89 75 dc 31 f3 8b 37 64 0f c7 0e 0f 94 c0 84 c0 74 b9 8b 75 e4 8b 45 dc 39 45 e0 74 0e 03 5f 14 <33> 1b 33 9f b4 00 00 00 0f 18 03 f7 45 ec 00 80 00 00 0f 85 3f 01 Jan 25 00:00:37 onza kernel: [45283.011254] EAX: 9e20b374 EBX: 6db23a14 ECX: 350d EDX: 350c Jan 25 00:00:37 onza kernel: [45283.017769] ESI: eac03a00 EDI: eac03a00 EBP: f461fd9c ESP: f461fd74 Jan 25 00:00:37 onza kernel: [45283.024304] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00010206 Jan 25 00:00:37 onza kernel: [45283.031245] CR0: 80050033 CR2: 6db23a14 CR3: 29d304a0 CR4: 06f0 Jan 25 00:00:37 onza kernel: [45283.037770] Call Trace: Jan 25 00:00:37 onza kernel: [45283.040395] ? ext4_htree_store_dirent+0x2e/0x120 Jan 25 00:00:37 onza kernel: [45283.045255] ext4_htree_store_dirent+0x2e/0x120 Jan 25 00:00:37 onza kernel: [45283.049951] htree_dirblock_to_tree+0xd2/0x230 Jan 25 00:00:37 onza kernel: [45283.054562] ext4_htree_fill_tree+0x7f/0x2c0 Jan 25 00:00:37 onza kernel: [45283.058991] ? kmem_cache_alloc_trace+0x167/0x1e0 Jan 25 00:00:37 onza kernel: [45283.063849] ? ext4_readdir+0x9d4/0xb10 Jan 25 00:00:37 onza kernel: [45283.067854] ext4_readdir+0x6aa/0xb10 Jan 25 00:00:37 onza kernel: [45283.071687] ? _copy_to_user+0x21/0x30 Jan 25 00:00:37 onza kernel: [45283.075597] ? do_statfs64+0x34/0x60 Jan 25 00:00:37 onza kernel: [45283.079334] ? security_file_permission+0x7c/0xb0 Jan 25 00:00:37 onza kernel: [45283.084306] iterate_dir+0x15c/0x1a0 Jan 25 00:00:37 onza kernel: [45283.087883] ksys_getdents64+0x6f/0x110 Jan 25 00:00:37 onza kernel: [45283.091853] ? iterate_dir+0x1a0/0x1a0 Jan 25 00:00:37 onza kernel: [45283.095771] sys_getdents64+0x16/0x20 Jan 25 00:00:37 onza kernel: [45283.099595] do_fast_syscall_32+0x7f/0x1e0 Jan 25 00:00:37 onza kernel: [45283.103858] entry_SYSENTER_32+0x4e/0x7c Jan 25 00:00:37 onza kernel: [45283.107938] EIP: 0xb7ef4d41 Jan 25 00:00:37 onza kernel: [45283.110898] Code: f6 ff ff 55 89 e5 8b 55 08 8b 80 5c cd ff ff 85 d2 74 02 89 02 5d c3 8b 04 24 c
[Kernel-packages] [Bug 1807406] Re: hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for response from ISHTP device
I have the exact same issue. My keyboard and touchpad stop working after returning from suspend. I'm not sure if this error message is related or not, but I found it in the Logs app right after they stopped working. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807406 Title: hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for response from ISHTP device Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello, Message after returning from suspension dmesg: [13383.967611] hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for response from ISHTP device [13383.967615] hid-sensor-hub 001F:8086:22D8.0002: timeout waiting for response from ISHTP device Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.19.0-8-generic 4.19.0-8.9 ProcVersionSignature: Ubuntu 4.19.0-8.9-generic 4.19.6 Uname: Linux 4.19.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2769 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Dec 7 12:02:26 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.0-8-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.19.0-8-generic N/A linux-backports-modules-4.19.0-8-generic N/A linux-firmware1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (4 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1807406/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822005] [NEW] ARM: Add support for the SDEI interface
Public bug reported: ARM defines a Software Delegated Exception Interface (SDEI) that has various uses, including an NMI-like mechanism for firmware to interrupt the OS w/ RAS (ACPI APEI) events. Support for this has landed upstream in the 5.1 merge window. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) 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/1822005 Title: ARM: Add support for the SDEI interface Status in linux package in Ubuntu: In Progress Bug description: ARM defines a Software Delegated Exception Interface (SDEI) that has various uses, including an NMI-like mechanism for firmware to interrupt the OS w/ RAS (ACPI APEI) events. Support for this has landed upstream in the 5.1 merge window. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821934] Re: [Hyper-V] Enable CONFIG_HOTPLUG_CPU in linux-azure
** Information type changed from Private Security to Public -- 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/1821934 Title: [Hyper-V] Enable CONFIG_HOTPLUG_CPU in linux-azure Status in linux-azure package in Ubuntu: New Bug description: We requested that CONFIG_HOTPLUG_CPU be disabled in bug 1776293. However, due to a recently discovered security issue, CONFIG_HOTPLUG_CPU needs to be re-enabled. There are some patches on LKML to address this security issue, but they are not in the Azure kernel yet, and may not be accepted upstream in their current form. If your interested, those two patches are available here: https://lkml.org/lkml/2019/3/26/893 https://lkml.org/lkml/2019/3/26/894 https://lkml.org/lkml/2019/3/26/895 To mitigate this security issue, the nosmt option needs to be passed on the boot line. However, the nosmt option will not work if CONFIG_HOTPLUG_CPU is disabled, which is the primary reason it needs to be turned back on at this time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1821934/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819695] Re: linux-gcp: 4.15.0-1029.31~16.04.1 -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: 1819698 phase: Testing phase-changed: Monday, 25. March 2019 15:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - 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-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1819695 Title: linux-gcp: 4.15.0-1029.31~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released 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 snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: 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: 1819698 phase: Testing phase-changed: Monday, 25. March 2019 15:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: 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/1819695/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819695] Re: linux-gcp: 4.15.0-1029.31~16.04.1 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1819695 Title: linux-gcp: 4.15.0-1029.31~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released 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 snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: 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: 1819698 phase: Testing phase-changed: Monday, 25. March 2019 15:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: 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/1819695/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813244] Re: systemd cause kernel trace "BUG: unable to handle kernel paging request at 6db23a14" on Cosmic i386
With this patch applied I can't reproduce the problem anymore. See also: https://lkml.org/lkml/2019/3/27/1762 ** Patch added: "openvswitch: fix flow actions reallocation" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813244/+attachment/5249928/+files/0001-openvswitch-fix-flow-actions-reallocation.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/1813244 Title: systemd cause kernel trace "BUG: unable to handle kernel paging request at 6db23a14" on Cosmic i386 Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: This issue was found after leaving a SUT to run overnight (was testing the ubuntu_cts_kernel test 13 hours ago before this happens). Can't tell if this is a regression, as I haven't find a way to reproduce it. But I do see similar reports on the Internet [1] After checking the systemd service timers, it looks like this is caused by the logrotate.service: $ sudo systemctl list-timers --all NEXT LEFT LAST PASSEDUNIT ACTIVATES Fri 2019-01-25 06:18:58 UTC 1h 40min left Thu 2019-01-24 06:34:15 UTC 22h ago apt-daily-upgrade.timer apt-daily-upgrade.service Fri 2019-01-25 09:15:54 UTC 4h 37min left Fri 2019-01-25 03:43:24 UTC 55min ago apt-daily.timer apt-daily.service Fri 2019-01-25 17:02:47 UTC 12h left Fri 2019-01-25 04:20:17 UTC 18min ago motd-news.timer motd-news.service Sat 2019-01-26 00:00:00 UTC 19h left Fri 2019-01-25 00:00:37 UTC 4h 38min ago logrotate.timer logrotate.service Sat 2019-01-26 04:02:38 UTC 23h left Fri 2019-01-25 04:02:38 UTC 36min ago systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.serv Mon 2019-01-28 00:00:00 UTC 2 days left Wed 2019-01-23 10:44:18 UTC 1 day 17h ago fstrim.timer fstrim.service n/a n/a n/a n/a snapd.snap-repair.timer snapd.snap-repair.service 7 timers listed. After this happens, you won't be able to reboot it with the command. $ sudo reboot sudo: unable to resolve host onza: Resource temporarily unavailable Killed Here is the error message, please refer to the attachment for a complete syslog: Jan 25 00:00:37 onza systemd[1]: Starting Rotate log files... Jan 25 00:00:37 onza kernel: [45282.956634] BUG: unable to handle kernel paging request at 6db23a14 Jan 25 00:00:37 onza kernel: [45282.962902] *pdpt = 33fa1001 *pde = Jan 25 00:00:37 onza kernel: [45282.968650] Oops: [#1] SMP Jan 25 00:00:37 onza kernel: [45282.971796] CPU: 0 PID: 407 Comm: systemd-journal Not tainted 4.18.0-14-generic #15-Ubuntu Jan 25 00:00:37 onza kernel: [45282.980330] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 Jan 25 00:00:37 onza kernel: [45282.988127] EIP: __kmalloc+0xc9/0x240 Jan 25 00:00:37 onza kernel: [45282.991785] Code: 4d e0 8d 4a 01 31 c6 8b 45 f0 89 75 dc 31 f3 8b 37 64 0f c7 0e 0f 94 c0 84 c0 74 b9 8b 75 e4 8b 45 dc 39 45 e0 74 0e 03 5f 14 <33> 1b 33 9f b4 00 00 00 0f 18 03 f7 45 ec 00 80 00 00 0f 85 3f 01 Jan 25 00:00:37 onza kernel: [45283.011254] EAX: 9e20b374 EBX: 6db23a14 ECX: 350d EDX: 350c Jan 25 00:00:37 onza kernel: [45283.017769] ESI: eac03a00 EDI: eac03a00 EBP: f461fd9c ESP: f461fd74 Jan 25 00:00:37 onza kernel: [45283.024304] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00010206 Jan 25 00:00:37 onza kernel: [45283.031245] CR0: 80050033 CR2: 6db23a14 CR3: 29d304a0 CR4: 06f0 Jan 25 00:00:37 onza kernel: [45283.037770] Call Trace: Jan 25 00:00:37 onza kernel: [45283.040395] ? ext4_htree_store_dirent+0x2e/0x120 Jan 25 00:00:37 onza kernel: [45283.045255] ext4_htree_store_dirent+0x2e/0x120 Jan 25 00:00:37 onza kernel: [45283.049951] htree_dirblock_to_tree+0xd2/0x230 Jan 25 00:00:37 onza kernel: [45283.054562] ext4_htree_fill_tree+0x7f/0x2c0 Jan 25 00:00:37 onza kernel: [45283.058991] ? kmem_cache_alloc_trace+0x167/0x1e0 Jan 25 00:00:37 onza kernel: [45283.063849] ? ext4_readdir+0x9d4/0xb10 Jan 25 00:00:37 onza kernel: [45283.067854] ext4_readdir+0x6aa/0xb10 Jan 25 00:00:37 onza kernel: [45283.071687] ? _copy_to_user+0x21/0x30 Jan 25 00:00:37 onza kernel: [45283.075597] ? do_statfs64+0x34/0x60 Jan 25 00:00:37 onza kernel: [45283.079334] ? security_file_permission+0x7c/0xb0 Jan 25 00:00:37 onza kernel: [45283.084306] iterate_dir+0x15c/0x1a0 Jan 25 00:00:37 onza kernel: [45283.087883] ksys_getdents64+0x6f/0x110 Jan 25 00:00:37 onza kernel: [45283.091853] ? iterate_dir+0x1a0/0x1a0 Jan 25 00:00:37 onza kernel: [45283.095771] sys_getdents64+0x16/0x20 Jan 25 00:00:37 onza kernel: [45283.099595] do_
[Kernel-packages] [Bug 1820326] Re: linux-fips: 4.4.0-1007.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 -- boot-testing-requested: true kernel-stable-master-bug: 1821724 - phase: Ready for Promote to Proposed - phase-changed: Wednesday, 27. March 2019 21:03 UTC + phase: Promote to Proposed + phase-changed: Wednesday, 27. March 2019 21:42 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- review in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820326 Title: linux-fips: 4.4.0-1007.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 promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: 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: 1821724 phase: Promote to Proposed phase-changed: Wednesday, 27. March 2019 21:42 UTC reason: promote-to-proposed: Ongoing -- review in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1820326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821936] Re: ALC274 unsupported
Apologies my first run of apport was mainline 5.0. I immediately rebooted and use a standard default kernel for 18.04. I deleted both mainlines since they didn't solve my issue anyway. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821936 Title: ALC274 unsupported Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1821936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820326] Re: linux-fips: 4.4.0-1007.9 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820326 Title: linux-fips: 4.4.0-1007.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 promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: 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: 1821724 phase: Ready for Promote to Proposed phase-changed: Wednesday, 27. March 2019 21:03 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/1820326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819698] Re: linux-gcp: 4.15.0-1029.31 -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 backports: bug 1819695 (xenial/linux-gcp) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819716 phase: Testing phase-changed: Thursday, 21. March 2019 18:39 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1029 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-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1819698 Title: linux-gcp: 4.15.0-1029.31 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released 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 snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp 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 backports: bug 1819695 (xenial/linux-gcp) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819716 phase: Testing phase-changed: Thursday, 21. March 2019 18:39 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: 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/1819698/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819695] Re: linux-gcp: 4.15.0-1029.31~16.04.1 -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 -- boot-testing-requested: true kernel-stable-master-bug: 1819698 phase: Testing phase-changed: Monday, 25. March 2019 15:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1029 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-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1819695 Title: linux-gcp: 4.15.0-1029.31~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released 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: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: 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: 1819698 phase: Testing phase-changed: Monday, 25. March 2019 15:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-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/1819695/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820326] Re: linux-fips: 4.4.0-1007.9 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed 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: 1821724 - phase: Promote to Proposed - phase-changed: Monday, 25. March 2019 20:33 UTC + phase: Ready for Promote to Proposed + phase-changed: Wednesday, 27. March 2019 21:03 UTC reason: - promote-to-proposed: Stalled -- review 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/1820326 Title: linux-fips: 4.4.0-1007.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 promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: 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: 1821724 phase: Ready for Promote to Proposed phase-changed: Wednesday, 27. March 2019 21:03 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/1820326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820326] Re: linux-fips: 4.4.0-1007.9 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820326 Title: linux-fips: 4.4.0-1007.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 promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: 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: 1821724 phase: Promote to Proposed phase-changed: Monday, 25. March 2019 20:33 UTC reason: promote-to-proposed: Stalled -- review FAILED To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1820326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821936] Re: ALC274 unsupported
** 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/1821936 Title: ALC274 unsupported Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1821936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820063] Re: [Hyper-V] KVP daemon fails to start on first boot of disco VM
** Tags added: bionic cosmic xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820063 Title: [Hyper-V] KVP daemon fails to start on first boot of disco VM Status in linux package in Ubuntu: Confirmed Bug description: Launching a recent daily image of disco on azure results in a VM in which the hv-kvp-daemon.service fails to start: $ systemctl status -o cat hv-kvp-daemon.service ● hv-kvp-daemon.service - Hyper-V KVP Protocol Daemon Loaded: loaded (/lib/systemd/system/hv-kvp-daemon.service; enabled; vendor pr Active: failed (Result: exit-code) since Thu 2019-03-14 13:07:15 UTC; 11min a Main PID: 219 (code=exited, status=1/FAILURE) Started Hyper-V KVP Protocol Daemon. KVP starting; pid is:219 open /dev/vmbus/hv_kvp failed; error: 2 No such file or directory hv-kvp-daemon.service: Main process exited, code=exited, status=1/FAILURE hv-kvp-daemon.service: Failed with result 'exit-code'. The instance was created with: $ az vm create --resource-group [redacted] --image Canonical:UbuntuServer:19.04-DAILY:19.04.201903130 --size Standard_D2_v2 --name disco-0313 As best as I can tell, the /dev/vmbus/hv_kvp isn't available when the hv-kvp-daemon.service starts, but it is available a few seconds later. Manually starting the daemon once I can ssh in works. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: N/A DistroRelease: Ubuntu 19.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-1011-azure root=PARTUUID=11894199-2ca2-4912-9c41-d28128744d57 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: User Name 4.18.0-1011.11-azure 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-1011-azure N/A linux-backports-modules-4.18.0-1011-azure N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: disco uec-images Uname: Linux 4.18.0-1011-azure x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 06/02/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090007 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090007:bd06/02/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: dmi.product.name: Virtual Machine dmi.product.uuid: 3b0f2160-7fc4-a646-904c-4248f04792d4 dmi.product.version: 7.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819658] Re: linux-aws: 4.4.0-1040.43 -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 -- boot-testing-requested: true kernel-stable-master-bug: 1821724 - phase: Ready for Testing - phase-changed: Wednesday, 27. March 2019 13:08 UTC + phase: Testing + phase-changed: Wednesday, 27. March 2019 20:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: 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/1819658 Title: linux-aws: 4.4.0-1040.43 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released 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: Confirmed 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 Trusty: 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: 1821724 phase: Testing phase-changed: Wednesday, 27. March 2019 20:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-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/1819658/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819658] Re: linux-aws: 4.4.0-1040.43 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- 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/1819658 Title: linux-aws: 4.4.0-1040.43 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released 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: Confirmed 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 Trusty: 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: 1821724 phase: Ready for Testing phase-changed: Wednesday, 27. March 2019 13:08 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-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/1819658/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821712] Re: linux-kvm: 4.4.0-1043.49 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- 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/1821712 Title: linux-kvm: 4.4.0-1043.49 -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: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Confirmed 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: 1821724 phase: Testing phase-changed: Wednesday, 27. March 2019 13:30 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1821712/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821724] Re: linux: 4.4.0-145.171 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821724 Title: linux: 4.4.0-145.171 -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: 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 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: Confirmed 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 package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed 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 1819658 (trusty/linux-aws), bug 1819659 (trusty/linux-lts-xenial) derivatives: bug 1819654 (linux-euclid), bug 1820326 (linux-fips), bug 1821712 (linux-kvm), bug 1821713 (linux-raspi2), bug 1821723 (linux-snapdragon), bug 1821726 (linux-aws) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Wednesday, 27. March 2019 12:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-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/1821724/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821713] Re: linux-raspi2: 4.4.0-1106.114 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- 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/1821713 Title: linux-raspi2: 4.4.0-1106.114 -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: 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 Xenial: Confirmed 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: 1821724 phase: Testing phase-changed: Wednesday, 27. March 2019 14:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress 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/1821713/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821726] Re: linux-aws: 4.4.0-1079.89 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- 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/1821726 Title: linux-aws: 4.4.0-1079.89 -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: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed 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: 1821724 phase: Testing phase-changed: Wednesday, 27. March 2019 12:01 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 snap-release-to-candidate: Pending -- snap not in candidate channel verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1821726/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821961] 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 1821961 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 ** Changed in: linux (Ubuntu Bionic) 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/1821961 Title: Fix for dual Intel NVMes Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: [Impact] SRU for LP: #1811755 doesn't really fix the issue. Only one of the two NVMe can be correctly enumerated. [Fix] There are two separate entries for the Intel NVMe device. Fix that. [Test] User confirms it works. [Regression Potential] The fix limits to Intel 760p/Pro 7600p SSD, and the fix has been verified by the bug reporter. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821961] [NEW] Fix for dual Intel NVMes
Public bug reported: [Impact] SRU for LP: #1811755 doesn't really fix the issue. Only one of the two NVMe can be correctly enumerated. [Fix] There are two separate entries for the Intel NVMe device. Fix that. [Test] User confirms it works. [Regression Potential] The fix limits to Intel 760p/Pro 7600p SSD, and the fix has been verified by the bug reporter. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821961 Title: Fix for dual Intel NVMes Status in linux package in Ubuntu: New Status in linux source package in Bionic: New Bug description: [Impact] SRU for LP: #1811755 doesn't really fix the issue. Only one of the two NVMe can be correctly enumerated. [Fix] There are two separate entries for the Intel NVMe device. Fix that. [Test] User confirms it works. [Regression Potential] The fix limits to Intel 760p/Pro 7600p SSD, and the fix has been verified by the bug reporter. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820755] Re: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found
I finally came up with a workaround that can be done in a preseed.cfg (until this can be fixed properly in the kernel image) d-i preseed/early_command string echo -e "#!/bin/sh\napt-install linux- base" > /usr/lib/post-base-installer.d/99-bug1820755; chmod +x /usr/lib /post-base-installer.d/99-bug1820755 In other words, have the early command (which runs before base- installer) set up another post-base-installer callback hook, to upgrade linux-base. Since base-installer runs its post_install_hooks between apt_update and install_kernel, this can pick up the linux-base from xenial-updates, which will let the kernel install succeed. Seems to work for me and ends up with everything at the right versions in the end. That seems better than trying to hold back the linux- image-4.4.0-143-generic, which would leave you vulnerable to USN-3910-1 . -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1820755 Title: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found Status in Blue Linux: New Status in linux package in Ubuntu: Confirmed Status in linux-base package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Status in linux-base source package in Xenial: Fix Released Bug description: Using a netboot install of Ubuntu 16.04 LTS server, the install fails when configuring the kernel. The failure will not let you move on. This seems to have happened after the release of https://lists.ubuntu.com/archives/ubuntu-security-announce/2019-March/004803.html The error logs Mar 18 17:09:50 in-target: Setting up linux-modules-4.4.0-143-generic (4.4.0-143.169) ... Mar 18 17:09:50 in-target: ^M Mar 18 17:09:51 in-target: Setting up linux-image-4.4.0-143-generic (4.4.0-143.169) ... Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: 50: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: Mar 18 17:09:51 in-target: linux-update-symlinks: not found Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: dpkg: error processing package linux-image-4.4.0-143-generic (--configure): Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: subprocess installed post-installation script returned error exit status 127 Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: dpkg: dependency problems prevent configuration of linux-modules-extra-4.4.0-143-generic: Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: linux-modules-extra-4.4.0-143-generic depends on linux-image-4.4.0-143-generic | linux-image-unsigned-4.4.0-143-generic; however: Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: Package linux-image-4.4.0-143-generic is not configured yet. Mar 18 17:09:51 in-target: ^M Mar To manage notifications about this bug go to: https://bugs.launchpad.net/bluelinux/+bug/1820755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815033] Re: qlcnic: Firmware aborts/hangs in QLogic NIC
Kernel was validated by the user that reported the issue - ran for more than 72h with no problems. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1815033 Title: qlcnic: Firmware aborts/hangs in QLogic NIC Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] * In multi-queue configurations for qlcnic driver, there is a corner case in which TX queue zero is used at same time for regular data transmission by one CPU while another uses the same queue descriptor for MAC configuration. * When such "race" indeed happens, it could lead to TX queue zero corruption, triggering as net result firmware aborts/hangs out of nowhere. The following kernel log messages were collected during the corruption event: qlcnic :01:00.0: Pause control frames disabled on all ports qlcnic :01:00.0: firmware hang detected qlcnic :01:00.0: Dumping hw/fw registers PEG_HALT_STATUS1: 0x40001502, PEG_HALT_STATUS2: 0x3de7a0, PEG_NET_0_PC: 0x6d268, PEG_NET_1_PC: 0x6d2ac, PEG_NET_2_PC: 0x149, PEG_NET_3_PC: 0x6e105, PEG_NET_4_PC: 0x1e00b [...] qlcnic :01:00.0: Detected state change from DEV_NEED_RESET, skipping ack check * The following device is known to suffer from the issue (lspci output), although a whole class of devices (named 82XX series from the vendor) are susceptible to this: 01:00.0 Ethernet controller [0200]: QLogic Corp. cLOM8214 1/10GbE Controller [1077:8020] * The fix is the following patch, present in mainline kernel as well as in supported stable branches: c333fa0c4f22 ("qlcnic: fix Tx descriptor corruption on 82xx devices"). Link for the patch in Linus tree: http://git.kernel.org/linus/c333fa0c4f22 [Test Case] * Unfortunately this is not easy to reproduce; we have a user report of the issue with a pretty reliable reproducer - user is running a NFS workload on top of the above PCI adapter. His problem goes away with the patch proposed here to SRU. His problem happens in both kernels 4.4 and 4.15, and the patch fixes it for both of them. (Notice this is a Bionic-only SRU, since Ubuntu 4.4 kernel got the patch from Greg's supported stable branch). [Regression Potential] * The patch scope is restricted to a single driver, and the code itself is self-contained - basically a restriction to specific tx_ring when setting filters. There is potential for regressions in this path for the driver which could cause different firmware issues for example, but the user testing exhibited great reliability - without the patch issue happens after ~6h of machine boot. With the patch the machine ran for more than 8 days without issues. * Also the patch is present in mainline kernel as well as supported stable branches, and is already present in Ubuntu 4.4 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815033/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821620] Re: Add HiSilicon SoC quirk for cpufreq
** Changed in: linux (Ubuntu Cosmic) Status: New => Invalid ** Changed in: linux (Ubuntu Bionic) Status: New => 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/1821620 Title: Add HiSilicon SoC quirk for cpufreq Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Invalid Status in linux source package in Cosmic: Invalid Status in linux source package in Disco: Fix Committed Bug description: [Impact] Some HiSilicon SoCs do not implement registers that the cpufreq subsystem uses to calculate current performance. This can result in undefined data being used in internal calculations, and being exposed to userspace via sysfs. [Test Case] Examine the exposed frequency under idle and load and make sure it looks sane: sudo cat /sys/devices/system/cpu/cpufreq/policy*/cpuinfo_cur_freq Note: On my test system, it happens to look sane w/o this quirk as well. This is because the undefined reads all happen to return 0x1 today, and that puts us into the avoid-divide-by-zero code path that happens to do the same thing as this quirk (report desired perf instead of actual). [Fix] 6c8d750f9784c cpufreq / cppc: Work around for Hisilicon CPPC cpufreq 1757d05f3112a ACPI / CPPC: Add a helper to get desired performance [Regression Risk] The fix is a quirk restricted to specific SoCs. It does rely on firmware behaving (overloading the desired_perf register w/ a correct actual perf value), so changes in firmware could lead to regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819614] Re: linux-aws: 4.18.0-1012.14 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => 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 1819613 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819624 phase: Testing phase-changed: Friday, 15. March 2019 18:01 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 -- 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/1819614 Title: linux-aws: 4.18.0-1012.14 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released 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 1819613 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819624 phase: Testing phase-changed: Friday, 15. March 2019 18:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: 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/1819614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819621] Re: linux-kvm: 4.18.0-1009.9 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => 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: 1819624 phase: Testing phase-changed: Friday, 15. March 2019 08:43 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED 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-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1819621 Title: linux-kvm: 4.18.0-1009.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released 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-kvm package in Ubuntu: Invalid Status in linux-kvm 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819624 phase: Testing phase-changed: Friday, 15. March 2019 08:43 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: 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/1819621/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819989] Re: Add basic support to NVLink2 passthrough
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819989 Title: Add basic support to NVLink2 passthrough Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Bug description: This bug exists to track the basic support to NVLink2 passthrough on Ubuntu 18.04 - for the guest side only. There's a relative small patchset that I'm going to send to Canonical Kernel Team using this buglink. On the host side we'll be running a custom version of Ubuntu 18.04 (kernel + qemu). However on the guest side it will be *very important* for clients to simply download the Ubuntu 18.04 from Canonical's website and have the NVLink2 working out of the box. For that, we have worked on a small patchset using only upstream patches without changing beyond our area. As soon as I send the patchset to the mailing list I'll update this bug with a link to that message. Thank you very much, Jose R. Ziviani To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819989/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821713] Re: linux-raspi2: 4.4.0-1106.114 -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: 1821724 phase: Testing phase-changed: Wednesday, 27. March 2019 14:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-beta: Pending -- snap not in beta channel - snap-release-to-edge: Pending -- snap not in edge channel + 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/1821713 Title: linux-raspi2: 4.4.0-1106.114 -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: 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: Confirmed 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 Xenial: Confirmed 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: 1821724 phase: Testing phase-changed: Wednesday, 27. March 2019 14:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress 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/1821713/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812410] Re: Intel x550 not negotiating to 10Gb on x299 chipset
@Kevin (thenewmanium) Can you run and post the response on your system? ethtool -i and ethtool -k I'm opening up that ticket I had open with Intel again to see if we can some traction from that. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812410 Title: Intel x550 not negotiating to 10Gb on x299 chipset Status in linux package in Ubuntu: Confirmed Bug description: I am having an issue with this particular machine auto negotiating 10Gb. The onboard LOM will only negotiate to 1Gb. If I run `ethtool -s advertise 0x1000`, the machine will delink and then negotiate to 10Gb and work as expecting. Rebooting the machine (or unplugging network cable) will cause it to negotiate to 1G again resulting in having to run the ethtool command again. This is what I have tried: Tried different cable from confirmed working machine that auto negotiates to 10Gb. Tried upgrading ixgbe driver to latest (5.5.3) Tried upgrading X550 firmware. I put an Intel x540-T1 card in the machine and that card works properly and negotiates to 10Gb automatically. Move the cable to the LOM x550, and it still negotiates to 1Gb. I also tried loading a live version of Fedora 29 (Kernel 4.18) with same exact symptoms. We have several other machine negotiating fine on the same exact switch. I have tried those cables to test this problematic machine with same result as above. We have a machine that is pretty similar in hardware that is not exhibiting this issue. It is an ASUS x99 motherboard, with the same LOM Intel x550 card, running on 16.04. The machine that is causing problems is an Asus x299 motherboard with the Intel x550 LOM card running 18.04 (16.04 won't work on the x299 chipset for some reason). I have a suspicion that it could potentially be related to the x299? The only way I have been able to get this problematic machine to negotiate to 10Gbps automatically is by plugging a cable directly from the LOM x550 of the problematic machine to another machines 10Gb network card. Doing that, the problematic machine will negotiate properly to 10Gb. I'm trying to find another 10Gb switch to test with to see if it could be unique to this combination of switch and machine. However, I'm reluctant to blame it on the switch since we have about several other machine working perfectly fine on the switch (some with the same exact x550 LOM). Other notes: https://serverfault.com/questions/949006/intel-x550-not-negotiating-to-10gb?noredirect=1#comment1233436_949006 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-12-14 (34 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: enp179s0f1 no wireless extensions. lono wireless extensions. enp179s0f0 no wireless extensions. MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=7e94e4fd-ff67-46c2-9b58-3f7bb3840be4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/30/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0905 dmi.board.asset.tag: Default string dmi.board.name: WS X299 SAGE/10G dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0905:bd11/30/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnWSX299SAGE/10G:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812410/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpa
[Kernel-packages] [Bug 1814069] Re: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2
Hi, For the current schedule of planned kernel stable updates please check: https://kernel.ubuntu.com/ Thanks ** Changed in: linux (Ubuntu Bionic) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814069 Title: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2 Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: In Progress Bug description: === SRU Justification === [Impact] NULL pointer dereference in netvsc_probe(). Module hv_netvsc is included in initramfs, so this blocks the boot process. For Hyper-V only supports single channel, rndis_filter_device_add() bails early and jump to tag "out". Subsequent code calls rndis_filter_device_remove() and returns ERR_PTR(ret), where ret is 0 (sucess). Because of that, it passes IS_ERR(nvdev) check in netvsc_probe() and cause a NULL pointer dereference, as nvdev now is 0: ... if (nvdev->num_chn > 1) schedule_work(&nvdev->subchan_work); [Fix] Correctly return net_device at the end of rndis_filter_device_add(). [Test] Users report positive result. [Regression Potenial] Low. Trivial change, patches are in upstream sometime. === Original Bug Report === Ubuntu stuck on booting on HyperV Server 2008R2. I saw kernel messages, seems to load ram image the boot is stuck. Seems to be a problem with hyperv drivers propably harddrive. Reverted back to the previous kernel. Description:Ubuntu 18.04.1 LTS Release:18.04Description:Ubuntu 18.04.1 LTS Release:18.04 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 31 08:52 seq crw-rw 1 root audio 116, 33 Jan 31 08:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=86036ccb-bc11-11e8-93c9-00155dfd7535 ro maybe-ubiquity ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090004 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 8531-7125-9206-2460-7819-2663-90 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090004:bd03/19/2009:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: dmi.product.name: Virtual Machine dmi.product.version: 7.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819695] Re: linux-gcp: 4.15.0-1029.31~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate 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: 1819698 phase: Testing phase-changed: Monday, 25. March 2019 15:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1029 regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-candidate: Pending -- snap not in candidate channel verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1819695 Title: linux-gcp: 4.15.0-1029.31~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released 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: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: 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: 1819698 phase: Testing phase-changed: Monday, 25. March 2019 15:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1029 regression-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/1819695/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821724] Re: linux: 4.4.0-145.171 -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 backports: bug 1819658 (trusty/linux-aws), bug 1819659 (trusty/linux-lts-xenial) derivatives: bug 1819654 (linux-euclid), bug 1820326 (linux-fips), bug 1821712 (linux-kvm), bug 1821713 (linux-raspi2), bug 1821723 (linux-snapdragon), bug 1821726 (linux-aws) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Wednesday, 27. March 2019 12:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-beta: Pending -- snap not in beta channel - snap-release-to-edge: Pending -- snap not in edge channel + 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 in Ubuntu. https://bugs.launchpad.net/bugs/1821724 Title: linux: 4.4.0-145.171 -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: 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 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: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed 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 package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed 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 1819658 (trusty/linux-aws), bug 1819659 (trusty/linux-lts-xenial) derivatives: bug 1819654 (linux-euclid), bug 1820326 (linux-fips), bug 1821712 (linux-kvm), bug 1821713 (linux-raspi2), bug 1821723 (linux-snapdragon), bug 1821726 (linux-aws) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Wednesday, 27. March 2019 12:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-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/1821724/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821408] Re: scsi: libsas: Support SATA PHY connection rate unmatch fixing during discovery
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Won't Fix ** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Won't Fix ** Changed in: linux (Ubuntu Xenial) Status: New => Won't Fix ** Description changed: [Impact] SATA disks may be unusable will not be usable when: - The disk is connected through a SAS expander - Controller uses a libsas-based driver (mvsas, aic94xx, hisi_sas) - link rate between expander & disk is greater than link between controller and expander + This is unlikely to occur in any production environment, but has + occurred in early silicon testing. Fixing this would be helpful in those + environments. + [Test Case] See conditions in "Impact" Can be simulated with: for f in /sys/class/sas_phy/phy-1\:*/maximum_linkrate; do - echo "3.0 Gbit" | sudo tee $f + echo "3.0 Gbit" | sudo tee $f done [Fix] cec9771d2e954 scsi: libsas: Support SATA PHY connection rate unmatch fixing during discovery [Regression Risk] Impact is restricted to drivers that use libsas: mvsas, aic94xx & hisi_sas. Code change is all within an "if" statement that meets these restrictions. A bug in this code could possibly reduce the speed of an otherwise working disk connection. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821408 Title: scsi: libsas: Support SATA PHY connection rate unmatch fixing during discovery Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Won't Fix Status in linux source package in Bionic: Won't Fix Status in linux source package in Cosmic: Won't Fix Status in linux source package in Disco: In Progress Bug description: [Impact] SATA disks may be unusable will not be usable when: - The disk is connected through a SAS expander - Controller uses a libsas-based driver (mvsas, aic94xx, hisi_sas) - link rate between expander & disk is greater than link between controller and expander This is unlikely to occur in any production environment, but has occurred in early silicon testing. Fixing this would be helpful in those environments. [Test Case] See conditions in "Impact" Can be simulated with: for f in /sys/class/sas_phy/phy-1\:*/maximum_linkrate; do echo "3.0 Gbit" | sudo tee $f done [Fix] cec9771d2e954 scsi: libsas: Support SATA PHY connection rate unmatch fixing during discovery [Regression Risk] Impact is restricted to drivers that use libsas: mvsas, aic94xx & hisi_sas. Code change is all within an "if" statement that meets these restrictions. A bug in this code could possibly reduce the speed of an otherwise working disk connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819701] Re: linux-ibm-gt: 4.15.0-1018.20 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-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: 1819716 - phase: Promote to Proposed - phase-changed: Wednesday, 27. March 2019 14:38 UTC + phase: Testing + phase-changed: Wednesday, 27. March 2019 16:41 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + 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 in Ubuntu. https://bugs.launchpad.net/bugs/1819701 Title: linux-ibm-gt: 4.15.0-1018.20 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed 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: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed 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: 1819716 phase: Testing phase-changed: Wednesday, 27. March 2019 16:41 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819701/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821726] Re: linux-aws: 4.4.0-1079.89 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge 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: 1821724 phase: Testing phase-changed: Wednesday, 27. March 2019 12:01 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 - snap-release-to-beta: Pending -- snap not in beta channel - snap-release-to-edge: Pending -- snap not in edge channel + snap-release-to-candidate: Pending -- snap not in candidate channel 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/1821726 Title: linux-aws: 4.4.0-1079.89 -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: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed 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: 1821724 phase: Testing phase-changed: Wednesday, 27. March 2019 12:01 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 snap-release-to-candidate: Pending -- snap not in candidate channel verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1821726/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821936] 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 1821936 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/1821936 Title: ALC274 unsupported Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1821936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819701] Re: linux-ibm-gt: 4.15.0-1018.20 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** 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: 1819716 phase: Promote to Proposed phase-changed: Wednesday, 27. March 2019 14:38 UTC reason: - promote-to-proposed: Ongoing -- review in progress + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819701 Title: linux-ibm-gt: 4.15.0-1018.20 -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 promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed 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: 1819716 phase: Promote to Proposed phase-changed: Wednesday, 27. March 2019 14:38 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819701/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821936] Re: ALC274 unsupported
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821936 Title: ALC274 unsupported Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1821936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812153] Re: CONFIG_SECURITY_SELINUX_DISABLE should be disabled on KVM kernel
** Changed in: linux-kvm (Ubuntu Disco) Status: In Progress => Fix Committed -- 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/1812153 Title: CONFIG_SECURITY_SELINUX_DISABLE should be disabled on KVM kernel Status in ubuntu-kernel-tests: In Progress Status in linux-kvm package in Ubuntu: Fix Committed Status in linux-kvm source package in Bionic: Fix Released Status in linux-kvm source package in Cosmic: Fix Committed Status in linux-kvm source package in Disco: Fix Committed Bug description: The test_081_config_security_selinux_disable test failed on the Bionic KVM kernel FAIL: test_081_config_security_selinux_disable (__main__.KernelSecurityConfigTest) Ensure CONFIG_SECURITY_SELINUX_DISABLE is disabled (LP: #1680315) -- Traceback (most recent call last): File "./test-kernel-security.py", line 2152, in test_081_config_security_selinux_disable self.assertKernelConfig('SECURITY_SELINUX_DISABLE', expected) File "./test-kernel-security.py", line 209, in assertKernelConfig self.assertKernelConfigUnset(name) File "./test-kernel-security.py", line 200, in assertKernelConfigUnset '%s option was expected to be unset in the kernel config' % name) AssertionError: SECURITY_SELINUX_DISABLE option was expected to be unset in the kernel config ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28 ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18 Uname: Linux 4.15.0-1028-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Thu Jan 17 04:31:59 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812153/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802480] Re: Crash when using IPsec VTI interfaces on 4.15 and 4.18.
The fix is available in commit: commit 0152eee6fc3b84298bb6a79961961734e8afa5b8 Author: Steffen Klassert Date: Thu Nov 22 07:26:24 2018 +0100 xfrm: Fix NULL pointer dereference in xfrm_input when skb_dst_force clea rs the dst_entry. Could be nice to backport this one. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802480 Title: Crash when using IPsec VTI interfaces on 4.15 and 4.18. Status in linux package in Ubuntu: Confirmed Bug description: Hey! After upgrading a few VPN to 4.15.0-38.41 (either Xenial or Bionic), we get random crashes. This also happens with the 4.18 in bionic- proposed. These crashes didn't happen with 4.4 from Xenial. Here is a stack trace: [ 31.154360] BUG: unable to handle kernel NULL pointer dereference at 0038 [ 31.162233] PGD 0 P4D 0 [ 31.164786] Oops: [#1] SMP PTI [ 31.168291] CPU: 5 PID: 42 Comm: ksoftirqd/5 Not tainted 4.18.0-11-generic #12~18.04.1-Ubuntu [ 31.176854] Hardware name: Supermicro Super Server/X10SDV-4C-7TP4F, BIOS 1.0b 11/21/2016 [ 31.184980] RIP: 0010:vti_rcv_cb+0xb9/0x1a0 [ip_vti] [ 31.189962] Code: 8b 44 24 70 0f c8 89 87 b4 00 00 00 48 8b 86 20 05 00 00 8b 80 f8 14 00 00 85 c0 75 05 48 85 d2 74 0e 48 8b 43 58 48 83 e0 fe 40 38 04 74 7d 44 89 b3 b4 00 00 00 49 8b 44 24 20 48 39 86 20 [ 31.208916] RSP: 0018:bc61832e3920 EFLAGS: 00010246 [ 31.214160] RAX: RBX: 9a3504964a00 RCX: 0002 [ 31.221328] RDX: 9a351add4080 RSI: 9a351aa08000 RDI: 9a3504964a00 [ 31.228485] RBP: bc61832e3940 R08: 0004 R09: c0aa612b [ 31.235643] R10: 0008f09b99881884 R11: 1884bd4e2d6b1fac R12: 9a3507b31900 [ 31.242803] R13: 9a3507b31000 R14: R15: 9a3504964a00 [ 31.249964] FS: () GS:9a35bfd4() knlGS: [ 31.258077] CS: 0010 DS: ES: CR0: 80050033 [ 31.263848] CR2: 0038 CR3: 00041a40a003 CR4: 003606e0 [ 31.271004] DR0: DR1: DR2: [ 31.278163] DR3: DR6: fffe0ff0 DR7: 0400 [ 31.285320] Call Trace: [ 31.287789] xfrm4_rcv_cb+0x4a/0x70 [ 31.291297] xfrm_input+0x58f/0x8f0 [ 31.294807] vti_input+0xaa/0x110 [ip_vti] [ 31.298926] vti_rcv+0x33/0x3c [ip_vti] [ 31.302783] xfrm4_esp_rcv+0x39/0x50 [ 31.306375] ip_local_deliver_finish+0x62/0x200 [ 31.310923] ip_local_deliver+0xdf/0xf0 [ 31.314775] ? ip_rcv_finish+0x420/0x420 [ 31.318718] ip_rcv_finish+0x126/0x420 [ 31.322486] ip_rcv+0x28f/0x360 [ 31.325655] ? inet_del_offload+0x40/0x40 [ 31.329686] __netif_receive_skb_core+0x48c/0xb70 [ 31.334413] ? kmem_cache_alloc+0xb4/0x1d0 [ 31.338532] ? __build_skb+0x2b/0xf0 [ 31.342128] __netif_receive_skb+0x18/0x60 [ 31.346244] ? __netif_receive_skb+0x18/0x60 [ 31.350536] netif_receive_skb_internal+0x45/0xe0 [ 31.355263] napi_gro_receive+0xc5/0xf0 [ 31.359141] mlx5e_handle_rx_cqe+0x1b2/0x5d0 [mlx5_core] [ 31.364476] ? skb_release_all+0x24/0x30 [ 31.368430] mlx5e_poll_rx_cq+0xd3/0x990 [mlx5_core] [ 31.373432] mlx5e_napi_poll+0x9b/0xc60 [mlx5_core] [ 31.378333] ? __switch_to_asm+0x34/0x70 [ 31.382270] ? __switch_to_asm+0x40/0x70 [ 31.386214] ? __switch_to_asm+0x34/0x70 [ 31.391056] ? __switch_to_asm+0x40/0x70 [ 31.395905] ? __switch_to_asm+0x34/0x70 [ 31.400743] net_rx_action+0x140/0x3a0 [ 31.405379] ? __switch_to+0xad/0x500 [ 31.409887] __do_softirq+0xe4/0x2bb [ 31.414448] run_ksoftirqd+0x2b/0x40 [ 31.418862] smpboot_thread_fn+0xfc/0x170 [ 31.423700] kthread+0x121/0x140 [ 31.427701] ? sort_range+0x30/0x30 [ 31.432040] ? kthread_create_worker_on_cpu+0x70/0x70 [ 31.437816] ret_from_fork+0x35/0x40 [ 31.442219] Modules linked in: esp6 authenc echainiv xfrm6_mode_tunnel xfrm4_mode_tunnel xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key xfrm_algo ip_vti ip_tunnel ip6_vti ip6_tunnel tunnel6 8021q garp mrp stp llc bonding ipt_REJECT nf_reject_ipv4 nfnetlink_log n fnetlink xt_NFLOG xt_hl xt_limit xt_nat xt_TCPMSS xt_HL xt_comment xt_tcpudp xt_multiport xt_conntrack iptable_filter iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat xt_connmark xt_mark iptable_mangle xt_CT nf_conntrack xt_addrtype iptable_raw bpfilter ipmi_ssif gpio_ ich intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass intel_cstate intel_rapl_perf input_leds joydev mei_me intel_pch_thermal ioatdma mei lpc_ich ipmi_si ipmi_devintf ipmi_msghandler acpi_pad mac_hid sch_fq_codel [ 31.519488] ib_iser rdma_cm iw_cm ib_cm iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_ta
[Kernel-packages] [Bug 1819624] Re: linux: 4.18.0-17.18 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => 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 1819623 (bionic/linux-hwe) derivatives: bug 1819612 (linux-raspi2), bug 1819614 (linux-aws), bug 1819618 (linux-azure), bug 1819620 (linux-gcp), bug 1819621 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Friday, 15. March 2019 23:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED certification-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 in Ubuntu. https://bugs.launchpad.net/bugs/1819624 Title: linux: 4.18.0-17.18 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress 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: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux 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 1819623 (bionic/linux-hwe) derivatives: bug 1819612 (linux-raspi2), bug 1819614 (linux-aws), bug 1819618 (linux-azure), bug 1819620 (linux-gcp), bug 1819621 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Friday, 15. March 2019 23:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-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/1819624/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812410] Re: Intel x550 not negotiating to 10Gb on x299 chipset
I'm pushing on Dell to push on Intel. Not getting a lot of traction on that but I'll update if I do. Definitely have this issue on all my Dell R640s with X550s though. I also suspect the ixgbe module here. The kernel 4.4.0-141 version is 4.2.1. Going to Ubuntu's 4.15.0-43 kernel takes it to 5.1.0 where the 1Gb negotiation issue pops up. I also tried upgrading ixgbe to 5.5.5 and saw the same issue, so it isn't fixed yet or anything. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812410 Title: Intel x550 not negotiating to 10Gb on x299 chipset Status in linux package in Ubuntu: Confirmed Bug description: I am having an issue with this particular machine auto negotiating 10Gb. The onboard LOM will only negotiate to 1Gb. If I run `ethtool -s advertise 0x1000`, the machine will delink and then negotiate to 10Gb and work as expecting. Rebooting the machine (or unplugging network cable) will cause it to negotiate to 1G again resulting in having to run the ethtool command again. This is what I have tried: Tried different cable from confirmed working machine that auto negotiates to 10Gb. Tried upgrading ixgbe driver to latest (5.5.3) Tried upgrading X550 firmware. I put an Intel x540-T1 card in the machine and that card works properly and negotiates to 10Gb automatically. Move the cable to the LOM x550, and it still negotiates to 1Gb. I also tried loading a live version of Fedora 29 (Kernel 4.18) with same exact symptoms. We have several other machine negotiating fine on the same exact switch. I have tried those cables to test this problematic machine with same result as above. We have a machine that is pretty similar in hardware that is not exhibiting this issue. It is an ASUS x99 motherboard, with the same LOM Intel x550 card, running on 16.04. The machine that is causing problems is an Asus x299 motherboard with the Intel x550 LOM card running 18.04 (16.04 won't work on the x299 chipset for some reason). I have a suspicion that it could potentially be related to the x299? The only way I have been able to get this problematic machine to negotiate to 10Gbps automatically is by plugging a cable directly from the LOM x550 of the problematic machine to another machines 10Gb network card. Doing that, the problematic machine will negotiate properly to 10Gb. I'm trying to find another 10Gb switch to test with to see if it could be unique to this combination of switch and machine. However, I'm reluctant to blame it on the switch since we have about several other machine working perfectly fine on the switch (some with the same exact x550 LOM). Other notes: https://serverfault.com/questions/949006/intel-x550-not-negotiating-to-10gb?noredirect=1#comment1233436_949006 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-12-14 (34 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: enp179s0f1 no wireless extensions. lono wireless extensions. enp179s0f0 no wireless extensions. MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=7e94e4fd-ff67-46c2-9b58-3f7bb3840be4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/30/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0905 dmi.board.asset.tag: Default string dmi.board.name: WS X299 SAGE/10G dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0905:bd11/30/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnWSX299SAGE/10G:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+sour
[Kernel-packages] [Bug 1819701] Re: linux-ibm-gt: 4.15.0-1018.20 -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 -- boot-testing-requested: true kernel-stable-master-bug: 1819716 - phase: Ready for Promote to Proposed - phase-changed: Wednesday, 27. March 2019 14:08 UTC + phase: Promote to Proposed + phase-changed: Wednesday, 27. March 2019 14:38 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- review in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819701 Title: linux-ibm-gt: 4.15.0-1018.20 -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 promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed 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: 1819716 phase: Promote to Proposed phase-changed: Wednesday, 27. March 2019 14:38 UTC reason: promote-to-proposed: Ongoing -- review in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819701/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820310] Re: linux-gcp: 5.0.0-1001.1 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-release Status: New => Confirmed ** Tags removed: block-proposed-disco ** Tags removed: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1819759 - phase: Ready for Testing - phase-changed: Monday, 25. March 2019 15:03 UTC + phase: Ready for Release + phase-changed: Wednesday, 27. March 2019 14:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress + promote-to-release: Pending -- ready to copy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1820310 Title: linux-gcp: 5.0.0-1001.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released 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-release series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux-gcp package in Ubuntu: Confirmed Status in linux-gcp source package in Disco: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1819759 phase: Ready for Release phase-changed: Wednesday, 27. March 2019 14:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-release: Pending -- ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1820310/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821713] Re: linux-raspi2: 4.4.0-1106.114 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** 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: 1821724 - phase: Promote to Proposed - phase-changed: Wednesday, 27. March 2019 12:31 UTC + phase: Testing + phase-changed: Wednesday, 27. March 2019 14:36 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + certification-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + snap-release-to-beta: Pending -- snap not in beta channel + snap-release-to-edge: Pending -- snap not in edge channel + 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/1821713 Title: linux-raspi2: 4.4.0-1106.114 -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: 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: Confirmed Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed 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 Xenial: Confirmed 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: 1821724 phase: Testing phase-changed: Wednesday, 27. March 2019 14:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in beta channel snap-release-to-edge: Pending -- snap not in edge channel verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1821713/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766851] Re: Missing `linux-update-symlinks` causes Linux package installation to fail
Related to #1820755 - although the new linux-base is now available in xenial-updates, the kernel packages do not version their depends to demand the new version, so apt-get will not necessarily install it (which causes base-installer to fail, since debootstrap will not have upgraded from xenial-updates prior to installing base- installer/kernel/image, and will not upgrade when the linux-image- generic Depends are already satisfied) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1766851 Title: Missing `linux-update-symlinks` causes Linux package installation to fail Status in linux-base package in Ubuntu: Confirmed Bug description: On Ubuntu 16.04.3 LTS, the installation of Linux 4.17-rc2 from [1] fails because `linux-update-symlinks` is not available. [1]: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc2/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1766851/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819701] Re: linux-ibm-gt: 4.15.0-1018.20 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819701 Title: linux-ibm-gt: 4.15.0-1018.20 -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 promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed 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: 1819716 phase: Ready for Promote to Proposed phase-changed: Wednesday, 27. March 2019 14:08 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/1819701/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819701] Re: linux-ibm-gt: 4.15.0-1018.20 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed 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: 1819716 - phase: Promote to Proposed - phase-changed: Tuesday, 26. March 2019 12:34 UTC + phase: Ready for Promote to Proposed + phase-changed: Wednesday, 27. March 2019 14:08 UTC reason: - promote-to-proposed: Stalled -- review 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/1819701 Title: linux-ibm-gt: 4.15.0-1018.20 -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 promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed 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: 1819716 phase: Ready for Promote to Proposed phase-changed: Wednesday, 27. March 2019 14:08 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/1819701/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819701] Re: linux-ibm-gt: 4.15.0-1018.20 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819701 Title: linux-ibm-gt: 4.15.0-1018.20 -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 promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed 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: 1819716 phase: Ready for Promote to Proposed phase-changed: Wednesday, 27. March 2019 14:08 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/1819701/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821929] Re: Bluetooth mouse is not able to connect
** Attachment added: "HCI trace captured by btmon" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1821929/+attachment/5249821/+files/hcitrace.snoop -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1821929 Title: Bluetooth mouse is not able to connect Status in bluez package in Ubuntu: New Bug description: I recently bought not expensive wireless mouse with bluetooth support: https://www.aliexpress.com/item/Wireless-Mouse-Bluetooth-Mouse-Silent-Computer-Mouse-PC-Mause-Wireless-Rechargeable-Ergonomic-Optical-USB-Mice-2/32879862474.html?spm=a2g0s.12269583.0.0.36ab310dUGrVZS I works in MacOS X and Windows but doesn't work in Linux. I suppose I can debug that mouse under Windows to collect more information if I have proper instructions. I collected some information about that mouse: # uname -a Linux asus-N752VX 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux # lsb_release -a Distributor ID:Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename:bionic # lsusb Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 0bda:8763 Realtek Semiconductor Corp. (BT usb) Bus 001 Device 002: ID 0bda:57f6 Realtek Semiconductor Corp. (Web cam) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub # usb-devices T: Bus=01 Lev=01 Prnt=01 Port=08 Cnt=04 Dev#= 6 Spd=12 MxCh= 0 D: Ver= 2.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=0bda ProdID=8763 Rev=02.00 S: Manufacturer=Realtek S: Product=Bluetooth Radio S: SerialNumber=00e04c01 C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=500mA I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb # bluetoothctl --version bluetoothctl: 5.48 # hciconfig -a hci0:Type: Primary Bus: USB BD Address: 94:E9:79:1A:89:1D ACL MTU: 820:8 SCO MTU: 255:16 UP RUNNING PSCAN RX bytes:1604 acl:0 sco:0 events:170 errors:0 TX bytes:28036 acl:0 sco:0 commands:166 errors:0 Features: 0xff 0xff 0xff 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT Name: 'asus-N752VX' Class: 0x1c010c Service Classes: Rendering, Capturing, Object Transfer Device Class: Computer, Laptop HCI Version: 4.0 (0x6) Revision: 0xe3e LMP Version: 4.0 (0x6) Subversion: 0x4380 Manufacturer: Realtek Semiconductor Corporation (93) # bluetoothctl [NEW] Controller 94:E9:79:1A:89:1D asus-N752VX [default] [NEW] Device 5A:4B:3C:0E:07:B2 Bluetooth Mouse 4.0 # show Controller 94:E9:79:1A:89:1D (public) Name: asus-N752VX Alias: asus-N752VX Class: 0x001c010c Powered: yes Discoverable: no Pairable: yes UUID: Headset AG(1112--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: OBEX Object Push (1105--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: IrMC Sync (1104--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: Vendor specific (5005--1000-8000-0002ee01) UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb) UUID: Phonebook Access Server (112f--1000-8000-00805f9b34fb) UUID: Message Access Server (1132--1000-8000-00805f9b34fb) UUID: Headset (1108--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0530 Discovering: no # devices Device 5A:4B:3C:0E:07:B2 Bluetooth Mouse 4.0 # info 5A:4B:3C:0E:07:B2 Device 5A:4B:3C:0E:07:B2 (public) Name: Bluetooth Mouse 4.0 Alias: Bluetooth Mouse 4.0 Class: 0x2580 Icon: input-mouse Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) Modalias: usb:v0A5Cp00
[Kernel-packages] [Bug 1821929] [NEW] Bluetooth mouse is not able to connect
Public bug reported: I recently bought not expensive wireless mouse with bluetooth support: https://www.aliexpress.com/item/Wireless-Mouse-Bluetooth-Mouse-Silent-Computer-Mouse-PC-Mause-Wireless-Rechargeable-Ergonomic-Optical-USB-Mice-2/32879862474.html?spm=a2g0s.12269583.0.0.36ab310dUGrVZS I works in MacOS X and Windows but doesn't work in Linux. I suppose I can debug that mouse under Windows to collect more information if I have proper instructions. I collected some information about that mouse: # uname -a Linux asus-N752VX 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux # lsb_release -a Distributor ID:Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename:bionic # lsusb Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 0bda:8763 Realtek Semiconductor Corp. (BT usb) Bus 001 Device 002: ID 0bda:57f6 Realtek Semiconductor Corp. (Web cam) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub # usb-devices T: Bus=01 Lev=01 Prnt=01 Port=08 Cnt=04 Dev#= 6 Spd=12 MxCh= 0 D: Ver= 2.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=0bda ProdID=8763 Rev=02.00 S: Manufacturer=Realtek S: Product=Bluetooth Radio S: SerialNumber=00e04c01 C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=500mA I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb # bluetoothctl --version bluetoothctl: 5.48 # hciconfig -a hci0:Type: Primary Bus: USB BD Address: 94:E9:79:1A:89:1D ACL MTU: 820:8 SCO MTU: 255:16 UP RUNNING PSCAN RX bytes:1604 acl:0 sco:0 events:170 errors:0 TX bytes:28036 acl:0 sco:0 commands:166 errors:0 Features: 0xff 0xff 0xff 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT Name: 'asus-N752VX' Class: 0x1c010c Service Classes: Rendering, Capturing, Object Transfer Device Class: Computer, Laptop HCI Version: 4.0 (0x6) Revision: 0xe3e LMP Version: 4.0 (0x6) Subversion: 0x4380 Manufacturer: Realtek Semiconductor Corporation (93) # bluetoothctl [NEW] Controller 94:E9:79:1A:89:1D asus-N752VX [default] [NEW] Device 5A:4B:3C:0E:07:B2 Bluetooth Mouse 4.0 # show Controller 94:E9:79:1A:89:1D (public) Name: asus-N752VX Alias: asus-N752VX Class: 0x001c010c Powered: yes Discoverable: no Pairable: yes UUID: Headset AG(1112--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: OBEX Object Push (1105--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: IrMC Sync (1104--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: Vendor specific (5005--1000-8000-0002ee01) UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb) UUID: Phonebook Access Server (112f--1000-8000-00805f9b34fb) UUID: Message Access Server (1132--1000-8000-00805f9b34fb) UUID: Headset (1108--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0530 Discovering: no # devices Device 5A:4B:3C:0E:07:B2 Bluetooth Mouse 4.0 # info 5A:4B:3C:0E:07:B2 Device 5A:4B:3C:0E:07:B2 (public) Name: Bluetooth Mouse 4.0 Alias: Bluetooth Mouse 4.0 Class: 0x2580 Icon: input-mouse Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) Modalias: usb:v0A5Cp0001d0129 # paired-devices Device 5A:4B:3C:0E:07:B2 Bluetooth Mouse 4.0 # trust 5A:4B:3C:0E:07:B2 Changing 5A:4B:3C:0E:07:B2 trust succeeded # connect 5A:4B:3C:0E:07:B2 Attempting to connect to 5A:4B:3C:0E:07:B2 Failed to connect: org.bluez.Error.Failed # rfkill list 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no 1: hci0: Bluetooth Soft blocked: no Hard blocked: no /var/log/syslog: 16:34:35 asus-N752VX bluetoothd[1313]: src/device.c:connect_profiles() /org/bluez/hci0/dev_5A_4B_3C_0E_07_B2 (all), client :1.197 16:34:35 asus-N752VX bluetoothd[1313]: profiles/input/device.c:input
[Kernel-packages] [Bug 1820755] Re: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found
Some more info: from http://changelogs.ubuntu.com/changelogs/pool/main/l /linux-base/linux-base_4.5ubuntu1~16.04.1/changelog, it looks like the actual cutoff would be Depends: linux-base (>= 4.1) On the question of workarounds, that confirms why pkgsel/upgrade didn't work, it's all in the base-installer udeb. The only hook point between apt-get update (where the new linux-base would be discovered) and the kernel (which currently assumes it's already installed) is the post_install_hooks call at https://salsa.debian.org/installer-team/base- installer/blob/master/debian/bootstrap-base.postinst#L188, which invokes scripts in /usr/lib/post-base-installer.d: https://salsa.debian.org /installer-team/base-installer/blob/master/library.sh#L265. And I find nothing in those hooks that would preseed can control. So I'm not finding any way around it except a fixed kernel package with the right (versioned) Depends on linux-base. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1820755 Title: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found Status in Blue Linux: New Status in linux package in Ubuntu: Confirmed Status in linux-base package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Status in linux-base source package in Xenial: Fix Released Bug description: Using a netboot install of Ubuntu 16.04 LTS server, the install fails when configuring the kernel. The failure will not let you move on. This seems to have happened after the release of https://lists.ubuntu.com/archives/ubuntu-security-announce/2019-March/004803.html The error logs Mar 18 17:09:50 in-target: Setting up linux-modules-4.4.0-143-generic (4.4.0-143.169) ... Mar 18 17:09:50 in-target: ^M Mar 18 17:09:51 in-target: Setting up linux-image-4.4.0-143-generic (4.4.0-143.169) ... Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: 50: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: Mar 18 17:09:51 in-target: linux-update-symlinks: not found Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: dpkg: error processing package linux-image-4.4.0-143-generic (--configure): Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: subprocess installed post-installation script returned error exit status 127 Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: dpkg: dependency problems prevent configuration of linux-modules-extra-4.4.0-143-generic: Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: linux-modules-extra-4.4.0-143-generic depends on linux-image-4.4.0-143-generic | linux-image-unsigned-4.4.0-143-generic; however: Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: Package linux-image-4.4.0-143-generic is not configured yet. Mar 18 17:09:51 in-target: ^M Mar To manage notifications about this bug go to: https://bugs.launchpad.net/bluelinux/+bug/1820755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821712] Re: linux-kvm: 4.4.0-1043.49 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** 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: 1821724 - phase: Promote to Proposed - phase-changed: Wednesday, 27. March 2019 11:10 UTC + phase: Testing + phase-changed: Wednesday, 27. March 2019 13:30 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + 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-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1821712 Title: linux-kvm: 4.4.0-1043.49 -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: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Confirmed 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: 1821724 phase: Testing phase-changed: Wednesday, 27. March 2019 13:30 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1821712/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748565]
Comment 24 suggests to me that this bug should be closed (?). Because it seems to eliminate the possibility of the message appearing with (0x0f). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1748565 Title: Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete (0x0f) Status in Linux: Confirmed 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 Status in Fedora: New Bug description: === SRU Justification === [Impact] Kernel constantly reports "Bluetooth: hci0: last event is not cmd complete (0x0f)" when using Bluetooth. [Fix] If the HCI event is Command Status, just bail because there's no further thing to do. [Test] Open Gnome Control Center's Bluetooth panel to start BT scan. The kernel keeps spewing out the messege. After applying the patch the message doesn't show anymore. [Regression Potential] Low. Upstream patch and succesfully tested. === Original Bug Report === Hello, dmesg: [ 3363.056494] Bluetooth: hci0: last event is not cmd complete (0x0f) Regards, -- Cristian ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-9-generic 4.15.0-9.10 ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2 Uname: Linux 4.15.0-9-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1811 F pulseaudio CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Fri Feb 9 20:35:29 2018 InstallationDate: Installed on 2017-10-13 (119 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-9-generic root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-9-generic N/A linux-backports-modules-4.15.0-9-generic N/A linux-firmware1.170 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1748565/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563]
maybe you have a "unique" mouse?try a different usb mouse and reboot -- 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563]
Or i'm very lucky and this is coincedence or yes, when my mice is connected (doesn't have other usb devices at the moment) to usb 2.0 that is nearest to power plug my boot is successfull without any special kernel arguments. -- 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818854] Re: [Ubuntu] vfio-ap: add subsystem to matrix device to avoid libudev failures
** Changed in: ubuntu-z-systems Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818854 Title: [Ubuntu] vfio-ap: add subsystem to matrix device to avoid libudev failures Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Status in linux source package in Disco: Fix Committed Bug description: SRU Justification: [Impact] * The vfio-ap driver will create a matrix device in sysfs without a subsystem link. * This causes failures in libudev that might also lead to libvirt errors. * A fix is upstream in master branch for kernel 5.1 [Fix] * 36360658eb5a6cf04bb9f2704d1e4ce54037ec99 3636065 "s390: vfio_ap: link the vfio_ap devices to the vfio_ap bus subsystem" [Test Case] * An s390x machine with at least one CryptoExpress card, where at least one AP and one 'Domain' is assigned to a particular LPAR. * Now running virsh nodedev-list before (and later after) construction the matrix device should expose the issue. * For details about how to setup a vfio-ap matrix device see: http://kvmonz.blogspot.com/2018/12/qemu-v31-released.html (see 2nd bullet: virtio-ap) [Regression Potential] * The regression potential can be considered as low since it only affects the s390x platform * and there it only affects the usage of AP (CryptoExpress) cards and it's driver/module * and again only affects the recently introduced virtual IO function of AP (vfio-ap). [Other Info] * It was already briefly discussed here: https://www.redhat.com/archives/libvir-list/2019-February/msg00837.html as well as reviewed and pushed. * Commit 3636065 from v5.1-rc1 * This affects ccw cards and their vf only, NOT vf of PCI/PCIe cards! * For details on virtio-ap/vfio-ap see bullet #2 here: http://kvmonz.blogspot.com/2018/12/qemu-v31-released.html _ ---Problem Description--- The vfio-ap driver will create a matrix device in sysfs without a subsystem link. This triggers failures in libudev that might also lead to libvirt errors (e.g. see https://www.redhat.com/archives/libvir-list/2019-February/msg00837.html) The proper fix is to add a subsystem link (e.g. by providing a dummy bus). A fix for that is upstream in master branch already for kernel 5.1 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=36360658eb5a6cf04bb9f2704d1e4ce54037ec99 This need to be applied to Bionic, Cosmic and Disco To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1818854/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820310] Re: linux-gcp: 5.0.0-1001.1 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1820310 Title: linux-gcp: 5.0.0-1001.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released 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-release series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in linux-gcp package in Ubuntu: Confirmed Status in linux-gcp source package in Disco: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1819759 phase: Ready for Testing phase-changed: Monday, 25. March 2019 15:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1820310/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818204] Re: Qualcomm Atheros QCA9377 wireless does not work
** Changed in: linux (Ubuntu) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818204 Title: Qualcomm Atheros QCA9377 wireless does not work Status in linux package in Ubuntu: Fix Committed Status in network-manager package in Ubuntu: Invalid Bug description: === SRU Justification === [Impact] Lenovo ideapad 530S-14ARR Wifi rfkill hard blocked [Fix] The platform in question doesn't have hardware RF switch, so quirk it off. [Test] User confirm it fixes the issue. [Regression Potential] Minimal. This fix is limited to one specific platform. === Original Bug Report === I have Lenovo 530s laptop with Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31). The menu shows that wireless is off. Turning on the wireless from the menu does not do anything. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 1 11:42:34 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-02-20 (8 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IpRoute: default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100 130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 130.232.69.176 metric 100 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 ada277fe-966d-33ff-aba2-8ba32d6ce5a9 ethernet 155143 pe 1. maaliskuuta 2019 11.42.13 yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes enx00e04c704f68 activated /org/freedesktop/NetworkManager/ActiveConnection/11 -- virbr0 dc46fe89-5b22-438a-85d5-37be48a077ea bridge 155143 pe 1. maaliskuuta 2019 11.42.13 no 0 no/org/freedesktop/NetworkManager/Settings/2 yes virbr0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled disabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sami 1315 F pulseaudio /dev/snd/controlC0: sami 1315 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-02-20 (11 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IpRoute: default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100 130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 130.232.69.176 metric 100 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown MachineType: LENOVO 81H1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.6-2ubuntu1.1 PackageArchitecture: amd64 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=UUID=a6aaac69-de44-4491-bfb7-0e57c9ff25cf ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 Tags: bionic wayland-session wayland-session Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/17/2018 dmi.bi
[Kernel-packages] [Bug 1811815] Re: Lenovo ideapad 330-15ICH Wifi rfkill hard blocked
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811815 Title: Lenovo ideapad 330-15ICH Wifi rfkill hard blocked Status in linux package in Ubuntu: Fix Committed Bug description: === SRU Justification === [Impact] Lenovo ideapad 330-15ICH Wifi rfkill hard blocked [Fix] The platform in question doesn't have hardware RF switch, so quirk it off. [Test] User confirm it fixes the issue. [Regression Potential] Minimal. This fix is limited to one specific platform. === Original Bug Report === The issue here is that the drivers/platform/x86/ideapad_laptop.c module assumes the Lenovo Ideapad 330-15ICH has a hardware RF-kill switch, reads the I/O port for its state, gets a zero, and therefore reports to the kernel that RFkill is hard-blocked. The current workaround is to blacklist the module to stop it being loaded. I've attached a simple patch for the module that teaches it that this model does not have a hardware RF kill switch. Original Report - Ubuntu 18.10 does not detect the Intel Dual Band Wireless-AC 3165 card, specifically on a Lenovo ideapad 330 laptop. A current workaround: - Blacklist the "ideapad-laptop" module. - Edit/create a file in "/etc/modprobe.d/" and name it "blacklist.conf" or something similar (if it does not already exist), and append "blacklist ideapad-laptop" to the file. Save and reboot. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dustin 1948 F pulseaudio /dev/snd/pcmC0D0p: dustin 1948 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 15 04:08:20 2019 InstallationDate: Installed on 2019-01-15 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:210e Acer, Inc Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 3938:1047 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81FK ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=fa5d161c-779c-4cf7-aa07-6da06d655747 ro acpi_osi=! "acpi_osi=Windows 2012" quiet splash nouveau.modeset=0 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7ZCN28WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15ICH dmi.modalias: dmi:bvnLENOVO:bvr7ZCN28WW:bd07/17/2018:svnLENOVO:pn81FK:pvrLenovoideapad330-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15ICH: dmi.product.family: ideapad 330-15ICH dmi.product.name: 81FK dmi.product.sku: LENOVO_MT_81FK_BU_idea_FM_ideapad 330-15ICH dmi.product.version: Lenovo ideapad 330-15ICH dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818854] Re: [Ubuntu] vfio-ap: add subsystem to matrix device to avoid libudev failures
Disco has already received the fix from upstream stable. ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Disco) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818854 Title: [Ubuntu] vfio-ap: add subsystem to matrix device to avoid libudev failures Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Status in linux source package in Disco: Fix Committed Bug description: SRU Justification: [Impact] * The vfio-ap driver will create a matrix device in sysfs without a subsystem link. * This causes failures in libudev that might also lead to libvirt errors. * A fix is upstream in master branch for kernel 5.1 [Fix] * 36360658eb5a6cf04bb9f2704d1e4ce54037ec99 3636065 "s390: vfio_ap: link the vfio_ap devices to the vfio_ap bus subsystem" [Test Case] * An s390x machine with at least one CryptoExpress card, where at least one AP and one 'Domain' is assigned to a particular LPAR. * Now running virsh nodedev-list before (and later after) construction the matrix device should expose the issue. * For details about how to setup a vfio-ap matrix device see: http://kvmonz.blogspot.com/2018/12/qemu-v31-released.html (see 2nd bullet: virtio-ap) [Regression Potential] * The regression potential can be considered as low since it only affects the s390x platform * and there it only affects the usage of AP (CryptoExpress) cards and it's driver/module * and again only affects the recently introduced virtual IO function of AP (vfio-ap). [Other Info] * It was already briefly discussed here: https://www.redhat.com/archives/libvir-list/2019-February/msg00837.html as well as reviewed and pushed. * Commit 3636065 from v5.1-rc1 * This affects ccw cards and their vf only, NOT vf of PCI/PCIe cards! * For details on virtio-ap/vfio-ap see bullet #2 here: http://kvmonz.blogspot.com/2018/12/qemu-v31-released.html _ ---Problem Description--- The vfio-ap driver will create a matrix device in sysfs without a subsystem link. This triggers failures in libudev that might also lead to libvirt errors (e.g. see https://www.redhat.com/archives/libvir-list/2019-February/msg00837.html) The proper fix is to add a subsystem link (e.g. by providing a dummy bus). A fix for that is upstream in master branch already for kernel 5.1 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=36360658eb5a6cf04bb9f2704d1e4ce54037ec99 This need to be applied to Bionic, Cosmic and Disco To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1818854/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819658] Re: linux-aws: 4.4.0-1040.43 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => 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: 1821724 - phase: Testing - phase-changed: Monday, 25. March 2019 15:07 UTC + phase: Ready for Testing + phase-changed: Wednesday, 27. March 2019 13:08 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: 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/1819658 Title: linux-aws: 4.4.0-1040.43 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released 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: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: 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: 1821724 phase: Ready for Testing phase-changed: Wednesday, 27. March 2019 13:08 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-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/1819658/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp