[Kernel-packages] [Bug 1773509] Re: ELANPAD ELAN0612 does not work, patch available
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Bionic) Status: Triaged => In Progress ** Changed in: linux (Ubuntu) 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/1773509 Title: ELANPAD ELAN0612 does not work, patch available Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: Seems there is a new version of the ELANPAD touchpad with identifier ELAN0612 that is being included in newer laptops. The kernel itself doesn't have support for this touchpad yet. However, the patch to get this working is trivial. Since people start being affected by this, would it be possible to include the patch in the ubuntu kernel packages until it is merged upstream? Especially, support in 18.04 would nice. The upstream bug at the Kernel project, including the patch is here: https://bugzilla.kernel.org/show_bug.cgi?id=199253 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773509/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773973] Re: Ubuntu 18.04 [ Garrison P8 ]: Machine crashes with oops while booting with 4.15.0-22-generic kernel.
this is a kernel crash; unassigning the Foundations Team. ** Changed in: ubuntu-power-systems Assignee: Canonical Foundations Team (canonical-foundations) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773973 Title: Ubuntu 18.04 [ Garrison P8 ]: Machine crashes with oops while booting with 4.15.0-22-generic kernel. Status in The Ubuntu-power-systems project: New Status in debian-installer package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: ---Problem Description--- Ubuntu 18.04 [ Garrison P8 ]: Machine crashes with oops while booting with 4.15.0-22-generic kernel. ---Environment-- Kernel Build: 4.15.0-22-generic System Name : ltc-garri1 Model/Type : P8 Platform: BML ---Uname output--- Unable to boot. ---Steps to reproduce-- 1. Install Ubuntu 18.04 on Garison BML from http://ports.ubuntu.com /ubuntu-ports/dists/bionic/main/installer- ppc64el/current/images/netboot/ubuntu-installer/ppc64el/ and try to boot. ---Logs Attaching console lob. [4.578205] Bad kernel stack pointer 7b0dd870 at c000b9ec [4.578244] Oops: Bad kernel stack pointer, sig: 6 [#11] [4.578271] LE SMP NR_CPUS=2048 NUMA PowerNV [4.578301] Modules linked in: [4.578324] CPU: 27 PID: 1225 Comm: modprobe Tainted: G D 4.15.0-22-generic #24-Ubuntu [4.578371] NIP: c000b9ec LR: CTR: [4.578413] REGS: c0003febbd40 TRAP: 0300 Tainted: G D (4.15.0-22-generic) [4.578460] MSR: 90001031 CR: XER: [4.578504] CFAR: c000b934 DAR: 0002b200 DSISR: 4000 SOFTE: -4611686018403131680 [4.578504] GPR00: 7b0dd870 [4.578504] GPR04: [4.578504] GPR08: [4.578504] GPR12: 75dcd8781700 0002b200 [4.578504] GPR16: [4.578504] GPR20: [4.578504] GPR24: [4.578504] GPR28: [4.615667] NIP [c000b9ec] fast_exception_return+0x9c/0x184 [4.616210] LR [] (null) [4.616237] Call Trace: [4.616768] Instruction dump: [4.616789] e84101a0 7c4ff120 e8410170 7c5a03a6 e8010070 e8410080 e8610088 e8810090 [4.617697] e8210078 7db243a6 7db142a6 7c0004ac 63ff 7db242a6 63ff [4.618195] ---[ end trace a0d70ba94f583cca ]--- [4.675899] usb 1-3.3: new high-speed USB device number 5 using xhci_hcd [4.782923] [4.783061] Key type encrypted registered [4.783087] AppArmor: AppArmor sha1 policy hashing enabled [4.783117] ima: No TPM chip found, activating TPM-bypass! (rc=-19) [4.783181] evm: HMAC attrs: 0x1 [4.806062] rtc-opal opal-rtc: setting system clock to 2018-05-29 07:49:29 UTC (1527580169) [4.806350] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) [4.806353] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) [4.807260] Freeing unused kernel memory: 4800K [4.807321] This architecture does not have kernel memory protection. == Comment: #2 - SEETEENA THOUFEEK - 2018-05-29 06:47:06 == Symptoms looks exactly like . https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1691978 . https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656908 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1773973/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767927] Re: ISST-LTE:pKVM:Ubuntu1804: rcu_sched self-detected stall on CPU follow by CPU ATTEMPT TO RE-ENTER FIRMWARE!
The activity log: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767927/+activity shows that it was removed by LP user 'bugproxy' - probably an accident of the Bugzilla bridge?! Looks like the Bugzilla bridge removed several tags (see log entry '2018-05-29 17:19:23'. @IBM please verify if the bridge behavior is correct and than expected. For now I added the tags again ... ** Tags added: kernel-da-key verification-needed-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/1767927 Title: ISST-LTE:pKVM:Ubuntu1804: rcu_sched self-detected stall on CPU follow by CPU ATTEMPT TO RE-ENTER FIRMWARE! Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: == Comment: #0 - Application Cdeadmin - 2018-03-20 14:10:53 == == Comment: #1 - Application Cdeadmin - 2018-03-20 14:10:54 == == Comment: #2 - Application Cdeadmin - 2018-03-20 14:10:56 == --- Comment From dougmill-ibm 2018-03-20 13:51:47 EDT --- This problem is not tied to a Linux distro. It will be fixed in firmware, as I understand it. Let us close any redundant issues for this same problem. Mark them as duplicate. == Comment: #3 - Application Cdeadmin - 2018-03-20 15:50:54 == --- Comment From mzipse 2018-03-20 15:44:26 EDT --- @stewart-ibm @svaidy , I need to you take a first look. The stop fixes that Vaidy had previously highlighted in a recent note are included in the 3/15 PNOR. == Comment: #5 - Application Cdeadmin - 2018-04-04 16:10:56 == --- Comment From haochanh 2018-04-04 16:04:07 EDT --- We update to 0330, bmc=1.18, then we hit bug 1134. Currently we are running with disable stop5 but still see the watchdog: hard lockup. After 2 hours of test run, I am seeing the "Watchdog: Lockup' and "became unstuck" [Wed Apr 4 13:38:25 2018] Watchdog CPU:42 Hard LOCKUP [Wed Apr 4 13:38:25 2018] Modules linked in: vhost_net vhost macvtap macvlan tap xfs xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter rpcsec_gss_krb5 nfsv4 nfs fscache rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx5_ib(OE) mlx5_core(OE) mlxfw(OE) cxl pnv_php mlx4_en(OE) mlx4_ib(OE) ib_core(OE) mlx4_core(OE) devlink mlx_compat(OE) kvm_hv kvm binfmt_misc dm_service_time dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua input_leds joydev mac_hid idt_89hpesx ipmi_powernv [Wed Apr 4 13:38:25 2018] vmx_crypto ipmi_devintf at24 ofpart uio_pdrv_genirq cmdlinepart uio powernv_flash ipmi_msghandler mtd crct10dif_vpmsum opal_prd ibmpowernv nfsd sch_fq_codel auth_rpcgss nfs_acl lockd grace sunrpc knem(OE) ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq ses enclosure scsi_transport_sas hid_generic usbhid hid lpfc ast i2c_algo_bit ttm drm_kms_helper nvmet_fc syscopyarea sysfillrect nvmet sysimgblt fb_sys_fops nvme_fc nvme_fabrics crc32c_vpmsum drm i40e scsi_transport_fc aacraid [last unloaded: mlxfw] [Wed Apr 4 13:38:25 2018] CPU: 42 PID: 0 Comm: swapper/42 Tainted: G OE4.15.0-12-generic #13 [Wed Apr 4 13:38:25 2018] NIP: c00a3ca4 LR: c00a3ca4 CTR: c0008000 [Wed Apr 4 13:38:25 2018] REGS: c00ff596fc40 TRAP: 0100 Tainted: G OE (4.15.0-12-generic) [Wed Apr 4 13:38:25 2018] MSR: 90001033 CR: 24004482 XER: 2004 [Wed Apr 4 13:38:25 2018] CFAR: c00ff596fda0 SOFTE: 42 GPR00: c00a3ca4 c00ff596fda0 c16eb200 c00ff596fc40 GPR04: b0001033 c00a3690 24004484 000ffa45 GPR08: 0001 c0d10ed8 00ff GPR12: 90121033 c7a3ce00 c00ff596ff90 GPR16: c0047840 c0047810 c11b5380 GPR20: 0800 c1722484 002a GPR24: 00a8 0007 0007 GPR28: c161d270 c00ffb666fd8 c161d528 0007 [Wed Apr 4 13:38:25 2018] NIP [c00a3ca4] power9_idle_type+0x24/0x40 [Wed Apr 4 13:38:25 2018] LR [c00a3ca4] power9_idle_type+0x24/0x40 [Wed Apr 4 13:38:25 2018] Call Trace:
[Kernel-packages] [Bug 159356] Re: System freeze on high memory usage
** Changed in: fedora Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/159356 Title: System freeze on high memory usage Status in linux package in Ubuntu: Confirmed Status in linux package in Arch Linux: New Status in Fedora: Won't Fix Bug description: I run a batch matlab job server here at my lab, running Dapper 6.06 (for the LTS). One of the users has submitted a very memory-consuming job, which successfully crashes the server. Upon closer inspection, the crash happens like this: 1. I run matlab with the given file (as an ordinary, unpriveleged user) 2. RAM usage quickly fills up 3. Once the RAM meter hits 100%, the system freezes: All SSH connections freeze up, and while switching VTs directly on the machine works, no new processes run - so one can't log in, or do anything if he is logged in. (Sometimes typing doesn't work at all) Note that the swap - while 7 gigs of it are available - is never used. (The machine has 7 gigs of RAM as well) I've tried the same on my Gutsy 32-bit box, and there was no system freezeup - matlab simply notified that the system was out of memory. However, it did this once memory was 100% in use - and still, swap didn't get used at all! (Though it is mounted correctly and shows up in "top" and "free"). So first thing's first - I'd like to eliminate the crash issue. I suppose I could switch the server to 32-bit, but I think that would be a performance loss, considering that it does a lot of heavy computation. There is no reason, however, that this should happen on a 64-bit machine anyway. Why does it? WORKAROUND: Enabling DMA in the BIOS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773973] Re: Ubuntu 18.04 [ Garrison P8 ]: Machine crashes with oops while booting with 4.15.0-22-generic kernel.
** Changed in: ubuntu-power-systems Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773973 Title: Ubuntu 18.04 [ Garrison P8 ]: Machine crashes with oops while booting with 4.15.0-22-generic kernel. Status in The Ubuntu-power-systems project: New Status in debian-installer package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: ---Problem Description--- Ubuntu 18.04 [ Garrison P8 ]: Machine crashes with oops while booting with 4.15.0-22-generic kernel. ---Environment-- Kernel Build: 4.15.0-22-generic System Name : ltc-garri1 Model/Type : P8 Platform: BML ---Uname output--- Unable to boot. ---Steps to reproduce-- 1. Install Ubuntu 18.04 on Garison BML from http://ports.ubuntu.com /ubuntu-ports/dists/bionic/main/installer- ppc64el/current/images/netboot/ubuntu-installer/ppc64el/ and try to boot. ---Logs Attaching console lob. [4.578205] Bad kernel stack pointer 7b0dd870 at c000b9ec [4.578244] Oops: Bad kernel stack pointer, sig: 6 [#11] [4.578271] LE SMP NR_CPUS=2048 NUMA PowerNV [4.578301] Modules linked in: [4.578324] CPU: 27 PID: 1225 Comm: modprobe Tainted: G D 4.15.0-22-generic #24-Ubuntu [4.578371] NIP: c000b9ec LR: CTR: [4.578413] REGS: c0003febbd40 TRAP: 0300 Tainted: G D (4.15.0-22-generic) [4.578460] MSR: 90001031 CR: XER: [4.578504] CFAR: c000b934 DAR: 0002b200 DSISR: 4000 SOFTE: -4611686018403131680 [4.578504] GPR00: 7b0dd870 [4.578504] GPR04: [4.578504] GPR08: [4.578504] GPR12: 75dcd8781700 0002b200 [4.578504] GPR16: [4.578504] GPR20: [4.578504] GPR24: [4.578504] GPR28: [4.615667] NIP [c000b9ec] fast_exception_return+0x9c/0x184 [4.616210] LR [] (null) [4.616237] Call Trace: [4.616768] Instruction dump: [4.616789] e84101a0 7c4ff120 e8410170 7c5a03a6 e8010070 e8410080 e8610088 e8810090 [4.617697] e8210078 7db243a6 7db142a6 7c0004ac 63ff 7db242a6 63ff [4.618195] ---[ end trace a0d70ba94f583cca ]--- [4.675899] usb 1-3.3: new high-speed USB device number 5 using xhci_hcd [4.782923] [4.783061] Key type encrypted registered [4.783087] AppArmor: AppArmor sha1 policy hashing enabled [4.783117] ima: No TPM chip found, activating TPM-bypass! (rc=-19) [4.783181] evm: HMAC attrs: 0x1 [4.806062] rtc-opal opal-rtc: setting system clock to 2018-05-29 07:49:29 UTC (1527580169) [4.806350] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) [4.806353] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) [4.807260] Freeing unused kernel memory: 4800K [4.807321] This architecture does not have kernel memory protection. == Comment: #2 - SEETEENA THOUFEEK - 2018-05-29 06:47:06 == Symptoms looks exactly like . https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1691978 . https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656908 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1773973/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773704] Re: Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset in Bionic 18.04
** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Bionic) Status: Triaged => In Progress ** Changed in: linux (Ubuntu) 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/1773704 Title: Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset in Bionic 18.04 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: A typo at line 184 in /drivers/usb/host/xhci-pci.c trashes a good fix. 183 if (pdev->vendor == PCI_VENDOR_ID_RENESAS && 184 pdev->device == 0x0014) 185 xhci->quirks |= XHCI_TRUST_TX_LENGTH; 186 if (pdev->vendor == PCI_VENDOR_ID_RENESAS && 187 pdev->device == 0x0015) 188 xhci->quirks |= XHCI_RESET_ON_RESUME; Line 184 should be identical to line 187, ie: should read pdev->device == 0x0015) I've compiled the kernel both with and without the typo. As written, hundreds of messages fill dmesg suggesting XHCI_TRUST_TX_LENGTH may be needed when zoneminder tries to access my USB webcams. With the fix applied as I've suggested the messages disappear. The typo is still present in 4.15.0-22.24 For more background, you may refer to bug ID #1710548 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773509] Re: ELANPAD ELAN0612 does not work, patch available
I built a test kernel with your patch. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1773509 Can you test this kernel and see if it resolves this bug? Note about installing test kernels: • If the test kernel is prior to 4.15(Bionic) you need to install the linux-image and linux-image-extra .deb packages. • If the test kernel is 4.15(Bionic) or newer, you need to install the linux-modules, linux-modules-extra and linux-image-unsigned .deb packages. Thanks in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773509 Title: ELANPAD ELAN0612 does not work, patch available Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: Seems there is a new version of the ELANPAD touchpad with identifier ELAN0612 that is being included in newer laptops. The kernel itself doesn't have support for this touchpad yet. However, the patch to get this working is trivial. Since people start being affected by this, would it be possible to include the patch in the ubuntu kernel packages until it is merged upstream? Especially, support in 18.04 would nice. The upstream bug at the Kernel project, including the patch is here: https://bugzilla.kernel.org/show_bug.cgi?id=199253 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773509/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770784] Comment bridged from LTC Bugzilla
--- Comment From cha...@us.ibm.com 2018-05-29 14:59 EDT---
Are we still seeing this issue reproduced or could this be related to some
other bug that has also been seen?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1770784
Title:
ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp4g4:ubuntu1604:P8 compat: guest
crashes in apparmor_file_alloc_security()
Status in The Ubuntu-power-systems project:
Triaged
Status in linux package in Ubuntu:
New
Bug description:
Test was running an Ubuntu 16.04 guest with a Ubuntu 18.04 host when
the guest dumped a vmcore.
According to the dump, the crash is actually a BUG_ON() raised from
apparmor_file_alloc_security() having called aa_begin_current_label()
which calls aa_current_raw_label() that in turn calls
aa_cred_raw_label() where the BUG_ON() resides:
static inline struct aa_label *aa_cred_raw_label(const struct cred *cred)
{
struct aa_task_ctx *ctx = cred_ctx(cred);
BUG_ON(!ctx || !ctx->label);
return ctx->label;
}
Now, the warnings we previously had seen raised from aa_file_perm()
may have been related since rcu_dereference() as fctx->label is NULL.
fctx = file_ctx(file);
rcu_read_lock();
flabel = rcu_dereference(fctx->label);
AA_BUG(!flabel);
KERNEL: /usr/lib/debug/boot/vmlinux-4.4.0-124-generic
DUMPFILE: dump.201805110830 [PARTIAL DUMP]
CPUS: 32
DATE: Fri May 11 06:30:35 2018
UPTIME: 03:40:43
LOAD AVERAGE: 102.77, 103.38, 100.54
TASKS: 862
NODENAME: boslcp4g4
RELEASE: 4.4.0-124-generic
VERSION: #148-Ubuntu SMP Wed May 2 13:02:22 UTC 2018
MACHINE: ppc64le (2134 Mhz)
MEMORY: 16 GB
PANIC: "kernel BUG at
/build/linux-VRGJAN/linux-4.4.0/security/apparmor/include/context.h:69!"
PID: 18397
COMMAND: "chgrp"
TASK: c0035be322c0 [THREAD_INFO: c0035b5c]
CPU: 10
STATE: TASK_RUNNING (PANIC)
crash> bt
PID: 18397 TASK: c0035be322c0 CPU: 10 COMMAND: "chgrp"
#0 [c0035b5c3430] crash_kexec at c0176274
#1 [c0035b5c35d0] die at c0020ef8
#2 [c0035b5c3660] _exception at c0021244
#3 [c0035b5c37f0] program_check_common at c0006208
Program Check [700] exception frame:
R0: c04923e4R1: c0035b5c3ae0R2: c15fa700
R3: c000fcd01a00R4: 0001R5: ffc0
R6: c000fcd01b00R7: 0003fe8dR8: c163a700
R9: 0001R10: R11:
R12: c04fd880R13: c7b06400R14:
R15: R16: 0013R17:
R18: 3fffb7501468R19: R20: 3fffb74ff7e0
R21: R22: R23: 3fffdf3cbd40
R24: 9001R25: 0041R26: f000
R27: c0035b5c3dd0R28: c16342f8R29: c000fcd01a00
R30: c000fcd01a00R31:
NIP: c04fd8c8MSR: 80029033OR3: c04923e0
CTR: c04fd880LR: c04923e4XER:
CCR: 24004248MQ: 0001DAR: c00328004288
DSISR: c0035b5c39e0 Syscall Result:
#4 [c0035b5c3ae0] apparmor_file_alloc_security at c04fd8c8
[Link Register] [c0035b5c3ae0] security_file_alloc at c04923e4
#5 [c0035b5c3b50] security_file_alloc at c04923e4 (unreliable)
#6 [c0035b5c3b90] get_empty_filp at c02e7010
#7 [c0035b5c3c10] path_openat at c02faa2c
#8 [c0035b5c3c90] do_filp_open at c02fc9bc
#9 [c0035b5c3db0] do_sys_open at c02e3150
#10 [c0035b5c3e30] system_call at c0009484
System Call [c01] exception frame:
R0: 0005R1: 3fffdf3cb8c0R2: 3fffb7507e00
R3: 0100270514b0R4: 0008R5: 3fffb7501ef8
R6: 0008R7: 9001R8: 3fffdf3cbd40
R9: R10: R11:
R12: R13: 3fffb750a190
NIP: 3fffb74dbdacMSR: 8280f033OR3: 0100270514b0
CTR: LR: 3fffb74b7034XER:
CCR: 44004442MQ: 0001DAR: 3fffb748
DSISR: 4000 Syscall Result: fffe
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1770784/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe :
Re: [Kernel-packages] [Bug 1773990] Re: package linux-image-4.15.0-20-generic 4.15.0-20.21 failed to install/upgrade: installed linux-image-4.15.0-20-generic package post-removal script subprocess ret
Yes it does. This bug report was then triggered automatically upon booting. Best, Jan On Tue, 29 May 2018, 17:50 Joseph Salisbury, wrote: > Does your system boot if you select the previous kernel version from the > GRUB menu? > > ** Package changed: linux-signed (Ubuntu) => linux (Ubuntu) > > ** Changed in: linux (Ubuntu) >Importance: Undecided => High > > ** Tags added: kernel-da-key > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1773990 > > Title: > package linux-image-4.15.0-20-generic 4.15.0-20.21 failed to > install/upgrade: installed linux-image-4.15.0-20-generic package post- > removal script subprocess returned error exit status 21 > > Status in linux package in Ubuntu: > New > > Bug description: > Happened after upgrading to 18.04 from 16.04. Ubuntu fails to boot > with kernel 4.15 as well. > > ProblemType: Package > DistroRelease: Ubuntu 18.04 > Package: linux-image-4.15.0-20-generic 4.15.0-20.21 > ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16 > Uname: Linux 4.13.0-39-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7 > AptOrdering: >linux-image-4.15.0-20-generic:amd64: Remove >NULL: ConfigurePending > Architecture: amd64 > Date: Tue May 29 16:12:20 2018 > DpkgTerminalLog: >Removing linux-image-4.15.0-20-generic (4.15.0-20.21) ... >Failed to create or replace /vmlinuz.old: Is a directory at > /usr/bin/linux-update-symlinks line 72. >dpkg: error processing package linux-image-4.15.0-20-generic (--remove): > installed linux-image-4.15.0-20-generic package post-removal script > subprocess returned error exit status 21 > DuplicateSignature: >package:linux-image-4.15.0-20-generic:4.15.0-20.21 >Removing linux-image-4.15.0-20-generic (4.15.0-20.21) ... >Failed to create or replace /vmlinuz.old: Is a directory at > /usr/bin/linux-update-symlinks line 72. >dpkg: error processing package linux-image-4.15.0-20-generic (--remove): > installed linux-image-4.15.0-20-generic package post-removal script > subprocess returned error exit status 21 > ErrorMessage: installed linux-image-4.15.0-20-generic package > post-removal script subprocess returned error exit status 21 > InstallationDate: Installed on 2016-05-10 (748 days ago) > InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 > (20160420.1) > Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, > 3.6.5-3 > PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, > 2.7.15~rc1-1 > RelatedPackageVersions: >dpkg 1.19.0.5ubuntu2 >apt 1.6.1 > SourcePackage: linux-signed > Title: package linux-image-4.15.0-20-generic 4.15.0-20.21 failed to > install/upgrade: installed linux-image-4.15.0-20-generic package > post-removal script subprocess returned error exit status 21 > UpgradeStatus: Upgraded to bionic on 2018-05-05 (24 days ago) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773990/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773990 Title: package linux-image-4.15.0-20-generic 4.15.0-20.21 failed to install/upgrade: installed linux-image-4.15.0-20-generic package post- removal script subprocess returned error exit status 21 Status in linux package in Ubuntu: Confirmed Bug description: Happened after upgrading to 18.04 from 16.04. Ubuntu fails to boot with kernel 4.15 as well. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 AptOrdering: linux-image-4.15.0-20-generic:amd64: Remove NULL: ConfigurePending Architecture: amd64 Date: Tue May 29 16:12:20 2018 DpkgTerminalLog: Removing linux-image-4.15.0-20-generic (4.15.0-20.21) ... Failed to create or replace /vmlinuz.old: Is a directory at /usr/bin/linux-update-symlinks line 72. dpkg: error processing package linux-image-4.15.0-20-generic (--remove): installed linux-image-4.15.0-20-generic package post-removal script subprocess returned error exit status 21 DuplicateSignature: package:linux-image-4.15.0-20-generic:4.15.0-20.21 Removing linux-image-4.15.0-20-generic (4.15.0-20.21) ... Failed to create or replace /vmlinuz.old: Is a directory at /usr/bin/linux-update-symlinks line 72. dpkg: error processing package linux-image-4.15.0-20-generic (--remove): installed linux-image-4.15.0-20-generic package post-removal script subprocess returned error exit status 21 ErrorMessage: installed linux-image-4.15.0-20-generic package post-removal script subprocess returned error exit status 21 InstallationDate: Installed on 2016-05-10 (748 days ago)
[Kernel-packages] [Bug 1773635] Re: AR3012 Bluetooth not start after an upgrade to 4.4.0-127
It seems that the build provided at https://people.canonical.com/~khfeng/lp1773635/ resolves the problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773635 Title: AR3012 Bluetooth not start after an upgrade to 4.4.0-127 Status in linux package in Ubuntu: Incomplete Bug description: I have an Atheros mixed WiFi+Bluetooth device which worked nice on a kernels prior to 4.4.0-127 But unfortunately after last upgrade (from 4.4.0-124 to 4.4.0-127) bluetooth is unable to start - no bluetooth indicator appears in notifications tray and no device could be discovered or connected to via bluetooth. Tailing a syslog provides following lines, related to bluetooth: May 27 12:15:16 K43T kernel: [ 228.102799] usbcore: registered new interface driver btusb May 27 12:15:16 K43T kernel: [ 228.109562] Bluetooth: hci0: don't support firmware rome 0x1020200 May 27 12:15:16 K43T systemd-udevd[4634]: Process '/bin/hciconfig hci0 up' failed with exit code 1. May 27 12:15:16 K43T kernel: [ 228.112017] Bluetooth: hci0: don't support firmware rome 0x1020200 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-127-generic 4.4.0-127.153 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: insanedeveloper 1937 F pulseaudio /dev/snd/controlC0: insanedeveloper 1937 F pulseaudio CurrentDesktop: Unity Date: Sun May 27 12:33:42 2018 HibernationDevice: RESUME=UUID=4a7e8ac6-783b-4a23-bfa9-8130cfef7945 InstallationDate: Installed on 2015-11-28 (910 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: ASUSTeK Computer Inc. K43TK ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic.efi.signed root=UUID=7dbd7b42-e67f-4416-8f6d-6c918e744fb7 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-127-generic N/A linux-backports-modules-4.4.0-127-generic N/A linux-firmware 1.157.18 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2017-01-08 (503 days ago) dmi.bios.date: 03/20/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 206 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K43TK dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr206:bd03/20/2012:svnASUSTeKComputerInc.:pnK43TK:pvr1.0:rvnASUSTeKComputerInc.:rnK43TK:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K43TK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773635/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773973] Re: Ubuntu 18.04 [ Garrison P8 ]: Machine crashes with oops while booting with 4.15.0-22-generic kernel.
Did this issue start with the 4.15.0-22 kernel? Was there a prior 4.15 based kernel that did not exhibit this bug? Could you also see if this bug happens with the Bionic -proposed or mainline kernel: See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Mainline can be downloaded from: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc7/ ** Tags added: kernel-da-key ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu) Importance: Undecided => Critical ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Also affects: debian-installer (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Bionic) Status: New => Incomplete ** 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/1773973 Title: Ubuntu 18.04 [ Garrison P8 ]: Machine crashes with oops while booting with 4.15.0-22-generic kernel. Status in The Ubuntu-power-systems project: New Status in debian-installer package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in debian-installer source package in Bionic: New Status in linux source package in Bionic: Incomplete Bug description: ---Problem Description--- Ubuntu 18.04 [ Garrison P8 ]: Machine crashes with oops while booting with 4.15.0-22-generic kernel. ---Environment-- Kernel Build: 4.15.0-22-generic System Name : ltc-garri1 Model/Type : P8 Platform: BML ---Uname output--- Unable to boot. ---Steps to reproduce-- 1. Install Ubuntu 18.04 on Garison BML from http://ports.ubuntu.com /ubuntu-ports/dists/bionic/main/installer- ppc64el/current/images/netboot/ubuntu-installer/ppc64el/ and try to boot. ---Logs Attaching console lob. [4.578205] Bad kernel stack pointer 7b0dd870 at c000b9ec [4.578244] Oops: Bad kernel stack pointer, sig: 6 [#11] [4.578271] LE SMP NR_CPUS=2048 NUMA PowerNV [4.578301] Modules linked in: [4.578324] CPU: 27 PID: 1225 Comm: modprobe Tainted: G D 4.15.0-22-generic #24-Ubuntu [4.578371] NIP: c000b9ec LR: CTR: [4.578413] REGS: c0003febbd40 TRAP: 0300 Tainted: G D (4.15.0-22-generic) [4.578460] MSR: 90001031 CR: XER: [4.578504] CFAR: c000b934 DAR: 0002b200 DSISR: 4000 SOFTE: -4611686018403131680 [4.578504] GPR00: 7b0dd870 [4.578504] GPR04: [4.578504] GPR08: [4.578504] GPR12: 75dcd8781700 0002b200 [4.578504] GPR16: [4.578504] GPR20: [4.578504] GPR24: [4.578504] GPR28: [4.615667] NIP [c000b9ec] fast_exception_return+0x9c/0x184 [4.616210] LR [] (null) [4.616237] Call Trace: [4.616768] Instruction dump: [4.616789] e84101a0 7c4ff120 e8410170 7c5a03a6 e8010070 e8410080 e8610088 e8810090 [4.617697] e8210078 7db243a6 7db142a6 7c0004ac 63ff 7db242a6 63ff [4.618195] ---[ end trace a0d70ba94f583cca ]--- [4.675899] usb 1-3.3: new high-speed USB device number 5 using xhci_hcd [4.782923] [4.783061] Key type encrypted registered [4.783087] AppArmor: AppArmor sha1 policy hashing enabled [4.783117] ima: No TPM chip found, activating TPM-bypass! (rc=-19) [4.783181] evm: HMAC attrs: 0x1 [4.806062] rtc-opal opal-rtc: setting system clock to 2018-05-29 07:49:29 UTC (1527580169) [4.806350] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) [4.806353] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) [4.807260] Freeing unused kernel memory: 4800K [4.807321] This architecture does not have kernel memory protection. == Comment: #2 - SEETEENA THOUFEEK - 2018-05-29 06:47:06 == Symptoms looks exactly like . https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1691978 . https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656908 To manage not
[Kernel-packages] [Bug 1773704] Re: Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset in Bionic 18.04
I built a patched test kernel. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1773704 Can you test this kernel and see if it resolves this bug? Note about installing test kernels: • If the test kernel is prior to 4.15(Bionic) you need to install the linux-image and linux-image-extra .deb packages. • If the test kernel is 4.15(Bionic) or newer, you need to install the linux-modules, linux-modules-extra and linux-image-unsigned .deb packages. Thanks in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773704 Title: Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset in Bionic 18.04 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: A typo at line 184 in /drivers/usb/host/xhci-pci.c trashes a good fix. 183 if (pdev->vendor == PCI_VENDOR_ID_RENESAS && 184 pdev->device == 0x0014) 185 xhci->quirks |= XHCI_TRUST_TX_LENGTH; 186 if (pdev->vendor == PCI_VENDOR_ID_RENESAS && 187 pdev->device == 0x0015) 188 xhci->quirks |= XHCI_RESET_ON_RESUME; Line 184 should be identical to line 187, ie: should read pdev->device == 0x0015) I've compiled the kernel both with and without the typo. As written, hundreds of messages fill dmesg suggesting XHCI_TRUST_TX_LENGTH may be needed when zoneminder tries to access my USB webcams. With the fix applied as I've suggested the messages disappear. The typo is still present in 4.15.0-22.24 For more background, you may refer to bug ID #1710548 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773973] Re: Ubuntu 18.04 [ Garrison P8 ]: Machine crashes with oops while booting with 4.15.0-22-generic kernel.
I think this is a clone of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773162. Can someone please test with the following kernel? http://kernel.ubuntu.com/~jsalisbury/lp1773162 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773973 Title: Ubuntu 18.04 [ Garrison P8 ]: Machine crashes with oops while booting with 4.15.0-22-generic kernel. Status in The Ubuntu-power-systems project: New Status in debian-installer package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in debian-installer source package in Bionic: New Status in linux source package in Bionic: Incomplete Bug description: ---Problem Description--- Ubuntu 18.04 [ Garrison P8 ]: Machine crashes with oops while booting with 4.15.0-22-generic kernel. ---Environment-- Kernel Build: 4.15.0-22-generic System Name : ltc-garri1 Model/Type : P8 Platform: BML ---Uname output--- Unable to boot. ---Steps to reproduce-- 1. Install Ubuntu 18.04 on Garison BML from http://ports.ubuntu.com /ubuntu-ports/dists/bionic/main/installer- ppc64el/current/images/netboot/ubuntu-installer/ppc64el/ and try to boot. ---Logs Attaching console lob. [4.578205] Bad kernel stack pointer 7b0dd870 at c000b9ec [4.578244] Oops: Bad kernel stack pointer, sig: 6 [#11] [4.578271] LE SMP NR_CPUS=2048 NUMA PowerNV [4.578301] Modules linked in: [4.578324] CPU: 27 PID: 1225 Comm: modprobe Tainted: G D 4.15.0-22-generic #24-Ubuntu [4.578371] NIP: c000b9ec LR: CTR: [4.578413] REGS: c0003febbd40 TRAP: 0300 Tainted: G D (4.15.0-22-generic) [4.578460] MSR: 90001031 CR: XER: [4.578504] CFAR: c000b934 DAR: 0002b200 DSISR: 4000 SOFTE: -4611686018403131680 [4.578504] GPR00: 7b0dd870 [4.578504] GPR04: [4.578504] GPR08: [4.578504] GPR12: 75dcd8781700 0002b200 [4.578504] GPR16: [4.578504] GPR20: [4.578504] GPR24: [4.578504] GPR28: [4.615667] NIP [c000b9ec] fast_exception_return+0x9c/0x184 [4.616210] LR [] (null) [4.616237] Call Trace: [4.616768] Instruction dump: [4.616789] e84101a0 7c4ff120 e8410170 7c5a03a6 e8010070 e8410080 e8610088 e8810090 [4.617697] e8210078 7db243a6 7db142a6 7c0004ac 63ff 7db242a6 63ff [4.618195] ---[ end trace a0d70ba94f583cca ]--- [4.675899] usb 1-3.3: new high-speed USB device number 5 using xhci_hcd [4.782923] [4.783061] Key type encrypted registered [4.783087] AppArmor: AppArmor sha1 policy hashing enabled [4.783117] ima: No TPM chip found, activating TPM-bypass! (rc=-19) [4.783181] evm: HMAC attrs: 0x1 [4.806062] rtc-opal opal-rtc: setting system clock to 2018-05-29 07:49:29 UTC (1527580169) [4.806350] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) [4.806353] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) [4.807260] Freeing unused kernel memory: 4800K [4.807321] This architecture does not have kernel memory protection. == Comment: #2 - SEETEENA THOUFEEK - 2018-05-29 06:47:06 == Symptoms looks exactly like . https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1691978 . https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656908 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1773973/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768103] Re: Lancer A0 Asic HBA's won't boot with 18.04
Please let us know when there's a revised kernel we can verify. thx Laurie -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768103 Title: Lancer A0 Asic HBA's won't boot with 18.04 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: We have discovered that an early asic model (A0) of our 16/32GB HBA's doesn't boot with the lpfc driver in Ubuntu 18.04. After further review and discussion, this has been deemed a low risk issue since early A0 HBA's were only ever shipped to OEMs for test purposes. These cards were never shipped to end customers. We have been working to replace those cards whenever we discover them. We'll leave it up to Canonical to decide whether they want to pull this in this single patch to an 18.04 subsequent update. Symptom: Ubuntu 18.04 with lpfc driver 12.0.0.0 they can't see LPe16002-M6 but can see LPe16002B-M6 Resolution: new lpfc driver patch update. scsi: lpfc: Fix WQ/CQ creation for older asic's. https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=4.18/scsi-queue&id=83fae8ca4ae09403bfb99542f1aaa292c06cb111 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768103/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770231] Re: Expose arm64 CPU topology to userspace
** Description changed: [Impact] Applications, particularly those in the HPC domain (e.g. openmpi), can be optimized for the processor and cache topology. However, the ARM CPU topology isn't correctly exposed to userspace. [Fix] The ACPI 6.2 specification introduced a Processor Properties Topology Table (PPTT). The linux kernel needs support for parsing this table, and exposing the parsed topology to userspace. + [Test Case] - TBD + A HiSilicon D06 without the fix: + + ubuntu@d06-1:~$ lscpu + Architecture:aarch64 + Byte Order: Little Endian + CPU(s): 96 + On-line CPU(s) list: 0-95 + Thread(s) per core: 1 + Core(s) per socket: 4 + Socket(s): 24 + NUMA node(s):4 + Vendor ID: 0x48 + Model: 0 + Stepping:0x0 + BogoMIPS:200.00 + NUMA node0 CPU(s): 0-23 + NUMA node1 CPU(s): 24-47 + NUMA node2 CPU(s): 48-71 + NUMA node3 CPU(s): 72-95 + Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics cpuid asimdrdm dcpop + + With the fix: + ubuntu@d06-1:~$ lscpu + Architecture:aarch64 + Byte Order: Little Endian + CPU(s): 96 + On-line CPU(s) list: 0-95 + Thread(s) per core: 1 + Core(s) per socket: 48 + Socket(s): 2 + NUMA node(s):4 + Vendor ID: 0x48 + Model: 0 + Stepping:0x0 + BogoMIPS:200.00 + L1d cache: 64K + L1i cache: 64K + L2 cache:512K + L3 cache:32768K + NUMA node0 CPU(s): 0-23 + NUMA node1 CPU(s): 24-47 + NUMA node2 CPU(s): 48-71 + NUMA node3 CPU(s): 72-95 + Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics cpuid asimdrdm dcpop + [Regression Risk] TBD -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770231 Title: Expose arm64 CPU topology to userspace Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: New Bug description: [Impact] Applications, particularly those in the HPC domain (e.g. openmpi), can be optimized for the processor and cache topology. However, the ARM CPU topology isn't correctly exposed to userspace. [Fix] The ACPI 6.2 specification introduced a Processor Properties Topology Table (PPTT). The linux kernel needs support for parsing this table, and exposing the parsed topology to userspace. [Test Case] A HiSilicon D06 without the fix: ubuntu@d06-1:~$ lscpu Architecture:aarch64 Byte Order: Little Endian CPU(s): 96 On-line CPU(s) list: 0-95 Thread(s) per core: 1 Core(s) per socket: 4 Socket(s): 24 NUMA node(s):4 Vendor ID: 0x48 Model: 0 Stepping:0x0 BogoMIPS:200.00 NUMA node0 CPU(s): 0-23 NUMA node1 CPU(s): 24-47 NUMA node2 CPU(s): 48-71 NUMA node3 CPU(s): 72-95 Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics cpuid asimdrdm dcpop With the fix: ubuntu@d06-1:~$ lscpu Architecture:aarch64 Byte Order: Little Endian CPU(s): 96 On-line CPU(s) list: 0-95 Thread(s) per core: 1 Core(s) per socket: 48 Socket(s): 2 NUMA node(s):4 Vendor ID: 0x48 Model: 0 Stepping:0x0 BogoMIPS:200.00 L1d cache: 64K L1i cache: 64K L2 cache:512K L3 cache:32768K NUMA node0 CPU(s): 0-23 NUMA node1 CPU(s): 24-47 NUMA node2 CPU(s): 48-71 NUMA node3 CPU(s): 72-95 Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics cpuid asimdrdm dcpop [Regression Risk] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770231/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772940] Re: linux-azure: 4.15.0-1013.13~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** 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-stable-master-bug: 1772927 phase: Packaging + kernel-stable-phase-changed:Tuesday, 29. May 2018 20:31 UTC + kernel-stable-phase:Uploaded ** 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-stable-master-bug: 1772927 - phase: Packaging - kernel-stable-phase-changed:Tuesday, 29. May 2018 20:31 UTC - kernel-stable-phase:Uploaded + phase: Uploaded -- 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/1772940 Title: linux-azure: 4.15.0-1013.13~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: 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-stable-master-bug: 1772927 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773520] Re: After update to 4.13-43 Intel Graphics are Laggy
I've added kernel-fixed-upstream tag - though note that it's not the head but the drm-tip branch which has the working kernel Linux hp-green 4.17.0-994-generic #201805290201 SMP Tue May 29 02:03:37 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ** 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/1773520 Title: After update to 4.13-43 Intel Graphics are Laggy Status in linux package in Ubuntu: Confirmed Bug description: After update to Kernel 4.13-43 the intel graphics seem to really lag - especially noticeable in apps which are using vsync, which, at least on my system, locks to 40fps unlike the previous kernel I have installed (4.13-41) which locks at a steady 60fps. See https://askubuntu.com/questions/1039189/today-i-got-an-update-and- graphics-are-not-working-right-on-ubuntu-16-04/1040545#1040545 for some other users with the same issue In short 4.13-41 doesn't have the problem 4.13-43 has the laggy problem --- ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: james 2835 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=ac1331a0-15f2-4832-aebc-48e3ad655add InstallationDate: Installed on 2016-05-31 (724 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 04f2:b50d Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Gaming Notebook Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-43-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-43-generic N/A linux-backports-modules-4.13.0-43-generic N/A linux-firmware 1.157.18 Tags: xenial Uname: Linux 4.13.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip docker libvirtd lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/16/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.53 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80A9 dmi.board.vendor: HP dmi.board.version: 91.18 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.53:bd09/16/2015:svnHP:pnHPPavilionGamingNotebook:pvrType1ProductConfigId:rvnHP:rn80A9:rvr91.18:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion Gaming Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773520/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773520] Re: After update to 4.13-43 Intel Graphics are Laggy
Hi Joseph, Kernel 4.17-rc7 still has the same issue, been digging though and have found a possible cause (Ignore the name of the bug...) https://bugs.freedesktop.org/show_bug.cgi?id=103497 This came from the following post on a Manjaro forum https://forum.manjaro.org/t/poor-opengl-performance-on-linux-4-14/35453 The drm-tip kernel does indeed resolve the issue for me bringing back 60FPS lock on the vsync'ed app I'm working on. Regards James ** Bug watch added: freedesktop.org Bugzilla #103497 https://bugs.freedesktop.org/show_bug.cgi?id=103497 ** Tags added: kernel-fixed-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773520 Title: After update to 4.13-43 Intel Graphics are Laggy Status in linux package in Ubuntu: Confirmed Bug description: After update to Kernel 4.13-43 the intel graphics seem to really lag - especially noticeable in apps which are using vsync, which, at least on my system, locks to 40fps unlike the previous kernel I have installed (4.13-41) which locks at a steady 60fps. See https://askubuntu.com/questions/1039189/today-i-got-an-update-and- graphics-are-not-working-right-on-ubuntu-16-04/1040545#1040545 for some other users with the same issue In short 4.13-41 doesn't have the problem 4.13-43 has the laggy problem --- ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: james 2835 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=ac1331a0-15f2-4832-aebc-48e3ad655add InstallationDate: Installed on 2016-05-31 (724 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 04f2:b50d Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Gaming Notebook Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-43-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-43-generic N/A linux-backports-modules-4.13.0-43-generic N/A linux-firmware 1.157.18 Tags: xenial Uname: Linux 4.13.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip docker libvirtd lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/16/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.53 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80A9 dmi.board.vendor: HP dmi.board.version: 91.18 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.53:bd09/16/2015:svnHP:pnHPPavilionGamingNotebook:pvrType1ProductConfigId:rvnHP:rn80A9:rvr91.18:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion Gaming Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773520/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773520] Re: After update to 4.13-43 Intel Graphics are Laggy
Also possible candidate for the patch: https://cgit.freedesktop.org/drm-tip/commit/?id=d93fa1b47b8fcd149b5091f18385304f402a8e15 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773520 Title: After update to 4.13-43 Intel Graphics are Laggy Status in linux package in Ubuntu: Confirmed Bug description: After update to Kernel 4.13-43 the intel graphics seem to really lag - especially noticeable in apps which are using vsync, which, at least on my system, locks to 40fps unlike the previous kernel I have installed (4.13-41) which locks at a steady 60fps. See https://askubuntu.com/questions/1039189/today-i-got-an-update-and- graphics-are-not-working-right-on-ubuntu-16-04/1040545#1040545 for some other users with the same issue In short 4.13-41 doesn't have the problem 4.13-43 has the laggy problem --- ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: james 2835 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=ac1331a0-15f2-4832-aebc-48e3ad655add InstallationDate: Installed on 2016-05-31 (724 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 04f2:b50d Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Gaming Notebook Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-43-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-43-generic N/A linux-backports-modules-4.13.0-43-generic N/A linux-firmware 1.157.18 Tags: xenial Uname: Linux 4.13.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip docker libvirtd lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/16/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.53 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80A9 dmi.board.vendor: HP dmi.board.version: 91.18 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.53:bd09/16/2015:svnHP:pnHPPavilionGamingNotebook:pvrType1ProductConfigId:rvnHP:rn80A9:rvr91.18:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion Gaming Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773520/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755490] Re: Incorrect information about display shown in unity-control-center
In case it helps, I've seen comments regarding some TVs encoding the aspect ratio (16/9 or 16/10) as though it was the size: https://github.com/linuxmint/slick-greeter/blob/master/files/usr/bin /slick-greeter-check-hidpi#L24-L29 Not sure what is the actual source of this information, though. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to hwdata in Ubuntu. https://bugs.launchpad.net/bugs/1755490 Title: Incorrect information about display shown in unity-control-center Status in hwdata package in Ubuntu: In Progress Status in unity-settings-daemon package in Ubuntu: In Progress Bug description: After connecting a LG 49UB850T-DA TV the following information is displayed in the unity-control-center: Goldstar Company Ltd 72" It's misleading since neither the company name nor the diagonal matches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1755490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764645] Re: Bluetooth not working
Bluetooth doesn't work on 4.5.0-22.24 on my laptop. The bug does seem specific to certain adaptors. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1764645 Title: Bluetooth not working Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: I've installed the Ubuntu Bionic Beta 2 and everything works fine but the bluetooth (perfectly working with Xenial). In bluetooth control panel the slider is impossible to move to "on". 1) Ubuntu Release (via 'lsb_release -rd') Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 2) Version of package (apt-cache policy gnome-bluetooth) gnome-bluetooth: Installato: 3.28.0-2 Candidato: 3.28.0-2 Tabella versione: *** 3.28.0-2 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen I expected to switch on the bluetooth. 4) What happened instead Bluetooth won't switch on. 5) Output of rfkill list is: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 6) Output of lspci -knn | grep Net -A3; lsusb; dmesg | grep -i blue is: 03:00.0 Network controller [0280]: Qualcomm Atheros AR9462 Wireless Network Adapter [168c:0034] (rev 01) Subsystem: Bigfoot Networks, Inc. Killer Wireless-N 1202 Half- size Mini PCIe Card [1a56:2003] Kernel driver in use: ath9k Kernel modules: ath9k 04:00.0 Ethernet controller [0200]: Qualcomm Atheros QCA8171 Gigabit Ethernet [1969:10a1] (rev 10) Bus 002 Device 002: ID 8087:8000 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:8008 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 004: ID 04f2:b414 Chicony Electronics Co., Ltd Bus 003 Device 003: ID 0cf3:3004 Atheros Communications, Inc. AR3012 Bluetooth 4.0 Bus 003 Device 002: ID 0b05:17c4 ASUSTek Computer, Inc. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [ 17.715399] Bluetooth: Core ver 2.22 [ 17.715414] Bluetooth: HCI device and connection manager initialized [ 17.715416] Bluetooth: HCI socket layer initialized [ 17.715418] Bluetooth: L2CAP socket layer initialized [ 17.715422] Bluetooth: SCO socket layer initialized [ 17.723207] Bluetooth: hci0: don't support firmware rome 0x1102 [ 18.600648] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 18.600649] Bluetooth: BNEP filters: protocol multicast [ 18.600651] Bluetooth: BNEP socket layer initialized ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-15-generic 4.15.0-15.16 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stormy 1484 F pulseaudio /dev/snd/controlC0: stormy 1484 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Apr 17 08:46:30 2018 HibernationDevice: RESUME=UUID=3f513ca9-6817-4099-9718-fee68d68ec11 InstallationDate: Installed on 2018-04-16 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) MachineType: ASUSTeK COMPUTER INC. G750JH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G750JH.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G750JH dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG750JH.206:bd12/02/2013:svnASUSTeKCOMPUTERINC.:pnG750JH:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG750JH:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: G dmi.product.name: G750JH dmi.product.version: 1.0 dmi.sys.vendor: A
[Kernel-packages] [Bug 1774063] [NEW] Bionic update: upstream stable patchset 2018-05-29
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2018-05-29 (ported from v4.14.37 and v4.16.5) from git://git.kernel.org/ mm,vmscan: Allow preallocating memory for register_shrinker(). btrfs: Fix race condition between delayed refs and blockgroup removal mac80211_hwsim: fix use-after-free bug in hwsim_exit_net Revert "KVM: X86: Fix SMRAM accessing even if VM is shutdown" RDMA/mlx5: Fix NULL dereference while accessing XRC_TGT QPs perf: Return proper values for user stack errors perf: Fix sample_max_stack maximum check netfilter: x_tables: limit allocation requests for blob rule heads netfilter: compat: reject huge allocation requests netfilter: compat: prepare xt_compat_init_offsets to return errors netfilter: x_tables: add counters allocation wrapper netfilter: x_tables: cap allocations at 512 mbyte alarmtimer: Init nanosleep alarm timer on stack RDMA/core: Reduce poll batch for direct cq polling irqchip/gic-v3: Change pr_debug message to pr_devel cpumask: Make for_each_cpu_wrap() available on UP as well irqchip/gic-v3: Ignore disabled ITS nodes perf test: Fix test trace+probe_libc_inet_pton.sh for s390x powerpc/powernv: IMC fix out of bounds memory access at shutdown locking/qspinlock: Ensure node->count is updated before initialising node x86/platform/UV: Fix GAM Range Table entries less than 1GB powerpc/mm/hash64: Zero PGD pages on allocation vfs/proc/kcore, x86/mm/kcore: Fix SMAP fault when dumping vsyscall user page PM / wakeirq: Fix unbalanced IRQ enable for wakeirq ACPI / EC: Restore polling during noirq suspend/resume phases bpf: fix rlimit in reuseport net selftest net: stmmac: discard disabled flags in interrupt status register SUNRPC: Don't call __UDPX_INC_STATS() from a preemptible context tools/libbpf: handle issues with bpf ELF objects containing .eh_frames net: Extra '_get' in declaration of arch_get_platform_mac_address svcrdma: Fix Read chunk round-up rxrpc: Don't put crypto buffers on the stack selftests/ftrace: Add some missing glob checks cpufreq: intel_pstate: Enable HWP during system resume on CPU0 bcache: return attach error when no cache set exist bcache: fix for data collapse after re-attaching an attached device bcache: fix for allocator and register thread race bcache: properly set task state in bch_writeback_thread() cifs: silence compiler warnings showing up with gcc-8.0.0 PM / domains: Fix up domain-idle-states OF parsing proc: fix /proc/*/map_files lookup arm64: spinlock: Fix theoretical trylock() A-B-A with LSE atomics RDS: IB: Fix null pointer issue bpf: sockmap, fix leaking maps with attached but not detached progs xen/grant-table: Use put_page instead of free_page xen-netfront: Fix race between device setup and open perf evsel: Fix period/freq terms setup MIPS: Generic: Support GIC in EIC mode perf record: Fix period option handling MIPS: TXx9: use IS_BUILTIN() for CONFIG_LEDS_CLASS ACPI / scan: Use acpi_bus_get_status() to initialize ACPI_TYPE_DEVICE devs ACPI / bus: Do not call _STA on battery devices with unmet dependencies ACPI: processor_perflib: Do not send _PPC change notification if not ready firmware: dmi_scan: Fix handling of empty DMI strings x86/dumpstack: Avoid uninitlized variable x86/power: Fix swsusp_arch_resume prototype netfilter: ipv6: nf_defrag: Kill frag queue on RFC2460 failure s390/eadm: fix CONFIG_BLOCK include dependency drm/nouveau/pmu/fuc: don't use movw directly anymore IB/core: Map iWarp AH type to undefined in rdma_ah_find_type IB/ipoib: Fix for potential no-carrier state IB/hfi1: Fix for potential refcount leak in hfi1_open_file() IB/hfi1: Re-order IRQ cleanup to address driver cleanup race blk-mq: fix discard merge with scheduler attached openvswitch: Remove padding from packet before L3+ conntrack processing mm/fadvise: discard partial page if endbyte is also EOF mm: pin address_space before dereferencing it while isolating an LRU page mm: thp: use down_read_trylock() in khugepaged to avoid long block sparc64: update pmdp_invalidate() to return old pmd value asm-generic: provide generic_pmdp_establish() mm/mempolicy: add nodes_empty check in SYSC_migrate_pages mm/mempolicy: fix the check of nodemask from user ocfs2: return error when we attempt to access a dirty bh in jbd2 ocfs2/acl: use 'ip_xattr_sem' to protect getting extended attribute ocfs2: return -EROFS to mount.ocfs2 if inode block is invalid fs/dax.c: release PMD lock even when there is no PMD support in DAX x86/kvm/vmx: do not use vm-exit instruction length for fast MMIO when running nested kvm: Map PFN-type memory regions as
[Kernel-packages] [Bug 1773973] Re: Ubuntu 18.04 [ Garrison P8 ]: Machine crashes with oops while booting with 4.15.0-22-generic kernel.
** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773973 Title: Ubuntu 18.04 [ Garrison P8 ]: Machine crashes with oops while booting with 4.15.0-22-generic kernel. Status in The Ubuntu-power-systems project: New Status in debian-installer package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in debian-installer source package in Bionic: New Status in linux source package in Bionic: Incomplete Bug description: ---Problem Description--- Ubuntu 18.04 [ Garrison P8 ]: Machine crashes with oops while booting with 4.15.0-22-generic kernel. ---Environment-- Kernel Build: 4.15.0-22-generic System Name : ltc-garri1 Model/Type : P8 Platform: BML ---Uname output--- Unable to boot. ---Steps to reproduce-- 1. Install Ubuntu 18.04 on Garison BML from http://ports.ubuntu.com /ubuntu-ports/dists/bionic/main/installer- ppc64el/current/images/netboot/ubuntu-installer/ppc64el/ and try to boot. ---Logs Attaching console lob. [4.578205] Bad kernel stack pointer 7b0dd870 at c000b9ec [4.578244] Oops: Bad kernel stack pointer, sig: 6 [#11] [4.578271] LE SMP NR_CPUS=2048 NUMA PowerNV [4.578301] Modules linked in: [4.578324] CPU: 27 PID: 1225 Comm: modprobe Tainted: G D 4.15.0-22-generic #24-Ubuntu [4.578371] NIP: c000b9ec LR: CTR: [4.578413] REGS: c0003febbd40 TRAP: 0300 Tainted: G D (4.15.0-22-generic) [4.578460] MSR: 90001031 CR: XER: [4.578504] CFAR: c000b934 DAR: 0002b200 DSISR: 4000 SOFTE: -4611686018403131680 [4.578504] GPR00: 7b0dd870 [4.578504] GPR04: [4.578504] GPR08: [4.578504] GPR12: 75dcd8781700 0002b200 [4.578504] GPR16: [4.578504] GPR20: [4.578504] GPR24: [4.578504] GPR28: [4.615667] NIP [c000b9ec] fast_exception_return+0x9c/0x184 [4.616210] LR [] (null) [4.616237] Call Trace: [4.616768] Instruction dump: [4.616789] e84101a0 7c4ff120 e8410170 7c5a03a6 e8010070 e8410080 e8610088 e8810090 [4.617697] e8210078 7db243a6 7db142a6 7c0004ac 63ff 7db242a6 63ff [4.618195] ---[ end trace a0d70ba94f583cca ]--- [4.675899] usb 1-3.3: new high-speed USB device number 5 using xhci_hcd [4.782923] [4.783061] Key type encrypted registered [4.783087] AppArmor: AppArmor sha1 policy hashing enabled [4.783117] ima: No TPM chip found, activating TPM-bypass! (rc=-19) [4.783181] evm: HMAC attrs: 0x1 [4.806062] rtc-opal opal-rtc: setting system clock to 2018-05-29 07:49:29 UTC (1527580169) [4.806350] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) [4.806353] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) [4.807260] Freeing unused kernel memory: 4800K [4.807321] This architecture does not have kernel memory protection. == Comment: #2 - SEETEENA THOUFEEK - 2018-05-29 06:47:06 == Symptoms looks exactly like . https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1691978 . https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656908 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1773973/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768431] Comment bridged from LTC Bugzilla
--- Comment From ukri...@us.ibm.com 2018-05-29 18:33 EDT--- I was able to install the kernel and run regression. It looks good. I do have 7 more patches that were added recently to upstream for cxlflash. We would like to have them included in bionic SRU as well. Details are given below. Please let me know if you can apply on top of this using this bugzilla or if you want me to open a new request for the same. Current commit ids of the patches in next/master tree - e0f76ad13085b730091256d7a2fbe3555f0686df scsi: cxlflash: Yield to active send threads d58188c306a010d32a250ae532c3daaae8c57346 scsi: cxlflash: Limit the debug logs in the IO path 32a9ae415b8a4258140312f91c71324950d9eba4 scsi: cxlflash: Acquire semaphore before invoking ioctl services e63a8d886d346e83607e4495ec21f1a0ca6398a2 scsi: cxlflash: Use local mutex for AFU serialization 5e12397a9706391543e87cf088fff89fe05f0ad0 scsi: cxlflash: Add include guards to backend.h de5d35aff5b34bc91a83adb0bf1788d3d23e92f4 scsi: cxlflash: Abstract hardware dependent assignments cd43c221bb5eb5a6400a62ae44a9979c8fc6c87e scsi: cxlflash: Isolate external module dependencies -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768431 Title: Request to revert SAUCE patches in the 18.04 SRU and update with upstream version Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: == Comment: #0 - UMA KRISHNAN - 2018-04-30 14:41:30 == ---Problem Description--- Request to revert SAUCE patches from 18.04 and apply the patches from next/master. Below set of cxlflash patches were submitted to Canonical after they were sent to the community. Based on review comments, there has been minor changes from that version. This BZ is to request reverting those SAUCE patches with the ones that are queued in next/master tree for 4.18. - SAUCE: cxlflash: Preserve number of interrupts for master contexts - SAUCE: cxlflash: Avoid clobbering context control register value - SAUCE: cxlflash: Add argument identifier names - SAUCE: cxlflash: Introduce OCXL backend - SAUCE: cxlflash: Hardware AFU for OCXL - SAUCE: cxlflash: Read host function configuration - SAUCE: cxlflash: Setup function acTag range - SAUCE: cxlflash: Read host AFU configuration - SAUCE: cxlflash: Setup AFU acTag range - SAUCE: cxlflash: Setup AFU PASID - SAUCE: cxlflash: Adapter context support for OCXL - SAUCE: cxlflash: Use IDR to manage adapter contexts - SAUCE: cxlflash: Support adapter file descriptors for OCXL - SAUCE: cxlflash: Support adapter context discovery - SAUCE: cxlflash: Support image reload policy modification - SAUCE: cxlflash: MMIO map the AFU - SAUCE: cxlflash: Support starting an adapter context - SAUCE: cxlflash: Support process specific mappings - SAUCE: cxlflash: Support AFU state toggling - SAUCE: cxlflash: Support reading adapter VPD data - SAUCE: cxlflash: Setup function OCXL link - SAUCE: cxlflash: Setup OCXL transaction layer - SAUCE: cxlflash: Support process element lifecycle - SAUCE: cxlflash: Support AFU interrupt management - SAUCE: cxlflash: Support AFU interrupt mapping and registration - SAUCE: cxlflash: Support starting user contexts - SAUCE: cxlflash: Support adapter context polling - SAUCE: cxlflash: Support adapter context reading - SAUCE: cxlflash: Support adapter context mmap and release - SAUCE: cxlflash: Support file descriptor mapping - SAUCE: cxlflash: Introduce object handle fop - SAUCE: cxlflash: Setup LISNs for user contexts - SAUCE: cxlflash: Setup LISNs for master contexts - SAUCE: cxlflash: Update synchronous interrupt status bits - SAUCE: cxlflash: Introduce OCXL context state machine - SAUCE: cxlflash: Register for translation errors - SAUCE: cxlflash: Support AFU reset - SAUCE: cxlflash: Enable OCXL operations Also, there are 3 additional patches added to end of this series that we would like to request being pulled into the SRU stream. These 3 patches address bug fixes. The commit ids for the patches queued in next/master tree are, 768999d6b1eadc6a13b1fba1886f1708f433d82b scsi: cxlflash: Preserve number of interrupts for master contexts 6c2b116dd38e3fbda10c3e3d5ac80ea7442e4f4d scsi: cxlflash: Avoid clobbering context control register value fcace1d5e11f518c6f91dd245fa1ac37393b47d3 scsi: cxlflash: Add argument identifier names 863dbdc0552f8bc100df48bb231089c382b89004 scsi: cxlflash: Introduce OCXL backend f2180daa83950ff8183f70b1b78d67cb13fd90b2 scsi: cxlflash: Hardware AFU for OCXL 1042535633554592d7d95a9cf83d2940803689e0 scsi: cxlflash: Read host function configuration ba84823a8b448207659753ae4f9c8b956923bada scsi: cxlflash: Setup function acTag range f55ced2dcd00ab257a2bb25eee619b75cda24817 scsi: cx
[Kernel-packages] [Bug 1772956] Re: linux-oem: 4.13.0-1029.32 -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/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 is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772951 phase: Uploaded + kernel-stable-phase-changed:Tuesday, 29. May 2018 23:02 UTC + kernel-stable-phase:Promoted to 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 -- boot-testing-requested: true kernel-stable-master-bug: 1772951 - phase: Uploaded - kernel-stable-phase-changed:Tuesday, 29. May 2018 23:02 UTC - kernel-stable-phase:Promoted to proposed + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- 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/1772956 Title: linux-oem: 4.13.0-1029.32 -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: 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772951 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772956/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770231] Re: Expose arm64 CPU topology to userspace
** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => dann frazier (dannf) ** Description changed: [Impact] Applications, particularly those in the HPC domain (e.g. openmpi), can be optimized for the processor and cache topology. However, the ARM CPU topology isn't correctly exposed to userspace. [Fix] - The ACPI 6.2 specification introduced a Processor Properties Topology Table (PPTT). The linux kernel needs support for parsing this table, and exposing the parsed topology to userspace. + The ACPI 6.2 specification introduced a Processor Properties Topology Table (PPTT). This is what ARM server vendors are using to expose their topology. The linux kernel needs support for parsing this table, and exposing the parsed topology to userspace. [Test Case] - A HiSilicon D06 without the fix: + A HiSilicon D06 without the fix. Note that it thinks I'm on a 24-socket system with 4 cores each. I'm not. I'm on a 2 socket system w/ 48 cores each. ubuntu@d06-1:~$ lscpu Architecture:aarch64 Byte Order: Little Endian CPU(s): 96 On-line CPU(s) list: 0-95 Thread(s) per core: 1 Core(s) per socket: 4 Socket(s): 24 NUMA node(s):4 Vendor ID: 0x48 Model: 0 Stepping:0x0 BogoMIPS:200.00 NUMA node0 CPU(s): 0-23 NUMA node1 CPU(s): 24-47 NUMA node2 CPU(s): 48-71 NUMA node3 CPU(s): 72-95 Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics cpuid asimdrdm dcpop - With the fix: + With the fix (and this is correct): ubuntu@d06-1:~$ lscpu Architecture:aarch64 Byte Order: Little Endian CPU(s): 96 On-line CPU(s) list: 0-95 Thread(s) per core: 1 Core(s) per socket: 48 Socket(s): 2 NUMA node(s):4 Vendor ID: 0x48 Model: 0 Stepping:0x0 BogoMIPS:200.00 L1d cache: 64K L1i cache: 64K L2 cache:512K L3 cache:32768K NUMA node0 CPU(s): 0-23 NUMA node1 CPU(s): 24-47 NUMA node2 CPU(s): 48-71 NUMA node3 CPU(s): 72-95 Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics cpuid asimdrdm dcpop + [Regression Risk] + Here's a patch-by patch risk analysis of the changeset: - [Regression Risk] - TBD + 0001-ACPICA-ACPI-6.2-Additional-PPTT-flags.patch + Just adds new #defines. No functional change. + + 0002-drivers-base-cacheinfo-move-cache_setup_of_node.patch + Moves code down in a file. No functional change. (I double-checked that the moved code is the same). + + 0003-drivers-base-cacheinfo-setup-DT-cache-properties-ear.patch + The code this touches is all #ifdef CONFIG_OF, which only applies to the ARM & Power ports of Ubuntu. I've tested on ARM. + + 0004-cacheinfo-rename-of_node-to-fw_token.patch + Renames a variable, and changes it's type from "struct device_node *" to "void *". No functional change. + + 0005-arm64-acpi-Create-arch-specific-cpu-to-acpi-id-helpe.patch + Adds a new function (but doesn't use it yet). + + 0006-ACPI-PPTT-Add-Processor-Properties-Topology-Table-pa.patch + Adds new code that isn't called yet. + + 0007-UBUNTU-Config-CONFIG_ACPI_PPTT-y.patch + Configures on the new code. + + 0008-ACPI-Enable-PPTT-support-on-ARM64.patch + Kconfig/Makefile bits for the new code. + + 0009-drivers-base-cacheinfo-Add-support-for-ACPI-based-fi.patch + Finally, we call the new code during initialization, so let's go back and look at that code. The first thing it does is to check for the presence of a PPTT table before proceeding, so the regression risk to systems *without* a PPTT table is negligible. The PPTT table was introduced in the ACPI 6.2 specification, which was released in May 2017. Regression risk should therefore be restricted to systems manufactured (or firmware updated) after that time that happened to include a PPTT table. I don't know of anyone other than ARM licensees doing this - but it's possible there are others. And, it's possible that there's a table out there that tickles a bug in the parsing code. Should that be the case, a hotfix would be to use an initrd to override/strip the PPTT from the XSDT table until a suitable fix is put in place. + + 0010-arm64-Add-support-for-ACPI-based-firmware-tables.patch + 0011-arm64-topology-rename-cluster_id.patch + 0012-arm64-topology-enable-ACPI-PPTT-based-CPU-topology.patch + These patches only touch arm64 code. I explicitly tested on an arm64 server. + + 0013-ACPI-Add-PPTT-to-injectable-table-list.patch + Allows users to override the PPTT table. No change to default behavior. ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Description changed: [Impact] Applications, particularly those in the HPC domain (e.g. openmpi), can be optimized for the processor and cache topology. However, the ARM CPU topology isn't correctly exposed
[Kernel-packages] [Bug 1772956] Re: linux-oem: 4.13.0-1029.32 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1772956 Title: linux-oem: 4.13.0-1029.32 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772951 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772956/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774082] [NEW] Trusty cannot load microcode for family 17h AMD processors
Public bug reported: [Impact] AMD has recently updated the microcode in the linux-firmware tree for family 17h processors to address Spectre variant 2. The Trusty 3.13 kernel cannot load the microcode because it is missing a backport of upstream patch f4e9b7af0cd58dd039a0fb2cd67d57cea4889abf which leaves AMD machines vulnerable. [Test Case] Test must be done on a 17h family processor: 1) Take note of the microcode version before applying updated microcode: $ sudo cat /sys/devices/system/cpu/cpu0/microcode/version 0x8001227 2) Get updated amd64-microcode package from the Ubuntu Security Team. Install it and reboot machine. 3) Verify that the microcode version has changed. [Regression Potential] The regression potential to the kernel revolves around the fact that the IBRS/IBPB implementation in the 3.13 kernel may not have been put through its paces yet due to a lack of available microcode updates. There could be a latent bug present that is uncovered. ** Affects: linux (Ubuntu) Importance: Critical Assignee: Tyler Hicks (tyhicks) Status: Invalid ** Affects: linux (Ubuntu Trusty) Importance: Undecided Assignee: Tyler Hicks (tyhicks) Status: In Progress ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Trusty) Status: New => In Progress ** Changed in: linux (Ubuntu Trusty) Assignee: (unassigned) => Tyler Hicks (tyhicks) ** Changed in: linux (Ubuntu) Status: In Progress => 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/1774082 Title: Trusty cannot load microcode for family 17h AMD processors Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: In Progress Bug description: [Impact] AMD has recently updated the microcode in the linux-firmware tree for family 17h processors to address Spectre variant 2. The Trusty 3.13 kernel cannot load the microcode because it is missing a backport of upstream patch f4e9b7af0cd58dd039a0fb2cd67d57cea4889abf which leaves AMD machines vulnerable. [Test Case] Test must be done on a 17h family processor: 1) Take note of the microcode version before applying updated microcode: $ sudo cat /sys/devices/system/cpu/cpu0/microcode/version 0x8001227 2) Get updated amd64-microcode package from the Ubuntu Security Team. Install it and reboot machine. 3) Verify that the microcode version has changed. [Regression Potential] The regression potential to the kernel revolves around the fact that the IBRS/IBPB implementation in the 3.13 kernel may not have been put through its paces yet due to a lack of available microcode updates. There could be a latent bug present that is uncovered. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774082] Re: Trusty cannot load microcode for family 17h AMD processors
The upstream fix has been applied to Xenial and newer kernels. This bug is only for Trusty. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774082 Title: Trusty cannot load microcode for family 17h AMD processors Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: In Progress Bug description: [Impact] AMD has recently updated the microcode in the linux-firmware tree for family 17h processors to address Spectre variant 2. The Trusty 3.13 kernel cannot load the microcode because it is missing a backport of upstream patch f4e9b7af0cd58dd039a0fb2cd67d57cea4889abf which leaves AMD machines vulnerable. [Test Case] Test must be done on a 17h family processor: 1) Take note of the microcode version before applying updated microcode: $ sudo cat /sys/devices/system/cpu/cpu0/microcode/version 0x8001227 2) Get updated amd64-microcode package from the Ubuntu Security Team. Install it and reboot machine. 3) Verify that the microcode version has changed. [Regression Potential] The regression potential to the kernel revolves around the fact that the IBRS/IBPB implementation in the 3.13 kernel may not have been put through its paces yet due to a lack of available microcode updates. There could be a latent bug present that is uncovered. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704799] Re: iwlwifi: 8260: missing iwlwifi-8000C-{22..30}.ucode firmware
Actually the current bug report was not against Ubuntu 16.04, codename:
Xenial Xerus. It is against missing firmware for newer kernels. Actually
Ubuntu 18.04 is using already 4.15 kernel. There are even newer to come
when time goes on. At that time when tested newer kernels, the Ubuntu
16.04 LTS was out and therefore used. As I described, also the newest
linux-firmware package found in Ubuntu 18.04 LTS still missing required
firmware.
** Changed in: linux-firmware (Ubuntu)
Status: Invalid => Confirmed
--
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/1704799
Title:
iwlwifi: 8260: missing iwlwifi-8000C-{22..30}.ucode firmware
Status in linux-firmware package in Ubuntu:
Confirmed
Bug description:
Filed a bug at https://bugzilla.kernel.org/show_bug.cgi?id=196395 but
filing it also here as suggested.
Using amd64 version from http://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.12.2/ in Xenial 16.04.2 LTS based Linux Mint 18.2.
Checking firmware files:
$ ls /lib/firmware/ | grep 8000C
iwlwifi-8000C-13.ucode
iwlwifi-8000C-16.ucode
iwlwifi-8000C-21.ucode
Missing modules that were required according logging output below:
iwlwifi-8000C-22.ucode
iwlwifi-8000C-23.ucode
iwlwifi-8000C-24.ucode
iwlwifi-8000C-25.ucode
iwlwifi-8000C-26.ucode
iwlwifi-8000C-27.ucode
iwlwifi-8000C-28.ucode
iwlwifi-8000C-29.ucode
iwlwifi-8000C-30.ucode
$ lspci | grep Wireless
04:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)
Initially following error output can be found in appropriate logs:
$ dmesg | grep iwlwifi
[ 10.011090] iwlwifi :04:00.0: Direct firmware load for
iwlwifi-8000C-30.ucode failed with error -2
[ 10.011238] iwlwifi :04:00.0: Direct firmware load for
iwlwifi-8000C-29.ucode failed with error -2
[ 10.012734] iwlwifi :04:00.0: Direct firmware load for
iwlwifi-8000C-28.ucode failed with error -2
[ 10.012747] iwlwifi :04:00.0: Direct firmware load for
iwlwifi-8000C-27.ucode failed with error -2
[ 10.012756] iwlwifi :04:00.0: Direct firmware load for
iwlwifi-8000C-26.ucode failed with error -2
[ 10.012764] iwlwifi :04:00.0: Direct firmware load for
iwlwifi-8000C-25.ucode failed with error -2
[ 10.012772] iwlwifi :04:00.0: Direct firmware load for
iwlwifi-8000C-24.ucode failed with error -2
[ 10.014057] iwlwifi :04:00.0: Direct firmware load for
iwlwifi-8000C-23.ucode failed with error -2
[ 10.014071] iwlwifi :04:00.0: Direct firmware load for
iwlwifi-8000C-22.ucode failed with error -2
[ 10.014073] iwlwifi :04:00.0: no suitable firmware found!
[ 10.014075] iwlwifi :04:00.0: minimum version required:
iwlwifi-8000C-22
[ 10.014077] iwlwifi :04:00.0: maximum version supported:
iwlwifi-8000C-30
[ 10.014078] iwlwifi :04:00.0: check
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
$ journalctl -b grep iwlwifi
July 17 01:29:22 host kernel: iwlwifi :04:00.0: Direct firmware load for
iwlwifi-8000C-30.ucode failed with error -2
July 17 01:29:22 host kernel: iwlwifi :04:00.0: Direct firmware load for
iwlwifi-8000C-29.ucode failed with error -2
July 17 01:29:22 host kernel: iwlwifi :04:00.0: Direct firmware load for
iwlwifi-8000C-28.ucode failed with error -2
July 17 01:29:22 host kernel: iwlwifi :04:00.0: Direct firmware load for
iwlwifi-8000C-27.ucode failed with error -2
July 17 01:29:22 host kernel: iwlwifi :04:00.0: Direct firmware load for
iwlwifi-8000C-26.ucode failed with error -2
July 17 01:29:22 host kernel: iwlwifi :04:00.0: Direct firmware load for
iwlwifi-8000C-25.ucode failed with error -2
July 17 01:29:22 host kernel: iwlwifi :04:00.0: Direct firmware load for
iwlwifi-8000C-24.ucode failed with error -2
July 17 01:29:22 host kernel: iwlwifi :04:00.0: Direct firmware load for
iwlwifi-8000C-23.ucode failed with error -2
July 17 01:29:22 host kernel: iwlwifi :04:00.0: Direct firmware load for
iwlwifi-8000C-22.ucode failed with error -2
July 17 01:29:22 host kernel: iwlwifi :04:00.0: no suitable firmware
found!
July 17 01:29:22 host kernel: iwlwifi :04:00.0: minimum version required:
iwlwifi-8000C-22
July 17 01:29:22 host kernel: iwlwifi :04:00.0: maximum version
supported: iwlwifi-8000C-30
July 17 01:29:22 host kernel: iwlwifi :04:00.0: check
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
$ modinfo iwlwifi | grep 1010; dmesg | grep iwl
alias: pci:v8086d24FDsv*sd1010bc*sc*i*
alias: pci:v8086d24F3sv*sd1010bc*sc*i*
alias: pci:v8086d095Asv*sd1010bc*sc*i*
[ 10.011090] iwlwifi :04:00.0: Direct firmware load for
iwlwifi-8000C-30.ucode failed with error -2
[ 10.011238] iwlwifi :04:0
[Kernel-packages] [Bug 1768431] Re: Request to revert SAUCE patches in the 18.04 SRU and update with upstream version
It would probably be best to open a new bug with a reason why they are needed for the SRU . That way we can keep the two separate. I'll submit an SRU request for this specific bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768431 Title: Request to revert SAUCE patches in the 18.04 SRU and update with upstream version Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: == Comment: #0 - UMA KRISHNAN - 2018-04-30 14:41:30 == ---Problem Description--- Request to revert SAUCE patches from 18.04 and apply the patches from next/master. Below set of cxlflash patches were submitted to Canonical after they were sent to the community. Based on review comments, there has been minor changes from that version. This BZ is to request reverting those SAUCE patches with the ones that are queued in next/master tree for 4.18. - SAUCE: cxlflash: Preserve number of interrupts for master contexts - SAUCE: cxlflash: Avoid clobbering context control register value - SAUCE: cxlflash: Add argument identifier names - SAUCE: cxlflash: Introduce OCXL backend - SAUCE: cxlflash: Hardware AFU for OCXL - SAUCE: cxlflash: Read host function configuration - SAUCE: cxlflash: Setup function acTag range - SAUCE: cxlflash: Read host AFU configuration - SAUCE: cxlflash: Setup AFU acTag range - SAUCE: cxlflash: Setup AFU PASID - SAUCE: cxlflash: Adapter context support for OCXL - SAUCE: cxlflash: Use IDR to manage adapter contexts - SAUCE: cxlflash: Support adapter file descriptors for OCXL - SAUCE: cxlflash: Support adapter context discovery - SAUCE: cxlflash: Support image reload policy modification - SAUCE: cxlflash: MMIO map the AFU - SAUCE: cxlflash: Support starting an adapter context - SAUCE: cxlflash: Support process specific mappings - SAUCE: cxlflash: Support AFU state toggling - SAUCE: cxlflash: Support reading adapter VPD data - SAUCE: cxlflash: Setup function OCXL link - SAUCE: cxlflash: Setup OCXL transaction layer - SAUCE: cxlflash: Support process element lifecycle - SAUCE: cxlflash: Support AFU interrupt management - SAUCE: cxlflash: Support AFU interrupt mapping and registration - SAUCE: cxlflash: Support starting user contexts - SAUCE: cxlflash: Support adapter context polling - SAUCE: cxlflash: Support adapter context reading - SAUCE: cxlflash: Support adapter context mmap and release - SAUCE: cxlflash: Support file descriptor mapping - SAUCE: cxlflash: Introduce object handle fop - SAUCE: cxlflash: Setup LISNs for user contexts - SAUCE: cxlflash: Setup LISNs for master contexts - SAUCE: cxlflash: Update synchronous interrupt status bits - SAUCE: cxlflash: Introduce OCXL context state machine - SAUCE: cxlflash: Register for translation errors - SAUCE: cxlflash: Support AFU reset - SAUCE: cxlflash: Enable OCXL operations Also, there are 3 additional patches added to end of this series that we would like to request being pulled into the SRU stream. These 3 patches address bug fixes. The commit ids for the patches queued in next/master tree are, 768999d6b1eadc6a13b1fba1886f1708f433d82b scsi: cxlflash: Preserve number of interrupts for master contexts 6c2b116dd38e3fbda10c3e3d5ac80ea7442e4f4d scsi: cxlflash: Avoid clobbering context control register value fcace1d5e11f518c6f91dd245fa1ac37393b47d3 scsi: cxlflash: Add argument identifier names 863dbdc0552f8bc100df48bb231089c382b89004 scsi: cxlflash: Introduce OCXL backend f2180daa83950ff8183f70b1b78d67cb13fd90b2 scsi: cxlflash: Hardware AFU for OCXL 1042535633554592d7d95a9cf83d2940803689e0 scsi: cxlflash: Read host function configuration ba84823a8b448207659753ae4f9c8b956923bada scsi: cxlflash: Setup function acTag range f55ced2dcd00ab257a2bb25eee619b75cda24817 scsi: cxlflash: Read host AFU configuration c5a8fec11278e245136c7f696c914269c58a6000 scsi: cxlflash: Setup AFU acTag range b42d68d728a63337bcb7860b59e6458946d94a84 scsi: cxlflash: Setup AFU PASID de25ec59a75802584aac97aed05fd94094dbbb58 scsi: cxlflash: Adapter context support for OCXL a76fc993e399f54b37f46107a31e817c779f2b82 scsi: cxlflash: Use IDR to manage adapter contexts 09f35da5fe218baf73f7b4efd281e2c19490512c scsi: cxlflash: Support adapter file descriptors for OCXL 17f9335bc59c1cf8f93617eee137e745abd71a3f scsi: cxlflash: Support adapter context discovery a5cfe355f23d4410d69af0e5b196b095463a0b4b scsi: cxlflash: Support image reload policy modification 0c62e7c091a4e0a01a7c6027fe719625ab2f521e scsi: cxlflash: MMIO map the AFU f39bab766ea4f0b3d5888fdd7d66babd7bef3966 scsi: cxlflash: Support starting an adapter context bef2014e8bd6391988b588acb969b48133072f17 scsi: cxlflash: Support process specific mappings 58b43437bd85565c7
[Kernel-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts
even if not the default ntp implementation, I think this is still a
valid bug task and should be tracked as such.
** Changed in: ntp (Ubuntu)
Importance: Undecided => Low
** Changed in: ntp (Ubuntu)
Status: Won't Fix => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1718227
Title:
replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
Status in aiccu package in Ubuntu:
Invalid
Status in aoetools package in Ubuntu:
New
Status in avahi package in Ubuntu:
New
Status in bind9 package in Ubuntu:
Invalid
Status in chrony package in Ubuntu:
Fix Released
Status in clamav package in Ubuntu:
Triaged
Status in controlaula package in Ubuntu:
Invalid
Status in epoptes package in Ubuntu:
New
Status in ethtool package in Ubuntu:
Triaged
Status in guidedog package in Ubuntu:
New
Status in htpdate package in Ubuntu:
New
Status in ifenslave package in Ubuntu:
Won't Fix
Status in ifmetric package in Ubuntu:
Won't Fix
Status in ifupdown-multi package in Ubuntu:
New
Status in ifupdown-scripts-zg2 package in Ubuntu:
Invalid
Status in isatapd package in Ubuntu:
New
Status in lprng package in Ubuntu:
New
Status in miredo package in Ubuntu:
New
Status in mythtv package in Ubuntu:
New
Status in nplan package in Ubuntu:
New
Status in nss-pam-ldapd package in Ubuntu:
New
Status in ntp package in Ubuntu:
Triaged
Status in openntpd package in Ubuntu:
New
Status in openresolv package in Ubuntu:
Won't Fix
Status in openssh package in Ubuntu:
New
Status in openvpn package in Ubuntu:
New
Status in openvswitch package in Ubuntu:
New
Status in postfix package in Ubuntu:
New
Status in quicktun package in Ubuntu:
New
Status in resolvconf package in Ubuntu:
New
Status in sendmail package in Ubuntu:
New
Status in shorewall-init package in Ubuntu:
New
Status in sidedoor package in Ubuntu:
New
Status in slrn package in Ubuntu:
New
Status in tinc package in Ubuntu:
New
Status in ubuntu-fan package in Ubuntu:
Fix Released
Status in ucarp package in Ubuntu:
New
Status in uml-utilities package in Ubuntu:
New
Status in uruk package in Ubuntu:
New
Status in vlan package in Ubuntu:
Won't Fix
Status in vzctl package in Ubuntu:
Triaged
Status in wide-dhcpv6 package in Ubuntu:
New
Status in wpa package in Ubuntu:
New
Bug description:
when network is configured with ifupdown, scripts in
/etc/network/ifup.d/ were called on network being brought up and
/etc/network/ifdown.d were called on network being brought down.
Any packages that shipped these hooks need to be verified to have the
same functionality under a netplan configured system.
# binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
# for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u
aiccu
aoetools
avahi
bind9
chrony
clamav
controlaula
epoptes
ethtool
guidedog
htpdate
ifenslave
ifmetric
ifupdown-extra
ifupdown-multi
ifupdown-scripts-zg2
isatapd
lprng
miredo
mythtv-backend
nss-pam-ldapd
ntp
openntpd
openresolv
openssh
openvpn
postfix
quicktun
resolvconf
sendmail
shorewall-init
sidedoor
slrn
tinc
ubuntu-fan
ucarp
uml-utilities
uruk
vlan
vzctl
wide-dhcpv6
wpa
Related bugs:
* bug 1718227: replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
* bug 1713803: replacement of resolvconf with systemd needs integration
* bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for
dhclient needs integration
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: netplan (not installed)
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Sep 19 10:53:08 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-07-23 (789 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: plan
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1718227/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772940] Re: linux-azure: 4.15.0-1013.13~16.04.2 -proposed tracker
** Summary changed: - linux-azure: 4.15.0-1013.13~16.04.1 -proposed tracker + linux-azure: 4.15.0-1013.13~16.04.2 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Released => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Released => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1772940 Title: linux-azure: 4.15.0-1013.13~16.04.2 -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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: 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-stable-master-bug: 1772927 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772940] Re: linux-azure: 4.15.0-1013.13~16.04.2 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released -- 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/1772940 Title: linux-azure: 4.15.0-1013.13~16.04.2 -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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: In Progress 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: 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-stable-master-bug: 1772927 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772940] Re: linux-azure: 4.15.0-1013.13~16.04.2 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released -- 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/1772940 Title: linux-azure: 4.15.0-1013.13~16.04.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: 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-stable-master-bug: 1772927 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774098] [NEW] [Dell Inspiron 7577] Kernel trace could be found for noveau driver
Public bug reported: CID: 201706-25581 Steps: 1. Install Bionic + update with LiveUSB 2. Boot to the desktop Result: After boot to desktop, the system looks OK, but you will see kernel trace in dmesg output (please find the attachment for the complete dmesg output): [ 35.825740] [ cut here ] [ 35.825742] nouveau :01:00.0: timeout [ 35.825785] WARNING: CPU: 1 PID: 196 at /build/linux-lZKWha/linux-4.15.0/drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:207 gf100_vmm_flush_+0x15c/0x1a0 [nouveau] [ 35.825785] Modules linked in: thunderbolt rfcomm ccm cmac bnep snd_hda_codec_hdmi nls_iso8859_1 snd_hda_codec_realtek snd_hda_codec_generic dell_laptop dell_smbios_smm dcdbas arc4 snd_hda_intel dell_smm_hwmon intel_rapl x86_pkg_temp_thermal intel_powerclamp snd_hda_codec coretemp snd_hda_core snd_hwdep snd_pcm kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul snd_seq_midi snd_seq_midi_event snd_rawmidi ghash_clmulni_intel pcbc snd_seq aesni_intel aes_x86_64 crypto_simd iwlmvm snd_seq_device glue_helper cryptd intel_cstate snd_timer uvcvideo mac80211 dell_smbios_wmi dell_wmi intel_rapl_perf dell_smbios videobuf2_vmalloc joydev input_leds videobuf2_memops serio_raw iwlwifi snd videobuf2_v4l2 btusb videobuf2_core dell_wmi_descriptor btrtl wmi_bmof intel_wmi_thunderbolt videodev btbcm soundcore [ 35.825808] cfg80211 media hid_multitouch btintel cdc_acm bluetooth idma64 ecdh_generic virt_dma mei_me intel_lpss_pci mei intel_lpss processor_thermal_device intel_pch_thermal intel_soc_dts_iosf int3403_thermal intel_hid int3402_thermal int3400_thermal shpchp acpi_thermal_rel int340x_thermal_zone mac_hid sparse_keymap tpm_crb acpi_pad sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 usbhid uas usb_storage nouveau i915 i2c_algo_bit ttm r8169 mxm_wmi psmouse mii drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops i2c_hid ahci drm libahci hid wmi video [ 35.825829] CPU: 1 PID: 196 Comm: kworker/1:2 Tainted: GW 4.15.0-22-generic #24-Ubuntu [ 35.825830] Hardware name: Dell Inc. Inspiron 7577/ , BIOS 1.4.2 01/25/2018 [ 35.825832] Workqueue: pm pm_runtime_work [ 35.825850] RIP: 0010:gf100_vmm_flush_+0x15c/0x1a0 [nouveau] [ 35.825851] RSP: 0018:a2be41aeb6c0 EFLAGS: 00010282 [ 35.825852] RAX: RBX: 92f1bc775e20 RCX: 0006 [ 35.825852] RDX: 0007 RSI: 0086 RDI: 92f1cf496490 [ 35.825853] RBP: a2be41aeb6f8 R08: 0001 R09: 064e [ 35.825854] R10: c08151e0 R11: R12: 92f1b1432c00 [ 35.825854] R13: 92f1b17f3840 R14: 0007e02c8820 R15: 92f1b6806000 [ 35.825855] FS: () GS:92f1cf48() knlGS: [ 35.825856] CS: 0010 DS: ES: CR0: 80050033 [ 35.825856] CR2: 7fc5a0b99000 CR3: 00027040a002 CR4: 003606e0 [ 35.825857] Call Trace: [ 35.825875] gp100_vmm_flush+0x17/0x20 [nouveau] [ 35.825891] nvkm_vmm_iter.constprop.13+0x2e5/0x880 [nouveau] [ 35.825905] ? gp100_vmm_pgt_sparse+0xd0/0xd0 [nouveau] [ 35.825915] ? nvkm_object_init+0xc2/0x190 [nouveau] [ 35.825930] nvkm_vmm_unmap_locked+0x8a/0xc0 [nouveau] [ 35.825944] ? gp100_vmm_pgt_sparse+0xd0/0xd0 [nouveau] [ 35.825957] nvkm_uvmm_mthd+0x662/0x8d0 [nouveau] [ 35.825967] nvkm_object_mthd+0x1a/0x30 [nouveau] [ 35.825977] nvkm_ioctl_mthd+0x5d/0xb0 [nouveau] [ 35.825987] nvkm_ioctl+0x11d/0x280 [nouveau] [ 35.826005] nvkm_client_ioctl+0x12/0x20 [nouveau] [ 35.826014] nvif_object_ioctl+0x47/0x50 [nouveau] [ 35.826022] nvif_object_mthd+0x129/0x150 [nouveau] [ 35.826040] ? nouveau_mem_host+0x122/0x1b0 [nouveau] [ 35.826048] nvif_vmm_unmap+0x3b/0x60 [nouveau] [ 35.826065] nouveau_vma_unmap+0x24/0x40 [nouveau] [ 35.826080] nouveau_bo_move_ntfy+0x9e/0xe0 [nouveau] [ 35.826083] ttm_bo_handle_move_mem+0x251/0x5c0 [ttm] [ 35.826086] ? ttm_bo_mem_space+0x39d/0x470 [ttm] [ 35.826088] ttm_bo_evict+0x13d/0x340 [ttm] [ 35.826090] ? find_next_bit+0xb/0x10 [ 35.826092] ttm_mem_evict_first+0x159/0x1b0 [ttm] [ 35.826094] ttm_bo_force_list_clean+0x6c/0x120 [ttm] [ 35.826096] ? pci_pm_runtime_resume+0xa0/0xa0 [ 35.826098] ttm_bo_evict_mm+0x26/0x50 [ttm] [ 35.826113] nouveau_do_suspend+0x81/0x2c0 [nouveau] [ 35.826128] nouveau_pmops_runtime_suspend+0x59/0xc0 [nouveau] [ 35.826129] pci_pm_runtime_suspend+0x64/0x180 [ 35.826131] ? pci_pm_runtime_resume+0xa0/0xa0 [ 35.826133] __rpm_callback+0xca/0x210 [ 35.826134] ? __switch_to_asm+0x40/0x70 [ 35.826135] ? __switch_to_asm+0x34/0x70 [ 35.826137] rpm_callback+0x24/0x80 [ 35.826138] ? pci_pm_runtime_resume+0xa0/0xa0 [ 35.826139] rpm_suspend+0x137/0x640 [ 35.826141] ? __switch_to_asm+0x40/0x70 [ 35.826142] pm_runtime_work+0x75/0xa0 [ 35.826143] process_one_work+0x1de/0x410 [ 35.826144] worker_thread+0x32/0x410 [ 35
[Kernel-packages] [Bug 1711407] Re: unregister_netdevice: waiting for lo to become free
I have the same issue, and I dump the vmcore, and find dst cache, hope it has
some help.
this leaked dst is in dst_busy_list, except dst_busy_list, nowhere I can find
it in
==
First case:
crash> rtable 0x880036fbba00 -x
struct rtable {
dst = {
callback_head = {
next = 0x880036fbb300,
func = 0x0
},
child = 0x0,
dev = 0x8817f15c3000,
ops = 0x8191f2c0 ,
_metrics = 0x815ef7d1,
expires = 0x0,
path = 0x880036fbba00,
from = 0x0,
xfrm = 0x0,
input = 0x8149f777 ,
{
output = 0x8149f762 ,
__UNIQUE_ID_rh_kabi_hide29 = {
output = 0x8149f762
},
{}
},
flags = 0x0,
pending_confirm = 0x0,
error = 0x0,
obsolete = 0x2,
header_len = 0x0,
trailer_len = 0x0,
tclassid = 0x0,
__pad_to_align_refcnt = {0xe, 0x80060},
__refcnt = {
counter = 0x1
},
__use = 0x0,
lastuse = 0x1000860b0,
{
next = 0x882fdaaa9800,
rt_next = 0x882fdaaa9800,
rt6_next = 0x882fdaaa9800,
dn_next = 0x882fdaaa9800
},
rh_reserved1 = 0x2,
rh_reserved2 = 0x85987845,
rh_reserved3 = 0x0,
rh_reserved4 = 0x0
},
rt_genid = 0x11,
rt_flags = 0x8000,
rt_type = 0x2,
rt_is_input = 0x1,
rt_uses_gateway = 0x0,
rt_iif = 0x0,
rt_gateway = 0x0,
rt_pmtu = 0x0,
rt_uncached = {
next = 0x880036fbbac0,
prev = 0x880036fbbac0
}
}
crash>
=
seconds case:
crash> rtable 8807ec0d9a00 -x
struct rtable {
dst = {
callback_head = {
next = 0x8807ec0db900,
func = 0x8119e250
},
child = 0x0,
dev = 0x8817ed384800,
ops = 0x81b18bc0 ,
_metrics = 0x817ca681,
expires = 0x0,
path = 0x8807ec0d9a00,
from = 0x0,
xfrm = 0x0,
input = 0x8162b200 ,
{
output = 0x8162b1e0 ,
__UNIQUE_ID_rh_kabi_hide29 = {
output = 0x8162b1e0
},
{}
},
flags = 0x6,
pending_confirm = 0x0,
error = 0x0,
obsolete = 0x2,
header_len = 0x0,
trailer_len = 0x0,
tclassid = 0x0,
__pad_to_align_refcnt = {0x880f6df8fec0, 0x0},
__refcnt = {
counter = 0x1
},
__use = 0x0,
lastuse = 0x1fcce9056,
{
next = 0x880404f49400,
rt_next = 0x880404f49400,
rt6_next = 0x880404f49400,
dn_next = 0x880404f49400
},
rh_reserved1 = 0x0,
rh_reserved2 = 0x0,
rh_reserved3 = 0x0,
rh_reserved4 = 0x0
},
rt_genid = 0x16,
rt_flags = 0x8000,
rt_type = 0x2,
rt_is_input = 0x0,
rt_uses_gateway = 0x0,
rt_iif = 0x0,
rt_gateway = 0x0,
rt_pmtu = 0x0,
rt_uncached = {
next = 0x8807ec0d9ac0,
prev = 0x8807ec0d9ac0
}
}
crash>
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1711407
Title:
unregister_netdevice: waiting for lo to become free
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Trusty:
In Progress
Status in linux source package in Xenial:
In Progress
Status in linux source package in Zesty:
Won't Fix
Status in linux source package in Artful:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
This is a "continuation" of bug 1403152, as that bug has been marked
"fix released" and recent reports of failure may (or may not) be a new
bug. Any further reports of the problem should please be reported
here instead of that bug.
--
[Impact]
When shutting down and starting containers the container network
namespace may experience a dst reference counting leak which results
in this message repeated in the logs:
unregister_netdevice: waiting for lo to become free. Usage count =
1
This can cause issues when trying to create net network namespace and
thus block a user from creating new containers.
[Test Case]
See comment 16, reproducer provided at https://github.com/fho/docker-
samba-loop
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774099] [NEW] iwlwifi Error sending STATISTICS_CMD: time out after 2000ms
Public bug reported: CID: 201706-25581 Dell Inspiron 7577 Steps: 1. Install Bionic + update with LiveUSB 2. Boot to the desktop Result: Wifi connection looks OK on both 2.4g and 5g network, but error message for iwlwifi could be found in dmesg: [ 73.936841] iwlwifi :3c:00.0: Error sending STATISTICS_CMD: time out after 2000ms. [ 73.936843] iwlwifi :3c:00.0: Current CMD queue read_ptr 198 write_ptr 199 [ 73.937703] iwlwifi :3c:00.0: Loaded firmware version: 34.0.1 [ 73.937705] iwlwifi :3c:00.0: 0x | ADVANCED_SYSASSERT [ 73.937707] iwlwifi :3c:00.0: 0x | trm_hw_status0 [ 73.937708] iwlwifi :3c:00.0: 0x | trm_hw_status1 [ 73.937709] iwlwifi :3c:00.0: 0x | branchlink2 [ 73.937710] iwlwifi :3c:00.0: 0x | interruptlink1 [ 73.937712] iwlwifi :3c:00.0: 0x | interruptlink2 [ 73.937713] iwlwifi :3c:00.0: 0x | data1 [ 73.937714] iwlwifi :3c:00.0: 0x | data2 [ 73.937715] iwlwifi :3c:00.0: 0x | data3 [ 73.937716] iwlwifi :3c:00.0: 0x | beacon time [ 73.937718] iwlwifi :3c:00.0: 0x | tsf low [ 73.937719] iwlwifi :3c:00.0: 0x000C | tsf hi [ 73.937720] iwlwifi :3c:00.0: 0x | time gp1 [ 73.937722] iwlwifi :3c:00.0: 0x0390CA61 | time gp2 [ 73.937723] iwlwifi :3c:00.0: 0x0001 | uCode revision type [ 73.937724] iwlwifi :3c:00.0: 0x0022 | uCode version major [ 73.937725] iwlwifi :3c:00.0: 0x | uCode version minor [ 73.937727] iwlwifi :3c:00.0: 0x0230 | hw version [ 73.937728] iwlwifi :3c:00.0: 0x00489000 | board version [ 73.937729] iwlwifi :3c:00.0: 0x8078F500 | hcmd [ 73.937731] iwlwifi :3c:00.0: 0x02722000 | isr0 [ 73.937732] iwlwifi :3c:00.0: 0x0080 | isr1 [ 73.937733] iwlwifi :3c:00.0: 0x08001802 | isr2 [ 73.937734] iwlwifi :3c:00.0: 0x00400082 | isr3 [ 73.937736] iwlwifi :3c:00.0: 0x | isr4 [ 73.937737] iwlwifi :3c:00.0: 0x00C6019C | last cmd Id [ 73.937738] iwlwifi :3c:00.0: 0x | wait_event [ 73.937739] iwlwifi :3c:00.0: 0xB30D | l2p_control [ 73.937741] iwlwifi :3c:00.0: 0x1C20 | l2p_duration [ 73.937742] iwlwifi :3c:00.0: 0x | l2p_mhvalid [ 73.937743] iwlwifi :3c:00.0: 0x00F0 | l2p_addr_match [ 73.937744] iwlwifi :3c:00.0: 0x000D | lmpm_pmg_sel [ 73.937746] iwlwifi :3c:00.0: 0x30101345 | timestamp [ 73.937747] iwlwifi :3c:00.0: 0x0034D8F0 | flow_handler [ 73.937822] iwlwifi :3c:00.0: 0x | ADVANCED_SYSASSERT [ 73.937823] iwlwifi :3c:00.0: 0x | umac branchlink1 [ 73.937824] iwlwifi :3c:00.0: 0x | umac branchlink2 [ 73.937825] iwlwifi :3c:00.0: 0x | umac interruptlink1 [ 73.937827] iwlwifi :3c:00.0: 0x | umac interruptlink2 [ 73.937828] iwlwifi :3c:00.0: 0x | umac data1 [ 73.937829] iwlwifi :3c:00.0: 0x | umac data2 [ 73.937830] iwlwifi :3c:00.0: 0x | umac data3 [ 73.937832] iwlwifi :3c:00.0: 0x | umac major [ 73.937833] iwlwifi :3c:00.0: 0x | umac minor [ 73.937834] iwlwifi :3c:00.0: 0x | frame pointer [ 73.937835] iwlwifi :3c:00.0: 0x | stack pointer [ 73.937837] iwlwifi :3c:00.0: 0x | last host cmd [ 73.937838] iwlwifi :3c:00.0: 0x | isr status reg [ 1056.908386] iwlwifi :3c:00.0: Microcode SW error detected. Restarting 0x200. [ 1056.908546] iwlwifi :3c:00.0: Start IWL Error Log Dump: [ 1056.908552] iwlwifi :3c:00.0: Status: 0x0100, count: 6 [ 1056.908558] iwlwifi :3c:00.0: Loaded firmware version: 34.0.1 [ 1056.908565] iwlwifi :3c:00.0: 0x0071 | ADVANCED_SYSASSERT [ 1056.908570] iwlwifi :3c:00.0: 0x02F0 | trm_hw_status0 [ 1056.908575] iwlwifi :3c:00.0: 0x | trm_hw_status1 [ 1056.908581] iwlwifi :3c:00.0: 0x00023FDC | branchlink2 [ 1056.908586] iwlwifi :3c:00.0: 0x0003915A | interruptlink1 [ 1056.908591] iwlwifi :3c:00.0: 0x0003915A | interruptlink2 [ 1056.908596] iwlwifi :3c:00.0: 0x | data1 [ 1056.908602] iwlwifi :3c:00.0: 0x1000 | data2 [ 1056.908607] iwlwifi :3c:00.0: 0x0783 | data3 [ 1056.908612] iwlwifi :3c:00.0: 0x01419617 | beacon time [ 1056.908618] iwlwifi :3c:00.0: 0x0ED741E2 | tsf low [ 1056.908623] iwlwifi :3c:00.0: 0x000D | tsf hi [ 1056.908628] iwlwifi :3c:00.0: 0x | time gp1 [ 1056.908634] iwlwifi :3c:00.0: 0x39CCC22B | time gp2 [ 1056.908639] iwlwifi :3c:00.0: 0x0001 | uCode revision type [ 1056.908644] iwlwifi :3c:00.0: 0x0022 | uCode version major [ 1056.908649] iwlwifi :3c:00.0: 0x | uCode version minor [ 1056.908654] iwlwifi :3c:00.0: 0x0230 | hw version [ 1056.908660] iwlwifi :3c:00.0: 0x00489000 | board version [ 1056.908665] iwlwifi :3c:00.0: 0
[Kernel-packages] [Bug 1774099] Re: iwlwifi Error sending STATISTICS_CMD: time out after 2000ms
** Description changed: CID: 201706-25581 Dell Inspiron 7577 Steps: - 1. Install Bionic + update with LiveUSB - 2. Boot to the desktop + 1. Install Bionic + update with LiveUSB + 2. Boot to the desktop Result: - Wifi connection looks OK on both 2.4g and 5g network, but error message for iwlwifi could be found in dmesg: + Wifi connection looks OK on both 2.4g and 5g network, but error message for iwlwifi could be found in dmesg: [ 73.936841] iwlwifi :3c:00.0: Error sending STATISTICS_CMD: time out after 2000ms. [ 73.936843] iwlwifi :3c:00.0: Current CMD queue read_ptr 198 write_ptr 199 [ 73.937703] iwlwifi :3c:00.0: Loaded firmware version: 34.0.1 - [ 73.937705] iwlwifi :3c:00.0: 0x | ADVANCED_SYSASSERT + [ 73.937705] iwlwifi :3c:00.0: 0x | ADVANCED_SYSASSERT [ 73.937707] iwlwifi :3c:00.0: 0x | trm_hw_status0 [ 73.937708] iwlwifi :3c:00.0: 0x | trm_hw_status1 [ 73.937709] iwlwifi :3c:00.0: 0x | branchlink2 [ 73.937710] iwlwifi :3c:00.0: 0x | interruptlink1 [ 73.937712] iwlwifi :3c:00.0: 0x | interruptlink2 [ 73.937713] iwlwifi :3c:00.0: 0x | data1 [ 73.937714] iwlwifi :3c:00.0: 0x | data2 [ 73.937715] iwlwifi :3c:00.0: 0x | data3 [ 73.937716] iwlwifi :3c:00.0: 0x | beacon time [ 73.937718] iwlwifi :3c:00.0: 0x | tsf low [ 73.937719] iwlwifi :3c:00.0: 0x000C | tsf hi [ 73.937720] iwlwifi :3c:00.0: 0x | time gp1 [ 73.937722] iwlwifi :3c:00.0: 0x0390CA61 | time gp2 [ 73.937723] iwlwifi :3c:00.0: 0x0001 | uCode revision type [ 73.937724] iwlwifi :3c:00.0: 0x0022 | uCode version major [ 73.937725] iwlwifi :3c:00.0: 0x | uCode version minor [ 73.937727] iwlwifi :3c:00.0: 0x0230 | hw version [ 73.937728] iwlwifi :3c:00.0: 0x00489000 | board version [ 73.937729] iwlwifi :3c:00.0: 0x8078F500 | hcmd [ 73.937731] iwlwifi :3c:00.0: 0x02722000 | isr0 [ 73.937732] iwlwifi :3c:00.0: 0x0080 | isr1 [ 73.937733] iwlwifi :3c:00.0: 0x08001802 | isr2 [ 73.937734] iwlwifi :3c:00.0: 0x00400082 | isr3 [ 73.937736] iwlwifi :3c:00.0: 0x | isr4 [ 73.937737] iwlwifi :3c:00.0: 0x00C6019C | last cmd Id [ 73.937738] iwlwifi :3c:00.0: 0x | wait_event [ 73.937739] iwlwifi :3c:00.0: 0xB30D | l2p_control [ 73.937741] iwlwifi :3c:00.0: 0x1C20 | l2p_duration [ 73.937742] iwlwifi :3c:00.0: 0x | l2p_mhvalid [ 73.937743] iwlwifi :3c:00.0: 0x00F0 | l2p_addr_match [ 73.937744] iwlwifi :3c:00.0: 0x000D | lmpm_pmg_sel [ 73.937746] iwlwifi :3c:00.0: 0x30101345 | timestamp [ 73.937747] iwlwifi :3c:00.0: 0x0034D8F0 | flow_handler [ 73.937822] iwlwifi :3c:00.0: 0x | ADVANCED_SYSASSERT [ 73.937823] iwlwifi :3c:00.0: 0x | umac branchlink1 [ 73.937824] iwlwifi :3c:00.0: 0x | umac branchlink2 [ 73.937825] iwlwifi :3c:00.0: 0x | umac interruptlink1 [ 73.937827] iwlwifi :3c:00.0: 0x | umac interruptlink2 [ 73.937828] iwlwifi :3c:00.0: 0x | umac data1 [ 73.937829] iwlwifi :3c:00.0: 0x | umac data2 [ 73.937830] iwlwifi :3c:00.0: 0x | umac data3 [ 73.937832] iwlwifi :3c:00.0: 0x | umac major [ 73.937833] iwlwifi :3c:00.0: 0x | umac minor [ 73.937834] iwlwifi :3c:00.0: 0x | frame pointer [ 73.937835] iwlwifi :3c:00.0: 0x | stack pointer [ 73.937837] iwlwifi :3c:00.0: 0x | last host cmd [ 73.937838] iwlwifi :3c:00.0: 0x | isr status reg [ 1056.908386] iwlwifi :3c:00.0: Microcode SW error detected. Restarting 0x200. [ 1056.908546] iwlwifi :3c:00.0: Start IWL Error Log Dump: [ 1056.908552] iwlwifi :3c:00.0: Status: 0x0100, count: 6 [ 1056.908558] iwlwifi :3c:00.0: Loaded firmware version: 34.0.1 - [ 1056.908565] iwlwifi :3c:00.0: 0x0071 | ADVANCED_SYSASSERT + [ 1056.908565] iwlwifi :3c:00.0: 0x0071 | ADVANCED_SYSASSERT [ 1056.908570] iwlwifi :3c:00.0: 0x02F0 | trm_hw_status0 [ 1056.908575] iwlwifi :3c:00.0: 0x | trm_hw_status1 [ 1056.908581] iwlwifi :3c:00.0: 0x00023FDC | branchlink2 [ 1056.908586] iwlwifi :3c:00.0: 0x0003915A | interruptlink1 [ 1056.908591] iwlwifi :3c:00.0: 0x0003915A | interruptlink2 [ 1056.908596] iwlwifi :3c:00.0: 0x | data1 [ 1056.908602] iwlwifi :3c:00.0: 0x1000 | data2 [ 1056.908607] iwlwifi :3c:00.0: 0x0783 | data3 [ 1056.908612] iwlwifi :3c:00.0: 0x01419617 | beacon time [ 1056.908618] iwlwifi :3c:00.0: 0x0ED741E2 | tsf low [ 1056.908623] iwlwifi :3c:00.0: 0x000
[Kernel-packages] [Bug 1774102] Re: [Dell Inspiron 7577] Wireless key does not work
Tested with 4.17rc7, issue still exist. ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1774102 Title: [Dell Inspiron 7577] Wireless key does not work Status in linux-signed package in Ubuntu: New Bug description: CID: 201706-25581 Dell Inspiron 7577 Steps: 1. Install Bionic + update with LiveUSB 2. Boot to the desktop 3. Press the Wireless key (Fn+ PrtScr) to kill wireless connection Result: The Wireless key is not working, from the dmesg it complains: [ 119.854458] dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed $ sudo showkey -k kb mode was ?UNKNOWN? [ if you are trying this under X, it might not work since the X server is also reading /dev/console ] press any key (program terminates 10s after last keypress)... keycode 240 press keycode 247 press keycode 247 release Nothing from showkey -s ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: User Name 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 30 12:04:08 2018 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1774102/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774098] Re: [Dell Inspiron 7577] Kernel trace could be found for noveau driver
Tested with 4.17rc7, issue still exist. [ 26.964590] [ cut here ] [ 26.964591] nouveau :01:00.0: timeout [ 26.964638] WARNING: CPU: 2 PID: 288 at /home/kernel/COD/linux/drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:207 gf100_vmm_flush_+0x15c/0x1a0 [nouveau] [ 26.964639] Modules linked in: rfcomm ccm bnep nls_iso8859_1 snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic intel_rapl x86_pkg_temp_thermal intel_powerclamp snd_hda_intel coretemp kvm_intel arc4 snd_hda_codec kvm snd_hda_core snd_hwdep snd_pcm irqbypass crct10dif_pclmul crc32_pclmul dell_laptop ghash_clmulni_intel dell_smm_hwmon pcbc iwlmvm snd_seq_midi snd_seq_midi_event mac80211 snd_rawmidi aesni_intel aes_x86_64 dell_wmi crypto_simd cryptd glue_helper intel_cstate dell_smbios intel_rapl_perf snd_seq dcdbas iwlwifi input_leds snd_seq_device snd_timer uvcvideo cfg80211 serio_raw snd intel_wmi_thunderbolt videobuf2_vmalloc videobuf2_memops dell_wmi_descriptor wmi_bmof videobuf2_v4l2 joydev btusb videobuf2_common btrtl soundcore btbcm mei_me btintel videodev mei idma64 hid_multitouch [ 26.964669] virt_dma media bluetooth cdc_acm intel_lpss_pci intel_lpss intel_pch_thermal ecdh_generic processor_thermal_device ucsi_acpi typec_ucsi intel_soc_dts_iosf typec shpchp int3403_thermal int3402_thermal int3400_thermal int340x_thermal_zone intel_hid acpi_thermal_rel mac_hid sparse_keymap acpi_pad sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid nouveau i915 mxm_wmi ttm i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse r8169 ahci mii libahci drm i2c_hid hid wmi video [ 26.964695] CPU: 2 PID: 288 Comm: kworker/2:2 Tainted: GW 4.17.0-041700rc7-generic #201805272130 [ 26.964695] Hardware name: Dell Inc. Inspiron 7577/, BIOS 1.4.2 01/25/2018 [ 26.964699] Workqueue: pm pm_runtime_work [ 26.964722] RIP: 0010:gf100_vmm_flush_+0x15c/0x1a0 [nouveau] [ 26.964723] RSP: 0018:add581f6b4c0 EFLAGS: 00010282 [ 26.964724] RAX: RBX: 925ffc79df40 RCX: 0006 [ 26.964725] RDX: 0007 RSI: 0096 RDI: 92600f5164b0 [ 26.964725] RBP: add581f6b4f8 R08: 050e R09: 0004 [ 26.964726] R10: 925ff1780511 R11: 0001 R12: 925ff1123000 [ 26.964727] R13: 925ff1340900 R14: 0005d002f1a0 R15: 925ff152c200 [ 26.964728] FS: () GS:92600f50() knlGS: [ 26.964729] CS: 0010 DS: ES: CR0: 80050033 [ 26.964730] CR2: 7fbdd53640c0 CR3: 0002ef60a002 CR4: 003606e0 [ 26.964731] Call Trace: [ 26.964753] gp100_vmm_flush+0x17/0x20 [nouveau] [ 26.964774] nvkm_vmm_iter.constprop.14+0x2e5/0x880 [nouveau] [ 26.964794] ? gp100_vmm_join+0x20/0x20 [nouveau] [ 26.964813] ? nvkm_vmm_map_choose+0xb0/0xb0 [nouveau] [ 26.964816] ? __update_load_avg_se.isra.41+0x1d9/0x1f0 [ 26.964817] ? __update_load_avg_se.isra.41+0x1d9/0x1f0 [ 26.964836] nvkm_vmm_map+0x21e/0x400 [nouveau] [ 26.964855] ? gp100_vmm_join+0x20/0x20 [nouveau] [ 26.964857] ? enqueue_task_fair+0xdc/0x850 [ 26.964876] nvkm_mem_map_dma+0x57/0x80 [nouveau] [ 26.964895] nvkm_uvmm_mthd+0x792/0x8d0 [nouveau] [ 26.964897] ? __switch_to_asm+0x40/0x70 [ 26.964911] nvkm_object_mthd+0x1a/0x30 [nouveau] [ 26.964925] nvkm_ioctl_mthd+0x5d/0xb0 [nouveau] [ 26.964939] nvkm_ioctl+0x11d/0x280 [nouveau] [ 26.964964] nvkm_client_ioctl+0x12/0x20 [nouveau] [ 26.964976] nvif_object_ioctl+0x47/0x50 [nouveau] [ 26.964987] nvif_object_mthd+0x129/0x150 [nouveau] [ 26.964989] ? __schedule+0x299/0x860 [ 26.965014] ? nouveau_do_suspend+0x2c0/0x2c0 [nouveau] [ 26.965016] ? _cond_resched+0x27/0x40 [ 26.965018] ? __kmalloc+0x66/0x250 [ 26.965031] ? nvif_vmm_map+0x3f/0xb0 [nouveau] [ 26.965043] nvif_vmm_map+0x88/0xb0 [nouveau] [ 26.965068] nouveau_mem_map+0x88/0xf0 [nouveau] [ 26.965091] nouveau_bo_move_m2mf.constprop.24+0x1bb/0x1d0 [nouveau] [ 26.965113] nouveau_bo_move+0xac/0x450 [nouveau] [ 26.965127] ? nvif_vmm_unmap+0x3b/0x60 [nouveau] [ 26.965149] ? nouveau_vma_unmap+0x24/0x40 [nouveau] [ 26.965154] ttm_bo_handle_move_mem+0x295/0x5b0 [ttm] [ 26.965157] ? ttm_bo_mem_space+0x391/0x470 [ttm] [ 26.965160] ttm_bo_evict+0x166/0x370 [ttm] [ 26.965162] ? try_to_wake_up+0x59/0x430 [ 26.965174] ? drm_mode_is_420+0x36/0x40 [drm] [ 26.965177] ttm_mem_evict_first+0x19a/0x220 [ttm] [ 26.965180] ttm_bo_force_list_clean+0xa1/0x170 [ttm] [ 26.965183] ttm_bo_evict_mm+0x26/0x50 [ttm] [ 26.965207] nouveau_do_suspend+0x81/0x2c0 [nouveau] [ 26.965243] nouveau_pmops_runtime_suspend+0x4f/0xb0 [nouveau] [ 26.965246] pci_pm_runtime_suspend+0x5f/0x180 [ 26.965248] ? pci_pm_runtime_resume+0xb0/0xb0 [ 26.965250] __rpm_callback+0xca/0x210 [ 26.965251] ? __switch_to_asm+0x40/0x70 [ 26.965252] ? __switch_to_a
[Kernel-packages] [Bug 1774102] [NEW] [Dell Inspiron 7577] Wireless key does not work
Public bug reported: CID: 201706-25581 Dell Inspiron 7577 Steps: 1. Install Bionic + update with LiveUSB 2. Boot to the desktop 3. Press the Wireless key (Fn+ PrtScr) to kill wireless connection Result: The Wireless key is not working, from the dmesg it complains: [ 119.854458] dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed $ sudo showkey -k kb mode was ?UNKNOWN? [ if you are trying this under X, it might not work since the X server is also reading /dev/console ] press any key (program terminates 10s after last keypress)... keycode 240 press keycode 247 press keycode 247 release Nothing from showkey -s ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: User Name 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 30 12:04:08 2018 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: 201706-25581 amd64 apport-bug bionic kernel-bug-exists-upstream taipei-lab -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1774102 Title: [Dell Inspiron 7577] Wireless key does not work Status in linux-signed package in Ubuntu: New Bug description: CID: 201706-25581 Dell Inspiron 7577 Steps: 1. Install Bionic + update with LiveUSB 2. Boot to the desktop 3. Press the Wireless key (Fn+ PrtScr) to kill wireless connection Result: The Wireless key is not working, from the dmesg it complains: [ 119.854458] dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed $ sudo showkey -k kb mode was ?UNKNOWN? [ if you are trying this under X, it might not work since the X server is also reading /dev/console ] press any key (program terminates 10s after last keypress)... keycode 240 press keycode 247 press keycode 247 release Nothing from showkey -s ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: User Name 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 30 12:04:08 2018 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1774102/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774082] Re: Trusty cannot load microcode for family 17h AMD processors
** Description changed: [Impact] AMD has recently updated the microcode in the linux-firmware tree for family 17h processors to address Spectre variant 2. The Trusty 3.13 kernel cannot load the microcode because it is missing a backport of upstream patch f4e9b7af0cd58dd039a0fb2cd67d57cea4889abf which leaves AMD machines vulnerable. [Test Case] Test must be done on a 17h family processor: 1) Take note of the microcode version before applying updated microcode: - $ sudo cat /sys/devices/system/cpu/cpu0/microcode/version - 0x8001227 + $ sudo cat /sys/devices/system/cpu/cpu0/microcode/version + 0x8001227 2) Get updated amd64-microcode package from the Ubuntu Security Team. Install it and reboot machine. 3) Verify that the microcode version has changed. + + Alternate test case (useful in the situation that the test system is + already running the latest microcode revision due to a BIOS update): + + 1) Fetch the latest 17h family microcode revision from here (you may + want to verify the signature): + + https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- + firmware.git/tree/amd-ucode/microcode_amd_fam17h.bin + + 2) Move it into /lib/firmware/amd-ucode/ + + 3) Force a microcode reload: + + $ echo 1 | sudo tee /sys/devices/system/cpu/microcode/reload + + 4) Verify that the following error message is *not* in your syslog: + + May 30 04:22:55 lodygin kernel: [ 388.290105] microcode: patch size mismatch + May 30 04:22:55 lodygin kernel: [ 388.290149] microcode: Patch-ID 0x08001227: size mismatch. [Regression Potential] The regression potential to the kernel revolves around the fact that the IBRS/IBPB implementation in the 3.13 kernel may not have been put through its paces yet due to a lack of available microcode updates. There could be a latent bug present that is uncovered. ** Description changed: [Impact] AMD has recently updated the microcode in the linux-firmware tree for family 17h processors to address Spectre variant 2. The Trusty 3.13 kernel cannot load the microcode because it is missing a backport of upstream patch f4e9b7af0cd58dd039a0fb2cd67d57cea4889abf which leaves AMD machines vulnerable. - [Test Case] + [Test Case (option 1)] Test must be done on a 17h family processor: 1) Take note of the microcode version before applying updated microcode: $ sudo cat /sys/devices/system/cpu/cpu0/microcode/version 0x8001227 2) Get updated amd64-microcode package from the Ubuntu Security Team. Install it and reboot machine. 3) Verify that the microcode version has changed. + [Test Case (option 2)] + Alternate test case (useful in the situation that the test system is already running the latest microcode revision due to a BIOS update): 1) Fetch the latest 17h family microcode revision from here (you may want to verify the signature): - https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- + https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/tree/amd-ucode/microcode_amd_fam17h.bin 2) Move it into /lib/firmware/amd-ucode/ 3) Force a microcode reload: - $ echo 1 | sudo tee /sys/devices/system/cpu/microcode/reload + $ echo 1 | sudo tee /sys/devices/system/cpu/microcode/reload 4) Verify that the following error message is *not* in your syslog: May 30 04:22:55 lodygin kernel: [ 388.290105] microcode: patch size mismatch May 30 04:22:55 lodygin kernel: [ 388.290149] microcode: Patch-ID 0x08001227: size mismatch. [Regression Potential] The regression potential to the kernel revolves around the fact that the IBRS/IBPB implementation in the 3.13 kernel may not have been put through its paces yet due to a lack of available microcode updates. There could be a latent bug present that is uncovered. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774082 Title: Trusty cannot load microcode for family 17h AMD processors Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: In Progress Bug description: [Impact] AMD has recently updated the microcode in the linux-firmware tree for family 17h processors to address Spectre variant 2. The Trusty 3.13 kernel cannot load the microcode because it is missing a backport of upstream patch f4e9b7af0cd58dd039a0fb2cd67d57cea4889abf which leaves AMD machines vulnerable. [Test Case (option 1)] Test must be done on a 17h family processor: 1) Take note of the microcode version before applying updated microcode: $ sudo cat /sys/devices/system/cpu/cpu0/microcode/version 0x8001227 2) Get updated amd64-microcode package from the Ubuntu Security Team. Install it and reboot machine. 3) Verify that the microcode version has changed. [Test Case (option 2)] Alternate test
[Kernel-packages] [Bug 1774082] Re: Trusty cannot load microcode for family 17h AMD processors
Fix submitted: https://lists.ubuntu.com/archives/kernel- team/2018-May/092825.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774082 Title: Trusty cannot load microcode for family 17h AMD processors Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: In Progress Bug description: [Impact] AMD has recently updated the microcode in the linux-firmware tree for family 17h processors to address Spectre variant 2. The Trusty 3.13 kernel cannot load the microcode because it is missing a backport of upstream patch f4e9b7af0cd58dd039a0fb2cd67d57cea4889abf which leaves AMD machines vulnerable. [Test Case (option 1)] Test must be done on a 17h family processor: 1) Take note of the microcode version before applying updated microcode: $ sudo cat /sys/devices/system/cpu/cpu0/microcode/version 0x8001227 2) Get updated amd64-microcode package from the Ubuntu Security Team. Install it and reboot machine. 3) Verify that the microcode version has changed. [Test Case (option 2)] Alternate test case (useful in the situation that the test system is already running the latest microcode revision due to a BIOS update): 1) Fetch the latest 17h family microcode revision from here (you may want to verify the signature): https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/tree/amd-ucode/microcode_amd_fam17h.bin 2) Move it into /lib/firmware/amd-ucode/ 3) Force a microcode reload: $ echo 1 | sudo tee /sys/devices/system/cpu/microcode/reload 4) Verify that the following error message is *not* in your syslog: May 30 04:22:55 lodygin kernel: [ 388.290105] microcode: patch size mismatch May 30 04:22:55 lodygin kernel: [ 388.290149] microcode: Patch-ID 0x08001227: size mismatch. [Regression Potential] The regression potential to the kernel revolves around the fact that the IBRS/IBPB implementation in the 3.13 kernel may not have been put through its paces yet due to a lack of available microcode updates. There could be a latent bug present that is uncovered. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774105] [NEW] [Dell Inspiron 7577] System hang during shutdown
Public bug reported: CID: 201706-25581 Dell Inspiron 7577 Steps: 1. Install Bionic + update with LiveUSB 2. Boot to the desktop 3. Poweroff / restart the system from the menu in the upper right corner Result: The system will hang before reaching the splash screen. The ctrl + alt + prtscr + b magic key combination is still alive. This is the last thing that could be seen from syslog: May 30 12:29:27 ubuntu-Inspiron-7577 systemd[858]: Stopping D-Bus User Message Bus... May 30 12:29:27 ubuntu-Inspiron-7577 gvfsd[1038]: A connection to the bus can't be made May 30 12:29:27 ubuntu-Inspiron-7577 gnome-session[942]: gnome-session-binary[942]: WARNING: Lost name on bus: org.gnome.SessionManager May 30 12:29:27 ubuntu-Inspiron-7577 gnome-session-binary[942]: WARNING: Lost name on bus: org.gnome.SessionManager May 30 12:29:27 ubuntu-Inspiron-7577 gnome-session[942]: gnome-session-binary[942]: CRITICAL: We failed, but the fail whale is dead. Sorry May 30 12:29:27 ubuntu-Inspiron-7577 gnome-session-binary[942]: CRITICAL: We failed, but the fail whale is dead. Sorry May 30 12:29:27 ubuntu-Inspiron-7577 gsd-xsettings[1223]: Error releasing name org.gtk.Settings: The connection is closed ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: User Name 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 30 12:34:00 2018 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: 201706-25581 amd64 apport-bug bionic taipei-lab -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1774105 Title: [Dell Inspiron 7577] System hang during shutdown Status in linux-signed package in Ubuntu: New Bug description: CID: 201706-25581 Dell Inspiron 7577 Steps: 1. Install Bionic + update with LiveUSB 2. Boot to the desktop 3. Poweroff / restart the system from the menu in the upper right corner Result: The system will hang before reaching the splash screen. The ctrl + alt + prtscr + b magic key combination is still alive. This is the last thing that could be seen from syslog: May 30 12:29:27 ubuntu-Inspiron-7577 systemd[858]: Stopping D-Bus User Message Bus... May 30 12:29:27 ubuntu-Inspiron-7577 gvfsd[1038]: A connection to the bus can't be made May 30 12:29:27 ubuntu-Inspiron-7577 gnome-session[942]: gnome-session-binary[942]: WARNING: Lost name on bus: org.gnome.SessionManager May 30 12:29:27 ubuntu-Inspiron-7577 gnome-session-binary[942]: WARNING: Lost name on bus: org.gnome.SessionManager May 30 12:29:27 ubuntu-Inspiron-7577 gnome-session[942]: gnome-session-binary[942]: CRITICAL: We failed, but the fail whale is dead. Sorry May 30 12:29:27 ubuntu-Inspiron-7577 gnome-session-binary[942]: CRITICAL: We failed, but the fail whale is dead. Sorry May 30 12:29:27 ubuntu-Inspiron-7577 gsd-xsettings[1223]: Error releasing name org.gtk.Settings: The connection is closed ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: User Name 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 30 12:34:00 2018 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) T
[Kernel-packages] [Bug 1772940] Re: linux-azure: 4.15.0-1013.13~16.04.2 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-xenial ** Tags added: 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 -- + boot-testing-requested: true kernel-stable-master-bug: 1772927 phase: Uploaded -- 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/1772940 Title: linux-azure: 4.15.0-1013.13~16.04.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772927 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773973] Comment bridged from LTC Bugzilla
--- Comment From pavra...@in.ibm.com 2018-05-30 01:55 EDT--- (In reply to comment #8) > Did this issue start with the 4.15.0-22 kernel? Was there a prior 4.15 > based kernel that did not exhibit this bug? > > Could you also see if this bug happens with the Bionic -proposed or mainline > kernel: > > See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to > enable and use -proposed. > > Mainline can be downloaded from: > http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc7/ Tested with given kernels below is the summary. 4.15.0-20-generic -> System boots 4.15.0-22-generic -> System fails to boots with oops 4.15.0-23-generic -> System fails to boots with oops 4.15.0-23-generic #26~lp1773162 -> System boots Thanks, Pavithra -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773973 Title: Ubuntu 18.04 [ Garrison P8 ]: Machine crashes with oops while booting with 4.15.0-22-generic kernel. Status in The Ubuntu-power-systems project: New Status in debian-installer package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in debian-installer source package in Bionic: New Status in linux source package in Bionic: Incomplete Bug description: ---Problem Description--- Ubuntu 18.04 [ Garrison P8 ]: Machine crashes with oops while booting with 4.15.0-22-generic kernel. ---Environment-- Kernel Build: 4.15.0-22-generic System Name : ltc-garri1 Model/Type : P8 Platform: BML ---Uname output--- Unable to boot. ---Steps to reproduce-- 1. Install Ubuntu 18.04 on Garison BML from http://ports.ubuntu.com /ubuntu-ports/dists/bionic/main/installer- ppc64el/current/images/netboot/ubuntu-installer/ppc64el/ and try to boot. ---Logs Attaching console lob. [4.578205] Bad kernel stack pointer 7b0dd870 at c000b9ec [4.578244] Oops: Bad kernel stack pointer, sig: 6 [#11] [4.578271] LE SMP NR_CPUS=2048 NUMA PowerNV [4.578301] Modules linked in: [4.578324] CPU: 27 PID: 1225 Comm: modprobe Tainted: G D 4.15.0-22-generic #24-Ubuntu [4.578371] NIP: c000b9ec LR: CTR: [4.578413] REGS: c0003febbd40 TRAP: 0300 Tainted: G D (4.15.0-22-generic) [4.578460] MSR: 90001031 CR: XER: [4.578504] CFAR: c000b934 DAR: 0002b200 DSISR: 4000 SOFTE: -4611686018403131680 [4.578504] GPR00: 7b0dd870 [4.578504] GPR04: [4.578504] GPR08: [4.578504] GPR12: 75dcd8781700 0002b200 [4.578504] GPR16: [4.578504] GPR20: [4.578504] GPR24: [4.578504] GPR28: [4.615667] NIP [c000b9ec] fast_exception_return+0x9c/0x184 [4.616210] LR [] (null) [4.616237] Call Trace: [4.616768] Instruction dump: [4.616789] e84101a0 7c4ff120 e8410170 7c5a03a6 e8010070 e8410080 e8610088 e8810090 [4.617697] e8210078 7db243a6 7db142a6 7c0004ac 63ff 7db242a6 63ff [4.618195] ---[ end trace a0d70ba94f583cca ]--- [4.675899] usb 1-3.3: new high-speed USB device number 5 using xhci_hcd [4.782923] [4.783061] Key type encrypted registered [4.783087] AppArmor: AppArmor sha1 policy hashing enabled [4.783117] ima: No TPM chip found, activating TPM-bypass! (rc=-19) [4.783181] evm: HMAC attrs: 0x1 [4.806062] rtc-opal opal-rtc: setting system clock to 2018-05-29 07:49:29 UTC (1527580169) [4.806350] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) [4.806353] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) [4.807260] Freeing unused kernel memory: 4800K [4.807321] This architecture does not have kernel memory protection. == Comment: #2 - SEETEENA THOUFEEK - 2018-05-29 06:47:06 == Symptoms looks exactly like . https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1691978 . https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656908 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1773973/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help
[Kernel-packages] [Bug 1773906] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773906 Title: Upgraded artful kernel oopses with null pointer dereference on pkt_setup_dev on insertion of mobile usb stick Status in linux package in Ubuntu: Confirmed Bug description: On insertion of a Huawei E173 mobile internet USB stick the artful kernel now oopses: BUG: unable to handle kernel NULL pointer dereference at 03d0 [ 633.710837] IP: pkt_setup_dev+0x2af/0x650 [pktcdvd] Issue seems to be related to the setup of the cdrom-like device hosted on the stick together with the UMTS modem. May possibly be due to some race as the usb stick configuration keeps changing until the device is properly switched to operate as a modem. Some of the times, UMTS modem remains detected notwithstanding the issue. After the issue, the system has problems in shutting down, though. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-generic 4.13.0.43.46 ProcVersionSignature: Ubuntu 4.13.0-43.48-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: callegar 2654 F pulseaudio /dev/snd/controlC1: callegar 2654 F pulseaudio CurrentDesktop: KDE Date: Tue May 29 08:27:52 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=c7dd5aac-abad-4cd0-9cac-552d49960853 InstallationDate: Installed on 2013-12-12 (1628 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Notebook W740SU ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-43-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-43-generic N/A linux-backports-modules-4.13.0-43-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-26 (214 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773906/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773912] [NEW] bluetoothd unable to establish connection after resume from suspend
You have been subscribed to a public bug:
Description: Ubuntu 18.04 LTS
Release:18.04
bluez:
Installed: 5.48-0ubuntu3
Candidate: 5.48-0ubuntu3
Version table:
*** 5.48-0ubuntu3 500
500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
3) What I expect to happen:
After resuming my Ubuntu from standby I expect my bluetooth daemon to connect
to my BT headset properly if I tell it to do so.
4) What actually happens:
After resuming I can click 'Connect as ADP Sink' in, for example, blueman, it
starts connecting, and aborts after a while.
When I restart the bluetoothd ('systemctl restart bluetoothd'), I can easily
connect my BT headset.
** Affects: bluez (Ubuntu)
Importance: Undecided
Status: New
--
bluetoothd unable to establish connection after resume from suspend
https://bugs.launchpad.net/bugs/1773912
You received this bug notification because you are a member of Kernel Packages,
which is subscribed to bluez in Ubuntu.
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772960] Re: linux: 4.4.0-128.154 -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 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772960 Title: linux: 4.4.0-128.154 -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: 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 upload-to-ppa series: Invalid 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 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 backports: bug 1772962 (linux-lts-xenial), bug 1772963 (linux-aws) derivatives: bug 1772964 (linux-kvm), bug 1772965 (linux-snapdragon), bug 1772966 (linux-aws), bug 1772968 (linux-raspi2), bug 1772969 (linux-euclid) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772960/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772966] Re: linux-aws: 4.4.0-1061.70 -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 -- 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/1772966 Title: linux-aws: 4.4.0-1061.70 -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 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 upload-to-ppa series: New 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 is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772960 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773912] [NEW] bluetoothd unable to establish connection after resume from suspend
*** This bug is a duplicate of bug 1759628 ***
https://bugs.launchpad.net/bugs/1759628
Public bug reported:
Description: Ubuntu 18.04 LTS
Release:18.04
bluez:
Installed: 5.48-0ubuntu3
Candidate: 5.48-0ubuntu3
Version table:
*** 5.48-0ubuntu3 500
500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
3) What I expect to happen:
After resuming my Ubuntu from standby I expect my bluetooth daemon to connect
to my BT headset properly if I tell it to do so.
4) What actually happens:
After resuming I can click 'Connect as ADP Sink' in, for example, blueman, it
starts connecting, and aborts after a while.
When I restart the bluetoothd ('systemctl restart bluetoothd'), I can easily
connect my BT headset.
** Affects: bluez (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "bluetoothd-log.txt"
https://bugs.launchpad.net/bugs/1773912/+attachment/5145865/+files/bluetoothd-log.txt
** Package changed: strongswan (Ubuntu) => bluez (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1773912
Title:
bluetoothd unable to establish connection after resume from suspend
Status in bluez package in Ubuntu:
New
Bug description:
Description: Ubuntu 18.04 LTS
Release:18.04
bluez:
Installed: 5.48-0ubuntu3
Candidate: 5.48-0ubuntu3
Version table:
*** 5.48-0ubuntu3 500
500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
3) What I expect to happen:
After resuming my Ubuntu from standby I expect my bluetooth daemon to connect
to my BT headset properly if I tell it to do so.
4) What actually happens:
After resuming I can click 'Connect as ADP Sink' in, for example, blueman, it
starts connecting, and aborts after a while.
When I restart the bluetoothd ('systemctl restart bluetoothd'), I can easily
connect my BT headset.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1773912/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773912] Re: bluetoothd unable to establish connection after resume from suspend
*** This bug is a duplicate of bug 1759628 ***
https://bugs.launchpad.net/bugs/1759628
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1759628, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.
** This bug has been marked a duplicate of bug 1759628
bluez regression: Bluetooth audio fails to reconnect after resume
--
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/1773912
Title:
bluetoothd unable to establish connection after resume from suspend
Status in bluez package in Ubuntu:
New
Bug description:
Description: Ubuntu 18.04 LTS
Release:18.04
bluez:
Installed: 5.48-0ubuntu3
Candidate: 5.48-0ubuntu3
Version table:
*** 5.48-0ubuntu3 500
500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
3) What I expect to happen:
After resuming my Ubuntu from standby I expect my bluetooth daemon to connect
to my BT headset properly if I tell it to do so.
4) What actually happens:
After resuming I can click 'Connect as ADP Sink' in, for example, blueman, it
starts connecting, and aborts after a while.
When I restart the bluetoothd ('systemctl restart bluetoothd'), I can easily
connect my BT headset.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1773912/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773912] Re: bluetoothd unable to establish connection after resume from suspend
*** This bug is a duplicate of bug 1759628 ***
https://bugs.launchpad.net/bugs/1759628
Kernel Version: 4.16.5
I also tried 'rfkill block bluetooth' and 'rfkill unblock bluetooth' after
resume, but no success.
--
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/1773912
Title:
bluetoothd unable to establish connection after resume from suspend
Status in bluez package in Ubuntu:
New
Bug description:
Description: Ubuntu 18.04 LTS
Release:18.04
bluez:
Installed: 5.48-0ubuntu3
Candidate: 5.48-0ubuntu3
Version table:
*** 5.48-0ubuntu3 500
500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
3) What I expect to happen:
After resuming my Ubuntu from standby I expect my bluetooth daemon to connect
to my BT headset properly if I tell it to do so.
4) What actually happens:
After resuming I can click 'Connect as ADP Sink' in, for example, blueman, it
starts connecting, and aborts after a while.
When I restart the bluetoothd ('systemctl restart bluetoothd'), I can easily
connect my BT headset.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1773912/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts
We handled chrony and ntp was demoted, so set ntp to Won't Fix in regard
to this bug.
** Changed in: ntp (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1718227
Title:
replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
Status in aiccu package in Ubuntu:
Invalid
Status in aoetools package in Ubuntu:
New
Status in avahi package in Ubuntu:
New
Status in bind9 package in Ubuntu:
Invalid
Status in chrony package in Ubuntu:
Fix Released
Status in clamav package in Ubuntu:
Triaged
Status in controlaula package in Ubuntu:
Invalid
Status in epoptes package in Ubuntu:
New
Status in ethtool package in Ubuntu:
Triaged
Status in guidedog package in Ubuntu:
New
Status in htpdate package in Ubuntu:
New
Status in ifenslave package in Ubuntu:
Won't Fix
Status in ifmetric package in Ubuntu:
Won't Fix
Status in ifupdown-multi package in Ubuntu:
New
Status in ifupdown-scripts-zg2 package in Ubuntu:
Invalid
Status in isatapd package in Ubuntu:
New
Status in lprng package in Ubuntu:
New
Status in miredo package in Ubuntu:
New
Status in mythtv package in Ubuntu:
New
Status in nplan package in Ubuntu:
New
Status in nss-pam-ldapd package in Ubuntu:
New
Status in ntp package in Ubuntu:
Won't Fix
Status in openntpd package in Ubuntu:
New
Status in openresolv package in Ubuntu:
Won't Fix
Status in openssh package in Ubuntu:
New
Status in openvpn package in Ubuntu:
New
Status in openvswitch package in Ubuntu:
New
Status in postfix package in Ubuntu:
New
Status in quicktun package in Ubuntu:
New
Status in resolvconf package in Ubuntu:
New
Status in sendmail package in Ubuntu:
New
Status in shorewall-init package in Ubuntu:
New
Status in sidedoor package in Ubuntu:
New
Status in slrn package in Ubuntu:
New
Status in tinc package in Ubuntu:
New
Status in ubuntu-fan package in Ubuntu:
Fix Released
Status in ucarp package in Ubuntu:
New
Status in uml-utilities package in Ubuntu:
New
Status in uruk package in Ubuntu:
New
Status in vlan package in Ubuntu:
Won't Fix
Status in vzctl package in Ubuntu:
Triaged
Status in wide-dhcpv6 package in Ubuntu:
New
Status in wpa package in Ubuntu:
New
Bug description:
when network is configured with ifupdown, scripts in
/etc/network/ifup.d/ were called on network being brought up and
/etc/network/ifdown.d were called on network being brought down.
Any packages that shipped these hooks need to be verified to have the
same functionality under a netplan configured system.
# binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
# for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u
aiccu
aoetools
avahi
bind9
chrony
clamav
controlaula
epoptes
ethtool
guidedog
htpdate
ifenslave
ifmetric
ifupdown-extra
ifupdown-multi
ifupdown-scripts-zg2
isatapd
lprng
miredo
mythtv-backend
nss-pam-ldapd
ntp
openntpd
openresolv
openssh
openvpn
postfix
quicktun
resolvconf
sendmail
shorewall-init
sidedoor
slrn
tinc
ubuntu-fan
ucarp
uml-utilities
uruk
vlan
vzctl
wide-dhcpv6
wpa
Related bugs:
* bug 1718227: replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
* bug 1713803: replacement of resolvconf with systemd needs integration
* bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for
dhclient needs integration
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: netplan (not installed)
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Sep 19 10:53:08 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-07-23 (789 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: plan
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1718227/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773897] Re: Bluetooth 3.0 mouses are automatically disconnected after connected
apport information ** Tags added: apport-collected third-party-packages ** Description changed: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 + --- + ApportVersion: 2.20.9-0ubuntu7 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2018-05-29 (0 days ago) + InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) + InterestingModules: rfcomm bnep btusb bluetooth + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 8087:0a2b Intel Corp. + Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. + Bus 001 Device 004: ID 27c6:5385 + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: Dell Inc. XPS 13 9370 + Package: bluez 5.48-0ubuntu3 [origin: unknown] + PackageArchitecture: amd64 + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 + Tags: third-party-packages bionic + Uname: Linux 4.15.0-22-generic x86_64 + UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 11/03/2017 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 0.3.13 + dmi.board.name: 0173S1 + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 9 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr: + dmi.product.family: XPS + dmi.product.name: XPS 13 9370 + dmi.sys.vendor: Dell Inc. + hciconfig: + hci0:Type: Primary Bus: USB + BD Address: D4:25:8B:4F:7E:D6 ACL MTU: 1021:4 SCO MTU: 96:6 + UP RUNNING PSCAN ISCAN + RX bytes:61781 acl:382 sco:0 events:536 errors:0 + TX bytes:7985 acl:69 sco:0 commands:168 errors:0 ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1773897/+attachment/5145892/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1773897 Title: Bluetooth 3.0 mouses are automatically disconnected after connected Status in OEM Priority Project: Incomplete Status in bluez package in Ubuntu: Incomplete Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: bluez 5.48-0ubuntu3 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.3.13 dmi.board.name
[Kernel-packages] [Bug 1773897] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1773897/+attachment/5145894/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1773897 Title: Bluetooth 3.0 mouses are automatically disconnected after connected Status in OEM Priority Project: Incomplete Status in bluez package in Ubuntu: Incomplete Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: bluez 5.48-0ubuntu3 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.3.13 dmi.board.name: 0173S1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: D4:25:8B:4F:7E:D6 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:61781 acl:382 sco:0 events:536 errors:0 TX bytes:7985 acl:69 sco:0 commands:168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1773897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773897] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1773897/+attachment/5145896/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1773897 Title: Bluetooth 3.0 mouses are automatically disconnected after connected Status in OEM Priority Project: Incomplete Status in bluez package in Ubuntu: Incomplete Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: bluez 5.48-0ubuntu3 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.3.13 dmi.board.name: 0173S1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: D4:25:8B:4F:7E:D6 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:61781 acl:382 sco:0 events:536 errors:0 TX bytes:7985 acl:69 sco:0 commands:168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1773897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773897] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1773897/+attachment/5145897/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1773897 Title: Bluetooth 3.0 mouses are automatically disconnected after connected Status in OEM Priority Project: Incomplete Status in bluez package in Ubuntu: Incomplete Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: bluez 5.48-0ubuntu3 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.3.13 dmi.board.name: 0173S1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: D4:25:8B:4F:7E:D6 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:61781 acl:382 sco:0 events:536 errors:0 TX bytes:7985 acl:69 sco:0 commands:168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1773897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773897] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1773897/+attachment/5145895/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1773897 Title: Bluetooth 3.0 mouses are automatically disconnected after connected Status in OEM Priority Project: Incomplete Status in bluez package in Ubuntu: Incomplete Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: bluez 5.48-0ubuntu3 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.3.13 dmi.board.name: 0173S1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: D4:25:8B:4F:7E:D6 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:61781 acl:382 sco:0 events:536 errors:0 TX bytes:7985 acl:69 sco:0 commands:168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1773897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773897] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1773897/+attachment/5145893/+files/Dependencies.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1773897 Title: Bluetooth 3.0 mouses are automatically disconnected after connected Status in OEM Priority Project: Incomplete Status in bluez package in Ubuntu: Incomplete Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: bluez 5.48-0ubuntu3 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.3.13 dmi.board.name: 0173S1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: D4:25:8B:4F:7E:D6 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:61781 acl:382 sco:0 events:536 errors:0 TX bytes:7985 acl:69 sco:0 commands:168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1773897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771919] Re: Support Realtek Bluetooth [0bda:c024]
** Also affects: linux-oem (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux-oem (Ubuntu Xenial) 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/1771919 Title: Support Realtek Bluetooth [0bda:c024] Status in HWE Next: New Status in linux-oem package in Ubuntu: In Progress Status in linux-oem source package in Xenial: Fix Committed Bug description: The driver rtk-btusb is already in ubuntu/rtl8821ce-bt. All we need to support this device is to add the ID to the driver and blacklist it in btusb. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1771919/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773635] Re: AR3012 Bluetooth not start after an upgrade to 4.4.0-127
Please try this kernel https://people.canonical.com/~khfeng/lp1773635/ Possible regression from this commit: commit c9829dd3f00809ccf10afeb904ba5c53c3c3d6e7 Author: Takashi Iwai Date: Thu Mar 15 17:02:34 2018 +0100 Bluetooth: btusb: Fix quirk for Atheros 1525/QCA6174 BugLink: http://bugs.launchpad.net/bugs/1764973 commit f44cb4b19ed40b655c2d422c9021ab2c2625adb6 upstream. The Atheros 1525/QCA6174 BT doesn't seem working properly on the recent kernels, as it tries to load a wrong firmware ar3k/AthrBT_0x0200.dfu and it fails. This seems to have been a problem for some time, and the known workaround is to apply BTUSB_QCA_ROM quirk instead of BTUSB_ATH3012. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773635 Title: AR3012 Bluetooth not start after an upgrade to 4.4.0-127 Status in linux package in Ubuntu: Confirmed Bug description: I have an Atheros mixed WiFi+Bluetooth device which worked nice on a kernels prior to 4.4.0-127 But unfortunately after last upgrade (from 4.4.0-124 to 4.4.0-127) bluetooth is unable to start - no bluetooth indicator appears in notifications tray and no device could be discovered or connected to via bluetooth. Tailing a syslog provides following lines, related to bluetooth: May 27 12:15:16 K43T kernel: [ 228.102799] usbcore: registered new interface driver btusb May 27 12:15:16 K43T kernel: [ 228.109562] Bluetooth: hci0: don't support firmware rome 0x1020200 May 27 12:15:16 K43T systemd-udevd[4634]: Process '/bin/hciconfig hci0 up' failed with exit code 1. May 27 12:15:16 K43T kernel: [ 228.112017] Bluetooth: hci0: don't support firmware rome 0x1020200 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-127-generic 4.4.0-127.153 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: insanedeveloper 1937 F pulseaudio /dev/snd/controlC0: insanedeveloper 1937 F pulseaudio CurrentDesktop: Unity Date: Sun May 27 12:33:42 2018 HibernationDevice: RESUME=UUID=4a7e8ac6-783b-4a23-bfa9-8130cfef7945 InstallationDate: Installed on 2015-11-28 (910 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: ASUSTeK Computer Inc. K43TK ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic.efi.signed root=UUID=7dbd7b42-e67f-4416-8f6d-6c918e744fb7 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-127-generic N/A linux-backports-modules-4.4.0-127-generic N/A linux-firmware 1.157.18 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2017-01-08 (503 days ago) dmi.bios.date: 03/20/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 206 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K43TK dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr206:bd03/20/2012:svnASUSTeKComputerInc.:pnK43TK:pvr1.0:rvnASUSTeKComputerInc.:rnK43TK:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K43TK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773635/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773897] Re: Bluetooth 3.0 mouses are automatically disconnected after connected
Thanks. Please try 5.49 (https://launchpad.net/~bluetooth/+archive/ubuntu/bluez). If the problem continues in 5.49 then please report the bug upstream here: https://bugzilla.kernel.org/enter_bug.cgi?product=Drivers&component=Bluetooth mentioning that it seems to be a regression starting at 6b34bdd96. -- 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/1773897 Title: Bluetooth 3.0 mouses are automatically disconnected after connected Status in OEM Priority Project: Incomplete Status in bluez package in Ubuntu: Incomplete Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: bluez 5.48-0ubuntu3 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.3.13 dmi.board.name: 0173S1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: D4:25:8B:4F:7E:D6 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:61781 acl:382 sco:0 events:536 errors:0 TX bytes:7985 acl:69 sco:0 commands:168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1773897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773897] Re: Bluetooth 3.0 mouses are automatically disconnected after connected
This bug still can be reproduced in BlueZ 5.49. -- 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/1773897 Title: Bluetooth 3.0 mouses are automatically disconnected after connected Status in OEM Priority Project: Incomplete Status in bluez package in Ubuntu: Incomplete Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: bluez 5.48-0ubuntu3 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.3.13 dmi.board.name: 0173S1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: D4:25:8B:4F:7E:D6 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:61781 acl:382 sco:0 events:536 errors:0 TX bytes:7985 acl:69 sco:0 commands:168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1773897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1708130] Re: ISST-LTE: Ubuntu16.04.03: PowerNV: 'ppc64_cpu' commands hangs while changing SMT value with Leaf IO and BASE tests
--- Comment From vipar...@in.ibm.com 2018-05-29 03:52 EDT--- (In reply to comment #67) > Hi Lata, > > We no longer have this test setup in our environment, pls close this > bugzilla as un reproducible . > > Thanks. Closing this Bug in IBM Bugzilla. ** Tags removed: targetmilestone-inin16043 ** Tags added: targetmilestone-inin--- -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1708130 Title: ISST-LTE: Ubuntu16.04.03: PowerNV: 'ppc64_cpu' commands hangs while changing SMT value with Leaf IO and BASE tests Status in The Ubuntu-power-systems project: Won't Fix Status in linux package in Ubuntu: Won't Fix Bug description: == Comment: #0 - INDIRA P. JOGA - 2017-07-07 03:56:54 == Description: -- Started Leaf IO and BASE(without smt tests)and then tried to change the SMT value manually where it hangs UBUNTU BUILD: 4.10.0-26-generic Steps to re-create: -- > Installed latest Ubuntu160403 kernel on system lotkvm 4.10.0-26-generic > Leaf microcode: KMIPP113 > Started Leaf IO and BASE tests(without smt tests). root@lotkvm:/home# show.report.py HOSTNAMEKERNEL VERSION DISTRO INFO ---- lotkvm 4.10.0-26-genericUbuntu 16.04.2 LTS \n \l Current Time: Tue Jul 4 00:55:37 2017 Job-IDFOCUS Start-Time DurationFunction --- -- 1 IO 20170704-00:44:45 0.0 hr(s) 10.0 min(s) IO_Focus 2 BASE20170704-00:44:52 0.0 hr(s) 10.0 min(s) Test FOCUS IO BASESUM TOTAL 76 25 101 FAIL 0 4 4 PASS 76 21 97 (%) (100%) (84%) (96%) >Now manually changed the smt value root@lotkvm:/home# ppc64_cpu --smt SMT=8 root@lotkvm:/home# date Tue Jul 4 00:46:01 CDT 2017 root@lotkvm:/home# ppc64_cpu --smt=2 root@lotkvm:/home# ppc64_cpu --smt SMT=2 root@lotkvm:/home# date Tue Jul 4 00:50:01 CDT 2017 root@lotkvm:/home# ppc64_cpu --smt=4 root@lotkvm:/home# ppc64_cpu --smt SMT=4 root@lotkvm:/home# date Tue Jul 4 00:54:38 CDT 2017 root@lotkvm:/home# ppc64_cpu --smt=8 [ 2055.142781] INFO: task jbd2/nvme0n1p6-:22052 blocked for more than 120 seconds. [ 2055.142915] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.142978] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.143150] INFO: task kworker/48:0H:21755 blocked for more than 120 seconds. [ 2055.143226] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.143289] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.143570] INFO: task kworker/u259:3:22436 blocked for more than 120 seconds. [ 2055.143647] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.143709] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.143953] INFO: task kworker/8:188:118516 blocked for more than 120 seconds. [ 2055.144029] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.144091] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.144289] INFO: task mkfs.ntfs:95505 blocked for more than 120 seconds. [ 2055.144353] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.144416] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.144600] INFO: task ppc64_cpu:80305 blocked for more than 120 seconds. [ 2055.144665] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.144727] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.144872] INFO: task rm:80950 blocked for more than 120 seconds. [ 2055.144936] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.144998] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.145133] INFO: task rm:80951 blocked for more than 120 seconds. [ 2055.145195] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.145257] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2175.974718] INFO: task jbd2/nvme0n1p6-:22052 blocked for more than 120 seconds. [ 2175.974848] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2175.974912] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2175.975068] INFO: task kworker/48:0H:21755 blocked for more than 120 seconds. [ 2175.975144] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2175.975206] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. > root@lotkvm:# ps -eaf | grep ppc* root 48054 12068 0 01:24 pts/000:00:00
[Kernel-packages] [Bug 1769980] Re: Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement
** Changed in: linux-oem (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux-oem (Ubuntu Xenial) Status: In Progress => Fix Committed ** Changed in: linux-oem (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1769980 Title: Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement Status in HWE Next: In Progress Status in OEM Priority Project: Triaged Status in crda package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in wireless-regdb package in Ubuntu: Fix Released Status in crda source package in Xenial: Invalid Status in linux source package in Xenial: Won't Fix Status in linux-firmware source package in Xenial: Fix Released Status in linux-oem source package in Xenial: Fix Committed Status in wireless-regdb source package in Xenial: Fix Committed Status in crda source package in Bionic: Invalid Status in linux source package in Bionic: Confirmed Status in linux-firmware source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Committed Status in wireless-regdb source package in Bionic: Fix Committed Bug description: Intel wireless driver and firmware require updates in order to meet the new ETSI regulation [1] for OEM machines shipped from factories. Intel provided us the following information for what are required to update: 1. Kernel driver: https://patchwork.kernel.org/patch/10322121/ https://patchwork.kernel.org/patch/10312731/ https://patchwork.kernel.org/patch/10312735/ https://patchwork.kernel.org/patch/10312733/ - 7260, 7265, 7265D and 3168 NICs, 4.15 plus above driver patches - 8000 series requires 4.16. - 9000 series requires 4.17. 2. linux-firmware Requires latest versions from linux-firmware.git 3. wireless-regdb update [1] http://www.etsi.org/deliver/etsi_en/301800_301899/301893/02.01.01_60/en_301893v020101p.pdf --- == SRU Justification for linux-firmware == [Impact] Intel released these firmware updates to support the new ETSI 5GHz Adaptivity Requirement, OEM has to meet it in order to ship. [Test Case] Check dmesg to confirm the correct firmware is loaded, make sure the revision is correct, and check wifi can functions properly. [Regression Potential] It is possible that there is regression introduced by Intel's firmware, so should make sure wifi still works properly after the new firmware is used. We have verified the new firmwares of 7260 and 7265D on 4.4 and 4.15 kernels. The 8000 and 9000 series firmwares have newer API versions and will need to confirm with subsequent driver changes. --- wireless-regdb SRU Justification Impact: New regulatory requirements in the EU necessitate updating our wireless regulatory database. Fix: New upstream release. Test Case: Minimal testing would be to reload the regdb (can be done with iw built from git or by rebooting) and verifying that you are able to change regulatory domains (e.g., sudo iw reg set US; iw reg get). Regression Potential: Minimal. Biggest risk would be the inability to load the new database due to the changes in signing, however testing will confirm that appropriate key is present. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1769980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773897] Re: Bluetooth 3.0 mouses are automatically disconnected after connected
Filed a upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=199873 ** Bug watch added: Linux Kernel Bug Tracker #199873 https://bugzilla.kernel.org/show_bug.cgi?id=199873 -- 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/1773897 Title: [regression] Bluetooth 3.0 mouses are automatically disconnected after connected Status in Bluez Utilities: Unknown Status in OEM Priority Project: New Status in bluez package in Ubuntu: New Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: bluez 5.48-0ubuntu3 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.3.13 dmi.board.name: 0173S1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: D4:25:8B:4F:7E:D6 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:61781 acl:382 sco:0 events:536 errors:0 TX bytes:7985 acl:69 sco:0 commands:168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1773897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773897] Re: Bluetooth 3.0 mouses are automatically disconnected after connected
** Also affects: bluez via https://bugzilla.kernel.org/show_bug.cgi?id=199873 Importance: Unknown Status: Unknown ** Changed in: bluez (Ubuntu) Status: Incomplete => New ** Summary changed: - Bluetooth 3.0 mouses are automatically disconnected after connected + [regression] Bluetooth 3.0 mouses are automatically disconnected after connected ** Changed in: oem-priority Status: Incomplete => New ** Tags added: regression-release -- 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/1773897 Title: [regression] Bluetooth 3.0 mouses are automatically disconnected after connected Status in Bluez Utilities: Unknown Status in OEM Priority Project: New Status in bluez package in Ubuntu: New Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: bluez 5.48-0ubuntu3 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.3.13 dmi.board.name: 0173S1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: D4:25:8B:4F:7E:D6 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:61781 acl:382 sco:0 events:536 errors:0 TX bytes:7985 acl:69 sco:0 commands:168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1773897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773897] Re: Bluetooth 3.0 mouses are automatically disconnected after connected
The attached file is the output of "journalctl -b". ** Attachment added: "journalctl-b.log" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1773897/+attachment/5145906/+files/journalctl-b.log -- 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/1773897 Title: Bluetooth 3.0 mouses are automatically disconnected after connected Status in OEM Priority Project: Incomplete Status in bluez package in Ubuntu: Incomplete Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: bluez 5.48-0ubuntu3 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.3.13 dmi.board.name: 0173S1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: D4:25:8B:4F:7E:D6 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:61781 acl:382 sco:0 events:536 errors:0 TX bytes:7985 acl:69 sco:0 commands:168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1773897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773897] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1773897/+attachment/5145898/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1773897 Title: Bluetooth 3.0 mouses are automatically disconnected after connected Status in OEM Priority Project: Incomplete Status in bluez package in Ubuntu: Incomplete Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: bluez 5.48-0ubuntu3 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.3.13 dmi.board.name: 0173S1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: D4:25:8B:4F:7E:D6 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:61781 acl:382 sco:0 events:536 errors:0 TX bytes:7985 acl:69 sco:0 commands:168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1773897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773897] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1773897/+attachment/5145900/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1773897 Title: Bluetooth 3.0 mouses are automatically disconnected after connected Status in OEM Priority Project: Incomplete Status in bluez package in Ubuntu: Incomplete Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: bluez 5.48-0ubuntu3 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.3.13 dmi.board.name: 0173S1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: D4:25:8B:4F:7E:D6 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:61781 acl:382 sco:0 events:536 errors:0 TX bytes:7985 acl:69 sco:0 commands:168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1773897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773897] syslog.txt
apport information ** Attachment added: "syslog.txt" https://bugs.launchpad.net/bugs/1773897/+attachment/5145903/+files/syslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1773897 Title: Bluetooth 3.0 mouses are automatically disconnected after connected Status in OEM Priority Project: Incomplete Status in bluez package in Ubuntu: Incomplete Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: bluez 5.48-0ubuntu3 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.3.13 dmi.board.name: 0173S1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: D4:25:8B:4F:7E:D6 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:61781 acl:382 sco:0 events:536 errors:0 TX bytes:7985 acl:69 sco:0 commands:168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1773897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773897] rfkill.txt
apport information ** Attachment added: "rfkill.txt" https://bugs.launchpad.net/bugs/1773897/+attachment/5145902/+files/rfkill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1773897 Title: Bluetooth 3.0 mouses are automatically disconnected after connected Status in OEM Priority Project: Incomplete Status in bluez package in Ubuntu: Incomplete Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: bluez 5.48-0ubuntu3 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.3.13 dmi.board.name: 0173S1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: D4:25:8B:4F:7E:D6 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:61781 acl:382 sco:0 events:536 errors:0 TX bytes:7985 acl:69 sco:0 commands:168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1773897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773897] getfacl.txt
apport information ** Attachment added: "getfacl.txt" https://bugs.launchpad.net/bugs/1773897/+attachment/5145901/+files/getfacl.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1773897 Title: Bluetooth 3.0 mouses are automatically disconnected after connected Status in OEM Priority Project: Incomplete Status in bluez package in Ubuntu: Incomplete Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: bluez 5.48-0ubuntu3 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.3.13 dmi.board.name: 0173S1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: D4:25:8B:4F:7E:D6 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:61781 acl:382 sco:0 events:536 errors:0 TX bytes:7985 acl:69 sco:0 commands:168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1773897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773897] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1773897/+attachment/5145899/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1773897 Title: Bluetooth 3.0 mouses are automatically disconnected after connected Status in OEM Priority Project: Incomplete Status in bluez package in Ubuntu: Incomplete Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: bluez 5.48-0ubuntu3 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.3.13 dmi.board.name: 0173S1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: D4:25:8B:4F:7E:D6 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:61781 acl:382 sco:0 events:536 errors:0 TX bytes:7985 acl:69 sco:0 commands:168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1773897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767088] Re: regression Aquantia Corp. AQC107 4.15.0-13-generic -> 4.15.0-20-generic ?
** Changed in: linux-oem (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1767088 Title: regression Aquantia Corp. AQC107 4.15.0-13-generic -> 4.15.0-20-generic ? Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: New Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Invalid Bug description: Anyone can confirm the atlantic kernel driver is not working with bionic 4.15.0-20-generic? The only thing I changed is installing kernel and modules 4.15.0-13-generic to get it working with the same packages and software. ethtool gives me this info: # ethtool diff 4.15.0-13-generic -> 4.15.0-20-generic 19c19 < Speed: 1Mb/s --- > Speed: Unknown! 26c26 < Link detected: yes --- > Link detected: no # ethtool -d diff 4.15.0-13-generic -> 4.15.0-20-generic 4,12c4,12 < 0x0010: 00 00 00 00 00 c0 64 c8 07 00 00 00 00 04 00 80 < 0x0020: 00 00 00 00 ff 03 00 00 08 00 00 00 04 00 00 00 < 0x0030: 00 00 00 00 00 80 0c d9 07 00 00 00 00 04 00 80 < 0x0040: 00 00 00 00 ff 03 00 00 08 00 00 00 04 00 00 00 < 0x0050: 00 00 00 00 00 40 68 c8 07 00 00 00 00 04 00 80 < 0x0060: 00 00 00 00 ff 03 00 00 08 00 00 00 04 00 00 00 < 0x0070: 00 00 00 00 00 80 c6 cc 07 00 00 00 00 04 00 80 < 0x0080: 00 00 00 00 ff 03 00 00 08 00 00 00 04 00 00 00 < 0x0090: 00 00 00 00 00 00 7e c8 07 00 00 00 00 10 00 80 --- > 0x0010: 00 00 00 00 00 c0 ae fc 07 00 00 00 00 04 00 80 > 0x0020: 00 00 00 00 ff 03 00 00 0b 00 00 00 04 00 00 00 > 0x0030: 00 00 00 00 00 00 b6 fc 07 00 00 00 00 04 00 80 > 0x0040: 00 00 00 00 ff 03 00 00 0b 00 00 00 04 00 00 00 > 0x0050: 00 00 00 00 00 40 b6 fc 07 00 00 00 00 04 00 80 > 0x0060: 00 00 00 00 ff 03 00 00 0b 00 00 00 04 00 00 00 > 0x0070: 00 00 00 00 00 00 be fc 07 00 00 00 00 04 00 80 > 0x0080: 00 00 00 00 ff 03 00 00 0b 00 00 00 04 00 00 00 > 0x0090: 00 00 00 00 00 00 af fc 07 00 00 00 00 10 00 80 14c14 < 0x00b0: 00 00 00 00 00 00 00 00 00 00 33 dc 07 00 00 00 --- > 0x00b0: 00 00 00 00 00 00 00 00 00 00 b3 fc 07 00 00 00 16c16 < 0x00d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 86 d6 --- > 0x00d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b7 fc 19c19 < 0x0100: 00 00 2b dd 07 00 00 00 00 10 00 80 00 00 00 00 --- > 0x0100: 00 00 bb fc 07 00 00 00 00 10 00 80 00 00 00 00 24c24 < 0x0150: 02 00 01 00 0e 5a de d2 00 be b0 1f 00 00 00 00 --- > 0x0150: 02 00 00 00 00 00 00 00 00 be b0 1f 00 00 00 00 Thanks. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-04 (22 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=ZFS=tank/root ro root=ZFS=tank/root boot=zfs zfs.zfs_arc_max=19327352832 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/14/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.20 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: C226M WS dmi.board.vendor: ASRockRack dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd11/14/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRockRack:rnC226MWS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be
[Kernel-packages] [Bug 1720930] Re: wlp3s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)
** Description changed: - When running artful on a new Zenbook Pro (uses Intel Wireless 8265), I - get a hung shutdown with the message "wlp3s0: failed to remove key (1, - ff:ff:ff:ff:ff:ff) from hardware (-22)". The kernel is also trying to - load firmware versions that do not exist on the system i.e. versions 33 - then 32 of the firmware. It then seems to load version 31 of the - firmware. Wireless features seem to work normally. The issues are just - at shutdown time. + ===SRU Justification=== + [Impact] + Message "wlp3s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from + hardware (-22)" showed when the system shutdown. + + [Test] + Users confirmed the patch fixes their issue. + + [Regression Potential] + Low. It's in mainline Linux, limited to iwlwifi, trivial change. + + Sara Sharon (1): + iwlwifi: mvm: fix "failed to remove key" message + + ==Original Bug Report=== + When running artful on a new Zenbook Pro (uses Intel Wireless 8265), I get a hung shutdown with the message "wlp3s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)". The kernel is also trying to load firmware versions that do not exist on the system i.e. versions 33 then 32 of the firmware. It then seems to load version 31 of the firmware. Wireless features seem to work normally. The issues are just at shutdown time. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: dylan 1621 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: dylan 1621 F pulseaudio CurrentDesktop: GNOME Date: Tue Oct 3 06:12:13 2017 HibernationDevice: RESUME=UUID=2b6908b4-d463-4170-9be5-556145c71a0e InstallationDate: Installed on 2017-10-02 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 003: ID 8087:0a2b Intel Corp. - Bus 001 Device 002: ID 13d3:5755 IMC Networks - Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. - Bus 001 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 003: ID 8087:0a2b Intel Corp. + Bus 001 Device 002: ID 13d3:5755 IMC Networks + Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX550VE ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic root=UUID=aa3dfd29-caf8-4882-906e-1b31b672d2c2 ro quiet splash threadirqs acpi_osi=! acpi_osi=Linux acpi_backlight=native vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-4.13.0-12-generic N/A - linux-backports-modules-4.13.0-12-generic N/A - linux-firmware 1.168 + linux-restricted-modules-4.13.0-12-generic N/A + linux-backports-modules-4.13.0-12-generic N/A + linux-firmware 1.168 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550VE.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX550VE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX550VE.300:bd06/05/2017:svnASUSTeKCOMPUTERINC.:pnUX550VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX550VE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720930 Title: wlp3s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22) Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in plymouth package in Ubuntu: Invalid Bug description: ===SRU Justification=== [Impact] Message "wlp3s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)" showed when the system shutdown. [Test] Users confirmed the patch fixes their issue. [Regression Potential] Low. It's in mainline Linux, limited to iwlwifi, trivial change. Sara Sharon (1): iwlwifi: mvm: fix "failed to remove key" message ==Original Bug Report=== When running artful on a new Zenbook Pro (uses Intel Wireless
[Kernel-packages] [Bug 1773940] [NEW] Enable AMD PCIe MP2 for AMDI0011
Public bug reported: ===SRU Justification=== [Impact] Touchpad doesn't work on Latitude 5495. [Test] I can confirm the driver from AMD works. All issues found by us should be fixed. [Fix] The touchpad connects to AMDI0011, which doesn't have any driver until now. I'll backport the patch to A/B/C once it's in mainline and gets thoroughly tested. [Regression Potential] Low. It's a new driver, shouldn't affect any other device. ** Affects: linux-oem (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773940 Title: Enable AMD PCIe MP2 for AMDI0011 Status in linux-oem package in Ubuntu: New Bug description: ===SRU Justification=== [Impact] Touchpad doesn't work on Latitude 5495. [Test] I can confirm the driver from AMD works. All issues found by us should be fixed. [Fix] The touchpad connects to AMDI0011, which doesn't have any driver until now. I'll backport the patch to A/B/C once it's in mainline and gets thoroughly tested. [Regression Potential] Low. It's a new driver, shouldn't affect any other device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem/+bug/1773940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704799] Re: iwlwifi: 8260: missing iwlwifi-8000C-{22..30}.ucode firmware
The problem persists
kernel: iwlwifi :02:00.0: enabling device ( -> 0002)
kernel: iwlwifi :02:00.0: firmware: failed to load iwlwifi-8000C-26.ucode
(-2)
kernel: iwlwifi :02:00.0: Direct firmware load for iwlwifi-8000C-26.ucode
failed with error -2
kernel: iwlwifi :02:00.0: firmware: failed to load iwlwifi-8000C-25.ucode
(-2)
kernel: iwlwifi :02:00.0: Direct firmware load for iwlwifi-8000C-25.ucode
failed with error -2
kernel: iwlwifi :02:00.0: firmware: failed to load iwlwifi-8000C-24.ucode
(-2)
kernel: iwlwifi :02:00.0: Direct firmware load for iwlwifi-8000C-24.ucode
failed with error -2
kernel: iwlwifi :02:00.0: firmware: failed to load iwlwifi-8000C-23.ucode
(-2)
kernel: iwlwifi :02:00.0: Direct firmware load for iwlwifi-8000C-23.ucode
failed with error -2
kernel: iwlwifi :02:00.0: firmware: direct-loading firmware
iwlwifi-8000C-22.ucode
kernel: iwlwifi :02:00.0: loaded firmware version 22.361476.0 op_mode iwlmvm
kernel: iwlwifi :02:00.0: Detected Intel(R) Dual Band Wireless AC 8260,
REV=0x208
kernel: iwlwifi :02:00.0: L1 Enabled - LTR Enabled
kernel: iwlwifi :02:00.0: L1 Enabled - LTR Enabled
kernel: iwlwifi :02:00.0 wlp2s0: renamed from wlan0
sensors[826]: iwlwifi-virtual-0
NetworkManager[821]: [1527579231.8894] rfkill1: found WiFi radio
killswitch (at
/sys/devices/pci:00/:00:1c.3/:02:00.0/ieee80211/phy0/rfkill1)
(driver iwlwifi)
kernel: iwlwifi :02:00.0: L1 Enabled - LTR Enabled
kernel: iwlwifi :02:00.0: L1 Enabled - LTR Enabled
kernel: iwlwifi :02:00.0: L1 Enabled - LTR Enabled
kernel: iwlwifi :02:00.0: L1 Enabled - LTR Enabled
kernel: iwlwifi :02:00.0: L1 Enabled - LTR Enabled
kernel: iwlwifi :02:00.0: L1 Enabled - LTR Enabled
kernel: iwlwifi :02:00.0: L1 Enabled - LTR Enabled
kernel: iwlwifi :02:00.0: L1 Enabled - LTR Enabled
--
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/1704799
Title:
iwlwifi: 8260: missing iwlwifi-8000C-{22..30}.ucode firmware
Status in linux-firmware package in Ubuntu:
Incomplete
Bug description:
Filed a bug at https://bugzilla.kernel.org/show_bug.cgi?id=196395 but
filing it also here as suggested.
Using amd64 version from http://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.12.2/ in Xenial 16.04.2 LTS based Linux Mint 18.2.
Checking firmware files:
$ ls /lib/firmware/ | grep 8000C
iwlwifi-8000C-13.ucode
iwlwifi-8000C-16.ucode
iwlwifi-8000C-21.ucode
Missing modules that were required according logging output below:
iwlwifi-8000C-22.ucode
iwlwifi-8000C-23.ucode
iwlwifi-8000C-24.ucode
iwlwifi-8000C-25.ucode
iwlwifi-8000C-26.ucode
iwlwifi-8000C-27.ucode
iwlwifi-8000C-28.ucode
iwlwifi-8000C-29.ucode
iwlwifi-8000C-30.ucode
$ lspci | grep Wireless
04:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)
Initially following error output can be found in appropriate logs:
$ dmesg | grep iwlwifi
[ 10.011090] iwlwifi :04:00.0: Direct firmware load for
iwlwifi-8000C-30.ucode failed with error -2
[ 10.011238] iwlwifi :04:00.0: Direct firmware load for
iwlwifi-8000C-29.ucode failed with error -2
[ 10.012734] iwlwifi :04:00.0: Direct firmware load for
iwlwifi-8000C-28.ucode failed with error -2
[ 10.012747] iwlwifi :04:00.0: Direct firmware load for
iwlwifi-8000C-27.ucode failed with error -2
[ 10.012756] iwlwifi :04:00.0: Direct firmware load for
iwlwifi-8000C-26.ucode failed with error -2
[ 10.012764] iwlwifi :04:00.0: Direct firmware load for
iwlwifi-8000C-25.ucode failed with error -2
[ 10.012772] iwlwifi :04:00.0: Direct firmware load for
iwlwifi-8000C-24.ucode failed with error -2
[ 10.014057] iwlwifi :04:00.0: Direct firmware load for
iwlwifi-8000C-23.ucode failed with error -2
[ 10.014071] iwlwifi :04:00.0: Direct firmware load for
iwlwifi-8000C-22.ucode failed with error -2
[ 10.014073] iwlwifi :04:00.0: no suitable firmware found!
[ 10.014075] iwlwifi :04:00.0: minimum version required:
iwlwifi-8000C-22
[ 10.014077] iwlwifi :04:00.0: maximum version supported:
iwlwifi-8000C-30
[ 10.014078] iwlwifi :04:00.0: check
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
$ journalctl -b grep iwlwifi
July 17 01:29:22 host kernel: iwlwifi :04:00.0: Direct firmware load for
iwlwifi-8000C-30.ucode failed with error -2
July 17 01:29:22 host kernel: iwlwifi :04:00.0: Direct firmware load for
iwlwifi-8000C-29.ucode failed with error -2
July 17 01:29:22 host kernel: iwlwifi :04:00.0: Direct firmware load for
iwlwifi-8000C-28.ucode failed with error -2
July 17 01:29:22 host kernel: iwlwifi :04:00.0: Direct firmware load for
iwlwifi-8000C-27.ucode failed with error -2
July 17 01:29:22 host kernel: iwlwifi
[Kernel-packages] [Bug 1773940] Re: Enable AMD PCIe MP2 for AMDI0011
** Tags added: originate-from-1734612 somerville -- 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/1773940 Title: Enable AMD PCIe MP2 for AMDI0011 Status in HWE Next: New Status in linux-oem package in Ubuntu: New Bug description: ===SRU Justification=== [Impact] Touchpad doesn't work on Latitude 5495. [Test] I can confirm the driver from AMD works. All issues found by us should be fixed. [Fix] The touchpad connects to AMDI0011, which doesn't have any driver until now. I'll backport the patch to A/B/C once it's in mainline and gets thoroughly tested. [Regression Potential] Low. It's a new driver, shouldn't affect any other device. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1773940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757402] Comment bridged from LTC Bugzilla
--- Comment From vipar...@in.ibm.com 2018-05-29 05:24 EDT--- (In reply to comment #122) > This has been committed to Bionic, as part of another bug. > > However, it looks like this would affect Artful as well. Would you be able > to confirm and test a patched kernel for Artful? > > Thanks. > Cascardo. Hello Canonical, IBM won't be able to test fix for Artful i.e. 17.10 as its no more being used and LTS one is only being used. This fix is already released and verified for Bionic (18.04) so i think we can go ahead and close this bug now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757402 Title: Ubuntu18.04:pKVM - Host in hung state and out of network after few hours of stress run on all guests Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Incomplete Status in linux source package in Bionic: Fix Released Bug description: == Comment: #0 - INDIRA P. JOGA - 2018-02-11 12:37:25 == Problem Description: === After few hours of run system is in hung state with, "rcu_sched detected stalls on CPUs/tasks" messages on the host IPMI console and host is out of network . Steps to re-create: == > Installed Ubuntu1804 on boslcp3 host. root@boslcp3:~# uname -a Linux boslcp3 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:15:55 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@boslcp3:~# uname -r 4.13.0-25-generic > root@boslcp3:~# ppc64_cpu --smt SMT is off > Hugepage set up echo 8500 > /proc/sys/vm/nr_hugepages > Defined the guests from host machine IdName State 2 boslcp3g2 shut off 3 boslcp3g3 shut off 4 boslcp3g4 shut off 6 boslcp3g1 shut off 7 boslcp3g5 shut off > Started and installed ubuntu1804 daily build on all the guests. root@boslcp3:~# virsh list --all IdName State 2 boslcp3g2 running 3 boslcp3g3 running 4 boslcp3g4 running 6 boslcp3g1 running 7 boslcp3g5 running > Started regression run (IO_BASE_TCP_NFS) tests on all 5 guests. NOTE: Removed madvise test case from BASE focus areas. > Run went fine for few hours on all guests. > After few hours of run ,Host system is in hung state and host console dumps CPU stall messages as below [SOL Session operational. Use ~? for help] [250867.133429] INFO: rcu_sched detected stalls on CPUs/tasks: [250867.133499] (detected by 86, t=62711832 jiffies, g=497, c=496, q=31987857) [250867.133554] All QSes seen, last rcu_sched kthread activity 62711828 (4357609080-4294897252), jiffies_till_next_fqs=1, root ->qsmask 0x0 [250867.133690] rcu_sched kthread starved for 62711828 jiffies! g497 c496 f0x2 RCU_GP_WAIT_FQS(3) ->state=0x100 [250931.133433] INFO: rcu_sched detected stalls on CPUs/tasks: [250931.133494] (detected by 3, t=62727832 jiffies, g=497, c=496, q=31995625) [250931.133572] All QSes seen, last rcu_sched kthread activity 62727828 (4357625080-4294897252), jiffies_till_next_fqs=1, root ->qsmask 0x0 [250931.133741] rcu_sched kthread starved for 62727828 jiffies! g497 c496 f0x2 RCU_GP_WAIT_FQS(3) ->state=0x100 [250995.133432] INFO: rcu_sched detected stalls on CPUs/tasks: [250995.133480] (detected by 54, t=62743832 jiffies, g=497, c=496, q=32004479) [250995.133526] All QSes seen, last rcu_sched kthread activity 62743828 (4357641080-4294897252), jiffies_till_next_fqs=1, root ->qsmask 0x0 [250995.133645] rcu_sched kthread starved for 62743828 jiffies! g497 c496 f0x2 RCU_GP_WAIT_FQS(3) ->state=0x100 > Not able to get the prompt > Ping /shh to boslcp3 also fails [ipjoga@kte ~]$ ping boslcp3 PING boslcp3.isst.aus.stglabs.ibm.com (10.33.0.157) 56(84) bytes of data. From kte.isst.aus.stglabs.ibm.com (10.33.11.31) icmp_seq=1 Destination Host Unreachable From kte.isst.aus.stglabs.ibm.com (10.33.11.31) icmp_seq=2 Destination Host Unreachable From kte.isst.aus.stglabs.ibm.com (10.33.11.31) icmp_seq=3 Destination Host Unreachable [ipjoga@kte ~]$ ssh root@boslcp3 ssh: connect to host boslcp3 port 22: No route to host > boslcp3 is not reachable > Attached boslcp3 host console logs == Comment: #1 - INDIRA P. JOGA - 2018-02-11 12:39:29 == Added Host console logs == Comment: #24 - VIPIN K. PARASHAR - 2018-02-16 05:46:13 == From Linux logs === [72072.290071] watchdog: BUG: soft lockup - CPU#132 stuck for 22s! [CPU 1
[Kernel-packages] [Bug 1766573] Re: linux < 4.11: unable to use netfilter logging from non-init namespaces
** Tags removed: verification-needed-xenial ** Tags added: verification-done-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/1766573 Title: linux < 4.11: unable to use netfilter logging from non-init namespaces Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: Was disabled by the following patch (linux 3.10): https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=69b34fb996b2 netfilter: xt_LOG: add net namespace support for xt_LOG And fixed in linux 4.11: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2851940ffee3 netfilter: allow logging from non-init namespaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766573/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768430] Re: aio-dio-subblock-eof-read test in aio_dio_bugs failed on s390x
** Also affects: linux (Ubuntu Artful) 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/1768430 Title: aio-dio-subblock-eof-read test in aio_dio_bugs failed on s390x Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Artful: New Status in linux source package in Bionic: New Bug description: It can be reproduced on zVM, zKVM and Ubuntu on LPAR This should not be considered as a regression, the test suite stopped on the first test in this test suite before. Steps: 1. git clone --depth=1 https://github.com/autotest/autotest-client-tests.git 2. make -C autotest-client-tests/aio_dio_bugs/src 3. sudo ./autotest-client-tests/aio_dio_bugs/src/aio-dio-subblock-eof-read eoftest Running 'apt-get install --yes --force-yes build-essential gcc' Reading package lists... Building dependency tree... Reading state information... build-essential is already the newest version (12.1ubuntu2). gcc is already the newest version (4:5.3.1-1ubuntu1). The following packages were automatically installed and are no longer required: linux-headers-4.4.0-121 linux-headers-4.4.0-121-generic linux-image-4.4.0-121-generic linux-image-extra-4.4.0-121-generic Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Running 'which gcc' /usr/bin/gcc Dependency libaio successfully built Running 'LD_LIBRARY_PATH=/home/ubuntu/autotest/client/deps/libaio/lib/ /home/ubuntu/autotest/client/tmp/aio_dio_bugs/src/aio-dio-subblock-eof-read eoftest' buffered read returned -1, should be 300 Exception escaping from test: Traceback (most recent call last): File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function return func(*args, **dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute postprocess_profiled_run, args, dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once self.run_once(*args, **dargs) File "/home/ubuntu/autotest/client/tests/aio_dio_bugs/aio_dio_bugs.py", line 42, in run_once utils.system(var_ld_path + ' ' + cmd) File "/home/ubuntu/autotest/client/shared/utils.py", line 1232, in system verbose=verbose).exit_status File "/home/ubuntu/autotest/client/shared/utils.py", line 918, in run "Command returned non-zero exit status") CmdError: Command failed, rc=1, Command returned non-zero exit status * Command: LD_LIBRARY_PATH=/home/ubuntu/autotest/client/deps/libaio/lib/ /home/ubuntu/autotest/client/tmp/aio_dio_bugs/src/aio-dio-subblock-eof- read eoftest Exit status: 1 Duration: 0.00215792655945 stdout: buffered read returned -1, should be 300 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-123-generic 4.4.0-123.147 ProcVersionSignature: Ubuntu 4.4.0-123.147-generic 4.4.128 Uname: Linux 4.4.0-123-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.16 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: Date: Wed May 2 02:21:12 2018 HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-123-generic N/A linux-backports-modules-4.4.0-123-generic N/A linux-firmware 1.157.17 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/+source/linux/+bug/1768430/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-pa
[Kernel-packages] [Bug 1246981] Re: Bluetooth mouse fails to re-connect after sleep.
Thanks!!! -- 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/1246981 Title: Bluetooth mouse fails to re-connect after sleep. Status in bluez package in Ubuntu: Confirmed Bug description: This exact harware was working faultlessly in 13.04. Since re- installing at 13.10 the mouse consistently failes to reconnect after the device either hybernates or ever goes to screen saver sleep. I have to remove the dive and re-add it each time (which works well). There are other issues with the bluetooth stack as well in that I have not found any way to use bluetooth tethering to my mobile which again worked well and was easy to configure in 13.04 Peter. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Fri Nov 1 16:44:37 2013 InstallationDate: Installed on 2013-10-19 (13 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Dell Inc. Latitude E6530 MarkForUpload: True PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=8283de78-9264-42bf-a8b4-25643fa1475f ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 07Y85M dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 20:16:D8:9C:38:E5 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:1817731 acl:117432 sco:0 events:5271 errors:0 TX bytes:37955 acl:131 sco:0 commands:5096 errors:0 syslog: Nov 1 14:50:19 pnunn-Latitude-E6530 bluetoothd[1015]: Discovery session 0x7f6489f7b450 with :1.582 activated Nov 1 14:50:25 pnunn-Latitude-E6530 bluetoothd[1015]: Unknown command complete for opcode 37 Nov 1 14:50:28 pnunn-Latitude-E6530 bluetoothd[1015]: Stopping discovery Nov 1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211132] input: Microsoft Bluetooth Notebook Mouse 5000 as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input29 Nov 1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211646] hid-generic 0005:045E:0700.000C: input,hidraw3: BLUETOOTH HID v1.00 Mouse [Microsoft Bluetooth Notebook Mouse 5000] on 20:16:d8:9c:38:e5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1246981/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773950] [NEW] package linux-firmware 1.173.1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Public bug reported: i have no cloue ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 AptOrdering: linux-firmware:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue May 29 01:35:08 2018 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-04-30 (28 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: linux-firmware Title: package linux-firmware 1.173.1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- 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/1773950 Title: package linux-firmware 1.173.1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in linux-firmware package in Ubuntu: New Bug description: i have no cloue ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 AptOrdering: linux-firmware:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue May 29 01:35:08 2018 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-04-30 (28 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: linux-firmware Title: package linux-firmware 1.173.1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1773950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773950] Re: package linux-firmware 1.173.1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- 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/1773950 Title: package linux-firmware 1.173.1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in linux-firmware package in Ubuntu: New Bug description: i have no cloue ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 AptOrdering: linux-firmware:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue May 29 01:35:08 2018 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-04-30 (28 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: linux-firmware Title: package linux-firmware 1.173.1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1773950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773964] [NEW] IPL: ppc64_cpu --frequency hang with INFO: rcu_sched detected stalls on CPUs/tasks on w34 and wsbmc016 with 920.1714.20170330n
You have been subscribed to a public bug: == Comment: #0 - Application Cdeadmin <> - 2018-05-22 09:36:12 == == Comment: #1 - Application Cdeadmin <> - 2018-05-22 09:36:14 == State: Open by: swanman on 22 May 2018 09:17:33 Both w34 and wsbmc016 are stopped on this failure, where we get hung up on the following FFDC gathering step in the OS: #(CDT) 2018/05/22 05:07:19.398218 - 0.211662 - Issuing: OS Execute Command ppc64_cpu --frequency ignore_err=1 #(CDT) 2018/05/22 05:07:19.437808 - 0.024108 - Issuing: ppc64_cpu --frequency , and the last console output shows: # tail -200 /var/log/obmc-console.log s this GP) idle=82a/140/0 softirq=2689/2689 fqs=241989 [13668.719850] (detected by 3, t=3075620 jiffies, g=30289, c=30288, q=796881) [13732.630691] INFO: rcu_sched detected stalls on CPUs/tasks: [13732.630727] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=242996 [13732.630757] (detected by 3, t=3091597 jiffies, g=30289, c=30288, q=799822) [13795.649568] INFO: rcu_sched detected stalls on CPUs/tasks: [13795.649597] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=243942 [13795.649631] (detected by 7, t=3107351 jiffies, g=30289, c=30288, q=802916) [13860.140483] INFO: rcu_sched detected stalls on CPUs/tasks: [13860.140516] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=244940 [13860.140557] (detected by 3, t=3123473 jiffies, g=30289, c=30288, q=806646) [13924.731404] INFO: rcu_sched detected stalls on CPUs/tasks: [13924.731438] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=245874 [13924.731484] (detected by 3, t=3139620 jiffies, g=30289, c=30288, q=809909) [13988.642290] INFO: rcu_sched detected stalls on CPUs/tasks: [13988.642321] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=246892 [13988.642362] (detected by 3, t=3155596 jiffies, g=30289, c=30288, q=813048) [14052.661176] INFO: rcu_sched detected stalls on CPUs/tasks: [14052.661211] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=247857 [14052.661266] (detected by 3, t=3171600 jiffies, g=30289, c=30288, q=816185) [14115.680024] INFO: rcu_sched detected stalls on CPUs/tasks: [14115.680051] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=248819 [14115.680085] (detected by 4, t=3187355 jiffies, g=30289, c=30288, q=819190) [14180.154911] INFO: rcu_sched detected stalls on CPUs/tasks: [14180.154945] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=249833 [14180.154986] (detected by 132, t=3203473 jiffies, g=30289, c=30288, q=822138) [14244.968067]I F: Ne talls onCPUs/tasks [14244669838] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=2[14244.669944] (detected by 3, t=3219600 jiffies, g=30289, c=30288, q=825384) [14308.748680] Id detected stalls on CPUs/tasks: [14308.748719] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=251755 [14308.748755] (detected by 3, t=3235620 jiffies, g=30289, c=30288, q=828445) [14333.081775] Watchdog CPU:132 Hard LOCKUP [14344.750295] Watchdog CPU:132 became unstuck [14372.735558] INFO: rcu_sched detected stalls on CPUs/tasks: [14372.735587] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=252722 [14372.735611] (detected by 6, t=3251616 jiffies, g=30289, c=30288, q=831375) [14435.910193] INFO: rcu_sched detected stalls on CPUs/tasks: [14435.910219] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=253675 [14435.910253] (detected by 3, t=3267409 jiffies, g=30289, c=30288, q=834375) [14500.167195] INFO: rcu_sched detected stalls on CPUs/tasks: [14500.167230] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=254601 [14500.167273] (detected by 134, t=3283473 jiffies, g=30289, c=30288, q=837600) [14564.664395] INFO: rcu_sched detected stalls on CPUs/tasks: [14564.664427] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=255493 [14564.664470] (detected by 3, t=3299596 jiffies, g=30289, c=30288, q=840539) [14628.665755] INFO: rcu_sched detected stalls on CPUs/tasks: [14628.665790] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=256471 [14628.665824] (detected by 3, t=3315596 jiffies, g=30289, c=30288, q=843505) [14692.759268] INFO: rcu_sched detected stalls on CPUs/tasks: [14692.759299] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=257372 [14692.759330] (detected by 3, t=3331620 jiffies, g=30289, c=30288, q=846522) [14755.916887] INFO: rcu_sched detected stalls on CPUs/tasks: [14755.916918] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=258248 [14755.916943] (detected by 3, t=3347409 jiffies, g=30289, c=30288, q=849740) [14820.17
[Kernel-packages] [Bug 1773964] Logs from w34
Default Comment by Bridge ** Attachment added: "Logs from w34" https://bugs.launchpad.net/bugs/1773964/+attachment/5146007/+files/w34_dmesg ** Changed in: ubuntu Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773964 Title: IPL: ppc64_cpu --frequency hang with INFO: rcu_sched detected stalls on CPUs/tasks on w34 and wsbmc016 with 920.1714.20170330n Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Application Cdeadmin <> - 2018-05-22 09:36:12 == == Comment: #1 - Application Cdeadmin <> - 2018-05-22 09:36:14 == State: Open by: swanman on 22 May 2018 09:17:33 Both w34 and wsbmc016 are stopped on this failure, where we get hung up on the following FFDC gathering step in the OS: #(CDT) 2018/05/22 05:07:19.398218 - 0.211662 - Issuing: OS Execute Command ppc64_cpu --frequency ignore_err=1 #(CDT) 2018/05/22 05:07:19.437808 - 0.024108 - Issuing: ppc64_cpu --frequency , and the last console output shows: # tail -200 /var/log/obmc-console.log s this GP) idle=82a/140/0 softirq=2689/2689 fqs=241989 [13668.719850] (detected by 3, t=3075620 jiffies, g=30289, c=30288, q=796881) [13732.630691] INFO: rcu_sched detected stalls on CPUs/tasks: [13732.630727] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=242996 [13732.630757] (detected by 3, t=3091597 jiffies, g=30289, c=30288, q=799822) [13795.649568] INFO: rcu_sched detected stalls on CPUs/tasks: [13795.649597] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=243942 [13795.649631] (detected by 7, t=3107351 jiffies, g=30289, c=30288, q=802916) [13860.140483] INFO: rcu_sched detected stalls on CPUs/tasks: [13860.140516] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=244940 [13860.140557] (detected by 3, t=3123473 jiffies, g=30289, c=30288, q=806646) [13924.731404] INFO: rcu_sched detected stalls on CPUs/tasks: [13924.731438] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=245874 [13924.731484] (detected by 3, t=3139620 jiffies, g=30289, c=30288, q=809909) [13988.642290] INFO: rcu_sched detected stalls on CPUs/tasks: [13988.642321] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=246892 [13988.642362] (detected by 3, t=3155596 jiffies, g=30289, c=30288, q=813048) [14052.661176] INFO: rcu_sched detected stalls on CPUs/tasks: [14052.661211] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=247857 [14052.661266] (detected by 3, t=3171600 jiffies, g=30289, c=30288, q=816185) [14115.680024] INFO: rcu_sched detected stalls on CPUs/tasks: [14115.680051] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=248819 [14115.680085] (detected by 4, t=3187355 jiffies, g=30289, c=30288, q=819190) [14180.154911] INFO: rcu_sched detected stalls on CPUs/tasks: [14180.154945] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=249833 [14180.154986] (detected by 132, t=3203473 jiffies, g=30289, c=30288, q=822138) [14244.968067]I F: Ne talls onCPUs/tasks [14244669838] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=2[14244.669944] (detected by 3, t=3219600 jiffies, g=30289, c=30288, q=825384) [14308.748680] Id detected stalls on CPUs/tasks: [14308.748719] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=251755 [14308.748755] (detected by 3, t=3235620 jiffies, g=30289, c=30288, q=828445) [14333.081775] Watchdog CPU:132 Hard LOCKUP [14344.750295] Watchdog CPU:132 became unstuck [14372.735558] INFO: rcu_sched detected stalls on CPUs/tasks: [14372.735587] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=252722 [14372.735611] (detected by 6, t=3251616 jiffies, g=30289, c=30288, q=831375) [14435.910193] INFO: rcu_sched detected stalls on CPUs/tasks: [14435.910219] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=253675 [14435.910253] (detected by 3, t=3267409 jiffies, g=30289, c=30288, q=834375) [14500.167195] INFO: rcu_sched detected stalls on CPUs/tasks: [14500.167230] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=254601 [14500.167273] (detected by 134, t=3283473 jiffies, g=30289, c=30288, q=837600) [14564.664395] INFO: rcu_sched detected stalls on CPUs/tasks: [14564.664427] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=255493 [14564.664470] (detected by 3, t=3299596 jiffies, g=30289, c=30288, q=840539) [1462
[Kernel-packages] [Bug 1773964] Re: IPL: ppc64_cpu --frequency hang with INFO: rcu_sched detected stalls on CPUs/tasks on w34 and wsbmc016 with 920.1714.20170330n
** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Status: New => Triaged ** Changed in: ubuntu-power-systems Importance: Undecided => Critical ** Changed in: ubuntu-power-systems Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Tags added: triage-g -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773964 Title: IPL: ppc64_cpu --frequency hang with INFO: rcu_sched detected stalls on CPUs/tasks on w34 and wsbmc016 with 920.1714.20170330n Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Application Cdeadmin <> - 2018-05-22 09:36:12 == == Comment: #1 - Application Cdeadmin <> - 2018-05-22 09:36:14 == State: Open by: swanman on 22 May 2018 09:17:33 Both w34 and wsbmc016 are stopped on this failure, where we get hung up on the following FFDC gathering step in the OS: #(CDT) 2018/05/22 05:07:19.398218 - 0.211662 - Issuing: OS Execute Command ppc64_cpu --frequency ignore_err=1 #(CDT) 2018/05/22 05:07:19.437808 - 0.024108 - Issuing: ppc64_cpu --frequency , and the last console output shows: # tail -200 /var/log/obmc-console.log s this GP) idle=82a/140/0 softirq=2689/2689 fqs=241989 [13668.719850] (detected by 3, t=3075620 jiffies, g=30289, c=30288, q=796881) [13732.630691] INFO: rcu_sched detected stalls on CPUs/tasks: [13732.630727] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=242996 [13732.630757] (detected by 3, t=3091597 jiffies, g=30289, c=30288, q=799822) [13795.649568] INFO: rcu_sched detected stalls on CPUs/tasks: [13795.649597] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=243942 [13795.649631] (detected by 7, t=3107351 jiffies, g=30289, c=30288, q=802916) [13860.140483] INFO: rcu_sched detected stalls on CPUs/tasks: [13860.140516] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=244940 [13860.140557] (detected by 3, t=3123473 jiffies, g=30289, c=30288, q=806646) [13924.731404] INFO: rcu_sched detected stalls on CPUs/tasks: [13924.731438] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=245874 [13924.731484] (detected by 3, t=3139620 jiffies, g=30289, c=30288, q=809909) [13988.642290] INFO: rcu_sched detected stalls on CPUs/tasks: [13988.642321] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=246892 [13988.642362] (detected by 3, t=3155596 jiffies, g=30289, c=30288, q=813048) [14052.661176] INFO: rcu_sched detected stalls on CPUs/tasks: [14052.661211] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=247857 [14052.661266] (detected by 3, t=3171600 jiffies, g=30289, c=30288, q=816185) [14115.680024] INFO: rcu_sched detected stalls on CPUs/tasks: [14115.680051] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=248819 [14115.680085] (detected by 4, t=3187355 jiffies, g=30289, c=30288, q=819190) [14180.154911] INFO: rcu_sched detected stalls on CPUs/tasks: [14180.154945] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=249833 [14180.154986] (detected by 132, t=3203473 jiffies, g=30289, c=30288, q=822138) [14244.968067]I F: Ne talls onCPUs/tasks [14244669838] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=2[14244.669944] (detected by 3, t=3219600 jiffies, g=30289, c=30288, q=825384) [14308.748680] Id detected stalls on CPUs/tasks: [14308.748719] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=251755 [14308.748755] (detected by 3, t=3235620 jiffies, g=30289, c=30288, q=828445) [14333.081775] Watchdog CPU:132 Hard LOCKUP [14344.750295] Watchdog CPU:132 became unstuck [14372.735558] INFO: rcu_sched detected stalls on CPUs/tasks: [14372.735587] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=252722 [14372.735611] (detected by 6, t=3251616 jiffies, g=30289, c=30288, q=831375) [14435.910193] INFO: rcu_sched detected stalls on CPUs/tasks: [14435.910219] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=253675 [14435.910253] (detected by 3, t=3267409 jiffies, g=30289, c=30288, q=834375) [14500.167195] INFO: rcu_sched detected stalls on CPUs/tasks: [14500.167230] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=2689/2689 fqs=254601 [14500.167273] (detected by 134, t=3283473 jiffies, g=30289, c=30288, q=837600) [14564.664395] INFO: rcu_sched detected stalls on CPUs/tasks: [14564.664427] 75-: (5904 ticks this GP) idle=82a/140/0 softirq=
[Kernel-packages] [Bug 1773912] Re: bluetoothd unable to establish connection after resume from suspend
*** This bug is a duplicate of bug 1759628 ***
https://bugs.launchpad.net/bugs/1759628
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bluez (Ubuntu)
Status: New => Confirmed
--
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/1773912
Title:
bluetoothd unable to establish connection after resume from suspend
Status in bluez package in Ubuntu:
Confirmed
Bug description:
Description: Ubuntu 18.04 LTS
Release:18.04
bluez:
Installed: 5.48-0ubuntu3
Candidate: 5.48-0ubuntu3
Version table:
*** 5.48-0ubuntu3 500
500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
3) What I expect to happen:
After resuming my Ubuntu from standby I expect my bluetooth daemon to connect
to my BT headset properly if I tell it to do so.
4) What actually happens:
After resuming I can click 'Connect as ADP Sink' in, for example, blueman, it
starts connecting, and aborts after a while.
When I restart the bluetoothd ('systemctl restart bluetoothd'), I can easily
connect my BT headset.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1773912/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759644] Re: [18.04] Regression: wired network does not work upon resume from suspend
I'm pretty sure this is a duplicate of #1752772 , right? Like Kai-Heng Feng mentioned above. If so, please mark as duplicate. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759644 Title: [18.04] Regression: wired network does not work upon resume from suspend Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: After upgrade to 18.04 (bionic) I've encountered the following regression: wired network connection does not work, when system is resumed from suspend. Reloading the kernel driver module seems to help: sudo modprobe -r r8169 sudo modprobe r8169 Could this be fixed structurally? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 28 20:08:20 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-01-06 (811 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IpRoute: default via 192.168.0.1 dev enp5s0 proto dhcp metric 100 169.254.0.0/16 dev enp5s0 scope link metric 1000 192.168.0.0/24 dev enp5s0 proto kernel scope link src 192.168.0.107 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to bionic on 2018-03-21 (6 days ago) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 7fa0c3a2-6ef0-37fd-9f9e-9029777aaf23 ethernet 1522260260 wo 28 mrt 2018 20:04:20 CEST yes 4294966297no /org/freedesktop/NetworkManager/Settings/3 yes enp5s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- dzente a899e56b-4048-43a8-bc38-9212d0af383b wifi 1493769143 wo 03 mei 2017 01:52:23 CEST yes 0 no /org/freedesktop/NetworkManager/Settings/1 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH enp5s0 ethernet connected/org/freedesktop/NetworkManager/Devices/4 Wired connection 1 7fa0c3a2-6ef0-37fd-9f9e-9029777aaf23 /org/freedesktop/NetworkManager/ActiveConnection/1 wlp4s0 wifi unavailable /org/freedesktop/NetworkManager/Devices/3 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/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 --- ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alexei 1673 F pulseaudio /dev/snd/controlC0: alexei 1673 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546 InstallationDate: Installed on 2016-01-06 (812 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-03-21 (7 days ago) UserGroup
[Kernel-packages] [Bug 1772956] Re: linux-oem: 4.13.0-1029.32 -proposed tracker
** Summary changed: - linux-oem: -proposed tracker + linux-oem: 4.13.0-1029.32 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Timo Aaltonen (tjaalton) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Timo Aaltonen (tjaalton) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Timo Aaltonen (tjaalton) -- 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/1772956 Title: linux-oem: 4.13.0-1029.32 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Xenial: 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-stable-master-bug: 1772951 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772956/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772970] Re: linux: 3.13.0-150.200 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing 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/1772970 Title: linux: 3.13.0-150.200 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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 upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: 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 backports: bug 1772971 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772970/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772963] Re: linux-aws: 4.4.0-1023.23 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete -- 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/1772963 Title: linux-aws: 4.4.0-1023.23 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: 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 upload-to-ppa series: New 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: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772960 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772963/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1751213] Re: kernel security test report that the lttng_probe_writeback module is tainted on Bionic s390x
This issue was only spotted on s390x, because the s390x instance won't get
re-deployed.
So the module inserted by the lttng test will stay there, and caught by this
security test.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1751213
Title:
kernel security test report that the lttng_probe_writeback module is
tainted on Bionic s390x
Status in lttng-modules:
New
Status in linux package in Ubuntu:
In Progress
Bug description:
This issue was only spotted on Bionic s390x instances.
FAIL: test_140_kernel_modules_not_tainted (__main__.KernelSecurityTest)
kernel modules are not marked with a taint flag (especially 'E' for
TAINT_UNSIGNED_MODULE)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 1727, in
test_140_kernel_modules_not_tainted
self.fail('Module \'%s\' is tainted: %s' % (fields[0], last_field))
AssertionError: Module 'lttng_probe_writeback' is tainted: (OE)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-10-generic 4.15.0-10.11
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-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.8-0ubuntu10
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: Fri Feb 23 07:43:00 2018
HibernationDevice: RESUME=UUID=caaee9b2-6bc1-4c8e-b26c-69038c092091
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': '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=c7d7bbcb-a039-4ead-abfe-7672dea0add4
crashkernel=196M
RelatedPackageVersions:
linux-restricted-modules-4.15.0-10-generic N/A
linux-backports-modules-4.15.0-10-generic N/A
linux-firmware 1.171
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/lttng-modules/+bug/1751213/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772951] Re: linux: 4.13.0-44.49 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing 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/1772951 Title: linux: 4.13.0-44.49 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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 upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Artful: 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 backports: bug 1772953 (linux-gcp), bug 1772956 (linux-oem), bug 1772957 (linux-hwe) derivatives: bug 1772952 (linux-raspi2) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772963] Re: linux-aws: 4.4.0-1023.23 -proposed tracker
4.4.0-1023.32 - aws Regression test CMPL, RTB. Issue to note in x86_64 (aws): libhugetlbfs - 1 failed (alloc-instantiate-race shared), bad config 3, only spotted on t2.small, passed on the rest ubuntu_kvm_unit_tests - test skipped, KVM not supported Skipped / blacklisted: * ubuntu_aufs_smoke_test * ubuntu_fan_smoke_test * ubuntu_kernel_selftests * ubuntu_loop_smoke_test * ubuntu_ltp * ubuntu_lttng_smoke_test * ubuntu_stress_smoke_test * ubuntu_sysdig_smoke_test * ubuntu_unionmount_overlayfs_suite * ubuntu_zfs_smoke_test * ubuntu_zram_smoke_test ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1772963 Title: linux-aws: 4.4.0-1023.23 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: 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 upload-to-ppa series: New 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: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772960 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772963/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1751213] Re: kernel security test report that the lttng_probe_writeback module is tainted on Bionic s390x
That makes sense. We need to force remove that module then.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1751213
Title:
kernel security test report that the lttng_probe_writeback module is
tainted on Bionic s390x
Status in lttng-modules:
New
Status in linux package in Ubuntu:
In Progress
Bug description:
This issue was only spotted on Bionic s390x instances.
FAIL: test_140_kernel_modules_not_tainted (__main__.KernelSecurityTest)
kernel modules are not marked with a taint flag (especially 'E' for
TAINT_UNSIGNED_MODULE)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 1727, in
test_140_kernel_modules_not_tainted
self.fail('Module \'%s\' is tainted: %s' % (fields[0], last_field))
AssertionError: Module 'lttng_probe_writeback' is tainted: (OE)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-10-generic 4.15.0-10.11
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-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.8-0ubuntu10
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: Fri Feb 23 07:43:00 2018
HibernationDevice: RESUME=UUID=caaee9b2-6bc1-4c8e-b26c-69038c092091
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': '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=c7d7bbcb-a039-4ead-abfe-7672dea0add4
crashkernel=196M
RelatedPackageVersions:
linux-restricted-modules-4.15.0-10-generic N/A
linux-backports-modules-4.15.0-10-generic N/A
linux-firmware 1.171
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/lttng-modules/+bug/1751213/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772931] Re: linux-aws: 4.15.0-1010.10 -proposed tracker
4.15.0-10010.10 - aws Regression test CMPL. Issue to note in x86_64 (aws): libhugetlbfs - failed to build on Bionic (bug 1707887) ubuntu_kvm_unit_tests - test skipped due to no KVM support ubuntu_ltp - test disabled ubuntu_lxc - lxc-tests package not available (bug 1758255) ubuntu_unionmount_overlayfs_suite - File unexpectedly on union layer (bug 1751243) Skipped / blacklisted: * ubuntu_seccomp * ubuntu_zram_smoke_test ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1772931 Title: linux-aws: 4.15.0-1010.10 -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: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772927 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772931/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
