[Kernel-packages] [Bug 1719795]
> Could you blacklist just hid-sensor-hub and see if you still see the > interrupt storm? Blacklisted hid-sensor-hub and get same result as with blacklisting i2c_hid - no interrupt storm. Power consumption is below 3 Watts per second in idle. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1719795 Title: Dell 7140 avarage power consumption in idle increased by 1.3-1.5 times due to events by INT3432 Status in Linux: Incomplete Status in linux package in Ubuntu: New Bug description: On Dell Venue 11 Pro 7140 average power consumption in idle increased by 1.3-1.5 times due to events coming from INT343A. According to powertop since Linux 4.10 INT3432:00 generate around two hundred events on average, in /sys/devices/pci:00/INT3432:00/i2c-6 there is two devices: INT343A and SMO91D0. AFAIK INT343A is rt286. With Linux 4.9.0-4.9.45, Linux 4.11.0-4.11.12 in idle there is around 100 wakeups per second in sum, battery discharge rate around 3-3.5 Watts per second. But with Linux 4.9.46-4.9.51, Linux 4.10.0-4.10.17, Linux 4.12.0rc1-4.13.3 - around 300 wakeups per second on average, due to events coming from INT3432:00. With Linux 4.13.3 battery discharge rate around 4.5 Watts per second. Probably some commit was backported to Linux 4.9 between .45 and .46 releases. I have no idea why issue is not reproducible on any Linux 4.11 release I tried. Sometimes INT3432 events rate fall from two hundred to one hundred for shorts period of time (for example I observe this right now on Linux 4.10.0 while removing/installing packages). Message like this sometimes appear in dmesg: [ 731.226730] i2c_hid i2c-SMO91D0:00: i2c_hid_get_input: incomplete report (53/13568) Complete dmesg with Linux 4.13.3 is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1719795/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1719795]
Created attachment 278485 /proc/interrupts content on Linux 4.18.6 normal boot with i2c_hid module blacklisted On boot with blacklisted i2c_hid there is 40-60 wakeups per second instead of 300+, /proc/interrupts content is attached. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1719795 Title: Dell 7140 avarage power consumption in idle increased by 1.3-1.5 times due to events by INT3432 Status in Linux: Incomplete Status in linux package in Ubuntu: New Bug description: On Dell Venue 11 Pro 7140 average power consumption in idle increased by 1.3-1.5 times due to events coming from INT343A. According to powertop since Linux 4.10 INT3432:00 generate around two hundred events on average, in /sys/devices/pci:00/INT3432:00/i2c-6 there is two devices: INT343A and SMO91D0. AFAIK INT343A is rt286. With Linux 4.9.0-4.9.45, Linux 4.11.0-4.11.12 in idle there is around 100 wakeups per second in sum, battery discharge rate around 3-3.5 Watts per second. But with Linux 4.9.46-4.9.51, Linux 4.10.0-4.10.17, Linux 4.12.0rc1-4.13.3 - around 300 wakeups per second on average, due to events coming from INT3432:00. With Linux 4.13.3 battery discharge rate around 4.5 Watts per second. Probably some commit was backported to Linux 4.9 between .45 and .46 releases. I have no idea why issue is not reproducible on any Linux 4.11 release I tried. Sometimes INT3432 events rate fall from two hundred to one hundred for shorts period of time (for example I observe this right now on Linux 4.10.0 while removing/installing packages). Message like this sometimes appear in dmesg: [ 731.226730] i2c_hid i2c-SMO91D0:00: i2c_hid_get_input: incomplete report (53/13568) Complete dmesg with Linux 4.13.3 is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1719795/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1719795]
OK, thanks. I kind of suspect that the sensor hub is the one generating those interrupts. Could you blacklist just hid-sensor-hub and see if you still see the interrupt storm? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1719795 Title: Dell 7140 avarage power consumption in idle increased by 1.3-1.5 times due to events by INT3432 Status in Linux: Incomplete Status in linux package in Ubuntu: New Bug description: On Dell Venue 11 Pro 7140 average power consumption in idle increased by 1.3-1.5 times due to events coming from INT343A. According to powertop since Linux 4.10 INT3432:00 generate around two hundred events on average, in /sys/devices/pci:00/INT3432:00/i2c-6 there is two devices: INT343A and SMO91D0. AFAIK INT343A is rt286. With Linux 4.9.0-4.9.45, Linux 4.11.0-4.11.12 in idle there is around 100 wakeups per second in sum, battery discharge rate around 3-3.5 Watts per second. But with Linux 4.9.46-4.9.51, Linux 4.10.0-4.10.17, Linux 4.12.0rc1-4.13.3 - around 300 wakeups per second on average, due to events coming from INT3432:00. With Linux 4.13.3 battery discharge rate around 4.5 Watts per second. Probably some commit was backported to Linux 4.9 between .45 and .46 releases. I have no idea why issue is not reproducible on any Linux 4.11 release I tried. Sometimes INT3432 events rate fall from two hundred to one hundred for shorts period of time (for example I observe this right now on Linux 4.10.0 while removing/installing packages). Message like this sometimes appear in dmesg: [ 731.226730] i2c_hid i2c-SMO91D0:00: i2c_hid_get_input: incomplete report (53/13568) Complete dmesg with Linux 4.13.3 is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1719795/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759836]
I also observed in my Dell laptop similar to Szymon that it relates to Touchpad. My workarounds- Soon after booting, stopping and starting systed-udev eliminates all bind and unbind problems and response drastically improves. I used the following commands in sequence- sudo systemctl stop systemd-udevd systemd-udevd-kernel.socket systemd- udevd-control.socket sudo systemctl start systemd-udevd systemd-udevd-kernel.socket systemd- udevd-control.socket My understanding- Before all hardware is discovered properly, bind/unbind start executing when no procedures are available and does not get reinitialized. After stopping and starting, it gets all the procedures in place. Probably, it is booting sequence problem. -- 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/1759836 Title: systemd-udevd consumes 100% of CPU Status in linux: Confirmed Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Bug description: The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1759836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel oops destroying interfaces on i386
Thanks, installed that in the test env, after a manual reboot I got: $ uname -a Linux autopkgtest 4.15.0-34-generic #38~lp1736390Commit12064551Reverted SMP Thu Sep 13 13:28:33 UTC i686 i686 i686 GNU/Linux The change is persistent into the autopkgtest: autopkgtest [05:11:17]: testbed running kernel: Linux 4.15.0-34-generic #38~lp1736390Commit12064551Reverted SMP Thu Sep 13 13:28:33 UTC The test kernel works fine where the other one failed. To be sure I ran it multiple times and with different cpu options enables in KVM (e.g. to also run the DPDK tests which need sse3). But they all worked, no crash. That said - yes reverting that change seems to be the solution. Yet for what was it needed and what would break if it is reverted? commit 120645513f55a4ac5543120d9e79925d30a0156f Author: Jarno Rajahalme Date: Fri Apr 21 16:48:06 2017 -0700 openvswitch: Add eventmask support to CT action. Add a new optional conntrack action attribute OVS_CT_ATTR_EVENTMASK, which can be used in conjunction with the commit flag (OVS_CT_ATTR_COMMIT) to set the mask of bits specifying which conntrack events (IPCT_*) should be delivered via the Netfilter netlink multicast groups. Default behavior depends on the system configuration, but typically a lot of events are delivered. This can be very chatty for the NFNLGRP_CONNTRACK_UPDATE group, even if only some types of events are of interest. Netfilter core init_conntrack() adds the event cache extension, so we only need to set the ctmask value. However, if the system is configured without support for events, the setting will be skipped due to extension not being found. That is odd, I thought in the past we had identified an Ubuntu-sauce patch, but that is a normal upstream change. I'd hope that other are affected as well and this is fixed, or could it be that we are affected by 1206455 due to some Ubuntu-sauce? For the sake of checking if latest upstream (no sauce and 4.19-rc3) might be better I ran the latest mainline kernel. autopkgtest [05:21:50]: testbed running kernel: Linux 4.19.0-041900rc3-generic #201809120832 SMP Wed Sep 12 12:47:16 UTC 2018 But that is crashing still. @James: can you estimate what we loose on non-i386 when reverting that change for now? @Joseph: what would we do now, report upstream - if so what exactly a description and link sent to the author and the ML as we don#t have a fix yet? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1736390 Title: openvswitch: kernel oops destroying interfaces on i386 Status in linux package in Ubuntu: In Progress Status in openvswitch package in Ubuntu: Invalid Status in linux source package in Artful: Won't Fix Status in openvswitch source package in Artful: Invalid Status in linux source package in Bionic: In Progress Status in openvswitch source package in Bionic: Invalid Status in linux source package in Cosmic: In Progress Status in openvswitch source package in Cosmic: Invalid Bug description: Reproducable on bionic using the autopkgtest's from openvswitch on i386: [ 41.420568] BUG: unable to handle kernel NULL pointer dereference at (null) [ 41.421000] IP: igmp_group_dropped+0x21/0x220 [ 41.421246] *pdpt = 1d62c001 *pde = [ 41.421659] Oops: [#1] SMP [ 41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse virtio_blk virtio_net pata_acpi floppy [ 41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW 4.13.0-18-generic #21-Ubuntu [ 41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 41.424849] Workqueue: netns cleanup_net [ 41.425071] task: db8fba80 task.stack: dba1 [ 41.425346] EIP: igmp_group_dropped+0x21/0x220 [ 41.425656] EFLAGS: 00010202 CPU: 0 [ 41.425864] EAX: EBX: dd726360 ECX: dba11e6c EDX: 0002 [ 41.426335] ESI: EDI: dd4db500 EBP: dba11dcc ESP: dba11d94 [ 41.426687] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 41.426990] CR0: 80050033 CR2: CR3: 1e6d6d60 CR4: 06f0 [ 41.427340] Call Trace: [ 41.427485] ? __wake_up+0x36/0x40 [ 41.427680] ip_mc_down+0x27/0x90 [ 41.427869] inetdev_event+0x398/0x4e0 [ 41.428082] ? skb_dequeue+0x5b/0x70 [ 41.428286] ? wireless_nlevent_flush+0x4c/0x90 [ 41.428541] notifier_call_chain+0x4e/0x70 [ 41.428772] raw_notifier_call_chain+0x11/0x20 [ 41.429023] call_netdevice_notifiers_info+0x2a/0x60 [ 41.429301]
[Kernel-packages] [Bug 1792501] Re: [Ubuntu18.04][Power9][DD2.2]package installation segfaults inside debian chroot env in P9 KVM guest with HTM enabled (kvm)
** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Package changed: ubuntu => linux (Ubuntu) ** Changed in: ubuntu-power-systems Importance: Undecided => Critical ** 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/1792501 Title: [Ubuntu18.04][Power9][DD2.2]package installation segfaults inside debian chroot env in P9 KVM guest with HTM enabled (kvm) Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Satheesh Rajendran - 2018-09-11 04:10:09 == ---Problem Description--- package installation segfaults inside debian chroot env in P9 KVM guest with HTM enabled ---Additional Hardware Info--- FW with tm-suspend-mode enabled #cd /sys/firmware/devicetree/base/ibm,opal/fw-features/ #ls -1 tm-suspend-mode enabled name phandle qemu-kvm 1:2.11+dfsg-1ubuntu7.4 Machine Type = Power9 DD2.2 ---Steps to Reproduce--- 1. Boot a P9 KVM guest Ubuntu 18.04 (with cap-htm=on, bydefault it is on) tried with upstream kernel aswell(same results) create tap device in host # tunctl -t tap1 -u `whoami`;brctl addif virbr0 tap1;ifconfig tap1 up #qemu-system-ppc64 -enable-kvm -M pseries -m 8192 -smp 4 -drive file=/home/sath/ubuntu-18.04-ppc64le.qcow2,format=qcow2,if=none,id=drive-scsi0 -device virtio-scsi-pci,id=drive-scsi0 -device scsi-hd,drive=drive-scsi0 -serial mon:stdio -enable-kvm -vga none -nographic -kernel /home/sath/vmlinux_4.19 -append root=/dev/sda2 rw console=tty0 console=ttyS0,115200 init=/sbin/init initcall_debug -netdev tap,id=mynet1,ifname=tap1,script=no,downscript=no -device virtio-net,netdev=mynet1,mac=52:55:00:d1:55:42 run dhclient inside guest. 2. # mkdir -p stretch # debootstrap stretch /stretch http://httpredir.debian.org/debian # chroot /stretch /# apt-get update && apt-get install -y make gcc ruby python ... [ 32.029474] random: crng init done [ 32.029477] random: 7 urandom warning(s) missed due to ratelimiting [ 500.300835] dpkg-deb[8704]: segfault (11) at c00037fa nip 7fffac2d098c lr 7fffac2d08c4 code 1 in libc-2.24.so[7fffac17+19] [ 500.300863] dpkg-deb[8704]: code: 4828 eb090010 2eb8 4096006c 419e0074 85270004 394a0001 794a0020 [ 500.300881] dpkg-deb[8704]: code: 71280001 408200a0 1d2a0018 7d2b4a14 2ea8 40960010 e9090008 ---uname output--- 4.15.0-34,4.19.0-rc3 ---Debugger--- A debugger is not configured Contact Information = sathe...@in.ibm.com Userspace tool common name: KVM Guest: Ubuntu GLIBC 2.27-3ubuntu1) stable release version 2.27, Chroot inside KVM Guest: Debian GLIBC 2.24-11+deb9u3) stable release version 2.24 Userspace rpm: KVM Guest: Ubuntu GLIBC 2.27-3ubuntu1) stable release version 2.27, Chroot inside KVM Guest: Debian GLIBC 2.24-11+deb9u3) stable release version 2.24 The userspace tool has the following bit modes: both Userspace tool obtained from project website: na *Additional Instructions for sathe...@in.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. -Attach ltrace and strace of userspace application. So latest update taken from https://github.ibm.com/powercloud/icp-ppc64le/issues/470 was able to recreate segfault using TM test cases /linux/tools/testing/selftests/powerpc/tm # ./tm-vmxcopy test: tm_vmxcopy tags: git_version:v4.19-rc3-0-g11da3a7f84f1-dirty !! child died by signal 11 failure: tm_vmxcopy this particular test on being run gets a signal 11 [267132.434651] tm-vmxcopy[641]: unhandled signal 11 at 0001 nip 000104ba122c lr 000104ba11e4 code 30001 [267253.708795] tm-vmxcopy[7861]: unhandled signal 11 at 0001 nip 00012a31122c lr 00012a3111e4 code 30001 [267385.064533] tm-vmxcopy[13314]: unhandled signal 11 at 0001 nip 0001235f122c lr 0001235f11e4 code 30001 == Comment: #12 - Michael Neuling - 2018-09-13 00:34:16 == Fixes r11 corruption. == Comment: #14 - Satheesh Rajendran - 2018-09-13 03:15:46 == Tested with above patch on KVM host and reported issue is fixed. # git log -1 commit 72664e47565f5de0a1fead1d9111c97b9b537713 (HEAD -> fix) Author: Michael Neuling Date: Thu Sep 13 15:33:47 2018 +1000 KVM: PPC: Book3S HV: Fix guest r11 corruption with POWER9 TM workarounds When we come into the softpatch handler (0x1500), we use r11 to store the HSRR0 for later use by the denorm handler. We also use the softpatch handler for the TM workarounds for POWER9. Unfortunately, in kvmppc_interrupt_hv we later store
[Kernel-packages] [Bug 1792501] [NEW] [Ubuntu18.04][Power9][DD2.2]package installation segfaults inside debian chroot env in P9 KVM guest with HTM enabled (kvm)
You have been subscribed to a public bug:
== Comment: #0 - Satheesh Rajendran - 2018-09-11 04:10:09
==
---Problem Description---
package installation segfaults inside debian chroot env in P9 KVM guest with
HTM enabled
---Additional Hardware Info---
FW with tm-suspend-mode enabled
#cd /sys/firmware/devicetree/base/ibm,opal/fw-features/
#ls -1 tm-suspend-mode
enabled
name
phandle
qemu-kvm 1:2.11+dfsg-1ubuntu7.4
Machine Type = Power9 DD2.2
---Steps to Reproduce---
1. Boot a P9 KVM guest Ubuntu 18.04 (with cap-htm=on, bydefault it is on)
tried with upstream kernel aswell(same results)
create tap device in host
# tunctl -t tap1 -u `whoami`;brctl addif virbr0 tap1;ifconfig tap1 up
#qemu-system-ppc64 -enable-kvm -M pseries -m 8192 -smp 4 -drive
file=/home/sath/ubuntu-18.04-ppc64le.qcow2,format=qcow2,if=none,id=drive-scsi0
-device virtio-scsi-pci,id=drive-scsi0 -device scsi-hd,drive=drive-scsi0
-serial mon:stdio -enable-kvm -vga none -nographic -kernel
/home/sath/vmlinux_4.19 -append root=/dev/sda2 rw console=tty0
console=ttyS0,115200 init=/sbin/init initcall_debug -netdev
tap,id=mynet1,ifname=tap1,script=no,downscript=no -device
virtio-net,netdev=mynet1,mac=52:55:00:d1:55:42
run dhclient inside guest.
2. # mkdir -p stretch
# debootstrap stretch /stretch http://httpredir.debian.org/debian
# chroot /stretch
/# apt-get update && apt-get install -y make gcc ruby python
...
[ 32.029474] random: crng init done
[ 32.029477] random: 7 urandom warning(s) missed due to ratelimiting
[ 500.300835] dpkg-deb[8704]: segfault (11) at c00037fa nip
7fffac2d098c lr 7fffac2d08c4 code 1 in libc-2.24.so[7fffac17+19]
[ 500.300863] dpkg-deb[8704]: code: 4828 eb090010 2eb8 4096006c
419e0074 85270004 394a0001 794a0020
[ 500.300881] dpkg-deb[8704]: code: 71280001 408200a0 1d2a0018 7d2b4a14
2ea8 40960010 e9090008
---uname output---
4.15.0-34,4.19.0-rc3
---Debugger---
A debugger is not configured
Contact Information = sathe...@in.ibm.com
Userspace tool common name:
KVM Guest: Ubuntu GLIBC 2.27-3ubuntu1) stable release version 2.27,
Chroot inside KVM Guest: Debian GLIBC 2.24-11+deb9u3) stable release version
2.24
Userspace rpm:
KVM Guest: Ubuntu GLIBC 2.27-3ubuntu1) stable release version 2.27,
Chroot inside KVM Guest: Debian GLIBC 2.24-11+deb9u3) stable release version
2.24
The userspace tool has the following bit modes: both
Userspace tool obtained from project website: na
*Additional Instructions for sathe...@in.ibm.com:
-Post a private note with access information to the machine that the bug is
occuring on.
-Attach ltrace and strace of userspace application.
So latest update taken from
https://github.ibm.com/powercloud/icp-ppc64le/issues/470
was able to recreate segfault using TM test cases
/linux/tools/testing/selftests/powerpc/tm
# ./tm-vmxcopy
test: tm_vmxcopy
tags: git_version:v4.19-rc3-0-g11da3a7f84f1-dirty
!! child died by signal 11
failure: tm_vmxcopy
this particular test on being run gets a signal 11
[267132.434651] tm-vmxcopy[641]: unhandled signal 11 at 0001 nip
000104ba122c lr 000104ba11e4 code 30001
[267253.708795] tm-vmxcopy[7861]: unhandled signal 11 at 0001 nip
00012a31122c lr 00012a3111e4 code 30001
[267385.064533] tm-vmxcopy[13314]: unhandled signal 11 at 0001 nip
0001235f122c lr 0001235f11e4 code 30001
== Comment: #12 - Michael Neuling - 2018-09-13
00:34:16 ==
Fixes r11 corruption.
== Comment: #14 - Satheesh Rajendran - 2018-09-13
03:15:46 ==
Tested with above patch on KVM host and reported issue is fixed.
# git log -1
commit 72664e47565f5de0a1fead1d9111c97b9b537713 (HEAD -> fix)
Author: Michael Neuling
Date: Thu Sep 13 15:33:47 2018 +1000
KVM: PPC: Book3S HV: Fix guest r11 corruption with POWER9 TM workarounds
When we come into the softpatch handler (0x1500), we use r11 to store
the HSRR0 for later use by the denorm handler.
We also use the softpatch handler for the TM workarounds for
POWER9. Unfortunately, in kvmppc_interrupt_hv we later store r11 out
to the vcpu assuming it's still what we got from userspace.
This causes r11 to be corrupted in the VCPU and hence when we restore
the guest, we get a corrupted r11. We've seen this when running TM
tests inside guests on P9.
This fixes the problem by only touching r11 in the denorm case.
Fixes: 4bb3c7a020 ("KVM: PPC: Book3S HV: Work around transactional memory
bugs in POWER9")
Cc: # 4.17+
Test-by: Suraj Jitindar Singh
Reviewed-by: Paul Mackerras
Signed-off-by: Michael Neuling
Regards,
-Satheesh
http://patchwork.ozlabs.org/patch/969256/
** Affects: ubuntu-power-systems
Importance: Undecided
Status: New
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
Status: New
**
[Kernel-packages] [Bug 1720343] Re: xfs test in xfstests will eat up all the space on i386 testing node with zesty kernel
Haven't see this on other newer releases, let's close this. (plus 17.10 EOL) ** Changed in: ubuntu-kernel-tests Status: Incomplete => Won't Fix ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1720343 Title: xfs test in xfstests will eat up all the space on i386 testing node with zesty kernel Status in ubuntu-kernel-tests: Won't Fix Status in linux package in Ubuntu: Won't Fix Bug description: The xfs test in xfstests test suite will consume all the HDD space on node rizzo with i386 Z-hwe kernel. (It's fine with amd64 Z-hwe kernel on the very same node) A huge file called "spc" will be generated in ~/autotest/client/tmp/tmp/xfstests-scratch. This is not a regression as this issue can be reproduced in the proposed kernel and 4.10.0-35-generic. Error log from jenkins: http://pastebin.ubuntu.com/25638750/ $ ls -lh total 254G -rw--- 1 root root0 Sep 29 10:11 0 -rw-r--r-- 1 root root0 Sep 29 09:47 094.fiemap -rw--- 1 root root 4.8K Sep 29 09:48 096.30645 -rw--- 1 root root0 Sep 29 10:11 1 -rw--- 1 root root0 Sep 29 10:11 2 -rw--- 1 root root0 Sep 29 10:11 3 -rw--- 1 root root0 Sep 29 10:11 4 -rw--- 1 root root 100M Sep 29 10:11 aligned_vector_rw -rw-r--r-- 1 root root 23 Sep 29 10:11 append -rw--- 1 root root 192K Sep 29 10:11 async_direct_io -rw--- 1 root root 64K Sep 29 09:48 attrval -rw--- 2 root root 160K Sep 29 09:48 bar -rw--- 1 root root 8.0K Sep 29 10:11 blackhole -rw--- 1 root root 24K Sep 29 10:11 buff_direct_coherency drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir1 drwxr-xr-x 2 root root 28K Sep 29 09:48 dir1020 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir12 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir135 drwxr-xr-x 2 root root 36K Sep 29 09:48 dir1530 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir18 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir2 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir202 drwxr-xr-x 2 root root 68K Sep 29 09:48 dir2295 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir27 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir3 drwxr-xr-x 2 root root 12K Sep 29 09:48 dir303 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir4 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir40 drwxr-xr-x 2 root root 12K Sep 29 09:48 dir454 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir5 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir60 drwxr-xr-x 2 root root 20K Sep 29 09:48 dir681 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir8 drwxr-xr-x 2 root root 4.0K Sep 29 09:48 dir90 -rw--- 1 root root 6.4M Sep 29 10:11 direct_io -rw--- 1 root root 128K Sep 29 10:11 eof-zeroing_direct -rw-r--r-- 1 root root 512K Sep 29 09:47 file1 -rw-r--r-- 1 root root 512K Sep 29 09:47 file2 -rw--- 2 root root 160K Sep 29 09:48 foo -rw--- 1 root root 128K Sep 29 10:11 fsb_edge_test drwxr-xr-x 2 root root 4.0K Sep 29 10:11 looptest -rwsr-xr-x 1 root root 127K Sep 29 10:10 ls drwx-- 2 root root 4.0K Sep 29 10:10 nosuid -rw-r--r-- 1 root root 9.4G Sep 29 10:11 small_vector_async -rw--- 1 root root 254G Sep 29 09:48 spc --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 29 04:10 seq crw-rw 1 root audio 116, 33 Sep 29 04:10 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R310 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic root=UUID=705d1285-e444-46fc-9c99-68bfe6ab3ba9 ro ProcVersionSignature: User Name 4.10.0-35.39~16.04.1-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-35-generic N/A linux-backports-modules-4.10.0-35-generic N/A linux-firmware 1.157.12 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images Uname: Linux 4.10.0-35-generic i686 UpgradeStatus: No upgrade
[Kernel-packages] [Bug 1720951] Re: seccomp test from upstream failed with "global.KILL_process"
17.10 EOL, let's close this. ** Changed in: ubuntu-kernel-tests Status: Incomplete => Won't Fix ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1720951 Title: seccomp test from upstream failed with "global.KILL_process" Status in ubuntu-kernel-tests: Won't Fix Status in linux package in Ubuntu: Won't Fix Bug description: Steps: 1. git clone https://github.com/torvalds/linux.git 2. make -C linux/tools/testing/selftests/seccomp all 3. home/ubuntu/linux/tools/testing/selftests/seccomp/seccomp_bpf [ RUN ] global.KILL_thread [ OK ] global.KILL_thread [ RUN ] global.KILL_process seccomp_bpf.c:714:global.KILL_process:Expected 0 (0) != (((signed char) (((status) & 0x7f) + 1) >> 1) > 0) (0) global.KILL_process: Test terminated by assertion [ FAIL ] global.KILL_process ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 ProcVersionSignature: User Name 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 3 04:55 seq crw-rw 1 root audio 116, 33 Oct 3 04:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Oct 3 06:53:20 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S2600CWR PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic root=UUID=5170da90-e3b5-4db0-bea9-22859499daf4 ro 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 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/20/2016 dmi.bios.vendor: Intel Corporation dmi.bios.version: SE5C610.86B.01.01.0018.072020161249 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: S2600CWR dmi.board.vendor: Intel Corporation dmi.board.version: H12884-261 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorporation:bvrSE5C610.86B.01.01.0018.072020161249:bd07/20/2016:svnIntelCorporation:pnS2600CWR:pvr:rvnIntelCorporation:rnS2600CWR:rvrH12884-261:cvn..:ct17:cvr..: dmi.product.family: Family dmi.product.name: S2600CWR dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1720951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792002] Re: Wireless signal extremely weak or not detected
hi Jeremy, Yes, Secure Boot Disabled in UEFI/BIOS settings Br, -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792002 Title: Wireless signal extremely weak or not detected Status in linux package in Ubuntu: Incomplete Bug description: Hi Support, I'm Linux Mint newbie started using from LM v18. I'm using HP245 series laptop with AMD A6-7310 APU & Wifi driver Realtek RTL8723BE. Currently I've migrated from Linux 18 (Sylvia) to Linux 19 (Tara) abt a month ago. I'm facing a WiFi signal problem whenever I've tried to upgrade to Kernel v4.15.0.33 or v4.15.0.34. The Wifi signal strength is either very weak & disconnects frequently or cannot be detected from very small distances (3-5 mtr). I've never had this issue till kernel v4.15.0.32 and everything was working fine and currently I had to downgrade or revert back to 4.15.0.32 again in order to receive signal to write this mail. Kindly resolve this error ASAP as I want to upgrade to the latest version. Regards, Joseph To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792002/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789146] Re: [Bug][CLX]assertion failure with util_range_rw using libpmemlog, possible kernel DAX bug
we have verified your kernel package, it works. Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1789146 Title: [Bug][CLX]assertion failure with util_range_rw using libpmemlog, possible kernel DAX bug Status in intel: Triaged Status in linux package in Ubuntu: Fix Committed Bug description: Description: On Mon, Apr 16, 2018 at 8:20 AM, Czurylo, Krzysztof wrote: > > I suspect the problem is caused by a bug in the kernel. > > I did a few experiments and it looks like the issue occurs only if the > filesystem is mounted with "-o dax". I can reproduce is both for xfs > and ext4, so it's not FS-specific, but rather DAX-specific. It also > reproduces on an emulated PMEM - no need to use real AEP DIMMs. > > Using the latest kernel (4.16.0) does not help. > > What happens: > > In debug version of libpmemlog (but also libpmemblk), the entire pool > is by default write-protected with mprotect(..., PROT_READ). > > When the program attempts to write some data to the pool (i.e. > pmemlog_append, pmemblk_write, ...), the library unprotects the pages > to be modified (usually just one or two pages) and once the data is > stored, the pages are protected again. > > Inside the kernel, mprotect splits the memory region associated with > the pool into 3 regions: the read-only head and tail + one r/w page in > the middle. > > The problem is that after the last step, the memory region associated > with the modified page is not merged with the adjacent regions having > the same protection flags (ro) to form one big read-only region again. > This leads to the situation where we have thousands of 4K memory > mappings per process that are tracked by the kernel separately. When > the number of maps exceeds the limit (default is 65536 - see: > /proc/sys/vm/max_map_count), mprotect fails with ENOMEM, which aborts > the program. Commitid: e1fb4a0864958fac2fb1b23f9f4562a9f90e3e8f dax: remove VM_MIXEDMAP for fsdax and device dax Target Kernel: 4.19 Target Release: 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1789146/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788603] Re: libvirt fails with failure to open mount namespace
** Changed in: libvirt (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788603 Title: libvirt fails with failure to open mount namespace Status in libvirt package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in libvirt source package in Bionic: Fix Released Status in linux source package in Bionic: Confirmed Status in libvirt source package in Cosmic: Fix Released Status in linux source package in Cosmic: In Progress Status in libvirt package in Debian: Fix Released Bug description: [Impact] * Libvirt will no more be able to start guests with newer kernels (>=4.18) * We brought a fix upstream that we want to backport to potentially affected releases (B+C) [Test Case] Note: This can but does not have to be tested in nested virtualization (Since we need to change the kernel it is probably the preferred way to do it in nested, so this is what I describe) 1. Get a KVM guest with the Release to test (Cosmic as an example) and give it a size to be able to host a nested guest $ sudo apt install uvtool-libvirt $ uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 release=cosmic label=daily $ uvt-kvm create --cpu 8 --memory 4096 --password ubuntu c-nested-kvm-4.18 arch=amd64 release=cosmic label=daily $ uvt-kvm ssh c-nested-kvm-4.18 2. In the guest set up another guest $ uvt-kvm ssh c-nested-kvm-4.18 $ uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 release=cosmic label=daily $ uvt-kvm create --password ubuntu c-nested-guest arch=amd64 release=cosmic label=daily $ sudo apt install uvtool-libvirt 3. The above will work, now get a kernel >=4.18 e.g. the mainline kernels at https://wiki.ubuntu.com/Kernel/MainlineBuilds $ wget (link of the day) $ sudo dpkg -i *.deb 4. reboot into the 4.18 kernel $ sudo reboot 5. Start the guest again $ virsh start c-nested-guest Without fix this will fail like: error: Failed to start domain c-nested-guest error: internal error: child reported: Kernel does not provide mount namespace: Permission denied And an associated Dmesg/Apparmor entry: [ 519.529760] audit: type=1400 audit(1535364820.976:27): apparmor="DENIED" operation="ptrace" profile="/usr/sbin/libvirtd" pid=1692 comm="libvirtd" requested_mask="read" denied_mask="read" peer="libvirt-4ae5dbbe-641c-4934-ae7c-956bcc8b9e2f" 6. In the guest update from PPA/Proposed that you want to test to bring in the libvirt package with the updated rules (Example with the PPA). $ sudo add-apt-repository ppa:ci-train-ppa-service/3381 $ sudo apt upgrade 7. Start the guest again and it will now work $ virsh start c-nested-guest [Regression Potential] * The change is "only" opening up the apparmor profile for libvirt a little bit for the access now being reported as read in addition. That should in itself be rather regression free, but in addition it has an ack of Jamie Strandboge to be sure from Securities POV (you can follow the upstreaming thread at to check: https://www.redhat.com/archives/libvir-list/2018-August/msg01597.html [Other Info] * This is no issue "yet" but would be one when the Cosmic Kernel becomes available as HWE kernel. We'd want to have the apparmor profile in libvirt ready at the time so that we never have users see this error in the Field on a Released Ubuntu version. --- $ virsh start cosmic-i386 error: Failed to start domain cosmic-i386 error: internal error: child reported: Kernel does not provide mount namespace: Permission denied Happens with 4.18 only, 4.17 is fine. 27013 openat(AT_FDCWD, "/proc/27012/ns/mnt", O_RDONLY) = -1 EACCES (Permission denied) Opening a self or parent mount namespace works fine as tested with cat /proc/self/ns/mnt and cat /proc/self/$$/mnt. Still investigating. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1788603/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730867] Re: [Feature][HMEM] Consume HMAT tables in Linux guest, create sysfs representation
** Description changed: Description: This is dependent upon these two other Jira features: [HMEM] Specify initial sysfs representation for heterogeneous memory [HMEM] Update QEMU prototype to the latest HMAT spec, R053 This task is to consume the newly updated HMAT talbles and create the sysfs representation. - Target Kernel: 4.19 + Target Kernel: TBD Target Release: 18.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730867 Title: [Feature][HMEM] Consume HMAT tables in Linux guest, create sysfs representation Status in intel: Won't Fix Status in linux package in Ubuntu: Expired Status in linux source package in Bionic: Expired Bug description: Description: This is dependent upon these two other Jira features: [HMEM] Specify initial sysfs representation for heterogeneous memory [HMEM] Update QEMU prototype to the latest HMAT spec, R053 This task is to consume the newly updated HMAT talbles and create the sysfs representation. Target Kernel: TBD Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730867/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789146] Re: [Bug][CLX]assertion failure with util_range_rw using libpmemlog, possible kernel DAX bug
hi, Joseph I have built a kernel by myself clone from below link. The version is 4.18. git://kernel.ubuntu.com/kernel-ppa/mirror/ubuntu-cosmic.git commit d4b160782ac74f5301651346495903a30cf752d3 (HEAD -> master, tag: Ubuntu-4.18.0-7.8, origin/master, origin/HEAD) Author: Seth Forshee Date: Tue Aug 28 11:09:06 2018 -0500 UBUNTU: Ubuntu-4.18.0-7.8 Signed-off-by: Seth Forshee in this branch, there is no patch. Test failed. I apply the new patch, the test works. Therefore for 4.18, it will be fine with patch. For your new kernel, I will have a try, will let you know the result. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1789146 Title: [Bug][CLX]assertion failure with util_range_rw using libpmemlog, possible kernel DAX bug Status in intel: Triaged Status in linux package in Ubuntu: Fix Committed Bug description: Description: On Mon, Apr 16, 2018 at 8:20 AM, Czurylo, Krzysztof wrote: > > I suspect the problem is caused by a bug in the kernel. > > I did a few experiments and it looks like the issue occurs only if the > filesystem is mounted with "-o dax". I can reproduce is both for xfs > and ext4, so it's not FS-specific, but rather DAX-specific. It also > reproduces on an emulated PMEM - no need to use real AEP DIMMs. > > Using the latest kernel (4.16.0) does not help. > > What happens: > > In debug version of libpmemlog (but also libpmemblk), the entire pool > is by default write-protected with mprotect(..., PROT_READ). > > When the program attempts to write some data to the pool (i.e. > pmemlog_append, pmemblk_write, ...), the library unprotects the pages > to be modified (usually just one or two pages) and once the data is > stored, the pages are protected again. > > Inside the kernel, mprotect splits the memory region associated with > the pool into 3 regions: the read-only head and tail + one r/w page in > the middle. > > The problem is that after the last step, the memory region associated > with the modified page is not merged with the adjacent regions having > the same protection flags (ro) to form one big read-only region again. > This leads to the situation where we have thousands of 4K memory > mappings per process that are tracked by the kernel separately. When > the number of maps exceeds the limit (default is 65536 - see: > /proc/sys/vm/max_map_count), mprotect fails with ENOMEM, which aborts > the program. Commitid: e1fb4a0864958fac2fb1b23f9f4562a9f90e3e8f dax: remove VM_MIXEDMAP for fsdax and device dax Target Kernel: 4.19 Target Release: 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1789146/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782689] Re: HDMI/DP audio can't work on the laptop of Dell Latitude 5495
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1782689 Title: HDMI/DP audio can't work on the laptop of Dell Latitude 5495 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Bug description: In the v2: the patchset is also sent to OEM-B since the OEM project is waiting for the patchset. The v1 introduced a building error, my investigation is shown as below: The declaration of "enum vga_switcheroo_client_id (*get_client_id)(struct pci_dev *pdev);"and the implementation of "static int nouveau_dsm_get_client_id(struct pci_dev *pdev)" exist in the kernel (bionic, artful) for a long time, but "-Werror=incompatible-pointer-types" didn't report it as an error, after applied these 2 patches, it is reported as an error, that is because the patch touches the definition of "enum vga_switcheroo_client_id", before applying these 2 patches, the vga_switcheroo_client_id includes a negative numer:VGA_SWITCHEROO_UNKNOWN_ID = -1, but after applying the patches, there is no negative number anymore in the "enum vga_swicheroo_client_id". I guess if the definition of enum includes negative number, the c compiler treat it as int type, that is why artful and bionic did not expose building error before. To fix the building error, I cherry-picked 4 more patches [3/6-6/6], and the purpose of those 4 patches is straightforward. In the v1: This bug comes from the OEM project, and the engineer Jim Qu from AMD took almost 2 weeks to investigate this problem, then he worte two patches to fix this problem and now the patches are merged to sound repository. According to Jim Qu's investigation, the root cause of this problem is: 1. there is two GPU on the system. iGPU has a audio codec for HDMI output, and dGPU is without audio codec it is only for offload rendering. 2. under runtime pm, when dGPU suspend, amdgpu will also call vgaswitchroo driver to power off audio which vgaswitchroo client is VGA_SWITCHEROO_DIS. 3. In current HDA audio driver, the iGPU's audio will register to vgaswitchroo as VGA_SWITCHEROO_DIS, therefore, the audio will be selected and powered off by runtime pm. [Impact] On the Dell Latitude 5495, If we plug a monitor with audio capability to the HDMI/DP ports, we can't find HDMI/DP audio sinks as expected, then we can't play any sound through HDMI/DP audio. [Fix] With these 6 patches, the driver will not always set vgaswicheroo clients of HDA audio as VGA_SWITCHEROO_DIS, it will set it to _DIS or _IGD with the help of callback function of DRM drivers. So on this machine, the vgaswicheroo client will be set _IGD, then it will not be powered off when discrete gpu is powered off. [Test Case] We tested plug/unplug detection and playback through HDMI/DP audio, everything works well. [Regression Potential] Very low, without these 6 patches, the vgaswitchroo client of audio will be set to _DIS unconditionally, it did not expose any problem because in the past, all the HDMI/DP audio codecs are in the discreate GPU. But on Latitude 5495, the HDMI/DP audio codec is in the integrated GPU, so we need to change the driver to let DRM driver decide if it is _DIS or _IGD, it will not introduce regression for old mahcines on old machines, the client will be set to _DIS as before. And we have tested these two patches on some old machines with two gpus like A+A, I+A and I+N, all of them worked well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1782689/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791745] Re: linux: 4.4.0-136.162 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791745 Title: linux: 4.4.0-136.162 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: 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: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow 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 1791746 (linux-aws), bug 1791747 (linux-lts-xenial) derivatives: bug 1791749 (linux-aws), bug 1791750 (linux-euclid), bug 1791751 (linux-kvm), bug 1791752 (linux-raspi2), bug 1791753 (linux-snapdragon) -- 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/1791745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791745] Re: linux: 4.4.0-136.162 -proposed tracker
Snap beta testing complete, no regressions found. Ready for promotion. Results here: https://trello.com/c/bvWNRqP4/380-pc-kernel-440-136162-153 ** Changed in: kernel-sru-workflow/snap-certification-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791745 Title: linux: 4.4.0-136.162 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: 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: Fix Released 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 1791746 (linux-aws), bug 1791747 (linux-lts-xenial) derivatives: bug 1791749 (linux-aws), bug 1791750 (linux-euclid), bug 1791751 (linux-kvm), bug 1791752 (linux-raspi2), bug 1791753 (linux-snapdragon) -- 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/1791745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1690085]
(In reply to Michaël Colignon from comment #420) > ... > I want to add another thing, about fixing it directly from the kernel. > As typical idle current seems (i am testing it again for see) not needed > under the other OS, that's because the core parking under this other OS is > partially disabled by DEFAULT on this OS as i said earlier in this thread. > > So it seems possible to fix it via the kernel, without make use of an uefi > parameters not enabled by default... I can perhaps confirm that. But I have to say first, I'm not a developer and I do not understand anything about Linux. I use an AMD Ryzen 5 1600 Six-Core @ 12x 3.2GHz with Gentoo as the operating system. So it's very easy for me to build a kernel just for my machine. (Without the whole Intel, ARM64, Android and Big-Data stuff.) I try the kernels with standard bios setup, without kernel parameters like "idle = nomwait", without OC. My bios only has Global C-states Auto (which is default) and enable/disable options. There is no "Idle Control to "Typical Current Idle"" in the BIOS. Only CONFIG_RCU_NOCB_CPU=y is set in the .config. BOOT_IMAGE=/boot/kernel-x86_64-4.19.0-rc3 root=UUID=465f9c93-09d0-441b-9440-8ec7799b557c ro real_root=/dev/sdd4 resume=/dev/sdd3 init=/usr/lib/systemd/systemd rootfstype=ext4 ./zenstates.py -l ... C6 State - Package - Enabled C6 State - Core - Enabled ... On this basis, It is to be confirmed by me that the kernel 4.17.14 works really well. But the series 4.18.x is cruel. Also the currently as "stable" declarated 4.18.7. Bad. Freeze or reboot every 2 - 3 hours. To my surprise, the 4.19.0-rcX work well. So far no soft lockups. I do not know why. But these are the subjective results of my playing with the kernels. I can also understand that the few kernel developers are working on priority issues. Please think of Specter and Meltdown. But a few clarifying information would be very welcome.. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ?
[Kernel-packages] [Bug 1761379] Re: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu
I built a test kernel with NO_JVMTI disabled in tools/perf/Makefile.config. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1761379 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/1761379 Title: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: ---Problem Description--- File libperf-jvmti.so is missing in linux-tools-common deb making it impossible to use perf for the JVM JITed methods ---uname output--- inux-image-4.13.0-36-generic Machine Type = not relevant ---Debugger--- A debugger is not configured ---Steps to Reproduce--- File libperf-jvmti.so is missing in linux-tools-common deb provided for Ubuntu 17.10 making it impossible to use perf for the JVM JITed methods. I also checked if the file is available on launchpad (https://launchpad.net/ubuntu/+source/linux) for Bionic Beaver proposed (main) at it's also absent there: gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-common_4.15.0-13.14_all.deb | fgrep jvm gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-4.15.0-13-generic_4.15.0-13.14_ppc64el.deb | fgrep jvm I do see the file in tools/perf/jvmti dir in the source .tar.gz, but apparently it's no being packaged in any .deb file? Thanks. Userspace tool common name: perf The userspace tool has the following bit modes: 64-bit Userspace tool obtained from project website: na To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1761379/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792045] Re: Ubuntu 18.04 external USB hard drive performance 1/10th of 16.04
Hi there, Thank you for your response. As requested I tested the newest mainline kernel 4.19-rc3. Unfortunately the issue persists. Something of note that I just discovered: A live session of 18.04 does NOT have this issue. The kernel version reported there is 4.15.0-29 (I think. Whatever ships on the amd64 ISO image). So I booted 18.04 to that kernel version during startup... and the issue is still there with that one external drive only. Another USB 3 thumb drive still writes at full performance (30 MB/s). This makes me think it isn't a kernel issue but rather some other package that got updated. ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Description changed: - From both a live and an installed 18.04 environment, I cannot get my - external 8TB sata hard drive (attached via USB 3) to write faster than - about 10 megabytes per second under Ubuntu 18.04. I have another that - writes at the expected full speed or close enough (100+ MBps). + I cannot get my external 8TB sata hard drive (attached via USB 3) to + write faster than about 10 megabytes per second under Ubuntu 18.04. I + have another that writes at the expected full speed or close enough + (100+ MBps). I have tried: * Changing the enclosure from the stock to a new one * Using usb-storage "quirks" options in modprobe conf files to work around any UAS incompatibilities with the bridge (many reports of the drive working at full performance when disabling UAS, no such luck for me) * Checking the disk for errors * Updating the kernel to the most recent mainline (4.18.6 at the time) * Checking UEFI settings (I'm already on the most recent revision of the firmware) * Applying all available updates * Changing USB ports * Checking dmesg for any obvious errors (dead end, I googled everything) Again, a different external 3TB USB 3 drive does not have any write speed issues at all, so it's not the computer (Intel NUC7PJYH). However, the very same drive in both of the enclosures I have used works *perfectly* in Ubuntu 16.04 on kernel 4.15.0-34 in both a live session and installed. I am not sure what the difference is between the two LTS versions that is causing this, but unfortunately I think I've reached the end of my know-how on this. Thank you for your time, and please let me know what other information I can provide. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE Date: Tue Sep 11 18:33:46 2018 InstallationDate: Installed on 2018-09-06 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 002: ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 002: ID 1997:2433 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation NUC7PJYH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=b40fd1a1-0de5-40bb-b598-7f4cd53daee1 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 08/21/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: JYGLKCPX.86A.0044.2018.0821.1915 dmi.board.name: NUC7JYB dmi.board.vendor: Intel Corporation dmi.board.version: J67969-401 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrJYGLKCPX.86A.0044.2018.0821.1915:bd08/21/2018:svnIntelCorporation:pnNUC7PJYH:pvrJ67992-401:rvnIntelCorporation:rnNUC7JYB:rvrJ67969-401:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC7PJYH dmi.product.version: J67992-401 dmi.sys.vendor: Intel Corporation -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.
[Kernel-packages] [Bug 1792396] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1792396/+attachment/5188602/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792396 Title: Touchpad is not working Status in linux package in Ubuntu: Confirmed Bug description: General information regarding the machine - 1. Model Number - ASUS FX753V 2. Manufacturer - ASUSTek Computer Inc. 3. Symptoms - Soon after giving repairs for flickering screen, when I got the laptop back, I found the touchpad to be completely unresponsive. Attaching an external mouse makes the pointer move, but nothing happens when I touch the touchpad. After browsing through the troubleshooting wiki page (https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo), I am hereby creating a bug report with the files dmesg, devices, and /var/log/Xorg.0.log attached. Hope to see some solutions! Would be really grateful if there any pointers to solve the issue. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shehjar1648 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-11 (94 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. GL753VE NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=26934e63-6775-4bde-9d16-c98265bb0b66 ro quiet splash psmouse.proto=bare vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/02/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL753VE.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL753VE 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.:bvrGL753VE.306:bd01/02/2018:svnASUSTeKCOMPUTERINC.:pnGL753VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL753VE 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/1792396/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792396] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1792396/+attachment/5188603/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792396 Title: Touchpad is not working Status in linux package in Ubuntu: Confirmed Bug description: General information regarding the machine - 1. Model Number - ASUS FX753V 2. Manufacturer - ASUSTek Computer Inc. 3. Symptoms - Soon after giving repairs for flickering screen, when I got the laptop back, I found the touchpad to be completely unresponsive. Attaching an external mouse makes the pointer move, but nothing happens when I touch the touchpad. After browsing through the troubleshooting wiki page (https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo), I am hereby creating a bug report with the files dmesg, devices, and /var/log/Xorg.0.log attached. Hope to see some solutions! Would be really grateful if there any pointers to solve the issue. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shehjar1648 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-11 (94 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. GL753VE NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=26934e63-6775-4bde-9d16-c98265bb0b66 ro quiet splash psmouse.proto=bare vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/02/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL753VE.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL753VE 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.:bvrGL753VE.306:bd01/02/2018:svnASUSTeKCOMPUTERINC.:pnGL753VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL753VE 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/1792396/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792396] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1792396/+attachment/5188604/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792396 Title: Touchpad is not working Status in linux package in Ubuntu: Confirmed Bug description: General information regarding the machine - 1. Model Number - ASUS FX753V 2. Manufacturer - ASUSTek Computer Inc. 3. Symptoms - Soon after giving repairs for flickering screen, when I got the laptop back, I found the touchpad to be completely unresponsive. Attaching an external mouse makes the pointer move, but nothing happens when I touch the touchpad. After browsing through the troubleshooting wiki page (https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo), I am hereby creating a bug report with the files dmesg, devices, and /var/log/Xorg.0.log attached. Hope to see some solutions! Would be really grateful if there any pointers to solve the issue. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shehjar1648 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-11 (94 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. GL753VE NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=26934e63-6775-4bde-9d16-c98265bb0b66 ro quiet splash psmouse.proto=bare vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/02/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL753VE.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL753VE 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.:bvrGL753VE.306:bd01/02/2018:svnASUSTeKCOMPUTERINC.:pnGL753VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL753VE 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/1792396/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792396] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1792396/+attachment/5188606/+files/WifiSyslog.txt ** 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/1792396 Title: Touchpad is not working Status in linux package in Ubuntu: Confirmed Bug description: General information regarding the machine - 1. Model Number - ASUS FX753V 2. Manufacturer - ASUSTek Computer Inc. 3. Symptoms - Soon after giving repairs for flickering screen, when I got the laptop back, I found the touchpad to be completely unresponsive. Attaching an external mouse makes the pointer move, but nothing happens when I touch the touchpad. After browsing through the troubleshooting wiki page (https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo), I am hereby creating a bug report with the files dmesg, devices, and /var/log/Xorg.0.log attached. Hope to see some solutions! Would be really grateful if there any pointers to solve the issue. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shehjar1648 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-11 (94 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. GL753VE NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=26934e63-6775-4bde-9d16-c98265bb0b66 ro quiet splash psmouse.proto=bare vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/02/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL753VE.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL753VE 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.:bvrGL753VE.306:bd01/02/2018:svnASUSTeKCOMPUTERINC.:pnGL753VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL753VE 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/1792396/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792396] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1792396/+attachment/5188594/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792396 Title: Touchpad is not working Status in linux package in Ubuntu: Confirmed Bug description: General information regarding the machine - 1. Model Number - ASUS FX753V 2. Manufacturer - ASUSTek Computer Inc. 3. Symptoms - Soon after giving repairs for flickering screen, when I got the laptop back, I found the touchpad to be completely unresponsive. Attaching an external mouse makes the pointer move, but nothing happens when I touch the touchpad. After browsing through the troubleshooting wiki page (https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo), I am hereby creating a bug report with the files dmesg, devices, and /var/log/Xorg.0.log attached. Hope to see some solutions! Would be really grateful if there any pointers to solve the issue. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shehjar1648 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-11 (94 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. GL753VE NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=26934e63-6775-4bde-9d16-c98265bb0b66 ro quiet splash psmouse.proto=bare vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/02/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL753VE.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL753VE 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.:bvrGL753VE.306:bd01/02/2018:svnASUSTeKCOMPUTERINC.:pnGL753VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL753VE 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/1792396/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792396] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1792396/+attachment/5188595/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792396 Title: Touchpad is not working Status in linux package in Ubuntu: Confirmed Bug description: General information regarding the machine - 1. Model Number - ASUS FX753V 2. Manufacturer - ASUSTek Computer Inc. 3. Symptoms - Soon after giving repairs for flickering screen, when I got the laptop back, I found the touchpad to be completely unresponsive. Attaching an external mouse makes the pointer move, but nothing happens when I touch the touchpad. After browsing through the troubleshooting wiki page (https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo), I am hereby creating a bug report with the files dmesg, devices, and /var/log/Xorg.0.log attached. Hope to see some solutions! Would be really grateful if there any pointers to solve the issue. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shehjar1648 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-11 (94 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. GL753VE NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=26934e63-6775-4bde-9d16-c98265bb0b66 ro quiet splash psmouse.proto=bare vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/02/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL753VE.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL753VE 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.:bvrGL753VE.306:bd01/02/2018:svnASUSTeKCOMPUTERINC.:pnGL753VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL753VE 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/1792396/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792396] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1792396/+attachment/5188593/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792396 Title: Touchpad is not working Status in linux package in Ubuntu: Confirmed Bug description: General information regarding the machine - 1. Model Number - ASUS FX753V 2. Manufacturer - ASUSTek Computer Inc. 3. Symptoms - Soon after giving repairs for flickering screen, when I got the laptop back, I found the touchpad to be completely unresponsive. Attaching an external mouse makes the pointer move, but nothing happens when I touch the touchpad. After browsing through the troubleshooting wiki page (https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo), I am hereby creating a bug report with the files dmesg, devices, and /var/log/Xorg.0.log attached. Hope to see some solutions! Would be really grateful if there any pointers to solve the issue. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shehjar1648 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-11 (94 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. GL753VE NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=26934e63-6775-4bde-9d16-c98265bb0b66 ro quiet splash psmouse.proto=bare vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/02/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL753VE.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL753VE 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.:bvrGL753VE.306:bd01/02/2018:svnASUSTeKCOMPUTERINC.:pnGL753VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL753VE 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/1792396/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792396] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1792396/+attachment/5188597/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792396 Title: Touchpad is not working Status in linux package in Ubuntu: Confirmed Bug description: General information regarding the machine - 1. Model Number - ASUS FX753V 2. Manufacturer - ASUSTek Computer Inc. 3. Symptoms - Soon after giving repairs for flickering screen, when I got the laptop back, I found the touchpad to be completely unresponsive. Attaching an external mouse makes the pointer move, but nothing happens when I touch the touchpad. After browsing through the troubleshooting wiki page (https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo), I am hereby creating a bug report with the files dmesg, devices, and /var/log/Xorg.0.log attached. Hope to see some solutions! Would be really grateful if there any pointers to solve the issue. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shehjar1648 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-11 (94 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. GL753VE NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=26934e63-6775-4bde-9d16-c98265bb0b66 ro quiet splash psmouse.proto=bare vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/02/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL753VE.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL753VE 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.:bvrGL753VE.306:bd01/02/2018:svnASUSTeKCOMPUTERINC.:pnGL753VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL753VE 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/1792396/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792396] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1792396/+attachment/5188600/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792396 Title: Touchpad is not working Status in linux package in Ubuntu: Confirmed Bug description: General information regarding the machine - 1. Model Number - ASUS FX753V 2. Manufacturer - ASUSTek Computer Inc. 3. Symptoms - Soon after giving repairs for flickering screen, when I got the laptop back, I found the touchpad to be completely unresponsive. Attaching an external mouse makes the pointer move, but nothing happens when I touch the touchpad. After browsing through the troubleshooting wiki page (https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo), I am hereby creating a bug report with the files dmesg, devices, and /var/log/Xorg.0.log attached. Hope to see some solutions! Would be really grateful if there any pointers to solve the issue. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shehjar1648 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-11 (94 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. GL753VE NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=26934e63-6775-4bde-9d16-c98265bb0b66 ro quiet splash psmouse.proto=bare vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/02/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL753VE.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL753VE 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.:bvrGL753VE.306:bd01/02/2018:svnASUSTeKCOMPUTERINC.:pnGL753VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL753VE 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/1792396/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792396] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1792396/+attachment/5188601/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792396 Title: Touchpad is not working Status in linux package in Ubuntu: Confirmed Bug description: General information regarding the machine - 1. Model Number - ASUS FX753V 2. Manufacturer - ASUSTek Computer Inc. 3. Symptoms - Soon after giving repairs for flickering screen, when I got the laptop back, I found the touchpad to be completely unresponsive. Attaching an external mouse makes the pointer move, but nothing happens when I touch the touchpad. After browsing through the troubleshooting wiki page (https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo), I am hereby creating a bug report with the files dmesg, devices, and /var/log/Xorg.0.log attached. Hope to see some solutions! Would be really grateful if there any pointers to solve the issue. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shehjar1648 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-11 (94 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. GL753VE NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=26934e63-6775-4bde-9d16-c98265bb0b66 ro quiet splash psmouse.proto=bare vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/02/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL753VE.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL753VE 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.:bvrGL753VE.306:bd01/02/2018:svnASUSTeKCOMPUTERINC.:pnGL753VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL753VE 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/1792396/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792396] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1792396/+attachment/5188599/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792396 Title: Touchpad is not working Status in linux package in Ubuntu: Confirmed Bug description: General information regarding the machine - 1. Model Number - ASUS FX753V 2. Manufacturer - ASUSTek Computer Inc. 3. Symptoms - Soon after giving repairs for flickering screen, when I got the laptop back, I found the touchpad to be completely unresponsive. Attaching an external mouse makes the pointer move, but nothing happens when I touch the touchpad. After browsing through the troubleshooting wiki page (https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo), I am hereby creating a bug report with the files dmesg, devices, and /var/log/Xorg.0.log attached. Hope to see some solutions! Would be really grateful if there any pointers to solve the issue. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shehjar1648 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-11 (94 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. GL753VE NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=26934e63-6775-4bde-9d16-c98265bb0b66 ro quiet splash psmouse.proto=bare vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/02/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL753VE.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL753VE 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.:bvrGL753VE.306:bd01/02/2018:svnASUSTeKCOMPUTERINC.:pnGL753VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL753VE 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/1792396/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792396] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1792396/+attachment/5188605/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792396 Title: Touchpad is not working Status in linux package in Ubuntu: Confirmed Bug description: General information regarding the machine - 1. Model Number - ASUS FX753V 2. Manufacturer - ASUSTek Computer Inc. 3. Symptoms - Soon after giving repairs for flickering screen, when I got the laptop back, I found the touchpad to be completely unresponsive. Attaching an external mouse makes the pointer move, but nothing happens when I touch the touchpad. After browsing through the troubleshooting wiki page (https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo), I am hereby creating a bug report with the files dmesg, devices, and /var/log/Xorg.0.log attached. Hope to see some solutions! Would be really grateful if there any pointers to solve the issue. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shehjar1648 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-11 (94 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. GL753VE NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=26934e63-6775-4bde-9d16-c98265bb0b66 ro quiet splash psmouse.proto=bare vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/02/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL753VE.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL753VE 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.:bvrGL753VE.306:bd01/02/2018:svnASUSTeKCOMPUTERINC.:pnGL753VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL753VE 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/1792396/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792396] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1792396/+attachment/5188598/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792396 Title: Touchpad is not working Status in linux package in Ubuntu: Confirmed Bug description: General information regarding the machine - 1. Model Number - ASUS FX753V 2. Manufacturer - ASUSTek Computer Inc. 3. Symptoms - Soon after giving repairs for flickering screen, when I got the laptop back, I found the touchpad to be completely unresponsive. Attaching an external mouse makes the pointer move, but nothing happens when I touch the touchpad. After browsing through the troubleshooting wiki page (https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo), I am hereby creating a bug report with the files dmesg, devices, and /var/log/Xorg.0.log attached. Hope to see some solutions! Would be really grateful if there any pointers to solve the issue. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shehjar1648 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-11 (94 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. GL753VE NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=26934e63-6775-4bde-9d16-c98265bb0b66 ro quiet splash psmouse.proto=bare vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/02/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL753VE.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL753VE 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.:bvrGL753VE.306:bd01/02/2018:svnASUSTeKCOMPUTERINC.:pnGL753VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL753VE 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/1792396/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792396] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1792396/+attachment/5188596/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792396 Title: Touchpad is not working Status in linux package in Ubuntu: Confirmed Bug description: General information regarding the machine - 1. Model Number - ASUS FX753V 2. Manufacturer - ASUSTek Computer Inc. 3. Symptoms - Soon after giving repairs for flickering screen, when I got the laptop back, I found the touchpad to be completely unresponsive. Attaching an external mouse makes the pointer move, but nothing happens when I touch the touchpad. After browsing through the troubleshooting wiki page (https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo), I am hereby creating a bug report with the files dmesg, devices, and /var/log/Xorg.0.log attached. Hope to see some solutions! Would be really grateful if there any pointers to solve the issue. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shehjar1648 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-11 (94 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. GL753VE NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=26934e63-6775-4bde-9d16-c98265bb0b66 ro quiet splash psmouse.proto=bare vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/02/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL753VE.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL753VE 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.:bvrGL753VE.306:bd01/02/2018:svnASUSTeKCOMPUTERINC.:pnGL753VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL753VE 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/1792396/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792396] Re: Touchpad is not working
apport information ** Tags added: apport-collected ** Description changed: General information regarding the machine - 1. Model Number - ASUS FX753V 2. Manufacturer - ASUSTek Computer Inc. 3. Symptoms - Soon after giving repairs for flickering screen, when I got the laptop back, I found the touchpad to be completely unresponsive. Attaching an external mouse makes the pointer move, but nothing happens when I touch the touchpad. - After browsing through the troubleshooting wiki page - (https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo), I am - hereby creating a bug report with the files dmesg, devices, and - /var/log/Xorg.0.log attached. Hope to see some solutions! Would be - really grateful if there any pointers to solve the issue. + After browsing through the troubleshooting wiki page (https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo), I am hereby creating a bug report with the files dmesg, devices, and /var/log/Xorg.0.log attached. Hope to see some solutions! Would be really grateful if there any pointers to solve the issue. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.2 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: shehjar1648 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2018-06-11 (94 days ago) + InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) + MachineType: ASUSTeK COMPUTER INC. GL753VE + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=26934e63-6775-4bde-9d16-c98265bb0b66 ro quiet splash psmouse.proto=bare vt.handoff=1 + ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-30-generic N/A + linux-backports-modules-4.15.0-30-generic N/A + linux-firmware 1.173.1 + Tags: bionic + Uname: Linux 4.15.0-30-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 01/02/2018 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: GL753VE.306 + dmi.board.asset.tag: ATN12345678901234567 + dmi.board.name: GL753VE + 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.:bvrGL753VE.306:bd01/02/2018:svnASUSTeKCOMPUTERINC.:pnGL753VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: + dmi.product.family: GL + dmi.product.name: GL753VE + dmi.product.version: 1.0 + dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1792396/+attachment/5188592/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792396 Title: Touchpad is not working Status in linux package in Ubuntu: Confirmed Bug description: General information regarding the machine - 1. Model Number - ASUS FX753V 2. Manufacturer - ASUSTek Computer Inc. 3. Symptoms - Soon after giving repairs for flickering screen, when I got the laptop back, I found the touchpad to be completely unresponsive. Attaching an external mouse makes the pointer move, but nothing happens when I touch the touchpad. After browsing through the troubleshooting wiki page (https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo), I am hereby creating a bug report with the files dmesg, devices, and /var/log/Xorg.0.log attached. Hope to see some solutions! Would be really grateful if there any pointers to solve the issue. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shehjar1648 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-11 (94 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. GL753VE NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=26934e63-6775-4bde-9d16-c98265bb0b66 ro quiet splash psmouse.proto=bare vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64
[Kernel-packages] [Bug 1792002] Re: Wireless signal extremely weak or not detected
Joseph, Is Secure Boot Disabled in UEFI/BIOS settings? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792002 Title: Wireless signal extremely weak or not detected Status in linux package in Ubuntu: Incomplete Bug description: Hi Support, I'm Linux Mint newbie started using from LM v18. I'm using HP245 series laptop with AMD A6-7310 APU & Wifi driver Realtek RTL8723BE. Currently I've migrated from Linux 18 (Sylvia) to Linux 19 (Tara) abt a month ago. I'm facing a WiFi signal problem whenever I've tried to upgrade to Kernel v4.15.0.33 or v4.15.0.34. The Wifi signal strength is either very weak & disconnects frequently or cannot be detected from very small distances (3-5 mtr). I've never had this issue till kernel v4.15.0.32 and everything was working fine and currently I had to downgrade or revert back to 4.15.0.32 again in order to receive signal to write this mail. Kindly resolve this error ASAP as I want to upgrade to the latest version. Regards, Joseph To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792002/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791749] Re: linux-aws: 4.4.0-1068.78 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** 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: 1791745 phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Thursday, 13. September 2018 21:01 UTC ** 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: 1791745 - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Thursday, 13. September 2018 21:01 UTC + 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-aws in Ubuntu. https://bugs.launchpad.net/bugs/1791749 Title: linux-aws: 4.4.0-1068.78 -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: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: 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: 1791745 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/1791749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780817] Re: kernel panic in nested VM with latest 4.15 kernel (4.15.0-24-generic)
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc3 ** Tags added: needs-bisect -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1780817 Title: kernel panic in nested VM with latest 4.15 kernel (4.15.0-24-generic) Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: When starting a nested VM in a Bionic VM, the "host" VM kernel panics following a simple drop to QEMU monitor by hitting A-c. For some reason kdump is unable to capture the kernel panic so I only have a screen capture of the panic. It also happens on the latest mainline kernel(4.18-rc4). It is fairly trivial to reproduce. In a Bionic VM, install qemu & ovmf and run the following : qemu-system-x86_64 -enable-kvm \ -name balloontest \ -display none \ -monitor none \ -nographic \ -nodefaults \ -m 2048M \ -serial mon:stdio \ -smp 2 \ -cpu host \ -drive if=pflash,format=raw,readonly,file=/usr/share/OVMF/OVMF_CODE.fd \ -drive if=pflash,format=raw,file=/home/caribou/balloon/efi.vars Use A-c to drop to QEMU monitor and . ^[]0;/opt/ocs/gotty-serial/nolp-cli^G^[]2;Loading...^G^[]2;avogadro^G[ 267.784299] general protection fault: [#1] SMP PTI [ 267.785834] Modules linked in: nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype ip6t_MASQUERADE nf_nat_masquerade_ipv6 ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter i> [ 267.804312] xor raid6_pq libcrc32c raid1 raid0 multipath linear floppy aesni_intel pata_acpi aes_x86_64 crypto_simd cryptd glue_helper psmouse i2c_piix4 virtio_net virtio_blk [ 267.807946] CPU: 6 PID: 0 Comm: swapper/6 Not tainted 4.15.0-24-generic #26-Ubuntu [ 267.809710] Hardware name: Scaleway Standard PC (i440FX + PIIX, 1996), BIOS 0.0.0 02/06/2015 [ 267.811666] RIP: 0010:native_write_cr4+0x4/0x10 [ 267.812727] RSP: 0018:8c01ffd83f48 EFLAGS: 00010006 [ 267.813960] RAX: 003626e0 RBX: 0046 RCX: 8c01ffd8 [ 267.815582] RDX: 8c01ffd94020 RSI: 8c01ffda5040 RDI: 003606e0 [ 267.817095] RBP: 8c01ffd83f48 R08: 00478079a547 R09: [ 267.818625] R10: R11: R12: 00025040 [ 267.820130] R13: 0001 R14: R15: [ 267.821638] FS: () GS:8c01ffd8() knlGS: [ 267.823352] CS: 0010 DS: ES: CR0: 80050033 [ 267.824592] CR2: CR3: 00058c00a006 CR4: 003626e0 [ 267.826108] DR0: DR1: DR2: [ 267.827567] DR3: DR6: fffe0ff0 DR7: 0400 [ 267.828973] Call Trace: [ 267.829470] [ 267.829893] hardware_disable+0xaa/0xc0 [kvm_intel] [ 267.830897] kvm_arch_hardware_disable+0x19/0x40 [kvm] [ 267.831928] hardware_disable_nolock+0x2b/0x30 [kvm] [ 267.832912] flush_smp_call_function_queue+0x4c/0xf0 [ 267.833911] generic_smp_call_function_single_interrupt+0x13/0x30 [ 267.835121] smp_call_function_interrupt+0x36/0xd0 [ 267.836069] call_function_interrupt+0x84/0x90 [ 267.836950] [ 267.837396] RIP: 0010:native_safe_halt+0x6/0x10 [ 267.838272] RSP: 0018:a2e1431afe80 EFLAGS: 0246 ORIG_RAX: ff03 [ 267.839698] RAX: acd97150 RBX: 0006 RCX: [ 267.840978] RDX: RSI: RDI: [ 267.842258] RBP: a2e1431afe80 R08: 0002 R09: [ 267.843554] R10: 00b3 R11: 00a6 R12: 0006 [ 267.844826] R13: R14: R15: [ 267.846107] ? __cpuidle_text_start+0x8/0x8 [ 267.846875] default_idle+0x20/0x100 [ 267.847533] arch_cpu_idle+0x15/0x20 [ 267.848186] default_idle_call+0x23/0x30 [ 267.848917] do_idle+0x172/0x1f0 [ 267.849516] cpu_startup_entry+0x73/0x80 [ 267.850255] start_secondary+0x1ab/0x200 [ 267.850971] secondary_startup_64+0xa5/0xb0 [ 267.851700] Code: 0f
[Kernel-packages] [Bug 1790096] Re: PTP no longuer working on igb since 4.15.0-33
I built a 4.15.0-35 test kernel. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1792100 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/1790096 Title: PTP no longuer working on igb since 4.15.0-33 Status in linux package in Ubuntu: Incomplete Bug description: ptp4l is no longer able to sync the PHC of a i350 (igb driver) since 4.15.0-33-generic. 4.15.0-32-generic work. It no longer reach the slave state and is stuck to UNCALIBRATED: Aug 31 10:03:29 ptp4l[1259]: [79.208] [0:enp7s0f1] port 1: link up Aug 31 10:03:29 ptp4l[1259]: [79.260] [0:enp7s0f1] port 1: FAULTY to LISTENING on INIT_COMPLETE Aug 31 10:03:30 ptp4l[1259]: [80.814] [0:enp7s0f1] port 1: new foreign master ec4670.fffe.009fc5-1 Aug 31 10:03:34 ptp4l[1259]: [84.815] [0:enp7s0f1] selected best master clock ec4670.fffe.009fc5 Aug 31 10:03:34 ptp4l[1259]: [84.815] [0:enp7s0f1] port 1: LISTENING to UNCALIBRATED on RS_SLAVE OR Aug 31 10:53:44 ptp4l[1259]: [3094.219] [0:enp7s0f1] timed out while polling for tx timestamp Aug 31 10:53:44 ptp4l[1259]: [3094.219] [0:enp7s0f1] increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bug Aug 31 10:53:44 ptp4l[1259]: [3094.219] [0:enp7s0f1] port 1: send delay request failed Aug 31 10:53:44 ptp4l[1259]: [3094.219] [0:enp7s0f1] port 1: UNCALIBRATED to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED) Aug 31 10:54:00 ptp4l[1259]: [3110.292] [0:enp7s0f1] port 1: FAULTY to LISTENING on INIT_COMPLETE Aug 31 10:54:02 ptp4l[1259]: [3112.052] [0:enp7s0f1] port 1: new foreign master ec4670.fffe.009fc5-1 Aug 31 10:54:06 ptp4l[1259]: [3116.053] [0:enp7s0f1] selected best master clock ec4670.fffe.009fc5 Aug 31 10:54:06 ptp4l[1259]: [3116.053] [0:enp7s0f1] port 1: LISTENING to UNCALIBRATED on RS_SLAVE On 4.15.0-32-generic: Aug 31 09:52:27 ptp4l[2392]: [654.860] [0:enp7s0f1] port 1: new foreign master ec4670.fffe.009fc5-1 Aug 31 09:52:31 ptp4l[2392]: [658.861] [0:enp7s0f1] selected best master clock ec4670.fffe.009fc5 Aug 31 09:52:31 ptp4l[2392]: [658.861] [0:enp7s0f1] port 1: LISTENING to UNCALIBRATED on RS_SLAVE Aug 31 09:52:33 ptp4l[2392]: [660.737] [0:enp7s0f1] port 1: minimum delay request interval 2^1 Aug 31 09:52:34 ptp4l[2392]: [662.037] [0:enp7s0f1] port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED I don't know if it is a driver change or a network/timekeeping change or other that is the root cause of this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790096/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775945] Re: Lenovi X1 Carbon regularly has frozen lock- or dark screen after closing lid
Would it be possible for you to test the proposed kernel and post back if it resolves this bug? See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you 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/1775945 Title: Lenovi X1 Carbon regularly has frozen lock- or dark screen after closing lid Status in linux package in Ubuntu: Confirmed Bug description: I was running ubuntu 17.10 for months with no issues. After upgrading to 18.04, closing the lid regularly (but not always) results in either: 1. The display staying on with a frozen lock-screen, or 2. The display powered off, but the notebook still powered on. In both cases the notebook does not respond. A five-second press of the power button to hard-reboot the computer is the only means of recovery. After powering the notebook back on, there are no files in /var/crash. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jun 9 00:00:48 2018 InstallationDate: Installed on 2018-06-02 (6 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/+bug/1775945/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790219] Re: Stuck on boot of my PC after switching to Nvidia-driver-390 proprietary driver and rebooting
** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1790219 Title: Stuck on boot of my PC after switching to Nvidia-driver-390 proprietary driver and rebooting Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: I was carrying out this testcase for proprietary Nvidia drivers testing: http://xorg.qa.ubuntu.com/qatracker/testcases/1704/info. After having installed Ubuntu 18.10 on a new partition on my PC, I switched to Nvidia-driver-390 proprietary driver from Additional Drivers tab of Software & Update and rebooted my PC. On reboot I got low resolution Ubuntu logo, pressing F1 I could read this message: (1 of 2) A start Job is running for Hold until snapd is fully seeded (15 min 23s/ no limit). (2 of 2) A start Job is running for Hold until snapd is fully seeded (15 min 25s/ no limit). I rebooted after waiting 15 minutes as I was tired of waiting. This is my display hardware: *-display description: VGA compatible controller product: GM206 [GeForce GTX 960] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller bus_master cap_list rom configuration: driver=nouveau latency=0 resources: irq:125 memory:de00-deff memory:c000-cfff memory:d000-d1ff ioport:e000(size=128) memory:c-d Link to the testcase revision Edit result My PC is a: product: XPS 8900 (06B8) vendor: Dell Inc. width: 64 bits To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1790219/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790652] Re: Oracle cosmic image does not find broadcom network device in Shape VMStandard2.1
I haven't specifically seen that one, but I'll check in with both the Oracle Linux team and our Hypervisor 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/1790652 Title: Oracle cosmic image does not find broadcom network device in Shape VMStandard2.1 Status in linux package in Ubuntu: Triaged Status in linux source package in Cosmic: Triaged Bug description: I tried to register and boot a cosmic image to verify new changes in it and in cloud-init. The image failed to bring up networking in the initramfs, and thus failed to find iscsi root. this could be user error. Here is what I did to publish the image. - use oci build tool [1]. following https://docs.cloud.oracle.com/iaas/Content/Compute/Tasks/imageimportexport.htm#ImportinganImage - Download a livefs build from cloudware https://launchpad.net/~cloudware/+livefs/ubuntu/cosmic/cpc/ example: livecd.ubuntu-cpc.oracle_bare_metal.img My image had version 20180821.1 - oci os bucket create --name=smoser-devel - oci os object put \ --parallel-upload-count=4 \ --part-size=10 \ --bucket-name=smoser-devel \ --file=/tmp/livecd.ubuntu-cpc.oracle_bare_metal.img \ --name=cosmic-20180821.1.img - import the object $ oci compute image import from-object \ --display-name=smoser-cosmic-20180821.1.img \ --launch-mode=NATIVE \ --namespace=intcanonical \ --bucket-name=smoser-devel \ --name=cosmic-20180821.1.img \ --source-image-type=QCOW2 Then I launched from the web UI a VM.Standard2.1. -- https://docs.cloud.oracle.com/iaas/Content/API/Concepts/cliconcepts.htm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790652/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748157] Re: [MIR] thunderbolt-tools
reconfirmed with Seth that this is good to go. Please add it to a seed or as a dependency to some package. ** Changed in: thunderbolt-tools (Ubuntu) Milestone: ubuntu-18.03 => ubuntu-18.10 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thunderbolt-tools in Ubuntu. Matching subscriptions: Kernel Packages https://bugs.launchpad.net/bugs/1748157 Title: [MIR] thunderbolt-tools Status in thunderbolt-tools package in Ubuntu: Confirmed Bug description: == Overview == Intel Thunderbolt userspace components provides components for using Intel Thunderbolt controllers with security level features. Thunderbolt™ technology is a transformational high-speed, dual protocol I/O that provides unmatched performance with up to 40Gbps bi- directional transfer speeds. It provides flexibility and simplicity by supporting both data (PCIe, USB3.1) and video (DisplayPort) on a single cable connection that can daisy-chain up to six devices. [ See https://github.com/intel/thunderbolt-software-user-space ] == Answers to UbuntuMainInclusionRequirements == = Requirements = 1. Availability Package is in universe: https://launchpad.net/ubuntu/+source/thunderbolt-tools 2. Rationale Package a device enabler for users with Thunderbolt technology 3. Security: No security issues exposed so far. However, the tools have only been in Ubuntu since 2017-12-09, so this currently is less than the 90 days threshold. 4. Quality assurance: * Manual is provided * No debconf questions higher than medium * No major outstanding bugs. I'm also helping Intel fix issues that I'm finding with static analysis tools such as scan-build, cppcheck and CoverityScan Bugs outstanding: #883857 please backport for stretch-backports #882525 thunderbolt-tools: FTBFS on kFreeBSD: _ZN5boost6system15system_categoryEv undefined - I can fix this, but it makes no sense to run on kFreeBSD * Exotic Hardware: Only Thunderbolt supported H/W is required, this is an industry standard and the support for the tools are in the 4.13+ kernels * No Test Suite shipped with the package * Does not rely on obsolete or demoted packages 5. UI standards: * This is a CLI tool. Tool has normal CLI style short help and man pages * No desktop file required as it is a CLI tool. 6. Binary Dependencies: libboost-dev(main) libboost-filesystem-dev (main) libboost-program-options-dev(main) udev(main) 7. Standards compliance: lintian clean and meets the FHS + Debian Policy standards to the best of my knowledge 8. Maintenance * Package owning team: The Ubuntu Kernel Team * Debian package maintained by Colin Ian King (myself from the Kernel Team) 9. Background Information The user-space components implement device approval support: a. Easier interaction with the kernel module for approving connected devices. b. ACL for auto-approving devices white-listed by the user. Tools provided by this package: tbtacl - triggered by udev (see the udev rules in tbtacl.rules). It auto-approves devices that are found in ACL. tbtadm - user-facing CLI tool. It provides operations for device approval, handling the ACL and more. The user-space components operate in coordination with the upstream Thunderbolt kernel driver (found in v4.13) to provide the Thunderbolt functionalities. These components are NOT compatible with the old out-of-tree Thunderbolt kernel module. = Security checks = http://cve.mitre.org/cve/cve.html: Search in the National Vulnerability Database using the package as a keyword * No CVEs found http://secunia.com/advisories/search/: search for the package as a keyword * No security advisories found Ubuntu CVE Tracker http://people.ubuntu.com/~ubuntu-security/cve/main.html * No http://people.ubuntu.com/~ubuntu-security/cve/universe.html * No http://people.ubuntu.com/~ubuntu-security/cve/partner.html * No Check for security relevant binaries. If any are present, this requires a more in-depth security review. Executables which have the suid or sgid bit set. * Not applicable Executables in /sbin, /usr/sbin. * None in these paths Packages which install daemons (/etc/init.d/*) * No Packages which open privileged ports (ports < 1024). * No Add-ons and plugins to security-sensitive software (filters, scanners, UI skins, etc) * This does exec tbtacl from udev with new udev rules, so this needs security checking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbolt-tools/+bug/1748157/+subscriptions -- Mailing
[Kernel-packages] [Bug 1791951] Re: nvidia-settings does not work when i install proprietary driver and reboot
** Changed in: nvidia-settings (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1791951
Title:
nvidia-settings does not work when i install proprietary driver and
reboot
Status in nvidia-settings package in Ubuntu:
Confirmed
Bug description:
- What I expected to happen:
Open nvidia-settings and switch between Intel and Nvidia graphic cards.
- What happened instead:
Steps (case 1):
1. Install propetary driver.
2. Reboot and select Wayland session.
3. Open nvidia-settings --> "ERROR: Unable to find display on any available
system"
Steps (case 2)
1. sudo prime-select intel.
2. Reboot and select Wayland session.
3. Open nvidia-settings --> "ERROR: Unable to find display on any available
system"
Steps (case 3)
1. sudo prime-select nvidia.
2. Reboot and select X11 session.
3. Open nvidia-settings. --> Not ERROR.
In my second test, this step generate an error:
"ERROR: NVIDIA driver is not loaded
ERROR: Unable to load info from any available system"
Steps (Case 4)
1. sudo prime-select intel.
2. Reboot and select X11 session.
3. Open nvidia-settings --> "ERROR: NVIDIA driver is not loaded
ERROR: Unable to load info from any available system"
Notes:
- The command: sudo prime-select nvidia[intel] always work
- Secure boot is disabled
SYSTEM INFORMATION:
Description: Ubuntu 18.04.1 LTS
Release: 18.04
nvidia-settings:
Installed: 396.54-0ubuntu0~gpu18.04.1
Candidate: 396.54-0ubuntu0~gpu18.04.1
Version table:
*** 396.54-0ubuntu0~gpu18.04.1 500
500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main
amd64 Packages
100 /var/lib/dpkg/status
390.42-0ubuntu1 500
500 http://co.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
lspci -v -s 02:00
02:00.0 3D controller: NVIDIA Corporation GP108M [GeForce MX150] (rev a1)
Subsystem: Lenovo GP108M [GeForce MX150]
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at e800 (32-bit, non-prefetchable) [size=16M]
Memory at 7000 (64-bit, prefetchable) [size=256M]
Memory at 8000 (64-bit, prefetchable) [size=32M]
I/O ports at d000 [size=128]
Capabilities:
Kernel driver in use: nvidia
Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia
{
"Version": "18.04",
"OEM": {
"Vendor": "LENOVO",
},
"BIOS": {
"Vendor": "LENOVO",
},
"CPU": {
"OpMode": "32-bit, 64-bit",
"CPUs": "8",
"Threads": "2",
"Cores": "4",
"Sockets": "1",
"Vendor": "GenuineIntel",
"Family": "6",
"Model": "142",
"Stepping": "10",
"Name": "Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz",
"Virtualization": "VT-x"
},
"Arch": "amd64",
"GPU": [
{
"Vendor": "8086",
"Model": "5917"
}
],
"RAM": 7.9,
"Disks": [
0
],
"Partitions": [
28.4,
0.3,
210.4
],
"Screens": [
{
"Size": "340mmx190mm",
"Resolution": "1368x768",
"Frequency": "59.71"
}
],
"Autologin": false,
"LivePatch": false,
"Session": {
"DE": "ubuntu:GNOME",
"Name": "ubuntu-wayland",
"Type": "wayland"
},
"Language": "en_US",
"Timezone": "America/Bogota",
"Install": {
"Media": "Ubuntu 18.04.1 LTS \"Bionic Beaver\" - Release amd64
(20180725)",
"Type": "GTK",
"OEM": false,
"PartitionMethod": "manual",
"DownloadUpdates": true,
"Language": "en",
"Minimal": true,
"RestrictedAddons": true,
"Stages": {
"0": "language",
"4": "console_setup",
"18": "console_setup",
"21": "wireless",
"86": "prepare",
"205": "partman",
"250": "partman",
"251": "partman",
"252": "partman",
"267": "partman",
"281": "partman",
"297": "partman",
"300": "start_install",
"314": "timezone",
"333": "usersetup",
"343": "user_done",
"800": "done"
}
}
}
Driver version: 396.54
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1791951/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788623] Re: regression: IPv6 PMTU discovery fails with source-specific routing
I started a kernel bisect between commit v4.14 final and v4.15-rc1. The kernel bisect will require testing of about 13 test kernels. I built the first test kernel, up to the following commit: 1be2172e96e33bfa22a5c7a651f768ef30ce3984 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1788623 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results. 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/1788623 Title: regression: IPv6 PMTU discovery fails with source-specific routing Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: IPv6 PMTU discovery fails when using source-specific routing on Ubuntu 18.04. I have attached a test case called pmtu-sads.sh which is based on tools/testing/selftests/net/pmtu.sh in the linux source. I have verified that the test fails on: Ubuntu 18.04 with 4.15.0-30.32 Ubuntu 18.04 with 4.17.0-041700.201806041953 Ubuntu 18.04 with 4.18.3-041803.201808180530 The test succeeds on Ubuntu 16.04 with 4.4.0.131.137 which makes it a regression. System information: Ubuntu 4.15.0-30.32-generic 4.15.18 Description: Ubuntu 18.04.1 LTS Release: 18.04 See below for a patch which is working for me. I'm currently using linux kernel 4.15.0-32.35 built from git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git with this patch. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-30-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=041f6e1e-4904-4760-8518-3a88dc288556 ro splash quiet vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791728] Re: linux-gcp: 4.15.0-1020.21 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Assignee: Kleber Sacilotto de Souza (kleber-souza) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Kleber Sacilotto de Souza (kleber-souza) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Kleber Sacilotto de Souza (kleber-souza) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1791728 Title: linux-gcp: 4.15.0-1020.21 -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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp 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 -- kernel-stable-master-bug: 1791719 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1791728/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792002] Re: Wireless signal extremely weak or not detected
Hi Jeremy & Joseph, Tried both your solutions and checked the thread but the problem neither got solved with Kernel v4.19 neither the tweaked version 4.15.33. Had to again revert back to v4.15.32 and everything is back to normal. Any other solution? Br, -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792002 Title: Wireless signal extremely weak or not detected Status in linux package in Ubuntu: Incomplete Bug description: Hi Support, I'm Linux Mint newbie started using from LM v18. I'm using HP245 series laptop with AMD A6-7310 APU & Wifi driver Realtek RTL8723BE. Currently I've migrated from Linux 18 (Sylvia) to Linux 19 (Tara) abt a month ago. I'm facing a WiFi signal problem whenever I've tried to upgrade to Kernel v4.15.0.33 or v4.15.0.34. The Wifi signal strength is either very weak & disconnects frequently or cannot be detected from very small distances (3-5 mtr). I've never had this issue till kernel v4.15.0.32 and everything was working fine and currently I had to downgrade or revert back to 4.15.0.32 again in order to receive signal to write this mail. Kindly resolve this error ASAP as I want to upgrade to the latest version. Regards, Joseph To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792002/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic
I'll ping upstream and the author of the patch that was reverted. However, before doing so, we should test the latest mainline kernel to see if the bug is already fixed upstream. Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc3 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1234 F pulseaudio /dev/snd/controlC0: al 1234 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Notebook Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8137 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.02 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792205] Re: CONFIG_BCH_CONST_PARAMS should be unset
** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792205 Title: CONFIG_BCH_CONST_PARAMS should be unset Status in linux package in Ubuntu: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: Quoting lib/bch.c: * Option CONFIG_BCH_CONST_PARAMS can be used to force fixed values of * parameters m and t; thus allowing extra compiler optimizations and providing * better (up to 2x) encoding performance. Using this option makes sense when * (m,t) are fixed and known in advance, e.g. when using BCH error correction * on a particular NAND flash device. Ubuntu's kernel targets generic hardware, so using this option is not a good idea. As a result of this option being enabled, nandsim's option "bch" is unusable: [34200.137521] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64 [34200.137522] [nandsim] using 8-bit/512 bytes BCH ECC [34200.137524] bch encoder/decoder was configured to support parameters m=14, t=4 only! --- Ubuntu 18.04.1 LTS, linux-image-4.15.0-34-generic: 4.15.0-34.37 (amd64) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792205/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791822] Re: [regression] MacBookPro14, 3 internal display is blank with kernel 4.18
kernel-bug-exists-upstream Not sure how to add a tag. Upstream also kills the touchpad and keyboard, but the ubuntu kernel works there. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Summary changed: - [regression] MacBookPro14,3 internal display is blank with kernel 4.18 + [regression] [kernel-bug-exists-upstream] MacBookPro14,3 internal display is blank with kernel 4.18 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791822 Title: [regression] [kernel-bug-exists-upstream] MacBookPro14,3 internal display is blank with kernel 4.18 Status in linux package in Ubuntu: Confirmed Bug description: After upgrading all packages and rebooting today, the internal display is blank. An external display works fine. I believe I also ran upgrades on Friday, so it was a fairly recent package. This is a MacBookPro14,3. I believe there was a kernel upgrade, not sure if there was an Xorg upgrade. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Sep 10 16:34:45 2018 DistUpgraded: 2018-09-05 11:35:19,089 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] No such file or directory: './xorg_fix_proprietary.py': './xorg_fix_proprietary.py') DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: applespi, 0.1, 4.17.0-9-generic, x86_64: installed applespi, 0.1, 4.18.0-7-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 460/560D / Pro 450/455/460/555/560] [1002:67ef] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Radeon Pro 555 [106b:017a] InstallationDate: Installed on 2018-09-05 (5 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Apple Inc. MacBookPro14,3 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic root=UUID=666e74b4-e3a0-4a21-ac25-36b7daa2d230 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2018-09-05 (5 days ago) dmi.bios.date: 06/26/2018 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP143.88Z.0178.B00.1806261159 dmi.board.name: Mac-551B86E5744E2388 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro14,3 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-551B86E5744E2388 dmi.modalias: dmi:bvnAppleInc.:bvrMBP143.88Z.0178.B00.1806261159:bd06/26/2018:svnAppleInc.:pnMacBookPro14,3:pvr1.0:rvnAppleInc.:rnMac-551B86E5744E2388:rvrMacBookPro14,3:cvnAppleInc.:ct9:cvrMac-551B86E5744E2388: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro14,3 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791822/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791754] Re: linux: 3.13.0-159.209 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791754 Title: linux: 3.13.0-159.209 -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 1791756 (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/1791754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790652] Re: Oracle cosmic image does not find broadcom network device in Shape VMStandard2.1
Copied from Seth's upstream mailing list posting https://www.spinics.net/lists/netdev/msg521428.html This is with a kernel based on 4.18.5, and it has also been seen with a 4.17-based kernel. I'm not currently aware of any working kernel version. The driver seems to be getting an error response from the firmware when trying to set the MAC address. [2.437420] Broadcom NetXtreme-C/E driver bnxt_en v1.9.1 [2.449820] bnxt_en :00:03.0 (unnamed net_device) (uninitialized): hwrm req_type 0xf seq id 0x5 error 0x [2.455610] bnxt_en :00:03.0 (unnamed net_device) (uninitialized): VF MAC address 00:00:17:02:05:d0 not approved by the PF [2.461443] bnxt_en :00:03.0: Unable to initialize mac address. [2.483531] bnxt_en: probe of :00:03.0 failed with error -99 Posting here in case @pgraydon-oracle has seen this. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790652 Title: Oracle cosmic image does not find broadcom network device in Shape VMStandard2.1 Status in linux package in Ubuntu: Triaged Status in linux source package in Cosmic: Triaged Bug description: I tried to register and boot a cosmic image to verify new changes in it and in cloud-init. The image failed to bring up networking in the initramfs, and thus failed to find iscsi root. this could be user error. Here is what I did to publish the image. - use oci build tool [1]. following https://docs.cloud.oracle.com/iaas/Content/Compute/Tasks/imageimportexport.htm#ImportinganImage - Download a livefs build from cloudware https://launchpad.net/~cloudware/+livefs/ubuntu/cosmic/cpc/ example: livecd.ubuntu-cpc.oracle_bare_metal.img My image had version 20180821.1 - oci os bucket create --name=smoser-devel - oci os object put \ --parallel-upload-count=4 \ --part-size=10 \ --bucket-name=smoser-devel \ --file=/tmp/livecd.ubuntu-cpc.oracle_bare_metal.img \ --name=cosmic-20180821.1.img - import the object $ oci compute image import from-object \ --display-name=smoser-cosmic-20180821.1.img \ --launch-mode=NATIVE \ --namespace=intcanonical \ --bucket-name=smoser-devel \ --name=cosmic-20180821.1.img \ --source-image-type=QCOW2 Then I launched from the web UI a VM.Standard2.1. -- https://docs.cloud.oracle.com/iaas/Content/API/Concepts/cliconcepts.htm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790652/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792205] Re: CONFIG_BCH_CONST_PARAMS should be unset
This option is selected as a result of having CONFIG_MTD_DOCG3. This seems to be very old hardware which only had experimental support, so I doubt there's any harm in disabling it. I agree that CONFIG_BCH_CONST_PARAMS looks to only make sense when the hardware is known. It seems it should be safe to disable these options. ** Changed in: linux (Ubuntu Cosmic) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Cosmic) Assignee: (unassigned) => Seth Forshee (sforshee) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792205 Title: CONFIG_BCH_CONST_PARAMS should be unset Status in linux package in Ubuntu: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: Quoting lib/bch.c: * Option CONFIG_BCH_CONST_PARAMS can be used to force fixed values of * parameters m and t; thus allowing extra compiler optimizations and providing * better (up to 2x) encoding performance. Using this option makes sense when * (m,t) are fixed and known in advance, e.g. when using BCH error correction * on a particular NAND flash device. Ubuntu's kernel targets generic hardware, so using this option is not a good idea. As a result of this option being enabled, nandsim's option "bch" is unusable: [34200.137521] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64 [34200.137522] [nandsim] using 8-bit/512 bytes BCH ECC [34200.137524] bch encoder/decoder was configured to support parameters m=14, t=4 only! --- Ubuntu 18.04.1 LTS, linux-image-4.15.0-34-generic: 4.15.0-34.37 (amd64) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792205/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic
A new kernel update 4.15.0.34 has been provided recently. This kernel doesn't work with / support rtl8723be either. It seems the fix has not been committed so far. 18.4.1 typically keeps two kernels, unless you modify /etc/kernel/postinst.d/apt-auto-removal, so to keep more kernels. Hence users that installed the latest kernel update will have not more kernel installed that supports rtl8723be !! The changes, that were applied in 4.15.0.33, have completely broken all system with rtl8223be meanwhile, unless you've made changes to the system how it handles kernel updates. So I think there is evidence to provide a kernel update including the fixes to support rtl8723be immediately. - Heribert -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1234 F pulseaudio /dev/snd/controlC0: al 1234 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Notebook Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8137 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.02 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769937] Re: Error reported when creating ZFS pool with "-t" option, despite successful pool creation
** Changed in: linux (Ubuntu Cosmic)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1769937
Title:
Error reported when creating ZFS pool with "-t" option, despite
successful pool creation
Status in linux package in Ubuntu:
Fix Committed
Status in zfs-linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Incomplete
Status in zfs-linux source package in Xenial:
New
Status in linux source package in Bionic:
Incomplete
Status in zfs-linux source package in Bionic:
New
Status in linux source package in Cosmic:
Fix Committed
Status in zfs-linux source package in Cosmic:
In Progress
Bug description:
== SRU Justification, Xenial, Bionic ==
Bug:
When creating a pool with the -t option on Ubuntu 18.04 LTS, it will
report an error and return a non-zero exit code, but the pool appears
to be successfully created.
For example:
# zpool create -O canmount=off -O mountpoint=none -R /mnt/rpool-25582 -t
rpool-25582 rpool /dev/mapper/loop2p1
cannot create 'rpool': no such pool or dataset
# zpool list
NAME SIZE ALLOC FREE EXPANDSZ FRAGCAP DEDUP HEALTH
ALTROOT
rpool-25582 69.5G 92.5K 69.5G - 0% 0% 1.00x ONLINE
/mnt/rpool-25582
# zpool export rpool-25582
# zpool import rpool
# zpool list
NAMESIZE ALLOC FREE EXPANDSZ FRAGCAP DEDUP HEALTH ALTROOT
rpool 69.5G 134K 69.5G - 0% 0% 1.00x ONLINE -
I opened an upstream bug against ZFS on Linux, here:
https://github.com/zfsonlinux/zfs/issues/7502
And it has been recently fixed, here:
https://github.com/zfsonlinux/zfs/pull/7509
Can this upstream fix be pulled into the Ubuntu 18.04 LTS packages?
Thanks,
Prakash
== Fix ==
Upstream zfs commit 4ceb8dd6fdfd ("Fix 'zpool create -t '")
== Test ==
Without the fix, creating a pool with -t will show an error message
such as:
"cannot create 'rpool': no such pool or dataset" and will return an
error number even though it successfully created the pool. With the
fix, the error is not shown and it exits with 0.
E.g.
pool create -O canmount=off -O mountpoint=none -R /mnt/rpool-25582 -t
rpool-25582 rpool /dev/mapper/loop2p1
cannot create 'rpool': no such pool or dataset
== Regression Potential ==
Small. This is an upstream fix that is know to fix the error. There
are no known subsequent changes to the fix hence suggesting it is a
good fix. The change is very limited and testing shows it does not
break any of the kernel team's ZFS regression testing.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769937/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790652] Re: Oracle cosmic image does not find broadcom network device in Shape VMStandard2.1
Just an update, I sent a report of the bug upstream over a week ago but haven't received any response. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790652 Title: Oracle cosmic image does not find broadcom network device in Shape VMStandard2.1 Status in linux package in Ubuntu: Triaged Status in linux source package in Cosmic: Triaged Bug description: I tried to register and boot a cosmic image to verify new changes in it and in cloud-init. The image failed to bring up networking in the initramfs, and thus failed to find iscsi root. this could be user error. Here is what I did to publish the image. - use oci build tool [1]. following https://docs.cloud.oracle.com/iaas/Content/Compute/Tasks/imageimportexport.htm#ImportinganImage - Download a livefs build from cloudware https://launchpad.net/~cloudware/+livefs/ubuntu/cosmic/cpc/ example: livecd.ubuntu-cpc.oracle_bare_metal.img My image had version 20180821.1 - oci os bucket create --name=smoser-devel - oci os object put \ --parallel-upload-count=4 \ --part-size=10 \ --bucket-name=smoser-devel \ --file=/tmp/livecd.ubuntu-cpc.oracle_bare_metal.img \ --name=cosmic-20180821.1.img - import the object $ oci compute image import from-object \ --display-name=smoser-cosmic-20180821.1.img \ --launch-mode=NATIVE \ --namespace=intcanonical \ --bucket-name=smoser-devel \ --name=cosmic-20180821.1.img \ --source-image-type=QCOW2 Then I launched from the web UI a VM.Standard2.1. -- https://docs.cloud.oracle.com/iaas/Content/API/Concepts/cliconcepts.htm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790652/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792309] Re: Fix I2C touchpanels' interrupt storms after system suspend
** Changed in: linux (Ubuntu Cosmic) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792309 Title: Fix I2C touchpanels' interrupt storms after system suspend Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: Fix Committed Bug description: [Impact] Some I2C touchpanels generate IRQ storm after system suspend/resume. [Test] After applying the fix, the IRQ storm stops generated by Raydium touchpanels. [Fix] Instead of requesting i2c reset, simply requesting the device to power on. The HID over I2C spec doesn't specify how the device should do upon resume from suspend, so some devices expect a power on instead of reset. [Regression Potential] Low. I tested other vendors' touchpanels, didn't observe any side effect. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1792309/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791731] Re: linux-kvm: 4.15.0-1022.22 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => Fix Committed ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Steve Langasek (vorlon) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1791731 Title: linux-kvm: 4.15.0-1022.22 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm 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: 1791719 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1791731/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791749] Re: linux-aws: 4.4.0-1068.78 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => Fix Committed ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Steve Langasek (vorlon) -- 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/1791749 Title: linux-aws: 4.4.0-1068.78 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New 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: 1791745 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1791749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791745] Re: linux: 4.4.0-136.162 -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/1791745 Title: linux: 4.4.0-136.162 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: 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 1791746 (linux-aws), bug 1791747 (linux-lts-xenial) derivatives: bug 1791749 (linux-aws), bug 1791750 (linux-euclid), bug 1791751 (linux-kvm), bug 1791752 (linux-raspi2), bug 1791753 (linux-snapdragon) -- 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/1791745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792419] Re: Xenial update to 4.4.155 stable release
** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The 4.4.155 upstream stable + patch set is now available. It should be included in the Ubuntu + kernel as well. - 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 4.4.155 upstream stable -patch set is now available. It should be included in the Ubuntu -kernel as well. + git://git.kernel.org/ -git://git.kernel.org/ + TEST CASE: TBD - TEST CASE: TBD - -The following patches from the 4.4.155 stable release shall be - applied: + The following patches from the 4.4.155 stable release shall be applied: + * net: 6lowpan: fix reserved space for single frames + * net: mac802154: tx: expand tailroom if necessary + * 9p/net: Fix zero-copy path in the 9p virtio transport + * net: lan78xx: Fix misplaced tasklet_schedule() call + * spi: davinci: fix a NULL pointer dereference + * drm/i915/userptr: reject zero user_size + * powerpc/fadump: handle crash memory ranges array index overflow + * powerpc/pseries: Fix endianness while restoring of r3 in MCE handler. + * fs/9p/xattr.c: catch the error of p9_client_clunk when setting xattr failed + * 9p/virtio: fix off-by-one error in sg list bounds check + * net/9p/client.c: version pointer uninitialized + * net/9p/trans_fd.c: fix race-condition by flushing workqueue before the kfree() + * dm cache metadata: save in-core policy_hint_size to on-disk superblock + * iio: ad9523: Fix displayed phase + * iio: ad9523: Fix return value for ad952x_store() + * vmw_balloon: fix inflation of 64-bit GFNs + * vmw_balloon: do not use 2MB without batching + * vmw_balloon: VMCI_DOORBELL_SET does not check status + * vmw_balloon: fix VMCI use when balloon built into kernel + * tracing: Do not call start/stop() functions when tracing_on does not change + * tracing/blktrace: Fix to allow setting same value + * kthread, tracing: Don't expose half-written comm when creating kthreads + * uprobes: Use synchronize_rcu() not synchronize_sched() + * 9p: fix multiple NULL-pointer-dereferences + * PM / sleep: wakeup: Fix build error caused by missing SRCU support + * pnfs/blocklayout: off by one in bl_map_stripe() + * ARM: tegra: Fix Tegra30 Cardhu PCA954x reset + * mm/tlb: Remove tlb_remove_table() non-concurrent condition + * iommu/vt-d: Add definitions for PFSID + * iommu/vt-d: Fix dev iotlb pfsid use + * osf_getdomainname(): use copy_to_user() + * sys: don't hold uts_sem while accessing userspace memory + * userns: move user access out of the mutex + * ubifs: Fix memory leak in lprobs self-check + * Revert "UBIFS: Fix potential integer overflow in allocation" + * ubifs: Check data node size before truncate + * ubifs: Fix synced_i_size calculation for xattr inodes + * pwm: tiehrpwm: Fix disabling of output of PWMs + * fb: fix lost console when the user unplugs a USB adapter + * udlfb: set optimal write delay + * getxattr: use correct xattr length + * bcache: release dc->writeback_lock properly in bch_writeback_thread() + * perf auxtrace: Fix queue resize + * fs/quota: Fix spectre gadget in do_quotactl + * x86/io: add interface to reserve io memtype for a resource range. (v1.1) + * drm/drivers: add support for using the arch wc mapping API. + * Linux 4.4.155 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792419 Title: Xenial update to 4.4.155 stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.155 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.155 stable release shall be applied: * net: 6lowpan: fix reserved space for single frames * net: mac802154: tx: expand tailroom if necessary *
[Kernel-packages] [Bug 1792349] Re: Memory leaking when running kubernetes cronjobs
I re-ran on 4.19.0-041900rc3-generic #201809120832 SMP Wed Sep 12 12:35:08 UTC 2018 and am still seeing the leak. ** Tags added: kernel-bug-exists-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/1792349 Title: Memory leaking when running kubernetes cronjobs Status in linux package in Ubuntu: Confirmed Bug description: We are using Kubernetes V1.8.15 with docker 18.03.1-ce. We schedule 50 Kubernetes cronjobs to run every 5 minutes. Each cronjob will create a simple busybox container, echo hello world, then terminate. In the data attached to the bug I let this run for 1 hour, and in this time the Available memory had reduced from 31256704 kB to 30461224 kB - so a loss of 776 MB. From previous longer runs we observe the available memory continues to drop. There doesn't appear to be any processes left behind, or any growth in any other processes to explain where the memory has gone. echo 3 > /proc/sys/vm/drop_caches causes some of the memory to be returned, but the majority remains leaked, and the only way to free it appears to be to reboot the system. We are currently running Ubuntu 4.15.0-32.35-generic 4.15.18 and have previously observed similar issues on Ubuntu 16.04 with Kernel 4.4.0-89-generic #112-Ubuntu SMP Mon Jul 31 19:38:41 UTC 2017 and Debian 9.4 running 4.9.0-6-amd64 #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02) The leak was more severe on the Debian system, and investigations there showed leaks in pcpu_get_vm_areas and were related to memory cgroups. Running with Kernel 4.17 on debian showed a leak at a similar rate to what we now observe on Ubuntu 18. This leak causes us issues as we need to run the cronjobs regularly and want the systems to remain up for months. Kubernetes will create a new cgroup each time the cronjob runs, but these are removed when the job completes (which takes a few seconds). If I use systemd-cgtop I don't see any increase in cgroups over time - but if I monitor /proc/cgroups over time I can see num_cgroups for memory increases. For the duration of the test I collected slabinfo, meminfo, vmallocinfo & cgroups - which I will attach to the bug. Each file is suffixed with the number of seconds since the start. *.0 & *.600 were taken before the test was started. The test was stopped shortly after the *.4200 files were generated. I then left the system idle for 10 minutes. I then ran echo 3 > /proc/sys/vm/drop_caches after *.4800 was generated. This seemed to free ~240MB - but this still leaves ~500MB lost. I then left the system idle for a further 20 minutes, and MemoryAvailable didn't seem to be increasing significantly. Note, the data attached is from running on kernel 4.18.7-041807-generic #201809090930 SMP Sun Sep 9 09:33:16 UTC 2018 (which I ran to verify the issue still exists in latest kernel) - however I was unable to run ubuntu-bug linux on this kernel as it complained about: *** Problem in linux-image-4.18.7-041807-generic The problem cannot be reported: This report is about a package that is not installed. So I switched back to 4.15.0-32.35-generic to raise the bug. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-32-generic 4.15.0-32.35 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 08:55 seq crw-rw 1 root audio 116, 33 Sep 13 08:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Thu Sep 13 08:55:46 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Xen HVM domU PciMultimedia: ProcEnviron: LANG=C.UTF-8 SHELL=/bin/bash TERM=xterm PATH=(custom, no user) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-32-generic root=UUID=6a84f0e4-8522-41cd-8ecb-d4a6fbecef8a ro earlyprintk RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 08/13/2018 dmi.bios.vendor: Xen dmi.bios.version: 4.7.5-1.21 dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias:
[Kernel-packages] [Bug 1792419] Re: Xenial update to 4.4.155 stable release
Again skip "x86/mm/pat: Fix L1TF stable backport for CPA, 2nd call" because we did not revert "x86/mm/pat: Ensure cpa->pfn only contains page frame numbers". -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792419 Title: Xenial update to 4.4.155 stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.155 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.155 stable release shall be applied: * net: 6lowpan: fix reserved space for single frames * net: mac802154: tx: expand tailroom if necessary * 9p/net: Fix zero-copy path in the 9p virtio transport * net: lan78xx: Fix misplaced tasklet_schedule() call * spi: davinci: fix a NULL pointer dereference * drm/i915/userptr: reject zero user_size * powerpc/fadump: handle crash memory ranges array index overflow * powerpc/pseries: Fix endianness while restoring of r3 in MCE handler. * fs/9p/xattr.c: catch the error of p9_client_clunk when setting xattr failed * 9p/virtio: fix off-by-one error in sg list bounds check * net/9p/client.c: version pointer uninitialized * net/9p/trans_fd.c: fix race-condition by flushing workqueue before the kfree() * dm cache metadata: save in-core policy_hint_size to on-disk superblock * iio: ad9523: Fix displayed phase * iio: ad9523: Fix return value for ad952x_store() * vmw_balloon: fix inflation of 64-bit GFNs * vmw_balloon: do not use 2MB without batching * vmw_balloon: VMCI_DOORBELL_SET does not check status * vmw_balloon: fix VMCI use when balloon built into kernel * tracing: Do not call start/stop() functions when tracing_on does not change * tracing/blktrace: Fix to allow setting same value * kthread, tracing: Don't expose half-written comm when creating kthreads * uprobes: Use synchronize_rcu() not synchronize_sched() * 9p: fix multiple NULL-pointer-dereferences * PM / sleep: wakeup: Fix build error caused by missing SRCU support * pnfs/blocklayout: off by one in bl_map_stripe() * ARM: tegra: Fix Tegra30 Cardhu PCA954x reset * mm/tlb: Remove tlb_remove_table() non-concurrent condition * iommu/vt-d: Add definitions for PFSID * iommu/vt-d: Fix dev iotlb pfsid use * osf_getdomainname(): use copy_to_user() * sys: don't hold uts_sem while accessing userspace memory * userns: move user access out of the mutex * ubifs: Fix memory leak in lprobs self-check * Revert "UBIFS: Fix potential integer overflow in allocation" * ubifs: Check data node size before truncate * ubifs: Fix synced_i_size calculation for xattr inodes * pwm: tiehrpwm: Fix disabling of output of PWMs * fb: fix lost console when the user unplugs a USB adapter * udlfb: set optimal write delay * getxattr: use correct xattr length * bcache: release dc->writeback_lock properly in bch_writeback_thread() * perf auxtrace: Fix queue resize * fs/quota: Fix spectre gadget in do_quotactl * x86/io: add interface to reserve io memtype for a resource range. (v1.1) * drm/drivers: add support for using the arch wc mapping API. * Linux 4.4.155 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792419/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792044] Re: update ENA driver to latest mainline version
** Description changed: Update ENA driver to latest mainline version as of this commit: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=0e1f4c76be241377d282e34ebea6d16ff7829747 + + For Bionic, the following commits: + + net: ena: fix incorrect usage of memory barriers + net: ena: fix missing calls to READ_ONCE + net: ena: fix missing lock during device destruction + net: ena: fix potential double ena_destroy_device() + net: ena: fix device destruction to gracefully free resources + net: ena: fix driver when PAGE_SIZE == 64kB + net: ena: fix surprise unplug NULL dereference kernel crash + net: ena: Fix use of uninitialized DMA address bits field + UBUNTU: SAUCE: ena: devm_kzalloc() -> devm_kcalloc() + net: ena: Eliminate duplicate barriers on weakly-ordered archs + net: ena: increase ena driver version to 1.5.0 + net: ena: add detection and recovery mechanism for handling missed/misrouted MSI-X + + For Xenial, the following commits: + + net: ena: fix incorrect usage of memory barriers + net: ena: fix missing calls to READ_ONCE + net: ena: fix missing lock during device destruction + net: ena: fix potential double ena_destroy_device() + net: ena: fix device destruction to gracefully free resources + net: ena: fix driver when PAGE_SIZE == 64kB + net: ena: fix surprise unplug NULL dereference kernel crash + net: ena: Fix use of uninitialized DMA address bits field + UBUNTU: SAUCE: ena: devm_kzalloc() -> devm_kcalloc() + net: ena: Eliminate duplicate barriers on weakly-ordered archs + net: ena: fix error handling in ena_down() sequence + net: ena: increase ena driver version to 1.5.0 + net: ena: add detection and recovery mechanism for handling missed/misrouted MSI-X + net: ena: fix race condition between device reset and link up setup + net: ena: increase ena driver version to 1.3.0 + net: ena: add new admin define for future support of IPv6 RSS + net: ena: add statistics for missed tx packets + net: ena: add power management ops to the ENA driver + net: ena: remove legacy suspend suspend/resume support + net: ena: improve ENA driver boot time. + net: ena: fix wrong max Tx/Rx queues on ethtool + net: ena: fix rare kernel crash when bar memory remap fails + net: ena: reduce the severity of some printouts + net: ena: Remove redundant unlikely() + + *Note that some of these were already present in the linux-aws variants + (the remainder will be picked up on their next rebase cycles). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792044 Title: update ENA driver to latest mainline version Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: Update ENA driver to latest mainline version as of this commit: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=0e1f4c76be241377d282e34ebea6d16ff7829747 For Bionic, the following commits: net: ena: fix incorrect usage of memory barriers net: ena: fix missing calls to READ_ONCE net: ena: fix missing lock during device destruction net: ena: fix potential double ena_destroy_device() net: ena: fix device destruction to gracefully free resources net: ena: fix driver when PAGE_SIZE == 64kB net: ena: fix surprise unplug NULL dereference kernel crash net: ena: Fix use of uninitialized DMA address bits field UBUNTU: SAUCE: ena: devm_kzalloc() -> devm_kcalloc() net: ena: Eliminate duplicate barriers on weakly-ordered archs net: ena: increase ena driver version to 1.5.0 net: ena: add detection and recovery mechanism for handling missed/misrouted MSI-X For Xenial, the following commits: net: ena: fix incorrect usage of memory barriers net: ena: fix missing calls to READ_ONCE net: ena: fix missing lock during device destruction net: ena: fix potential double ena_destroy_device() net: ena: fix device destruction to gracefully free resources net: ena: fix driver when PAGE_SIZE == 64kB net: ena: fix surprise unplug NULL dereference kernel crash net: ena: Fix use of uninitialized DMA address bits field UBUNTU: SAUCE: ena: devm_kzalloc() -> devm_kcalloc() net: ena: Eliminate duplicate barriers on weakly-ordered archs net: ena: fix error handling in ena_down() sequence net: ena: increase ena driver version to 1.5.0 net: ena: add detection and recovery mechanism for handling missed/misrouted MSI-X net: ena: fix race condition between device reset and link up setup net: ena: increase ena driver version to 1.3.0 net: ena: add new admin define for future support of IPv6 RSS net: ena: add statistics for missed tx packets net: ena: add power management ops to the ENA driver net: ena: remove legacy suspend suspend/resume support net: ena: improve ENA driver boot time. net: ena: fix wrong max Tx/Rx queues on ethtool
[Kernel-packages] [Bug 1792393] Re: Kernel 4.15.0-35.38 fails to build with CONFIG_XFS_ONLINE_SCRUB enabled
** Changed in: linux-gcp (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1792393
Title:
Kernel 4.15.0-35.38 fails to build with CONFIG_XFS_ONLINE_SCRUB
enabled
Status in linux package in Ubuntu:
Fix Released
Status in linux-gcp package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
In Progress
Status in linux-gcp source package in Bionic:
Fix Committed
Bug description:
SRU Justification:
Impact:
The backport of a78ee256c325 ("xfs: convert XFS_AGFL_SIZE to a helper
function") done as part of "Bionic update: upstream stable patchset 2018-08-24"
(bug 1788897) is incomplete, causing the build to fail if
CONFIG_XFS_ONLINE_SCRUB is selected.
/tmp/kernel-kleber-79aa9f7-Y9dG/build/fs/xfs/scrub/agheader.c: In function
'xfs_scrub_walk_agfl':
/tmp/kernel-kleber-79aa9f7-Y9dG/build/fs/xfs/scrub/agheader.c:96:24: error:
implicit declaration of function 'XFS_AGFL_SIZE'; did you mean 'XFS_ACL_SIZE'?
[-Werror=implicit-function-declaration]
for (i = flfirst; i < XFS_AGFL_SIZE(mp); i++) {
^
XFS_ACL_SIZE
The backport didn't replace all the occurrences of the XFS_AGFL_SIZE
by the xfs_agfl_size function.
Fix:
A SAUCE patch is needed to fix the backport, given that the problem doesn't
exist with mainline.
Testcase:
Enable CONFIG_XFS_ONLINE_SCRUB and compile the kernel.
Note: bionic/linux doesn't have this config option enabled. The only
4.15 kernel with this config is bionic/linux-gcp, so it affects only
this kernel and its backport.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792393/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792419] [NEW] Xenial update to 4.4.155 stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.155 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.155 stable release shall be applied: ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Xenial) Importance: Medium Assignee: Stefan Bader (smb) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Stefan Bader (smb) ** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792419 Title: Xenial update to 4.4.155 stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.155 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.155 stable release shall be applied: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792419/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792044] Re: update ENA driver to latest mainline version
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792044 Title: update ENA driver to latest mainline version Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: Update ENA driver to latest mainline version as of this commit: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=0e1f4c76be241377d282e34ebea6d16ff7829747 For Bionic, the following commits: net: ena: fix incorrect usage of memory barriers net: ena: fix missing calls to READ_ONCE net: ena: fix missing lock during device destruction net: ena: fix potential double ena_destroy_device() net: ena: fix device destruction to gracefully free resources net: ena: fix driver when PAGE_SIZE == 64kB net: ena: fix surprise unplug NULL dereference kernel crash net: ena: Fix use of uninitialized DMA address bits field UBUNTU: SAUCE: ena: devm_kzalloc() -> devm_kcalloc() net: ena: Eliminate duplicate barriers on weakly-ordered archs net: ena: increase ena driver version to 1.5.0 net: ena: add detection and recovery mechanism for handling missed/misrouted MSI-X For Xenial, the following commits: net: ena: fix incorrect usage of memory barriers net: ena: fix missing calls to READ_ONCE net: ena: fix missing lock during device destruction net: ena: fix potential double ena_destroy_device() net: ena: fix device destruction to gracefully free resources net: ena: fix driver when PAGE_SIZE == 64kB net: ena: fix surprise unplug NULL dereference kernel crash net: ena: Fix use of uninitialized DMA address bits field UBUNTU: SAUCE: ena: devm_kzalloc() -> devm_kcalloc() net: ena: Eliminate duplicate barriers on weakly-ordered archs net: ena: fix error handling in ena_down() sequence net: ena: increase ena driver version to 1.5.0 net: ena: add detection and recovery mechanism for handling missed/misrouted MSI-X net: ena: fix race condition between device reset and link up setup net: ena: increase ena driver version to 1.3.0 net: ena: add new admin define for future support of IPv6 RSS net: ena: add statistics for missed tx packets net: ena: add power management ops to the ENA driver net: ena: remove legacy suspend suspend/resume support net: ena: improve ENA driver boot time. net: ena: fix wrong max Tx/Rx queues on ethtool net: ena: fix rare kernel crash when bar memory remap fails net: ena: reduce the severity of some printouts net: ena: Remove redundant unlikely() *Note that some of these were already present in the linux-aws variants (the remainder will be picked up on their next rebase cycles). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791908] Re: uvcvideo: Failed to query (GET_INFO) UVC control 4 on unit 2: -32 (exp. 1).
** Tags added: kernel-bug-exists-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/1791908 Title: uvcvideo: Failed to query (GET_INFO) UVC control 4 on unit 2: -32 (exp. 1). Status in linux package in Ubuntu: Confirmed Bug description: at each boot I see the messages: 10:34:47 kernel: uvcvideo: Failed to query (GET_INFO) UVC control 4 on unit 2: -32 (exp. 1). 10:34:47 kernel: uvcvideo: Failed to query (GET_INFO) UVC control 4 on unit 1: -32 (exp. 1). 10:34:46 kernel: uvcvideo: Failed to query (GET_INFO) UVC control 2 on unit 1: -32 (exp. 1). this happen on a partition running Ubuntu 18.10 kernel 4.18.0-7-generic but not on the partition running Ubuntu 18.04 kernel 4.15.0-34 on same hardware The integrated webcam works fine and i don't have other webcam connected. corrado@corrado-HP-p6-cc-0904:~$ uname -a Linux corrado-HP-p6-cc-0904 4.18.0-7-generic #8-Ubuntu SMP Tue Aug 28 18:24:42 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux corrado@corrado-HP-p6-cc-0904:~$ inxi -Fx System:Host: corrado-HP-p6-cc-0904 Kernel: 4.18.0-7-generic x86_64 bits: 64 compiler: gcc v: 8.2.0 Desktop: Gnome 3.30.0 Distro: Ubuntu 18.10 (Cosmic Cuttlefish) Machine: Type: Laptop System: Hewlett-Packard product: HP 250 G3 Notebook PC v: 0991100600087 serial: Mobo: Hewlett-Packard model: 2211 v: 86.49 serial: UEFI: Insyde v: F.36 date: 12/18/2014 Battery: ID-1: BAT1 charge: 20.9 Wh condition: 20.9/20.9 Wh (100%) model: 13-42 OA03031 status: Full CPU: Topology: Dual Core model: Intel Core i5-4210U bits: 64 type: MT MCP arch: Haswell rev: 1 L2 cache: 3072 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19155 Speed: 1024 MHz min/max: 800/2700 MHz Core speeds (MHz): 1: 1098 2: 1098 3: 1097 4: 1101 Graphics: Device-1: Intel Haswell-ULT Integrated Graphics driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.1 driver: i915 resolution: 1366x768~60Hz OpenGL: renderer: Mesa DRI Intel Haswell Mobile v: 4.5 Mesa 18.1.5 direct render: Yes Audio: Device-1: Intel Haswell-ULT HD Audio driver: snd_hda_intel v: kernel bus ID: 00:03.0 Device-2: Intel 8 Series HD Audio driver: snd_hda_intel v: kernel bus ID: 00:1b.0 Sound Server: ALSA v: k4.18.0-7-generic Network: Device-1: Realtek RTL810xE PCI Express Fast Ethernet driver: r8169 v: 2.3LK-NAPI port: 3000 bus ID: 08:00.0 IF: enp8s0 state: down mac: 5c:b9:01:06:ba:ce Device-2: Ralink RT3290 Wireless 802.11n 1T/1R PCIe driver: rt2800pci v: 2.3.0 bus ID: 09:00.0 IF: wlp9s0f0 state: up mac: ac:d1:b8:82:03:5d Drives:Local Storage: total: 465.76 GiB used: 16.78 GiB (3.6%) ID-1: /dev/sda vendor: Seagate model: ST500LT012-1DG142 size: 465.76 GiB Partition: ID-1: / size: 31.25 GiB used: 5.99 GiB (19.2%) fs: ext4 dev: /dev/sda6 ID-2: swap-1 size: 4.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 Sensors: System Temperatures: cpu: 40.0 C mobo: 40.0 C Fan Speeds (RPM): N/A Info: Processes: 198 Uptime: 17m Memory: 3.79 GiB used: 1.02 GiB (26.9%) Init: systemd runlevel: 5 Compilers: gcc: N/A Shell: bash v: 4.4.19 inxi: 3.0.22 corrado@corrado-HP-p6-cc-0904:~$ --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: corrado2680 F pulseaudio /dev/snd/controlC1: corrado2680 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-09-05 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180903) MachineType: Hewlett-Packard HP 250 G3 Notebook PC Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic root=UUID=451b1d0c-94ef-4cbc-bc70-c33f546fa75e ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 RelatedPackageVersions: linux-restricted-modules-4.18.0-7-generic N/A linux-backports-modules-4.18.0-7-generic N/A linux-firmware1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: cosmic Uname: Linux 4.18.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/18/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.36 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2211 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.49 dmi.chassis.asset.tag:
[Kernel-packages] [Bug 1792392] Re: Xenial update to 4.4.154 stable release
Modified "usb/phy: fix PPC64 build errors in phy-fsl-usb.c". It looks like we already got some protection but using CONFIG_PPC instead of CONFIG_PPC32 which seems pointless as CONFIG_PPC sounds like being set in both 32/64bit cases. Skipped "fscache: Allow cancelled operations to be enqueued" and "cachefiles: Fix refcounting bug in backing-file read monitoring" as they are already applied for bug #1774336. Skipped "cachefiles: Wait rather than BUG'ing on "Unexpected object collision"" as it is already applied for bug #1776254. Skipped "x86/spectre: Add missing family 6 check to microcode check" because this changes the bad microcode check which we have dropped. Skipped "s390/pci: fix out of bounds access during irq setup" because it is already applied for bug #1790480. ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The 4.4.154 upstream stable + patch set is now available. It should be included in the Ubuntu + kernel as well. - 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 4.4.154 upstream stable -patch set is now available. It should be included in the Ubuntu -kernel as well. + git://git.kernel.org/ -git://git.kernel.org/ + TEST CASE: TBD - TEST CASE: TBD - -The following patches from the 4.4.154 stable release shall be - applied: + The following patches from the 4.4.154 stable release shall be applied: + * sched/sysctl: Check user input value of sysctl_sched_time_avg + * Cipso: cipso_v4_optptr enter infinite loop + * vti6: fix PMTU caching and reporting on xmit + * xfrm: fix missing dst_release() after policy blocking lbcast and multicast + * xfrm: free skb if nlsk pointer is NULL + * mac80211: add stations tied to AP_VLANs during hw reconfig + * nl80211: Add a missing break in parse_station_flags + * drm/bridge: adv7511: Reset registers on hotplug + * scsi: libiscsi: fix possible NULL pointer dereference in case of TMF + * drm/imx: imx-ldb: disable LDB on driver bind + * drm/imx: imx-ldb: check if channel is enabled before printing warning + * usb: gadget: r8a66597: Fix two possible sleep-in-atomic-context bugs in + init_controller() + * usb: gadget: r8a66597: Fix a possible sleep-in-atomic-context bugs in + r8a66597_queue() + * usb/phy: fix PPC64 build errors in phy-fsl-usb.c + * tools: usb: ffs-test: Fix build on big endian systems + * usb: gadget: f_uac2: fix endianness of 'struct cntrl_*_lay3' + * tools/power turbostat: fix -S on UP systems + * net: caif: Add a missing rcu_read_unlock() in caif_flow_cb + * qed: Fix possible race for the link state value. + * atl1c: reserve min skb headroom + * net: prevent ISA drivers from building on PPC32 + * can: mpc5xxx_can: check of_iomap return before use + * i2c: davinci: Avoid zero value of CLKH + * media: staging: omap4iss: Include asm/cacheflush.h after generic includes + * bnx2x: Fix invalid memory access in rss hash config path. + * net: axienet: Fix double deregister of mdio + * selftests/ftrace: Add snapshot and tracing_on test case + * zswap: re-check zswap_is_full() after do zswap_shrink() + * tools/power turbostat: Read extended processor family from CPUID + * Revert "MIPS: BCM47XX: Enable 74K Core ExternalSync for PCIe erratum" + * enic: handle mtu change for vf properly + * arc: fix build errors in arc/include/asm/delay.h + * arc: fix type warnings in arc/mm/cache.c + * drivers: net: lmc: fix case value for target abort error + * scsi: fcoe: drop frames in ELS LOGO error path + * scsi: vmw_pvscsi: Return DID_RESET for status SAM_STAT_COMMAND_TERMINATED + * mm/memory.c: check return value of ioremap_prot + * cifs: add missing debug entries for kconfig options + * cifs: check kmalloc before use + * smb3: Do not send SMB3 SET_INFO if nothing changed + * smb3: don't request leases in symlink creation and query + * btrfs: don't leak ret from do_chunk_alloc + * s390/kvm: fix deadlock when killed by oom + * ext4: check for NUL characters in extended attribute's name + * ext4: sysfs: print ext4_super_block fields as little-endian + * ext4: reset error code in ext4_find_entry in fallback + * arm64: mm: check for upper PAGE_SHIFT bits in pfn_valid() + * KVM: arm/arm64: Skip updating PTE entry if no change + * KVM: arm/arm64: Skip updating PMD entry if no change + * x86/speculation/l1tf: Fix overflow in
[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel oops destroying interfaces on i386
There is a 32bit kernel now posted to: http://kernel.ubuntu.com/~jsalisbury/lp1736390 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1736390 Title: openvswitch: kernel oops destroying interfaces on i386 Status in linux package in Ubuntu: In Progress Status in openvswitch package in Ubuntu: Invalid Status in linux source package in Artful: Won't Fix Status in openvswitch source package in Artful: Invalid Status in linux source package in Bionic: In Progress Status in openvswitch source package in Bionic: Invalid Status in linux source package in Cosmic: In Progress Status in openvswitch source package in Cosmic: Invalid Bug description: Reproducable on bionic using the autopkgtest's from openvswitch on i386: [ 41.420568] BUG: unable to handle kernel NULL pointer dereference at (null) [ 41.421000] IP: igmp_group_dropped+0x21/0x220 [ 41.421246] *pdpt = 1d62c001 *pde = [ 41.421659] Oops: [#1] SMP [ 41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse virtio_blk virtio_net pata_acpi floppy [ 41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW 4.13.0-18-generic #21-Ubuntu [ 41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 41.424849] Workqueue: netns cleanup_net [ 41.425071] task: db8fba80 task.stack: dba1 [ 41.425346] EIP: igmp_group_dropped+0x21/0x220 [ 41.425656] EFLAGS: 00010202 CPU: 0 [ 41.425864] EAX: EBX: dd726360 ECX: dba11e6c EDX: 0002 [ 41.426335] ESI: EDI: dd4db500 EBP: dba11dcc ESP: dba11d94 [ 41.426687] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 41.426990] CR0: 80050033 CR2: CR3: 1e6d6d60 CR4: 06f0 [ 41.427340] Call Trace: [ 41.427485] ? __wake_up+0x36/0x40 [ 41.427680] ip_mc_down+0x27/0x90 [ 41.427869] inetdev_event+0x398/0x4e0 [ 41.428082] ? skb_dequeue+0x5b/0x70 [ 41.428286] ? wireless_nlevent_flush+0x4c/0x90 [ 41.428541] notifier_call_chain+0x4e/0x70 [ 41.428772] raw_notifier_call_chain+0x11/0x20 [ 41.429023] call_netdevice_notifiers_info+0x2a/0x60 [ 41.429301] dev_close_many+0x9d/0xe0 [ 41.429509] rollback_registered_many+0xd7/0x380 [ 41.429768] unregister_netdevice_many.part.102+0x10/0x80 [ 41.430075] default_device_exit_batch+0x134/0x160 [ 41.430344] ? do_wait_intr_irq+0x80/0x80 [ 41.430650] ops_exit_list.isra.8+0x4d/0x60 [ 41.430886] cleanup_net+0x18e/0x260 [ 41.431090] process_one_work+0x1a0/0x390 [ 41.431317] worker_thread+0x37/0x450 [ 41.431525] kthread+0xf3/0x110 [ 41.431714] ? process_one_work+0x390/0x390 [ 41.431941] ? kthread_create_on_node+0x20/0x20 [ 41.432187] ret_from_fork+0x19/0x24 [ 41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00 [ 41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94 [ 41.433750] CR2: [ 41.433961] ---[ end trace 595db54cab84070c ]--- system then becomes unresponsive; no further interfaces can be created. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788754] Re: linux-azure: 4.15.0-1023.24~14.04.1 -proposed tracker
** Tags removed: block-proposed block-proposed-trusty ** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1788754 Title: linux-azure: 4.15.0-1023.24~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure 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: 1788744 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/1788754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788623] Re: regression: IPv6 PMTU discovery fails with source-specific routing
Yes, 4.15.0-041500rc1-generic exhibits the 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/1788623 Title: regression: IPv6 PMTU discovery fails with source-specific routing Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: IPv6 PMTU discovery fails when using source-specific routing on Ubuntu 18.04. I have attached a test case called pmtu-sads.sh which is based on tools/testing/selftests/net/pmtu.sh in the linux source. I have verified that the test fails on: Ubuntu 18.04 with 4.15.0-30.32 Ubuntu 18.04 with 4.17.0-041700.201806041953 Ubuntu 18.04 with 4.18.3-041803.201808180530 The test succeeds on Ubuntu 16.04 with 4.4.0.131.137 which makes it a regression. System information: Ubuntu 4.15.0-30.32-generic 4.15.18 Description: Ubuntu 18.04.1 LTS Release: 18.04 See below for a patch which is working for me. I'm currently using linux kernel 4.15.0-32.35 built from git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git with this patch. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-30-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=041f6e1e-4904-4760-8518-3a88dc288556 ro splash quiet vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788754] Re: linux-azure: 4.15.0-1023.24~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => 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/1788754 Title: linux-azure: 4.15.0-1023.24~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure 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: 1788744 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/1788754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791908] Re: uvcvideo: Failed to query (GET_INFO) UVC control 4 on unit 2: -32 (exp. 1).
installed new kernel corrado@corrado-HP-p7-cc-0911:~$ uname -a Linux corrado-HP-p7-cc-0911 4.19.0-041900rc3-generic #201809120832 SMP Wed Sep 12 12:35:08 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux corrado@corrado-HP-p7-cc-0911:~$ problem not fixed ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791908/+attachment/5188485/+files/syslog ** 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/1791908 Title: uvcvideo: Failed to query (GET_INFO) UVC control 4 on unit 2: -32 (exp. 1). Status in linux package in Ubuntu: Confirmed Bug description: at each boot I see the messages: 10:34:47 kernel: uvcvideo: Failed to query (GET_INFO) UVC control 4 on unit 2: -32 (exp. 1). 10:34:47 kernel: uvcvideo: Failed to query (GET_INFO) UVC control 4 on unit 1: -32 (exp. 1). 10:34:46 kernel: uvcvideo: Failed to query (GET_INFO) UVC control 2 on unit 1: -32 (exp. 1). this happen on a partition running Ubuntu 18.10 kernel 4.18.0-7-generic but not on the partition running Ubuntu 18.04 kernel 4.15.0-34 on same hardware The integrated webcam works fine and i don't have other webcam connected. corrado@corrado-HP-p6-cc-0904:~$ uname -a Linux corrado-HP-p6-cc-0904 4.18.0-7-generic #8-Ubuntu SMP Tue Aug 28 18:24:42 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux corrado@corrado-HP-p6-cc-0904:~$ inxi -Fx System:Host: corrado-HP-p6-cc-0904 Kernel: 4.18.0-7-generic x86_64 bits: 64 compiler: gcc v: 8.2.0 Desktop: Gnome 3.30.0 Distro: Ubuntu 18.10 (Cosmic Cuttlefish) Machine: Type: Laptop System: Hewlett-Packard product: HP 250 G3 Notebook PC v: 0991100600087 serial: Mobo: Hewlett-Packard model: 2211 v: 86.49 serial: UEFI: Insyde v: F.36 date: 12/18/2014 Battery: ID-1: BAT1 charge: 20.9 Wh condition: 20.9/20.9 Wh (100%) model: 13-42 OA03031 status: Full CPU: Topology: Dual Core model: Intel Core i5-4210U bits: 64 type: MT MCP arch: Haswell rev: 1 L2 cache: 3072 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19155 Speed: 1024 MHz min/max: 800/2700 MHz Core speeds (MHz): 1: 1098 2: 1098 3: 1097 4: 1101 Graphics: Device-1: Intel Haswell-ULT Integrated Graphics driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.1 driver: i915 resolution: 1366x768~60Hz OpenGL: renderer: Mesa DRI Intel Haswell Mobile v: 4.5 Mesa 18.1.5 direct render: Yes Audio: Device-1: Intel Haswell-ULT HD Audio driver: snd_hda_intel v: kernel bus ID: 00:03.0 Device-2: Intel 8 Series HD Audio driver: snd_hda_intel v: kernel bus ID: 00:1b.0 Sound Server: ALSA v: k4.18.0-7-generic Network: Device-1: Realtek RTL810xE PCI Express Fast Ethernet driver: r8169 v: 2.3LK-NAPI port: 3000 bus ID: 08:00.0 IF: enp8s0 state: down mac: 5c:b9:01:06:ba:ce Device-2: Ralink RT3290 Wireless 802.11n 1T/1R PCIe driver: rt2800pci v: 2.3.0 bus ID: 09:00.0 IF: wlp9s0f0 state: up mac: ac:d1:b8:82:03:5d Drives:Local Storage: total: 465.76 GiB used: 16.78 GiB (3.6%) ID-1: /dev/sda vendor: Seagate model: ST500LT012-1DG142 size: 465.76 GiB Partition: ID-1: / size: 31.25 GiB used: 5.99 GiB (19.2%) fs: ext4 dev: /dev/sda6 ID-2: swap-1 size: 4.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 Sensors: System Temperatures: cpu: 40.0 C mobo: 40.0 C Fan Speeds (RPM): N/A Info: Processes: 198 Uptime: 17m Memory: 3.79 GiB used: 1.02 GiB (26.9%) Init: systemd runlevel: 5 Compilers: gcc: N/A Shell: bash v: 4.4.19 inxi: 3.0.22 corrado@corrado-HP-p6-cc-0904:~$ --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: corrado2680 F pulseaudio /dev/snd/controlC1: corrado2680 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-09-05 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180903) MachineType: Hewlett-Packard HP 250 G3 Notebook PC Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic root=UUID=451b1d0c-94ef-4cbc-bc70-c33f546fa75e ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 RelatedPackageVersions: linux-restricted-modules-4.18.0-7-generic N/A linux-backports-modules-4.18.0-7-generic N/A linux-firmware1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: cosmic Uname: Linux
[Kernel-packages] [Bug 1791756] Re: linux-lts-trusty: 3.13.0-159.209~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-precise ** 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: 1791754 phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1791756 Title: linux-lts-trusty: 3.13.0-159.209~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: 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: 1791754 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1791756/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792195] Re: Signal 7 error when running GPFS tracing in cluster
** 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/1792195 Title: Signal 7 error when running GPFS tracing in cluster Status in linux package in Ubuntu: New Bug description: -- Problem Description -- GPFS mmfsd daemon is mapping shared tracing buffer(allocated from kernel driver using vmalloc) and then writing trace records from user space threads in parallel. While the SIGBUS happened, the access virtual memory address is in the mapped range, no overflow on access. Worked with Benjamin Herrenschmidt on GPFS tracing kernel driver code and he made a suggestion as workaround on the driver code to bypass the problem, and it works the workaround code change as below: - rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, PAGE_SHARED); + rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, __pgprot(pgprot_val(PAGE_SHARED)|_PAGE_DIRTY); As Benjamin mentioned, this is a Linux kernel bug and this is just a workaround. He will give the details about the kernel bug and why this workaround works The root cause is that for PTEs created by a driver at mmap time (ie, that aren't created dynamically at fault time), it's not legit for ptep_set_access_flags() to make them invalid even temporarily. A concurrent access while they are invalid will be unable to service the page fault and will cause as SIGBUS. Thankfully such PTEs shouldn't normally be the subject of a RO->RW privilege escalation. What happens is that the GPFS driver creates the PTEs using remap_pfn_range(...,PAGE_SHARED). PAGE_SHARED has _PAGE_ACCESSED (R) but not _PAGE_DIRTY (C) set. Thus on the first write, we try set C and while doing so, hit the above workaround, which causes the problem described earlier. The proposed patch will ensure we only do the Nest MMU hack when changing _PAGE_RW and not for normal R/C updates. The workaround tested by the GPFS team consists of adding _PAGE_DIRTY to the mapping created by remap_pfn_range() to avoid the RC update fault completely. This is fixed by these: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd0dbb73e01306a1060e56f81e5fe287be936477 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f08d08f3db55452d31ba4a37c702da6245876b96 Since DD1 support is still in (ie, 2bf1071a8d50928a4ae366bb3108833166c2b70c is not applied) the second doesn't apply cleanly. Did you want that attached? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792396] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1792396 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: 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/1792396 Title: Touchpad is not working Status in linux package in Ubuntu: Incomplete Bug description: General information regarding the machine - 1. Model Number - ASUS FX753V 2. Manufacturer - ASUSTek Computer Inc. 3. Symptoms - Soon after giving repairs for flickering screen, when I got the laptop back, I found the touchpad to be completely unresponsive. Attaching an external mouse makes the pointer move, but nothing happens when I touch the touchpad. After browsing through the troubleshooting wiki page (https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo), I am hereby creating a bug report with the files dmesg, devices, and /var/log/Xorg.0.log attached. Hope to see some solutions! Would be really grateful if there any pointers to solve the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792396/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792195] [NEW] Signal 7 error when running GPFS tracing in cluster
You have been subscribed to a public bug: -- Problem Description -- GPFS mmfsd daemon is mapping shared tracing buffer(allocated from kernel driver using vmalloc) and then writing trace records from user space threads in parallel. While the SIGBUS happened, the access virtual memory address is in the mapped range, no overflow on access. Worked with Benjamin Herrenschmidt on GPFS tracing kernel driver code and he made a suggestion as workaround on the driver code to bypass the problem, and it works the workaround code change as below: - rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, PAGE_SHARED); + rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, __pgprot(pgprot_val(PAGE_SHARED)|_PAGE_DIRTY); As Benjamin mentioned, this is a Linux kernel bug and this is just a workaround. He will give the details about the kernel bug and why this workaround works The root cause is that for PTEs created by a driver at mmap time (ie, that aren't created dynamically at fault time), it's not legit for ptep_set_access_flags() to make them invalid even temporarily. A concurrent access while they are invalid will be unable to service the page fault and will cause as SIGBUS. Thankfully such PTEs shouldn't normally be the subject of a RO->RW privilege escalation. What happens is that the GPFS driver creates the PTEs using remap_pfn_range(...,PAGE_SHARED). PAGE_SHARED has _PAGE_ACCESSED (R) but not _PAGE_DIRTY (C) set. Thus on the first write, we try set C and while doing so, hit the above workaround, which causes the problem described earlier. The proposed patch will ensure we only do the Nest MMU hack when changing _PAGE_RW and not for normal R/C updates. The workaround tested by the GPFS team consists of adding _PAGE_DIRTY to the mapping created by remap_pfn_range() to avoid the RC update fault completely. This is fixed by these: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd0dbb73e01306a1060e56f81e5fe287be936477 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f08d08f3db55452d31ba4a37c702da6245876b96 Since DD1 support is still in (ie, 2bf1071a8d50928a4ae366bb3108833166c2b70c is not applied) the second doesn't apply cleanly. Did you want that attached? ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: architecture-ppc64le bot-comment bugnameltc-171273 severity-high targetmilestone-inin1804 -- Signal 7 error when running GPFS tracing in cluster https://bugs.launchpad.net/bugs/1792195 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792396] Re: Touchpad is not working
attaching Xorg.0.log ** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792396/+attachment/5188475/+files/Xorg.0.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792396 Title: Touchpad is not working Status in linux package in Ubuntu: Incomplete Bug description: General information regarding the machine - 1. Model Number - ASUS FX753V 2. Manufacturer - ASUSTek Computer Inc. 3. Symptoms - Soon after giving repairs for flickering screen, when I got the laptop back, I found the touchpad to be completely unresponsive. Attaching an external mouse makes the pointer move, but nothing happens when I touch the touchpad. After browsing through the troubleshooting wiki page (https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo), I am hereby creating a bug report with the files dmesg, devices, and /var/log/Xorg.0.log attached. Hope to see some solutions! Would be really grateful if there any pointers to solve the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792396/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792396] Re: Touchpad is not working
attaching dmesg file ** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792396/+attachment/5188474/+files/dmesg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792396 Title: Touchpad is not working Status in linux package in Ubuntu: Incomplete Bug description: General information regarding the machine - 1. Model Number - ASUS FX753V 2. Manufacturer - ASUSTek Computer Inc. 3. Symptoms - Soon after giving repairs for flickering screen, when I got the laptop back, I found the touchpad to be completely unresponsive. Attaching an external mouse makes the pointer move, but nothing happens when I touch the touchpad. After browsing through the troubleshooting wiki page (https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo), I am hereby creating a bug report with the files dmesg, devices, and /var/log/Xorg.0.log attached. Hope to see some solutions! Would be really grateful if there any pointers to solve the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792396/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792396] [NEW] Touchpad is not working
Public bug reported: General information regarding the machine - 1. Model Number - ASUS FX753V 2. Manufacturer - ASUSTek Computer Inc. 3. Symptoms - Soon after giving repairs for flickering screen, when I got the laptop back, I found the touchpad to be completely unresponsive. Attaching an external mouse makes the pointer move, but nothing happens when I touch the touchpad. After browsing through the troubleshooting wiki page (https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo), I am hereby creating a bug report with the files dmesg, devices, and /var/log/Xorg.0.log attached. Hope to see some solutions! Would be really grateful if there any pointers to solve the issue. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bionic touchpad ** Attachment added: "devices" https://bugs.launchpad.net/bugs/1792396/+attachment/5188473/+files/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792396 Title: Touchpad is not working Status in linux package in Ubuntu: Incomplete Bug description: General information regarding the machine - 1. Model Number - ASUS FX753V 2. Manufacturer - ASUSTek Computer Inc. 3. Symptoms - Soon after giving repairs for flickering screen, when I got the laptop back, I found the touchpad to be completely unresponsive. Attaching an external mouse makes the pointer move, but nothing happens when I touch the touchpad. After browsing through the troubleshooting wiki page (https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo), I am hereby creating a bug report with the files dmesg, devices, and /var/log/Xorg.0.log attached. Hope to see some solutions! Would be really grateful if there any pointers to solve the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792396/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791804] Re: kexec fails with "Unhandled rela relocation: R_X86_64_PLT32"
Bionic is not affected, because this relocation seems to be generated by new binutils. Tested that bionic kexec-tools can load a linux-hwe-edge 4.18 kernel. ** Changed in: kexec-tools (Ubuntu Bionic) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1791804 Title: kexec fails with "Unhandled rela relocation: R_X86_64_PLT32" Status in kexec-tools package in Ubuntu: Fix Committed Status in kexec-tools source package in Bionic: Invalid Status in kexec-tools source package in Cosmic: Fix Committed Bug description: [Impact] Without this fix, kexec won't be able to load kernels on amd64. [Test Case] kexec has been tested to be able to load a 4.18 kernel. [Regression Potential] As the fix is only applied to the x86_64 portion of kexec, only this platform should be affected. Package with fix has been tested there. When running kexec with 4.18, it fails. $ sudo kexec -l /boot/vmlinuz-4.18.0-5-generic --initrd /boot/initrd.img-4.18.0-5-generic --append "`cat /proc/cmdline`" Unhandled rela relocation: R_X86_64_PLT32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1791804/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791719] Re: linux: 4.15.0-35.38 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791719 Title: linux: 4.15.0-35.38 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: 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 1791732 (linux-azure), bug 1791734 (linux-azure), bug 1791737 (linux-azure-edge), bug 1791738 (linux-gcp), bug 1791740 (linux-hwe), bug 1791744 (linux-hwe-edge) derivatives: bug 1791720 (linux-raspi2), bug 1791724 (linux-oem), bug 1791725 (linux-aws), bug 1791726 (linux-azure), bug 1791728 (linux-gcp), bug 1791731 (linux-kvm) kernel-stable-phase:Uploaded kernel-stable-phase-changed:Wednesday, 12. September 2018 11:03 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1791719/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792002] Re: Wireless signal extremely weak or not detected
Likely duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792002 Title: Wireless signal extremely weak or not detected Status in linux package in Ubuntu: Incomplete Bug description: Hi Support, I'm Linux Mint newbie started using from LM v18. I'm using HP245 series laptop with AMD A6-7310 APU & Wifi driver Realtek RTL8723BE. Currently I've migrated from Linux 18 (Sylvia) to Linux 19 (Tara) abt a month ago. I'm facing a WiFi signal problem whenever I've tried to upgrade to Kernel v4.15.0.33 or v4.15.0.34. The Wifi signal strength is either very weak & disconnects frequently or cannot be detected from very small distances (3-5 mtr). I've never had this issue till kernel v4.15.0.32 and everything was working fine and currently I had to downgrade or revert back to 4.15.0.32 again in order to receive signal to write this mail. Kindly resolve this error ASAP as I want to upgrade to the latest version. Regards, Joseph To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792002/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792393] [NEW] Kernel 4.15.0-35.38 fails to build with CONFIG_XFS_ONLINE_SCRUB enabled
Public bug reported:
SRU Justification:
Impact:
The backport of a78ee256c325 ("xfs: convert XFS_AGFL_SIZE to a helper
function") done as part of "Bionic update: upstream stable patchset 2018-08-24"
(bug 1788897) is incomplete, causing the build to fail if
CONFIG_XFS_ONLINE_SCRUB is selected.
/tmp/kernel-kleber-79aa9f7-Y9dG/build/fs/xfs/scrub/agheader.c: In function
'xfs_scrub_walk_agfl':
/tmp/kernel-kleber-79aa9f7-Y9dG/build/fs/xfs/scrub/agheader.c:96:24: error:
implicit declaration of function 'XFS_AGFL_SIZE'; did you mean 'XFS_ACL_SIZE'?
[-Werror=implicit-function-declaration]
for (i = flfirst; i < XFS_AGFL_SIZE(mp); i++) {
^
XFS_ACL_SIZE
The backport didn't replace all the occurrences of the XFS_AGFL_SIZE by
the xfs_agfl_size function.
Fix:
A SAUCE patch is needed to fix the backport, given that the problem doesn't
exist with mainline.
Testcase:
Enable CONFIG_XFS_ONLINE_SCRUB and compile the kernel.
Note: bionic/linux doesn't have this config option enabled. The only
4.15 kernel with this config is bionic/linux-gcp, so it affects only
this kernel and its backport.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: linux-gcp (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: In Progress
** Affects: linux-gcp (Ubuntu Bionic)
Importance: Undecided
Status: In Progress
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: linux (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu)
Status: Invalid => Fix Released
** Also affects: linux-gcp (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => In Progress
** Changed in: linux-gcp (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux-gcp (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1792393
Title:
Kernel 4.15.0-35.38 fails to build with CONFIG_XFS_ONLINE_SCRUB
enabled
Status in linux package in Ubuntu:
Fix Released
Status in linux-gcp package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
In Progress
Status in linux-gcp source package in Bionic:
In Progress
Bug description:
SRU Justification:
Impact:
The backport of a78ee256c325 ("xfs: convert XFS_AGFL_SIZE to a helper
function") done as part of "Bionic update: upstream stable patchset 2018-08-24"
(bug 1788897) is incomplete, causing the build to fail if
CONFIG_XFS_ONLINE_SCRUB is selected.
/tmp/kernel-kleber-79aa9f7-Y9dG/build/fs/xfs/scrub/agheader.c: In function
'xfs_scrub_walk_agfl':
/tmp/kernel-kleber-79aa9f7-Y9dG/build/fs/xfs/scrub/agheader.c:96:24: error:
implicit declaration of function 'XFS_AGFL_SIZE'; did you mean 'XFS_ACL_SIZE'?
[-Werror=implicit-function-declaration]
for (i = flfirst; i < XFS_AGFL_SIZE(mp); i++) {
^
XFS_ACL_SIZE
The backport didn't replace all the occurrences of the XFS_AGFL_SIZE
by the xfs_agfl_size function.
Fix:
A SAUCE patch is needed to fix the backport, given that the problem doesn't
exist with mainline.
Testcase:
Enable CONFIG_XFS_ONLINE_SCRUB and compile the kernel.
Note: bionic/linux doesn't have this config option enabled. The only
4.15 kernel with this config is bionic/linux-gcp, so it affects only
this kernel and its backport.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792393/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791719] Re: linux: 4.15.0-35.38 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791719 Title: linux: 4.15.0-35.38 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: 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 1791732 (linux-azure), bug 1791734 (linux-azure), bug 1791737 (linux-azure-edge), bug 1791738 (linux-gcp), bug 1791740 (linux-hwe), bug 1791744 (linux-hwe-edge) derivatives: bug 1791720 (linux-raspi2), bug 1791724 (linux-oem), bug 1791725 (linux-aws), bug 1791726 (linux-azure), bug 1791728 (linux-gcp), bug 1791731 (linux-kvm) kernel-stable-phase:Uploaded kernel-stable-phase-changed:Wednesday, 12. September 2018 11:03 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1791719/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792387] Re: Single arch and single flavour kernels ship an unordered config file
Patch: https://lists.ubuntu.com/archives/kernel- team/2018-September/095430.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/1792387 Title: Single arch and single flavour kernels ship an unordered config file 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 Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: Single arch and single flavour kernels, such as the cloud kernels, are currently shipping a config file (that is installed under /boot) that is not properly ordered as the ones generated the master kernels. The problem occurs because `make silendoldconfig` in "debian/rules.d/2 -binary-arch.mk" does not re-writes the config file (and thus does not sort it) when no changes are made. Although cloud kernels and other custom kernels are affected, the master kernels are the correct place to fix the problem. The custom kernels will inherit the fix automatically when rebased. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792387/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791746] Re: linux-aws: 4.4.0-1030.33 -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/1791746 Title: linux-aws: 4.4.0-1030.33 -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: 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-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: 1791745 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/1791746/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789131] Re: Probable regression with EXT3 file systems and CVE-2018-1093 patches
I can confirm that the kernel 3.13.0-159-generic from trusty-proposed
solves the problem.
** Tags removed: verification-needed-trusty
** Tags added: verification-done-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/1789131
Title:
Probable regression with EXT3 file systems and CVE-2018-1093 patches
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Trusty:
Fix Committed
Bug description:
== SRU Justification ==
Mainline commit 7dac4a1726a9 introduced a regression in v4.17-rc1, which
made it's way into Trusty via upstream stable updates. This regression
is resolved by mainline commit 22be37acce25. This commit has been cc'd
to upstream stable, but has not made it's way into Trusty as of yet.
== Fix ==
22be37acce25 ("ext4: fix bitmap position validation")
== Regression Potential ==
Low. This commit has been cc'd to upstream stable, so it has had
additional upstream review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
A customer reported on all of their ext3 and none of their ext4
systems that the file system was in read-only mode, I believe after
rebooting into 3.13.0-157.207 from 3.13.0-156.206. Here is the output
of tune2fs -l for one of the file systems:
tune2fs 1.42.12 (29-Aug-2014)
Last mounted on: /
Filesystem UUID: 748f503a-443d-4769-8dd2-45ff46b48555
Filesystem magic number: 0xEF53
Filesystem revision #:1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index
filetype needs_recovery sparse_super large_file
Filesystem flags: signed_directory_hash
Default mount options:(none)
Filesystem state: clean with errors
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 1966080
Block count: 7863296
Reserved block count: 393164
Free blocks: 4568472
Free inodes: 1440187
First block: 0
Block size: 4096
Fragment size:4096
Reserved GDT blocks: 1022
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
RAID stride: 128
RAID stripe width:512
Filesystem created: Thu Feb 25 21:54:24 2016
Last mount time: Fri Aug 24 07:40:51 2018
Last write time: Fri Aug 24 07:40:51 2018
Mount count: 1
Maximum mount count: 25
Last checked: Fri Aug 24 07:38:54 2018
Check interval: 15552000 (6 months)
Next check after: Wed Feb 20 07:38:54 2019
Lifetime writes: 7381 GB
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode:8
Default directory hash: half_md4
Directory Hash Seed: d6564a54-cd2a-4804-ad94-1e4e0e47933a
Journal backup: inode blocks
FS Error count: 210
First error time: Fri Aug 24 07:40:51 2018
First error function: ext4_validate_block_bitmap
First error line #: 376
First error inode #: 0
First error block #: 0
Last error time: Sun Aug 26 19:35:16 2018
Last error function: ext4_remount
Last error line #:4833
Last error inode #: 0
Last error block #: 0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789131/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790480] Re: random oopses on s390 systems using NVMe devices
adjusting tags according to comment #8 ** 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/1790480 Title: random oopses on s390 systems using NVMe devices Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: == SRU Justification == IBM is requesting a fix for the following issue found with NVMe devices on s390x: The trigger is a PCI function whose driver requests more interrupts than the architectural maximum. Currently this is only possible with a machine that supports 64 CPUs (or more) with a NVMe function attached. Note that the LPAR does not have to use >=64 CPUs since the NVMe driver uses num_possible_cpus() which is resolved to the machine maximum on s390 (since all CPUs are hot-pluggable). The oops happens after the driver calls pci_alloc_irq_vectors during device probing - so most likely the system will panic during boot. The fix has been cc'ed to stable@, but hasn't been picked up for Bionic yet. == Fix == 866f3576a72b s390/pci: fix out of bounds access during irq setup == Regression Potential == Low. Affects only s390x systems with more than 64 cpus and NVMe function enabled. == Test case == Boot the kernel in an affected environment. === Original bug description === Random oopses on s390 systems using NVMe and running the Ubuntu 18.04.1 kernel have been reported. Bisect of the upstream kernel points to: 16ccfff28976 nvme: pci: pass max vectors as num_possible_cpus() to pci_alloc_irq_vectors This commit is correct but reveals a bug in s390s IRQ setup routine. A fix is available fixed via: Commit-ID : 866f3576a72b2233a76dffb80290f8086dc49e17 Need also be applied for Ubuntu 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1790480/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792392] [NEW] Xenial update to 4.4.154 stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.154 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.154 stable release shall be applied: ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Xenial) Importance: Medium Assignee: Stefan Bader (smb) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Stefan Bader (smb) ** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792392 Title: Xenial update to 4.4.154 stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.154 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.154 stable release shall be applied: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792392/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792100] Re: Boot hangs at "loading initial ramdisk..."
The linux-headers package shouldn't be needed to test for this bug. You should only need to install the linux-modules, linux-modules-extra and linux-image-unsigned .deb packages. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792100 Title: Boot hangs at "loading initial ramdisk..." Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: I cannot load a kernel beyond 4.15.0-32-generic on my machine. Both 4.15.0-33-generic and 4.15.0-34-generic hang at "loading initial ramdisk...". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kms2233 F pulseaudio /dev/snd/controlC1: kms2233 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Sep 12 10:52:00 2018 HibernationDevice: RESUME=UUID=c3d34d19-9e9e-4967-ac45-f1d699cf5eef InstallationDate: Installed on 2018-01-05 (249 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Dell Inc. Precision Tower 7810 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=90d43be7-a2f7-4500-8b88-9bd7a549d96d ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-05-02 (132 days ago) dmi.bios.date: 06/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A27 dmi.board.name: 0KJCC5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA27:bd06/25/2018:svnDellInc.:pnPrecisionTower7810:pvr:rvnDellInc.:rn0KJCC5:rvrA00:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 7810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792100/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792215] Re: watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [kworker/2:2:271]
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc3 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** 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/1792215 Title: watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [kworker/2:2:271] Status in linux package in Ubuntu: Incomplete Bug description: System will not load desktop graphical display after entering login details at the login screen. Only way to launch GUI is to drop to a terminal at the login screen and then run startx at which point the GUI does load up ProblemType: KernelOops DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-7-generic 4.18.0-7.8 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1567 F pulseaudio ck429 2554 F pulseaudio Date: Wed Sep 12 20:23:02 2018 Failure: oops InstallationDate: Installed on 2018-09-12 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) MachineType: HP HP ENVY Laptop 13-ah0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-7-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [kworker/2:2:271] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8482 dmi.board.vendor: HP dmi.board.version: 69.28 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/07/2018:svnHP:pnHPENVYLaptop13-ah0xxx:pvrType1ProductConfigId:rvnHP:rn8482:rvr69.28:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ah0xxx dmi.product.sku: 4EY21EA#ABU dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792215/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1709889] Re: Ubuntu 18.04: Bug in cfq scheduler, I/Os do not get submitted to adapter for a very long time.
After discussion with Michael Ranweiler, moving to medium.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1709889
Title:
Ubuntu 18.04: Bug in cfq scheduler, I/Os do not get submitted to
adapter for a very long time.
Status in Linux:
Unknown
Status in The Ubuntu-power-systems project:
Triaged
Status in linux package in Ubuntu:
New
Status in linux source package in Zesty:
Won't Fix
Status in linux source package in Bionic:
Triaged
Bug description:
---Problem Description---
When running stress test, sometimes seeing IO hung in dmesg or seeing "Host
adapter abort request" error.
---Steps to Reproduce---
There are two ways to re-create the issues:
(1)running HTX, you will see IO timeout backtrace in dmesg in several hours
(2)running some IO test, then reboot system, repeat this two steps, it takes
long time to re-create the issue.
---uname output---
4.10.0-11-generic
The bulk of the effort for this issue is currently being worked in
MicroSemi's JIRA https://jira.pmcs.com/browse/ESDIBMOP-133.
Ran an interesting test: Ran HTX until I started getting the "stall"
messages on the console, then shutdown HTX and examined the I/O
counters for the tested disks in sysfs:
root@bostonp15:~# for i in
/sys/devices/pci0003:00/0003:00:00.0/0003:01:00.0/host0/target0:2:[2345]/0:2:[2345]:0;
do echo ${i##*/} $(<${i}/iorequest_cnt) $(<${i}/iodone_cnt); done
0:2:2:0 0x5eba3d 0x5eba3d
0:2:3:0 0x773cc9 0x773cc9
0:2:4:0 0x782c61 0x782c61
0:2:5:0 0x5ca134 0x5ca134
root@bostonp15:~#
So, none of the disks showed any evidence of having lost an I/O. I
then restarted HTX and aside from having to manually restart one of
the disks, see no problems with the testing. It appears that what was
"hung" was purely in userland.
This does not absolve the kernel or aacraid driver from blame, but it
shows that the OS "believes" that it completed the I/O and thus
removed it from the queue. What we don't know is whether the OS truly
notified HTX about the completion, or if HTX (or userland libraries)
just failed to process the notification.
Tests are running again, will see what happens next.
Update from JIRA:
I have run some more experiments. Not sure what it tells us, but
here's what I've seen.
First test, ran until I got kernel messages about stalled tasks, then
shutdown HTX. After HTX was down, I checked the above mentioned
counters and found that on each disk iorequest_cnt matched iodone_cnt.
The disks were usable and I could restart HTX. This suggests that the
problem is not in the PM8069 firmware, and makes the case for the
aacraid driver having a bug somewhat weaker. However, this merely says
that the driver "completed" the I/O as far as the kernel is concerned,
not that a completion rippled back to the application.
I restarted HTX and have run until errors. This time, I am leaving HTX
running and observing. Two of the disks reached the HTX error
threshold and the testers stopped (those 2 disks are now idle).
Another disks saw errors but then stopped and appears to be running
fine now. The last disk has not seen any errors (yet). On the two idle
(errored-out) disks I see iorequest_cnt matches iodone_cnt. I am able
to "terminate and restart" the two idle disks and HTX appears to be
testing them again "normally". Note that no reboot was required,
further supporting the evidence that, as far as the kernel is
concerned, there is nothing wrong with the disks and their I/O paths.
So, I don't believe this completely eliminates aacraid from the
picture, especially given we don't see this behavior on other
systems/drivers. But, it probably moves the focus of the investigation
away form the adapter firmware.
Tried build upstream 4.11 kernel on Ubuntu. This still gets the hangs.
Both Ubuntu 4.10 and upstream 4.11 have aacraid driver
1.2.1[50792]-custom.
Good new/bad news... While doing an initial evaluation of the LSI-3008
SAS HBA on Boston and Ubuntu 17.04, I am hitting this same problem.
So, it appears to have nothing specific to do with the PM8069 or
aacraid driver.
Some notes on reproduce this. I have been using the github release of
HTX, built using the following steps:
1. apt install make gcc g++ git libncurses5-dev libcxl-dev libdapl-dev
(others may be required)
2. git clone https://github.com/open-power/HTX
3. cd HTX
4. make
5. make deb
Then install the resulting "htxubuntu.deb" package.
Note, HTX will not test disks that have a filesystem or OS installed,
so there must be at least two disks made available to HTX by clearing
any previous data. A partition table is optional, in my testing I have
none.
Also, it may be desirable to run HTX somewhere other than the console,
leaving the console free to watch for messages.
To run:
A. su - htx
[Kernel-packages] [Bug 1792349] Re: Memory leaking when running kubernetes cronjobs
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc3 ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792349 Title: Memory leaking when running kubernetes cronjobs Status in linux package in Ubuntu: Confirmed Bug description: We are using Kubernetes V1.8.15 with docker 18.03.1-ce. We schedule 50 Kubernetes cronjobs to run every 5 minutes. Each cronjob will create a simple busybox container, echo hello world, then terminate. In the data attached to the bug I let this run for 1 hour, and in this time the Available memory had reduced from 31256704 kB to 30461224 kB - so a loss of 776 MB. From previous longer runs we observe the available memory continues to drop. There doesn't appear to be any processes left behind, or any growth in any other processes to explain where the memory has gone. echo 3 > /proc/sys/vm/drop_caches causes some of the memory to be returned, but the majority remains leaked, and the only way to free it appears to be to reboot the system. We are currently running Ubuntu 4.15.0-32.35-generic 4.15.18 and have previously observed similar issues on Ubuntu 16.04 with Kernel 4.4.0-89-generic #112-Ubuntu SMP Mon Jul 31 19:38:41 UTC 2017 and Debian 9.4 running 4.9.0-6-amd64 #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02) The leak was more severe on the Debian system, and investigations there showed leaks in pcpu_get_vm_areas and were related to memory cgroups. Running with Kernel 4.17 on debian showed a leak at a similar rate to what we now observe on Ubuntu 18. This leak causes us issues as we need to run the cronjobs regularly and want the systems to remain up for months. Kubernetes will create a new cgroup each time the cronjob runs, but these are removed when the job completes (which takes a few seconds). If I use systemd-cgtop I don't see any increase in cgroups over time - but if I monitor /proc/cgroups over time I can see num_cgroups for memory increases. For the duration of the test I collected slabinfo, meminfo, vmallocinfo & cgroups - which I will attach to the bug. Each file is suffixed with the number of seconds since the start. *.0 & *.600 were taken before the test was started. The test was stopped shortly after the *.4200 files were generated. I then left the system idle for 10 minutes. I then ran echo 3 > /proc/sys/vm/drop_caches after *.4800 was generated. This seemed to free ~240MB - but this still leaves ~500MB lost. I then left the system idle for a further 20 minutes, and MemoryAvailable didn't seem to be increasing significantly. Note, the data attached is from running on kernel 4.18.7-041807-generic #201809090930 SMP Sun Sep 9 09:33:16 UTC 2018 (which I ran to verify the issue still exists in latest kernel) - however I was unable to run ubuntu-bug linux on this kernel as it complained about: *** Problem in linux-image-4.18.7-041807-generic The problem cannot be reported: This report is about a package that is not installed. So I switched back to 4.15.0-32.35-generic to raise the bug. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-32-generic 4.15.0-32.35 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 08:55 seq crw-rw 1 root audio 116, 33 Sep 13 08:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Thu Sep 13 08:55:46 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Xen HVM domU PciMultimedia: ProcEnviron: LANG=C.UTF-8 SHELL=/bin/bash TERM=xterm PATH=(custom, no user) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-32-generic root=UUID=6a84f0e4-8522-41cd-8ecb-d4a6fbecef8a ro earlyprintk RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A
[Kernel-packages] [Bug 1792102] Re: Ubuntu18.04: GPU total memory is reduced
I built a test kernel with commit 7acf50e4efa6. The test kernel can be
downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1792102
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/1792102
Title:
Ubuntu18.04: GPU total memory is reduced
Status in The Ubuntu-power-systems project:
Triaged
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
== Comment: #0 - Michael Ranweiler - 2018-09-10
19:26:14 ==
Due to a recent change for powernv, now the total GPU memory is no
longer available. This impacts performance for any
application/benchmark has a large GPU memory utilization.
Previous amount of memory : 16128MiB
Current amount of available memory : 15360MiB
From Anton, describing the recent change.:
powerpc/powernv: Increase memory block size to 1GB on radix
Memory hot unplug on PowerNV radix hosts is broken. Our memory block
size is 256MB but since we map the linear region with very large
pages, each pte we tear down maps 1GB.
A hot unplug of one 256MB memory block results in 768MB of memory
getting unintentionally unmapped. At this point we are likely to oops.
Fix this by increasing our memory block size to 1GB on PowerNV radix
hosts.
Fixes: 4b5d62ca17a1 ("powerpc/mm: add radix__remove_section_mapping()")
This is fixed with:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7acf50e4efa6
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1792102/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1709889] Re: Ubuntu 18.04: Bug in cfq scheduler, I/Os do not get submitted to adapter for a very long time.
** Changed in: ubuntu-power-systems
Importance: Critical => Medium
** Changed in: linux (Ubuntu)
Importance: Critical => Medium
** Changed in: linux (Ubuntu Zesty)
Importance: Critical => Medium
** Changed in: linux (Ubuntu Bionic)
Importance: Critical => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1709889
Title:
Ubuntu 18.04: Bug in cfq scheduler, I/Os do not get submitted to
adapter for a very long time.
Status in Linux:
Unknown
Status in The Ubuntu-power-systems project:
Triaged
Status in linux package in Ubuntu:
New
Status in linux source package in Zesty:
Won't Fix
Status in linux source package in Bionic:
Triaged
Bug description:
---Problem Description---
When running stress test, sometimes seeing IO hung in dmesg or seeing "Host
adapter abort request" error.
---Steps to Reproduce---
There are two ways to re-create the issues:
(1)running HTX, you will see IO timeout backtrace in dmesg in several hours
(2)running some IO test, then reboot system, repeat this two steps, it takes
long time to re-create the issue.
---uname output---
4.10.0-11-generic
The bulk of the effort for this issue is currently being worked in
MicroSemi's JIRA https://jira.pmcs.com/browse/ESDIBMOP-133.
Ran an interesting test: Ran HTX until I started getting the "stall"
messages on the console, then shutdown HTX and examined the I/O
counters for the tested disks in sysfs:
root@bostonp15:~# for i in
/sys/devices/pci0003:00/0003:00:00.0/0003:01:00.0/host0/target0:2:[2345]/0:2:[2345]:0;
do echo ${i##*/} $(<${i}/iorequest_cnt) $(<${i}/iodone_cnt); done
0:2:2:0 0x5eba3d 0x5eba3d
0:2:3:0 0x773cc9 0x773cc9
0:2:4:0 0x782c61 0x782c61
0:2:5:0 0x5ca134 0x5ca134
root@bostonp15:~#
So, none of the disks showed any evidence of having lost an I/O. I
then restarted HTX and aside from having to manually restart one of
the disks, see no problems with the testing. It appears that what was
"hung" was purely in userland.
This does not absolve the kernel or aacraid driver from blame, but it
shows that the OS "believes" that it completed the I/O and thus
removed it from the queue. What we don't know is whether the OS truly
notified HTX about the completion, or if HTX (or userland libraries)
just failed to process the notification.
Tests are running again, will see what happens next.
Update from JIRA:
I have run some more experiments. Not sure what it tells us, but
here's what I've seen.
First test, ran until I got kernel messages about stalled tasks, then
shutdown HTX. After HTX was down, I checked the above mentioned
counters and found that on each disk iorequest_cnt matched iodone_cnt.
The disks were usable and I could restart HTX. This suggests that the
problem is not in the PM8069 firmware, and makes the case for the
aacraid driver having a bug somewhat weaker. However, this merely says
that the driver "completed" the I/O as far as the kernel is concerned,
not that a completion rippled back to the application.
I restarted HTX and have run until errors. This time, I am leaving HTX
running and observing. Two of the disks reached the HTX error
threshold and the testers stopped (those 2 disks are now idle).
Another disks saw errors but then stopped and appears to be running
fine now. The last disk has not seen any errors (yet). On the two idle
(errored-out) disks I see iorequest_cnt matches iodone_cnt. I am able
to "terminate and restart" the two idle disks and HTX appears to be
testing them again "normally". Note that no reboot was required,
further supporting the evidence that, as far as the kernel is
concerned, there is nothing wrong with the disks and their I/O paths.
So, I don't believe this completely eliminates aacraid from the
picture, especially given we don't see this behavior on other
systems/drivers. But, it probably moves the focus of the investigation
away form the adapter firmware.
Tried build upstream 4.11 kernel on Ubuntu. This still gets the hangs.
Both Ubuntu 4.10 and upstream 4.11 have aacraid driver
1.2.1[50792]-custom.
Good new/bad news... While doing an initial evaluation of the LSI-3008
SAS HBA on Boston and Ubuntu 17.04, I am hitting this same problem.
So, it appears to have nothing specific to do with the PM8069 or
aacraid driver.
Some notes on reproduce this. I have been using the github release of
HTX, built using the following steps:
1. apt install make gcc g++ git libncurses5-dev libcxl-dev libdapl-dev
(others may be required)
2. git clone https://github.com/open-power/HTX
3. cd HTX
4. make
5. make deb
Then install the resulting "htxubuntu.deb" package.
Note, HTX will not test disks that have a filesystem or OS installed,
so there must be at least two disks made available to HTX by clearing
any
[Kernel-packages] [Bug 1792383] Re: Xenial update to 4.4.153 stable release
Skipped "x86/mm/pat: Fix L1TF stable backport for CPA" because that would only be required if we had reverted "86/mm/pat: Ensure cpa->pfn only contains page frame numbers" which upstream stable did in 4.4.104 but we did not. By sheer luck this failed to apply because of incorrect use of tabs and spaces in our version. Not sure what the issues were which led to the revert but if we ever have to we also need to pick up this one. Manual adaption of "ovl: Ensure upper filesystem supports d_type" due to delta introduced by "UBUNTU: SAUCE: overlay: add backwards compatible overlayfs format support V4". ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The 4.4.153 upstream stable + patch set is now available. It should be included in the Ubuntu + kernel as well. - 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 4.4.153 upstream stable -patch set is now available. It should be included in the Ubuntu -kernel as well. + git://git.kernel.org/ -git://git.kernel.org/ + TEST CASE: TBD - TEST CASE: TBD - -The following patches from the 4.4.153 stable release shall be - applied: + The following patches from the 4.4.153 stable release shall be applied: + * x86/mm: Fix use-after-free of ldt_struct + * ovl: Ensure upper filesystem supports d_type + * ovl: Do d_type check only if work dir creation was successful + * ovl: warn instead of error if d_type is not supported + * Linux 4.4.153 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792383 Title: Xenial update to 4.4.153 stable release Status in linux package in Ubuntu: New Status in linux source package in Xenial: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.153 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.153 stable release shall be applied: * x86/mm: Fix use-after-free of ldt_struct * ovl: Ensure upper filesystem supports d_type * ovl: Do d_type check only if work dir creation was successful * ovl: warn instead of error if d_type is not supported * Linux 4.4.153 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792383/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792387] [NEW] Single arch and single flavour kernels ship an unordered config file
Public bug reported: Single arch and single flavour kernels, such as the cloud kernels, are currently shipping a config file (that is installed under /boot) that is not properly ordered as the ones generated the master kernels. The problem occurs because `make silendoldconfig` in "debian/rules.d/2 -binary-arch.mk" does not re-writes the config file (and thus does not sort it) when no changes are made. Although cloud kernels and other custom kernels are affected, the master kernels are the correct place to fix the problem. The custom kernels will inherit the fix automatically when rebased. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Marcelo Cerri (mhcerri) Status: In Progress ** Affects: linux (Ubuntu Trusty) Importance: Undecided Assignee: Marcelo Cerri (mhcerri) Status: In Progress ** Affects: linux (Ubuntu Xenial) Importance: Undecided Assignee: Marcelo Cerri (mhcerri) Status: In Progress ** Affects: linux (Ubuntu Bionic) Importance: Undecided Assignee: Marcelo Cerri (mhcerri) Status: In Progress ** Affects: linux (Ubuntu Cosmic) Importance: Undecided Assignee: Marcelo Cerri (mhcerri) Status: In Progress ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Trusty) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Cosmic) Status: New => In Progress ** Changed in: linux (Ubuntu Trusty) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Changed in: linux (Ubuntu Cosmic) Assignee: (unassigned) => Marcelo Cerri (mhcerri) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792387 Title: Single arch and single flavour kernels ship an unordered config file 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 Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: Single arch and single flavour kernels, such as the cloud kernels, are currently shipping a config file (that is installed under /boot) that is not properly ordered as the ones generated the master kernels. The problem occurs because `make silendoldconfig` in "debian/rules.d/2 -binary-arch.mk" does not re-writes the config file (and thus does not sort it) when no changes are made. Although cloud kernels and other custom kernels are affected, the master kernels are the correct place to fix the problem. The custom kernels will inherit the fix automatically when rebased. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792387/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792383] [NEW] Xenial update to 4.4.153 stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.153 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.153 stable release shall be applied: ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Xenial) Importance: Medium Assignee: Stefan Bader (smb) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Stefan Bader (smb) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792383 Title: Xenial update to 4.4.153 stable release Status in linux package in Ubuntu: New Status in linux source package in Xenial: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.153 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.153 stable release shall be applied: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792383/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
