[Kernel-packages] [Bug 1760545] Re: [18.04] GLK hang after a while
Thanks! Is there a timeline for wen this new linux-generic kernel may be released for 18.04 / 4.15.x? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1760545 Title: [18.04] GLK hang after a while Status in linux package in Ubuntu: In Progress Status in linux-oem package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Released Bug description: SRU Justification [Impact] i915 lacks information about the glk_dmc_ver1_04.bin firmware file in modinfo, so it is not included in the initrd along with the i915 driver. Thus the firmware does not get loaded. Loading the firmware is said to prevent a hang. In addition to that, this also causes GLK's HDMI audio codec stops working after S3. [Fix] Add a MODULE_FIRMWARE statement for the firmware. This information is required to let initramfs-tools includes the firmware. [Test Case] Without the firmware there will be a "Direct firmware load for i915/glk_dmc_ver1_04.bin failed with error -2" line in dmesg. With the firmware there is no such message. I can confirm the GLK HDMI audio issue is gone when firmware is loaded. [Regression Potential] Minimal. Will only be loaded by i915 for specific hardware, and loading the firmware is known to fix a hang. --- Description: Platform information: Label: GLK02SDP Processor: Silver N5000 Bios: GELKRVPA.X64.0083.B30.1801162142 OS: Ubuntu 18.04 Kernel: 4.15.0-10-generic Details: Power on, and enter into the system; After a period, sometimes about 20 minutes, sometimes 1 hour, the machine will hang. We can only power it off manually, then power on to enter into OS again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760545/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795453] Re: IO's are issued with incorrect Scatter Gather Buffer
The 63bit dma_mask was just a test to understand the adress-wraparound by the fw. Nothing specific. PERC didn't go offline. Always ended up with OOM btw. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1795453 Title: IO's are issued with incorrect Scatter Gather Buffer Status in linux package in Ubuntu: Confirmed Bug description: We have observed that OS is sending the IO's (SCSI Read/Write) with incorrect Scatter Gather Buffer address . i.e OS is sending the IO with 64 bit Scatter Gather Buffer address , such that if we add the length with buffer address then it causes the roll over . Here is the data we captured in our driver (Printed the SGE details which was sent by OS) sgl_ptr->Address = f000 [14547.313240] sgl_ptr->Length = 1000 [14547.313241] sge_count = 18 [14547.313242] cmd->index = 9d9 Note : This issue is observed only when virtualization is enabled Product : Broadcom (LSI) Megaraid H840 controller --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 12 16:35 seq crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R7415 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.18.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 09/07/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.2 dmi.board.vendor: Dell Inc. dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R7415 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R7415 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 12 16:35 seq crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R7415 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.18.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 09/07/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.2 dmi.board.vendor: Dell Inc. dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R7415 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R7415 dmi.sys.vendor: Dell Inc. --- ProblemType:
[Kernel-packages] [Bug 1743027] Re: error loading realtime clock since upgrading to 17.10
Within the 4 computer I have running Ubuntu, only one, my Toshiba Satellite Laptop with the current 4.15 Kernels available from the Ubuntu 16.04.5 and 18.04.1 Repositories fails to create the /dev/rtc device... NOTE: The 3 other Ubuntu Machine are not effected by this CONFIG_WDAT_WDT Bug... Downgrading to the current Generic 4.4 Kernel from the Ubuntu 16.04.5 Repository is one Solution... Another Solution is the 4.18 Kernel currently available from Ubuntu the 18.10 Repository!!! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1743027 Title: error loading realtime clock since upgrading to 17.10 Status in linux package in Ubuntu: Confirmed Bug description: (originally asked over at askubuntu.com, but is still unresolved: https://askubuntu.com/questions/971349/problem-with-real-time-clock- since-upgrading-to-ubuntu-17-10) I recently upgraded from Ubuntu 17.04 to Ubuntu 17.10 using the software update process. The update completed without any errors, and Ubuntu 17.10 is now running without any major issues. However, I was running a script previously that uses rtcwake which has since stopped working. The script automatically hibernates my laptop after a set period of time in sleep mode, and was working perfectly in Ubuntu 17.04. In the process of troubleshooting, I discovered that the problem was with rtcwake which is complaining about /dev/rtc0 missing. Here is output from a sample rtcwake command: peter@haven:~$ rtcwake -m no -s 1300 rtcwake: assuming RTC uses UTC ... rtcwake: /dev/rtc0: unable to find device: No such file or directory I verified that in fact, that directory is missing. Since this was working prior to the upgrade, I have to assume that it was there previously, but I don't know for sure. In researching the error, I found some suggestions to get further information with timedatectl and hwclock, so here are the results from those commands as well. Output of timedatectl: peter@haven:~$ timedatectl Local time: Fri 2017-10-27 19:06:26 EDT Universal time: Fri 2017-10-27 23:06:26 UTC RTC time: n/a Time zone: America/New_York (EDT, -0400) Network time on: yes NTP synchronized: yes RTC in local TZ: no Output of hwclock --debug: peter@haven:~$ sudo hwclock --debug [sudo] password for peter: hwclock from util-linux 2.30.1 Trying to open: /dev/rtc0 Trying to open: /dev/rtc Trying to open: /dev/misc/rtc No usable clock interface found. hwclock: Cannot access the Hardware Clock via any known method. UPDATE When I boot with my old kernel, 4.10.0-37-generic the real-time clock works fine. I get the following RTC messages in dmesg when I boot the 4.13.0-16-generic kernel: peter@haven:~$ dmesg | grep -i rtc [0.089393] RTC time: 17:03:55, date: 11/01/17 [1.238784] rtc_cmos 00:01: RTC can wake from S4 [1.238794] rtc_cmos: probe of 00:01 failed with error -16 [1.295459] hctosys: unable to open rtc device (rtc0) UPDATE #2 Well, I was starting to believe that I had a hardware issue, since discovering I was unable to save changes to my BIOS and could not boot from USB. As it turns out, my laptop was bitten by this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147 causing my BIOS to be locked in a read-only state. Once I resolved the BIOS issue, and fixed the USB boot problem, I did a live boot of Ubuntu 17.10. The issue with my real time clock still exists under this clean boot scenario, yet when I boot other distros, like Linux Mint 18.3 and the real time clock works fine. I feel this definitely has something to do with the Ubuntu install, perhaps even a kernel bug. UPDATE #3 More evidence to suggest this is a kernel bug: I live-booted a copy of Antergos Linux, which was using the Arch kernel 4.14.12-1-ARCH and it exhibited the same problem with the real time clock as Ubuntu 17.10. In addition, I confirmed that the Linux Mint version I booted earlier (see Update #2) was on the Ubuntu kernel 4.10.0-38-generic. So, I suspect that sometime between kernels 4.10 and 4.13 this bug was introduced. --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1832 F pulseaudio /dev/snd/controlC1: peter 1832 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=a602efe1-467d-4ac4-806f-1b931c91cdad InstallationDate: Installed on 2017-04-05 (292 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: LENOVO 20354 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
[Kernel-packages] [Bug 1792349] Re: Memory leaking when running kubernetes cronjobs
More patches are required: https://lkml.org/lkml/2018/11/2/182 It looks we'll have to wait for some time, before the kernel stabilizes... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792349 Title: Memory leaking when running kubernetes cronjobs Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Bug description: We are using Kubernetes V1.8.15 with docker 18.03.1-ce. We schedule 50 Kubernetes cronjobs to run every 5 minutes. Each cronjob will create a simple busybox container, echo hello world, then terminate. In the data attached to the bug I let this run for 1 hour, and in this time the Available memory had reduced from 31256704 kB to 30461224 kB - so a loss of 776 MB. From previous longer runs we observe the available memory continues to drop. There doesn't appear to be any processes left behind, or any growth in any other processes to explain where the memory has gone. echo 3 > /proc/sys/vm/drop_caches causes some of the memory to be returned, but the majority remains leaked, and the only way to free it appears to be to reboot the system. We are currently running Ubuntu 4.15.0-32.35-generic 4.15.18 and have previously observed similar issues on Ubuntu 16.04 with Kernel 4.4.0-89-generic #112-Ubuntu SMP Mon Jul 31 19:38:41 UTC 2017 and Debian 9.4 running 4.9.0-6-amd64 #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02) The leak was more severe on the Debian system, and investigations there showed leaks in pcpu_get_vm_areas and were related to memory cgroups. Running with Kernel 4.17 on debian showed a leak at a similar rate to what we now observe on Ubuntu 18. This leak causes us issues as we need to run the cronjobs regularly and want the systems to remain up for months. Kubernetes will create a new cgroup each time the cronjob runs, but these are removed when the job completes (which takes a few seconds). If I use systemd-cgtop I don't see any increase in cgroups over time - but if I monitor /proc/cgroups over time I can see num_cgroups for memory increases. For the duration of the test I collected slabinfo, meminfo, vmallocinfo & cgroups - which I will attach to the bug. Each file is suffixed with the number of seconds since the start. *.0 & *.600 were taken before the test was started. The test was stopped shortly after the *.4200 files were generated. I then left the system idle for 10 minutes. I then ran echo 3 > /proc/sys/vm/drop_caches after *.4800 was generated. This seemed to free ~240MB - but this still leaves ~500MB lost. I then left the system idle for a further 20 minutes, and MemoryAvailable didn't seem to be increasing significantly. Note, the data attached is from running on kernel 4.18.7-041807-generic #201809090930 SMP Sun Sep 9 09:33:16 UTC 2018 (which I ran to verify the issue still exists in latest kernel) - however I was unable to run ubuntu-bug linux on this kernel as it complained about: *** Problem in linux-image-4.18.7-041807-generic The problem cannot be reported: This report is about a package that is not installed. So I switched back to 4.15.0-32.35-generic to raise the bug. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-32-generic 4.15.0-32.35 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 08:55 seq crw-rw 1 root audio 116, 33 Sep 13 08:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Thu Sep 13 08:55:46 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Xen HVM domU PciMultimedia: ProcEnviron: LANG=C.UTF-8 SHELL=/bin/bash TERM=xterm PATH=(custom, no user) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-32-generic root=UUID=6a84f0e4-8522-41cd-8ecb-d4a6fbecef8a ro earlyprintk RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 08/13/2018 dmi.bios.vendor: Xen dmi.bios.version:
[Kernel-packages] [Bug 1800838] Re: Lenovo P52 laptop fan control incorrect
how do you know the 2nd fan is not working? let me check it in your way on my p52 too. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800838 Title: Lenovo P52 laptop fan control incorrect Status in acpi package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Pure system ubuntu 18.04.1 with all update running on Lenovo p52 laptop. CPU fans speed is very low by default and start running only after 65 degrees. As a result laptop is very hot all the time independ what I am running. proc shows that level control is auto cat /proc/acpi/ibm/fan status: enabled speed:0 level:auto but it is impossible to switch fan on echo level full-speed > /proc/acpi/ibm/fan lspci: 00:00.0 Host bridge: Intel Corporation Device 3ec4 (rev 07) 00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 07) 00:04.0 Signal processing controller: Intel Corporation Skylake Processor Thermal Subsystem (rev 07) 00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Device a379 (rev 10) 00:14.0 USB controller: Intel Corporation Device a36d (rev 10) 00:14.2 RAM memory: Intel Corporation Device a36f (rev 10) 00:14.3 Network controller: Intel Corporation Device a370 (rev 10) 00:15.0 Serial bus controller [0c80]: Intel Corporation Device a368 (rev 10) 00:16.0 Communication controller: Intel Corporation Device a360 (rev 10) 00:1c.0 PCI bridge: Intel Corporation Device a338 (rev f0) 00:1c.7 PCI bridge: Intel Corporation Device a33f (rev f0) 00:1d.0 PCI bridge: Intel Corporation Device a330 (rev f0) 00:1e.0 Communication controller: Intel Corporation Device a328 (rev 10) 00:1f.0 ISA bridge: Intel Corporation Device a30e (rev 10) 00:1f.3 Audio device: Intel Corporation Device a348 (rev 10) 00:1f.4 SMBus: Intel Corporation Device a323 (rev 10) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Device a324 (rev 10) 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (7) I219-V (rev 10) 01:00.0 VGA compatible controller: NVIDIA Corporation Device 1cbb (rev a1) 01:00.1 Audio device: NVIDIA Corporation GP107GL High Definition Audio Controller (rev a1) 70:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 71:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd Device a808 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: acpi (not installed) ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Wed Oct 31 15:16:32 2018 InstallationDate: Installed on 2018-10-26 (5 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: acpi UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Dependencies: gcc-8-base 8.2.0-1ubuntu2~18.04 libc6 2.27-3ubuntu1 libgcc1 1:8.2.0-1ubuntu2~18.04 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-26 (5 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/1800838/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800901] Re: Updating breaks wifi on Intel Compute Stick
I updated to the most recent Bios from Intel FC0038: https://downloadcenter.intel.com/download/28070/BIOS-Update-FCBYT10H- 86A- Initial result is faster network access after power up and connectivity remains working after 10 reboots. *-firmware description: BIOS vendor: Intel Corp. physical id: 0 version: FCBYT10H.86A.0038.2018.0802.1745 date: 08/02/2018 size: 64KiB capacity: 6528KiB capabilities: pci upgrade shadowing cdboot bootselect edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int14serial int17printer acpi usb biosbootspecification uefi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800901 Title: Updating breaks wifi on Intel Compute Stick Status in linux package in Ubuntu: Incomplete Bug description: On an Intel Compute Stick model STCK1A8LFC the stock install works fine. The default kernel: uname -a Linux joe-STCK1A8LFC 3.16.0-34-generic #47~14.04.1-Ubuntu SMP Fri Apr 10 17:49:16 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux When an apt-get update/upgrade is run all network connectivity is lost. Run wpa_cli scan shows no networks at all. A return to the factory default returns connectivity. Any help would be greatly appreciated. Cheers,-Joe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799497] Re: 4.15 kernel hard lockup about once a week
Correct.. I ould like to give it some more time to see if it doesn't happen. So far so good, no lockups. I hadnt have to restart any server in a week and a half. I'll try to prepare the same setup on another server with zram-config to see if it happens again on that particular server -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799497 Title: 4.15 kernel hard lockup about once a week Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: My main server has been running into hard lockups about once a week ever since I switched to the 4.15 Ubuntu 18.04 kernel. When this happens, nothing is printed to the console, it's effectively stuck showing a login prompt. The system is running with panic=1 on the cmdline but isn't rebooting so the kernel isn't even processing this as a kernel panic. As this felt like a potential hardware issue, I had my hosting provider give me a completely different system, different motherboard, different CPU, different RAM and different storage, I installed that system on 18.04 and moved my data over, a week later, I hit the issue again. We've since also had a LXD user reporting similar symptoms here also on varying hardware: https://github.com/lxc/lxd/issues/5197 My system doesn't have a lot of memory pressure with about 50% of free memory: root@vorash:~# free -m totalusedfree shared buff/cache available Mem: 31819 17574 402 513 13842 13292 Swap: 159092687 13222 I will now try to increase console logging as much as possible on the system in the hopes that next time it hangs we can get a better idea of what happened but I'm not too hopeful given the complete silence on the console when this occurs. System is currently on: Linux vorash 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux But I've seen this since the GA kernel on 4.15 so it's not a recent regression. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 23 16:12 seq crw-rw 1 root audio 116, 33 Oct 23 16:12 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Cannot stat file /proc/22822/fd/10: Permission denied Cannot stat file /proc/22831/fd/10: Permission denied DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=none CRYPTSETUP=n IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation S1200SP NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=575c878a-0be6-4806-9c83-28f67aedea65 ro biosdevname=0 net.ifnames=0 panic=1 verbose console=tty0 console=ttyS0,115200n8 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 01/25/2018 dmi.bios.vendor: Intel Corporation dmi.bios.version: S1200SP.86B.03.01.1029.012520180838 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: S1200SP dmi.board.vendor: Intel Corporation dmi.board.version: H57532-271 dmi.chassis.asset.tag: dmi.chassis.type: 23 dmi.chassis.vendor: ... dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorporation:bvrS1200SP.86B.03.01.1029.012520180838:bd01/25/2018:svnIntelCorporation:pnS1200SP:pvr:rvnIntelCorporation:rnS1200SP:rvrH57532-271:cvn...:ct23:cvr..: dmi.product.family: Family dmi.product.name: S1200SP
[Kernel-packages] [Bug 1730331] Re: ath10k_pci: firmware crashed!
** Bug watch added: Red Hat Bugzilla #1560973 https://bugzilla.redhat.com/show_bug.cgi?id=1560973 ** Also affects: linux-firmware (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1560973 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1730331 Title: ath10k_pci: firmware crashed! Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware package in Fedora: Unknown Bug description: ... Nov 4 18:35:50 akane kernel: [ 10.216896] ath10k_pci :04:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043222ff sub : Nov 4 18:35:50 akane kernel: [ 10.216908] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 Nov 4 18:35:50 akane kernel: [ 10.217641] ath10k_pci :04:00.0: firmware ver 10.2.4.70.63-2 api 5 features no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 4ff9e14d Nov 4 18:35:50 akane kernel: [ 10.228600] kvm: Nested Virtualization enabled Nov 4 18:35:50 akane kernel: [ 10.228611] kvm: Nested Paging enabled Nov 4 18:35:50 akane kernel: [ 10.258913] ath10k_pci :04:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08 Nov 4 18:35:50 akane kernel: [ 10.263535] MCE: In-kernel MCE decoding enabled. Nov 4 18:35:50 akane kernel: [ 10.271401] EDAC amd64: Node 0: DRAM ECC enabled. Nov 4 18:35:50 akane kernel: [ 10.271416] EDAC amd64: F16h_M30h detected (node 0). Nov 4 18:35:50 akane kernel: [ 10.271491] EDAC MC: DCT0 chip selects: Nov 4 18:35:50 akane kernel: [ 10.271494] EDAC amd64: MC: 0: 4096MB 1: 0MB Nov 4 18:35:50 akane kernel: [ 10.271523] EDAC amd64: MC: 2: 0MB 3: 0MB Nov 4 18:35:50 akane kernel: [ 10.271526] EDAC amd64: MC: 4: 0MB 5: 0MB Nov 4 18:35:50 akane kernel: [ 10.271528] EDAC amd64: MC: 6: 0MB 7: 0MB Nov 4 18:35:50 akane kernel: [ 10.271530] EDAC MC: DCT1 chip selects: Nov 4 18:35:50 akane kernel: [ 10.271532] EDAC amd64: MC: 0: 0MB 1: 0MB Nov 4 18:35:50 akane kernel: [ 10.271534] EDAC amd64: MC: 2: 0MB 3: 0MB Nov 4 18:35:50 akane kernel: [ 10.271537] EDAC amd64: MC: 4: 0MB 5: 0MB Nov 4 18:35:50 akane kernel: [ 10.271539] EDAC amd64: MC: 6: 0MB 7: 0MB Nov 4 18:35:50 akane kernel: [ 10.271541] EDAC amd64: using x4 syndromes. Nov 4 18:35:50 akane kernel: [ 10.271542] EDAC amd64: MCT channel count: 1 Nov 4 18:35:50 akane kernel: [ 10.271829] EDAC MC0: Giving out device to module amd64_edac controller F16h_M30h: DEV :00:18.3 (INTERRUPT) Nov 4 18:35:50 akane kernel: [ 10.271892] EDAC PCI0: Giving out device to module amd64_edac controller EDAC PCI controller: DEV :00:18.2 (POLLED) Nov 4 18:35:50 akane kernel: [ 10.271894] AMD64 EDAC driver v3.5.0 Nov 4 18:35:50 akane kernel: [ 10.532131] EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: errors=remount-ro Nov 4 18:35:50 akane kernel: [ 10.575859] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: errors=remount-ro Nov 4 18:35:50 akane kernel: [ 11.397803] ath10k_pci :04:00.0: firmware crashed! (uuid f75dd562-d1bb-40a7-8454-fdc5f86cb8aa) Nov 4 18:35:50 akane kernel: [ 11.407389] ath10k_pci :04:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043222ff sub : Nov 4 18:35:50 akane kernel: [ 11.407395] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 Nov 4 18:35:50 akane kernel: [ 11.408085] ath10k_pci :04:00.0: firmware ver 10.2.4.70.63-2 api 5 features no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 4ff9e14d Nov 4 18:35:50 akane kernel: [ 11.408148] ath10k_pci :04:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08 Nov 4 18:35:50 akane kernel: [ 11.408156] ath10k_pci :04:00.0: htt-ver 0.0 wmi-op 5 htt-op 2 cal otp max-sta 128 raw 0 hwcrypto 1 Nov 4 18:35:50 akane kernel: [ 11.410197] ath10k_pci :04:00.0: firmware register dump: Nov 4 18:35:50 akane kernel: [ 11.416213] ath10k_pci :04:00.0: [00]: 0x4100016C 0x15B3 0x009BFF84 0x00955B31 Nov 4 18:35:50 akane kernel: [ 11.424559] ath10k_pci :04:00.0: [04]: 0x009BFF84 0x00060130 0x0013 0x Nov 4 18:35:50 akane kernel: [ 11.432767] ath10k_pci :04:00.0: [08]: 0x009C8EA4 0x7170 0x0001 0x00435300 Nov 4 18:35:50 akane kernel: [ 11.441059] ath10k_pci :04:00.0: [12]: 0x0009 0x 0x00958360 0x0095836B Nov 4 18:35:50 akane kernel: [ 11.449397] ath10k_pci :04:00.0: [16]: 0x00958080 0x0094078E 0x 0x Nov 4 18:35:50 akane kernel: [ 11.457686] ath10k_pci :04:00.0: [20]: 0x409BFF84 0x0040AB44 0x004101E0 0x000C Nov 4 18:35:50 akane kernel: [ 11.466132] ath10k_pci :04:00.0: [24]: 0x809BFE1C
[Kernel-packages] [Bug 1795292] Re: ELAN469D touch pad not working
Also on v4.19.0, same touchpad and Laptop, Lenovo 330s-15ARR, I can test if anyone has a new build. I'd love to get this laptop working with Ubuntu :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1795292 Title: ELAN469D touch pad not working Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: I installed Bionic Beaver and now upgraded to Cosmic Cuttlefish on this Lenovo Ideapad 330S-15ARR laptop. The touch pad doesn't work in either. Some possibly relevant info from dmesg: i2c_hid i2c-ELAN469D:00: i2c-ELAN469D:00 supply vdd not found, using dummy regulator i2c_designware AMDI0010:01: controller timed out ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-7-generic 4.18.0-7.8 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xorbit 2086 F pulseaudio /dev/snd/pcmC1D0p: xorbit 2086 F...m pulseaudio /dev/snd/controlC0: xorbit 2086 F pulseaudio CurrentDesktop: GNOME Date: Sun Sep 30 23:14:26 2018 InstallationDate: Installed on 2018-09-20 (10 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 81FB ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic processor.max_cstate=1 rcu_nocbs=0-7 pcie_aspm=off pci=noaer quiet splash vt.handoff=1 elan_i2c.dyndbg=+p RelatedPackageVersions: linux-restricted-modules-4.18.0-7-generic N/A linux-backports-modules-4.18.0-7-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-09-30 (0 days ago) dmi.bios.date: 06/08/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7WCN22WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330S-15ARR dmi.modalias: dmi:bvnLENOVO:bvr7WCN22WW:bd06/08/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR: dmi.product.family: ideapad 330S-15ARR dmi.product.name: 81FB dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR dmi.product.version: Lenovo ideapad 330S-15ARR dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-09-20 (13 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: cosmic Uname: Linux 4.19.0-041900rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to cosmic on 2018-09-30 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1795292/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799400] Re: linux-lts-trusty: 3.13.0-162.212~precise1 -proposed tracker
** 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: 1799399 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Testing in progress verification-testing: Testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1799400 Title: linux-lts-trusty: 3.13.0-162.212~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1799399 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800976] Re: linux 4.4.0-139.165 ADT test failure with linux 4.4.0-139.165
** Also affects: qa-regression-testing Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800976 Title: linux 4.4.0-139.165 ADT test failure with linux 4.4.0-139.165 Status in QA Regression Testing: New Status in linux package in Ubuntu: Incomplete Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux/20181031_081513_a6a49@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20181031_104204_a6a49@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux/20181031_062840_a6a49@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/linux/20181031_055910_a6a49@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1800976/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799400] Re: linux-lts-trusty: 3.13.0-162.212~precise1 -proposed tracker
3.13.0-162.212~precise1 - generic Regression test CMPL, RTB. Issue to note in amd64: ubuntu_qrt_kernel_security - CONFIG_RETPOLINE=y in kernel (bug 1786894) Issue to note in i386: ubuntu_qrt_kernel_security - CONFIG_RETPOLINE=y in kernel (bug 1786894) ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1799400 Title: linux-lts-trusty: 3.13.0-162.212~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1799399 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801232] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801232 Title: Ubuntu MATE crashes when too many external USB drives are mounted. Status in linux package in Ubuntu: Confirmed Bug description: I had the following drives mounted: /media/robert/Shared - a second partition of the first internal hard drive with an NTFS /media/robert/4TB LaCie - an external USB 3 drive with an NTFS /media/robert/4TB G-Drive - an external USB 3 drive with an NTFS /media/robert/4TB Seagate 1 - an external USB 3 drive with an NTFS file system /media/robert/4TB Seagate 2 - an external USB 3 drive with an NTFS file system /media/robert/4TB Seagate 3 - an external USB 3 drive with an HFS+ file system /media/robert/4TB Seagate 5 - an external USB 3 drive with an NTFS file system /media/robert/5TB Seagate 1 - an external USB 3 drive with an ext4 file system Detected but not mounted were: Win10 - a partition on my second hard drive with an NTFS file system U MATE 14 - a partition on my second hard drive with an ext4 file system Windows10 - a partition on my second hard drive with an NTFS file system 701 GB Volume - a partition on my second hard drive with an ext4 file system 83 GB Volume - a partition on my second hard drive with an ext4 file system Also attached but not detected is a 6TB Seagate USB 3 drive. The HFS+ files system was using hfs package. I was copying files from a directory in 4TB Seagate 3 to 4TB Seagate 1 using the Terminal cp -anR command. Once all the files had been copied I intended to reformat the drive with a NTFS file system. I was using VueScan and it began misbehaving after I had deleted and renamed some directories with CAJA. I exited VueScan and tried to restart it. The initial splash screen displayed, then the program hang. I tried it again. Same results. I aborted the terminal copy and did a system shutdown. I saw the Ubuntu shutdown screen. I waited, and waited. I went to bed. After 8 hours the shutdown screen was still being displayed. I had to turn the power off. Then I disconnected most of the external drives. I turned power back on and rebooted. The 6TB drive did appear and was mounted. I had to disconnect- reconnect the 4TB Seagate 3 (HFS+ file system) a number of times and reboot before it would mount. VueScan started properly and works fine. It had been working properly before - the error was that Caja would not show the newly scanned files that VueScan produced. After restarting Ubuntu they showed up proving that VueScan was not at fault. Caja is complaining when I try to delete files - see attachment, ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-38-generic 4.15.0-38.41 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robert 2122 F pulseaudio /dev/snd/controlC0: robert 2122 F pulseaudio CurrentDesktop: MATE Date: Thu Nov 1 22:20:39 2018 HibernationDevice: RESUME=UUID=aa95f07d-f769-44ca-8b33-0c5b3c78bdeb InstallationDate: Installed on 2018-10-25 (8 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=26dc3ca5-f3ae-47eb-92b6-4f02ed5ba4f0 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A 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.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A: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:
[Kernel-packages] [Bug 1801232] [NEW] Ubuntu MATE crashes when too many external USB drives are mounted.
Public bug reported: I had the following drives mounted: /media/robert/Shared - a second partition of the first internal hard drive with an NTFS /media/robert/4TB LaCie - an external USB 3 drive with an NTFS /media/robert/4TB G-Drive - an external USB 3 drive with an NTFS /media/robert/4TB Seagate 1 - an external USB 3 drive with an NTFS file system /media/robert/4TB Seagate 2 - an external USB 3 drive with an NTFS file system /media/robert/4TB Seagate 3 - an external USB 3 drive with an HFS+ file system /media/robert/4TB Seagate 5 - an external USB 3 drive with an NTFS file system /media/robert/5TB Seagate 1 - an external USB 3 drive with an ext4 file system Detected but not mounted were: Win10 - a partition on my second hard drive with an NTFS file system U MATE 14 - a partition on my second hard drive with an ext4 file system Windows10 - a partition on my second hard drive with an NTFS file system 701 GB Volume - a partition on my second hard drive with an ext4 file system 83 GB Volume - a partition on my second hard drive with an ext4 file system Also attached but not detected is a 6TB Seagate USB 3 drive. The HFS+ files system was using hfs package. I was copying files from a directory in 4TB Seagate 3 to 4TB Seagate 1 using the Terminal cp -anR command. Once all the files had been copied I intended to reformat the drive with a NTFS file system. I was using VueScan and it began misbehaving after I had deleted and renamed some directories with CAJA. I exited VueScan and tried to restart it. The initial splash screen displayed, then the program hang. I tried it again. Same results. I aborted the terminal copy and did a system shutdown. I saw the Ubuntu shutdown screen. I waited, and waited. I went to bed. After 8 hours the shutdown screen was still being displayed. I had to turn the power off. Then I disconnected most of the external drives. I turned power back on and rebooted. The 6TB drive did appear and was mounted. I had to disconnect-reconnect the 4TB Seagate 3 (HFS+ file system) a number of times and reboot before it would mount. VueScan started properly and works fine. It had been working properly before - the error was that Caja would not show the newly scanned files that VueScan produced. After restarting Ubuntu they showed up proving that VueScan was not at fault. Caja is complaining when I try to delete files - see attachment, ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-38-generic 4.15.0-38.41 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robert 2122 F pulseaudio /dev/snd/controlC0: robert 2122 F pulseaudio CurrentDesktop: MATE Date: Thu Nov 1 22:20:39 2018 HibernationDevice: RESUME=UUID=aa95f07d-f769-44ca-8b33-0c5b3c78bdeb InstallationDate: Installed on 2018-10-25 (8 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=26dc3ca5-f3ae-47eb-92b6-4f02ed5ba4f0 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A 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.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A: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 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug bionic ** Attachment added: "Caja can't find Trash" https://bugs.launchpad.net/bugs/1801232/+attachment/5208083/+files/Caja%20Screenshot%20at%202018-11-01%2022-50-41.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801232 Title: Ubuntu MATE crashes when too many external USB drives are mounted. Status in linux package in Ubuntu: Confirmed Bug description: I had the following drives mounted: /media/robert/Shared
[Kernel-packages] [Bug 1800770] Re: Thunderbolt runtime D3 and PCIe D3 Cold support
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- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. 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-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1800770 Title: Thunderbolt runtime D3 and PCIe D3 Cold support Status in HWE Next: New Status in linux-oem package in Ubuntu: Fix Committed Status in linux-oem source package in Bionic: Fix Committed Bug description: [Impact] Currently in Ubuntu Bionic 4.15 kernel, we already support thunderbolt to enter runtime D3 Hot, and require BIOS' assist to cut off the power of the thunderbolt. After OSI "Windows 2017.2" (Windows 10 version 1709), BIOS stop cutting off the power of thunderbolt, and leave it to OS to set thunderbolt to D3 Cold. It consumes more than 2+Watt during short/long idle when thunderbolt is in D3 Hot, instead of D3 Cold. [Fix] To add D3 Cold support, we mainly require this patchset[1] which is targeted to enter v4.20. To avoid conflicts and solve error/warning message, I cherry picked 142 and backported 10 commit. I also cherry picked the "Windows 2017.2" OSI commit[2] as a whole. [Test] Verified on 2 machines with Alpine Ridge thunderbolt and 1 machine with Titan Ridge thunderbolt, after S3 30 times, hotplug the thunderbolt dockering, the HDMI output, Ethernet, USB disk are still working. And verified the SRU stress test on another Alpine Ridge thunderbolt machine, the result is positive. [Regression Potential] Medium. Although other engineers and I have done some testing on some machines, our QA will do a more thoroughly testing when the kernel is in proposed archive. 1. https://www.spinics.net/lists/linux-acpi/msg83977.html 2. https://git.kernel.org/pub/scm/linux/kernel/git/mnyman/xhci.git/commit/?h=for-usb-next=140a6c8af798dfcc06796f907656604c6914 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1800770/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792562] Re: nvidia-kernel-source-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed to build [error: too few arguments to function ‘drm_atomic_helper_set_config’]
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1792562 Title: nvidia-kernel-source-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed to build [error: too few arguments to function ‘drm_atomic_helper_set_config’] Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: ?? ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-kernel-source-390 390.77-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 DKMSKernelVersion: 4.15.0-35-generic Date: Fri Sep 14 13:31:51 2018 Dependencies: DuplicateSignature: dkms:nvidia-kernel-source-390:390.77-0ubuntu0.18.04.1:/var/lib/dkms/nvidia/390.77/build/nvidia-drm/nvidia-drm-helper.h:69:16: error: too few arguments to function ‘drm_atomic_helper_set_config’ InstallationDate: Installed on 2018-01-25 (231 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageVersion: 390.77-0ubuntu0.18.04.1 Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 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.3ubuntu0.1 SourcePackage: nvidia-graphics-drivers-390 Title: nvidia-kernel-source-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1792562/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800901] Re: Updating breaks wifi on Intel Compute Stick
Notes as it is currently unreliable on WiFi, making appport-collect hard. After restoring from the recovery partition I am able to add this WPA2 network. I then run apt-get upgrade and it gets buggy. Thanks for helping out. root@joe-STCK1A8LFC:~# apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: chestersmill-settings cups-filters cups-filters-core-drivers grub-common grub-efi-amd64 grub-efi-amd64-bin grub-efi-amd64-signed grub2-common linux-generic-lts-utopic linux-headers-generic-lts-utopic linux-image-generic-lts-utopic linux-signed-generic-lts-utopic linux-signed-image-generic-lts-utopic python3-software-properties python3-update-manager qpdf shim shim-signed software-properties-common software-properties-gtk update-manager update-manager-core update-notifier update-notifier-common The following packages will be upgraded: accountsservice activity-log-manager activity-log-manager-control-center apparmor apparmor-easyprof apport apport-gtk apt apt-transport-https apt-utils aptdaemon aptdaemon-data apturl apturl-common avahi-autoipd avahi-daemon avahi-utils base-files bash bash-completion bind9-host binutils bluez bluez-cups bsdutils btrfs-tools ca-certificates click click-apparmor compiz compiz-core compiz-gnome compiz-plugins-default coreutils cpio cpp-4.8 cups cups-browsed cups-bsd cups-client cups-common cups-core-drivers cups-daemon cups-ppdc cups-server-common dbus dbus-x11 desktop-file-utils dh-python dkms dnsmasq-base dnsutils dosfstools dpkg e2fslibs e2fsprogs ecryptfs-utils efibootmgr eject empathy empathy-common eog evince evince-common evolution-data-server evolution-data-server-common evolution-data-server-online-accounts file file-roller fontconfig fontconfig-config fonts-droid fonts-opensymbol fuse gcc-4.8 gcc-4.8-base gcc-4.9-base gdb gdisk ghostscript ghostscript-x gir1.2-click-0.4 gir1.2-ebook-1.2 gir1.2-ebookcontacts-1.2 gir1.2-edataserver-1.2 gir1.2-gdkpixbuf-2.0 gir1.2-gst-plugins-base-1.0 gir1.2-gstreamer-1.0 gir1.2-gtk-3.0 gir1.2-gudev-1.0 gir1.2-ibus-1.0 gir1.2-javascriptcoregtk-3.0 gir1.2-networkmanager-1.0 gir1.2-soup-2.4 gir1.2-udisks-2.0 gir1.2-vte-2.90 gir1.2-webkit-3.0 gir1.2-wnck-3.0 glib-networking glib-networking-common glib-networking-services gnome-contacts gnome-desktop3-data gnome-keyring gnome-user-guide gnupg gpgv gstreamer0.10-plugins-base gstreamer0.10-plugins-base-apps gstreamer0.10-plugins-good gstreamer0.10-pulseaudio gstreamer0.10-x gstreamer1.0-plugins-base gstreamer1.0-plugins-base-apps gstreamer1.0-plugins-good gstreamer1.0-pulseaudio gstreamer1.0-tools gstreamer1.0-x gvfs gvfs-backends gvfs-bin gvfs-common gvfs-daemons gvfs-fuse gvfs-libs hplip hplip-data ibus ibus-gtk ibus-gtk3 ifupdown im-config indicator-session init-system-helpers initramfs-tools initramfs-tools-bin initscripts iproute iproute2 irqbalance isc-dhcp-client isc-dhcp-common klibc-utils kmod kpartx kpartx-boot krb5-locales landscape-client-ui-install libaccountsservice0 libapparmor-perl libapparmor1 libapt-inst1.5 libapt-pkg4.12 libarchive-zip-perl libarchive13 libasan0 libasn1-8-heimdal libatomic1 libavahi-client3 libavahi-common-data libavahi-common3 libavahi-core7 libavahi-glib1 libavahi-gobject0 libbind9-90 libblkid1 libbluetooth3 libc-bin libc-dev-bin libc6 libc6-dev libcamel-1.2-45 libcgmanager0 libclick-0.4-0 libcomerr2 libcompizconfig0 libcups2 libcupscgi1 libcupsfilters1 libcupsimage2 libcupsmime1 libcupsppdc1 libcurl3 libcurl3-gnutls libdb5.3 libdbus-1-3 libdebian-installer4 libdecoration0 libdns100 libdpkg-perl libdrm-intel1 libdrm-nouveau2 libdrm-radeon1 libdrm2 libebackend-1.2-7 libebook-1.2-14 libebook-contacts-1.2-0 libecal-1.2-16 libecryptfs0 libedata-book-1.2-20 libedata-cal-1.2-23 libedataserver-1.2-18 libelf1 libevdocument3-4 libevview3-3 libexempi3 libexiv2-12 libexpat1 libffi6 libfontconfig1 libfontembed1 libfreerdp1 libfreetype6 libfuse2 libgail-3-0 libgail-common libgail18 libgbm1 libgc1c2 libgcc-4.8-dev libgcc1 libgcrypt11 libgd3 libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-common libglib2.0-0 libglib2.0-bin libglib2.0-data libgnome-desktop-3-7 libgnutls-openssl27 libgnutls26 libgomp1 libgraphite2-3 libgs9 libgs9-common libgssapi-krb5-2 libgssapi3-heimdal libgstreamer-plugins-base0.10-0 libgstreamer-plugins-base1.0-0 libgstreamer-plugins-good1.0-0 libgstreamer1.0-0 libgtk-3-0 libgtk-3-bin libgtk-3-common libgtk2.0-0 libgtk2.0-bin libgtk2.0-common libgudev-1.0-0 libgweather-3-6 libgweather-common libharfbuzz-icu0 libharfbuzz0b libhcrypto4-heimdal libheimbase1-heimdal libheimntlm0-heimdal libhpmud0 libhunspell-1.3-0 libhx509-5-heimdal libibus-1.0-5 libicu52 libidn11 libido3-0.1-0 libimobiledevice4 libisc95 libisccc90 libisccfg90 libitm1 libjasper1 libjavascriptcoregtk-3.0-0 libjbig2dec0 libjpeg-turbo8 libk5crypto3
[Kernel-packages] [Bug 563265] Re: package nvidia-* failed to install/upgrade: nvidia-current kernel module failed to build / make[2]: *** No rule to make target `modules'. Stop.
** Also affects: nvidia-graphics-drivers-390 (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/563265 Title: package nvidia-* failed to install/upgrade: nvidia-current kernel module failed to build / make[2]: *** No rule to make target `modules'. Stop. Status in nvidia-graphics-drivers package in Ubuntu: Invalid Status in nvidia-graphics-drivers-331 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-367 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: After getting the latest updates in lucid, including the 2.6.32-20 kernel, and rebooting the machine, X only started in low graphics mode. After I started to investigate it seemed like the nvidia kernel module failed to build. I tried to reinstall nvidia-current (apt-get autoremove nvidia-current, apt-get install nvidia-current) but it failed with the following message. root@thor:~# apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0B of additional disk space will be used. Setting up nvidia-current (195.36.15-0ubuntu2) ... Removing old nvidia-current-195.36.15 DKMS files... -- Deleting module version: 195.36.15 completely from the DKMS tree. -- Done. Loading new nvidia-current-195.36.15 DKMS files... Building for 2.6.32-19-generic and 2.6.32-20-generic Building for architecture x86_64 Module build for the currently running kernel was skipped since the kernel source for this kernel does not seem to be installed. Building initial module for 2.6.32-20-generic Error! Bad return status for module build on kernel: 2.6.32-20-generic (x86_64) Consult the make.log in the build directory /var/lib/dkms/nvidia-current/195.36.15/build/ for more information. dpkg: error processing nvidia-current (--configure): subprocess installed post-installation script returned error exit status 10 Processing triggers for python-gmenu ... Rebuilding /usr/share/applications/desktop.en_US.utf8.cache... Processing triggers for python-support ... Errors were encountered while processing: nvidia-current E: Sub-process /usr/bin/dpkg returned an error code (1) The make.log contains the following information root@thor:~# cat /var/lib/dkms/nvidia-current/195.36.15/build/make.log DKMS make.log for nvidia-current-195.36.15 for kernel 2.6.32-20-generic (x86_64) Wed Apr 14 20:34:45 EEST 2010 NVIDIA: calling KBUILD... make[2]: *** No rule to make target `modules'. Stop. NVIDIA: left KBUILD. nvidia.ko failed to build! make[1]: *** [module] Error 1 make: *** [module] Error 2 If I try to activate the nvidia drivers using jockey-gtk or jockey- text, I get the following error root@thor:~# jockey-text -e xorg:nvidia_current Searching for available drivers... SystemError: installArchives() failed Meanwhile, the proprietary nvidia drivers continue to happily work in 2.6.32-19 kernel. Only building the module for 2.6.32-20 seems to fail. Thank you for your help. Please let me know if I can give you any more relevant debugging information. This machine was upgraded from 9.04 to 10.04, for all that it matters. ProblemType: Package DistroRelease: Ubuntu 10.04 Package: nvidia-current 195.36.15-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic x86_64 Architecture: amd64 CurrentDmesg: [ 22.352714] ppdev: user-space parallel port driver [ 31.65] eth0: no IPv6 routers present [ 35.870840] UDF-fs: Partition marked readonly; forcing readonly mount [ 35.899382] UDF-fs INFO UDF: Mounting volume 'CIVCOMPLETEEU', timestamp 2007/09/22 01:42 (10b4) Date: Wed Apr 14 21:07:06 2010 DkmsStatus: nvidia-current, 195.36.15: added ErrorMessage: nvidia-current kernel module failed to build InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) MachineType: System manufacturer P5Q PackageVersion: 195.36.15-0ubuntu2 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic root=UUID=2846018c-2e2a-4803-8a02-ad3c18f7c317 ro quiet splash SourcePackage: nvidia-graphics-drivers Title: package nvidia-current 195.36.15-0ubuntu2 failed to install/upgrade: nvidia-current kernel module failed to build XorgConf: dmi.bios.date: 08/20/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1306 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag:
[Kernel-packages] [Bug 563265] Re: package nvidia-* failed to install/upgrade: nvidia-current kernel module failed to build / make[2]: *** No rule to make target `modules'. Stop.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/563265 Title: package nvidia-* failed to install/upgrade: nvidia-current kernel module failed to build / make[2]: *** No rule to make target `modules'. Stop. Status in nvidia-graphics-drivers package in Ubuntu: Invalid Status in nvidia-graphics-drivers-331 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-367 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: After getting the latest updates in lucid, including the 2.6.32-20 kernel, and rebooting the machine, X only started in low graphics mode. After I started to investigate it seemed like the nvidia kernel module failed to build. I tried to reinstall nvidia-current (apt-get autoremove nvidia-current, apt-get install nvidia-current) but it failed with the following message. root@thor:~# apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0B of additional disk space will be used. Setting up nvidia-current (195.36.15-0ubuntu2) ... Removing old nvidia-current-195.36.15 DKMS files... -- Deleting module version: 195.36.15 completely from the DKMS tree. -- Done. Loading new nvidia-current-195.36.15 DKMS files... Building for 2.6.32-19-generic and 2.6.32-20-generic Building for architecture x86_64 Module build for the currently running kernel was skipped since the kernel source for this kernel does not seem to be installed. Building initial module for 2.6.32-20-generic Error! Bad return status for module build on kernel: 2.6.32-20-generic (x86_64) Consult the make.log in the build directory /var/lib/dkms/nvidia-current/195.36.15/build/ for more information. dpkg: error processing nvidia-current (--configure): subprocess installed post-installation script returned error exit status 10 Processing triggers for python-gmenu ... Rebuilding /usr/share/applications/desktop.en_US.utf8.cache... Processing triggers for python-support ... Errors were encountered while processing: nvidia-current E: Sub-process /usr/bin/dpkg returned an error code (1) The make.log contains the following information root@thor:~# cat /var/lib/dkms/nvidia-current/195.36.15/build/make.log DKMS make.log for nvidia-current-195.36.15 for kernel 2.6.32-20-generic (x86_64) Wed Apr 14 20:34:45 EEST 2010 NVIDIA: calling KBUILD... make[2]: *** No rule to make target `modules'. Stop. NVIDIA: left KBUILD. nvidia.ko failed to build! make[1]: *** [module] Error 1 make: *** [module] Error 2 If I try to activate the nvidia drivers using jockey-gtk or jockey- text, I get the following error root@thor:~# jockey-text -e xorg:nvidia_current Searching for available drivers... SystemError: installArchives() failed Meanwhile, the proprietary nvidia drivers continue to happily work in 2.6.32-19 kernel. Only building the module for 2.6.32-20 seems to fail. Thank you for your help. Please let me know if I can give you any more relevant debugging information. This machine was upgraded from 9.04 to 10.04, for all that it matters. ProblemType: Package DistroRelease: Ubuntu 10.04 Package: nvidia-current 195.36.15-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic x86_64 Architecture: amd64 CurrentDmesg: [ 22.352714] ppdev: user-space parallel port driver [ 31.65] eth0: no IPv6 routers present [ 35.870840] UDF-fs: Partition marked readonly; forcing readonly mount [ 35.899382] UDF-fs INFO UDF: Mounting volume 'CIVCOMPLETEEU', timestamp 2007/09/22 01:42 (10b4) Date: Wed Apr 14 21:07:06 2010 DkmsStatus: nvidia-current, 195.36.15: added ErrorMessage: nvidia-current kernel module failed to build InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) MachineType: System manufacturer P5Q PackageVersion: 195.36.15-0ubuntu2 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic root=UUID=2846018c-2e2a-4803-8a02-ad3c18f7c317 ro quiet splash SourcePackage: nvidia-graphics-drivers Title: package nvidia-current 195.36.15-0ubuntu2 failed to install/upgrade: nvidia-current kernel module failed to build XorgConf: dmi.bios.date: 08/20/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1306 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q dmi.board.vendor: ASUSTeK Computer INC.
[Kernel-packages] [Bug 1776445] Re: nvidia-dkms-390 390.48-0ubuntu3: nvidia kernel module failed to build [ make: *** No rule to make target 'modules'. Stop.]
*** This bug is a duplicate of bug 563265 *** https://bugs.launchpad.net/bugs/563265 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 563265, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Summary changed: - nvidia-dkms-390 390.48-0ubuntu3: nvidia kernel module failed to build + nvidia-dkms-390 390.48-0ubuntu3: nvidia kernel module failed to build [ make: *** No rule to make target 'modules'. Stop.] ** Tags added: cosmic ** This bug has been marked a duplicate of bug 563265 package nvidia-* failed to install/upgrade: nvidia-current kernel module failed to build / make[2]: *** No rule to make target `modules'. Stop. -- 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/1776445 Title: nvidia-dkms-390 390.48-0ubuntu3: nvidia kernel module failed to build [ make: *** No rule to make target 'modules'. Stop.] Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: I am a noob, so a detailed explanation of the problem and steps and procedures of fixing it would be appreciated thanks. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-dkms-390 390.48-0ubuntu3 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 DKMSBuildLog: DKMS make.log for nvidia-390.48 for kernel 4.15.0-23-generic (x86_64) Tue Jun 12 09:56:49 WAT 2018 make: *** No rule to make target 'modules'. Stop. DKMSKernelVersion: 4.15.0-23-generic Date: Tue Jun 12 09:56:50 2018 InstallationDate: Installed on 2018-04-30 (42 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageVersion: 390.48-0ubuntu3 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: nvidia-graphics-drivers-390 Title: nvidia-dkms-390 390.48-0ubuntu3: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1776445/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801025] Re: nvidia-dkms-390 390.87-0ubuntu1: nvidia kernel module failed to build
*** This bug is a duplicate of bug 563265 *** https://bugs.launchpad.net/bugs/563265 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1776445, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1776445 nvidia-dkms-390 390.48-0ubuntu3: nvidia kernel module failed to build [ make: *** No rule to make target 'modules'. Stop.] ** This bug is no longer a duplicate of bug 1776445 nvidia-dkms-390 390.48-0ubuntu3: nvidia kernel module failed to build [ make: *** No rule to make target 'modules'. Stop.] ** This bug has been marked a duplicate of bug 563265 package nvidia-* failed to install/upgrade: nvidia-current kernel module failed to build / make[2]: *** No rule to make target `modules'. Stop. -- 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/1801025 Title: nvidia-dkms-390 390.87-0ubuntu1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: Nvidia Driver not loading ProblemType: Package DistroRelease: Ubuntu 18.10 Package: nvidia-dkms-390 390.87-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 DKMSBuildLog: DKMS make.log for nvidia-390.87 for kernel 4.18.0-10-generic (x86_64) Thu 1 Nov 10:42:36 EAT 2018 make: *** No rule to make target 'modules'. Stop. DKMSKernelVersion: 4.18.0-10-generic Date: Thu Nov 1 10:42:37 2018 InstallationDate: Installed on 2018-10-19 (12 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageVersion: 390.87-0ubuntu1 Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.6-1 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SourcePackage: nvidia-graphics-drivers-390 Title: nvidia-dkms-390 390.87-0ubuntu1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1801025/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801181] Re: Pixelized display
Can you please provide a photo of the "Pixelized display"? ** Tags added: radeon ** Changed in: xorg-server (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/1801181 Title: Pixelized display Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Artefakty upgrading to 18.04 lts three iż a problem without display. I have no duch problem on 16.04 lts --- CurrentDmesg.txt: [ 29.779035] radeon :01:00.0: r600_check_texture_resource:1566 tex pitch (1680, 0x40, 1) invalid [ 29.779082] [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream ! [ 30.612745] radeon :01:00.0: r600_check_texture_resource:1566 tex pitch (1680, 0x40, 1) invalid [ 30.612804] [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream ! -- ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Thu Nov 1 22:51:23 2018 DistUpgraded: 2018-11-01 22:32:47,052 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] No such file or directory: './xorg_fix_proprietary.py') DistroCodename: bionic DistroVariant: ubuntu DkmsStatus:  bcmwl, 6.30.223.271+bdcom, 4.15.0-38-generic, x86_64: installed  bcmwl, 6.30.223.271+bdcom, 4.4.0-130-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard:  Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller])    Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:2115]  Advanced Micro Devices, Inc. [AMD/ATI] RV635/M86 [Mobility Radeon HD 3650] [1002:9591] (prog-if 00 [VGA controller])    Subsystem: Lenovo RV635/M86 [Mobility Radeon HD 3650] [17aa:2116] InstallationDate: Installed on 2015-03-10 (1332 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: LENOVO 2087A37 PccardctlIdent:  Socket 0:    no product info available PccardctlStatus:  Socket 0:    no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=76e45c9b-b94c-414a-9c7f-cfbbafb58a1a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-11-01 (0 days ago) dmi.bios.date: 10/12/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6FET93WW (3.23 ) dmi.board.name: 2087A37 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6FET93WW(3.23):bd10/12/2012:svnLENOVO:pn2087A37:pvrThinkPadT500:rvnLENOVO:rn2087A37:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T500 dmi.product.name: 2087A37 dmi.product.version: ThinkPad T500 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Nov 1 20:57:30 2018 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801181/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801202] Re: Xorg freeze
Unfortunately your harddisk is failing, which is a hardware error.
Consider replacing the harddisk with a new one and then reinstall Ubuntu
:(
** Changed in: xorg-server (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1801202
Title:
Xorg freeze
Status in linux package in Ubuntu:
Invalid
Status in xorg-server package in Ubuntu:
Invalid
Bug description:
The screen freezes suddenly when i'm trying to play an online video or
when i have too many tabs or folders open.
---
CurrentDmesg.txt:
[ 5465.753948] ata1.00: exception Emask 0x0 SAct 0x1c04 SErr 0x0 action 0x0
[ 5465.753954] ata1.00: irq_stat 0x4008
[ 5465.753959] ata1.00: failed command: READ FPDMA QUEUED
[ 5465.753969] ata1.00: cmd 60/00:10:00:9b:f5/01:00:53:00:00/40 tag 2 ncq dma
131072 in
res 41/40:00:c0:9b:f5/00:01:53:00:00/00 Emask 0x409
(media error)
[ 5465.753973] ata1.00: status: { DRDY ERR }
[ 5465.753976] ata1.00: error: { UNC }
[ 5466.031887] ata1.00: configured for UDMA/133
[ 5466.031915] sd 0:0:0:0: [sda] tag#2 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[ 5466.031921] sd 0:0:0:0: [sda] tag#2 Sense Key : Medium Error [current]
[ 5466.031925] sd 0:0:0:0: [sda] tag#2 Add. Sense: Unrecovered read error -
auto reallocate failed
[ 5466.031932] sd 0:0:0:0: [sda] tag#2 CDB: Read(10) 28 00 53 f5 9b 00 00 01
00 00
[ 5466.031935] print_req_error: I/O error, dev sda, sector 1408605120
[ 5466.031994] ata1: EH complete
---
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 2 01:04:22 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 390.77, 4.15.0-36-generic, x86_64: installed
 nvidia, 390.77, 4.15.0-38-generic, x86_64: installed
DpkgLog:
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Very infrequently
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e]
(rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:382b]
   Subsystem: Lenovo GM108M [GeForce 920MX] [17aa:382b]
InstallationDate: Installed on 2018-10-04 (28 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
MachineType: LENOVO 80QQ
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic
root=UUID=b0abddd7-646b-4707-bf44-54c3fc3ea828 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/21/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: E0CN63WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Nano 5B6
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 100-15IBD
dmi.modalias:
dmi:bvnLENOVO:bvrE0CN63WW:bd10/21/2016:svnLENOVO:pn80QQ:pvrLenovoideapad100-15IBD:rvnLENOVO:rnNano5B6:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad100-15IBD:
dmi.product.family: IDEAPAD
dmi.product.name: 80QQ
dmi.product.version: Lenovo ideapad 100-15IBD
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801202/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801114] Re: linux-aws: 4.18.0-1004.5 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1799445 phase: Packaging reason: - prepare-package: Version not specified + prepare-package: Package not yet uploaded + prepare-package-meta: Package not yet uploaded -- 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/1801114 Title: linux-aws: 4.18.0-1004.5 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1799445 phase: Packaging reason: prepare-package: Package not yet uploaded prepare-package-meta: Package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1801114/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801114] Re: linux-aws: 4.18.0-1004.5 -proposed tracker
** Summary changed: - linux-aws: -proposed tracker + linux-aws: 4.18.0-1004.5 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) -- 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/1801114 Title: linux-aws: 4.18.0-1004.5 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1799445 phase: Packaging reason: prepare-package: Package not yet uploaded prepare-package-meta: Package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1801114/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801202] Re: Xorg freeze
It seems to have problems with your hard drive.
--
Cristian Aravena Romero (caravena)
** 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/1801202
Title:
Xorg freeze
Status in linux package in Ubuntu:
Incomplete
Status in xorg-server package in Ubuntu:
New
Bug description:
The screen freezes suddenly when i'm trying to play an online video or
when i have too many tabs or folders open.
---
CurrentDmesg.txt:
[ 5465.753948] ata1.00: exception Emask 0x0 SAct 0x1c04 SErr 0x0 action 0x0
[ 5465.753954] ata1.00: irq_stat 0x4008
[ 5465.753959] ata1.00: failed command: READ FPDMA QUEUED
[ 5465.753969] ata1.00: cmd 60/00:10:00:9b:f5/01:00:53:00:00/40 tag 2 ncq dma
131072 in
res 41/40:00:c0:9b:f5/00:01:53:00:00/00 Emask 0x409
(media error)
[ 5465.753973] ata1.00: status: { DRDY ERR }
[ 5465.753976] ata1.00: error: { UNC }
[ 5466.031887] ata1.00: configured for UDMA/133
[ 5466.031915] sd 0:0:0:0: [sda] tag#2 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[ 5466.031921] sd 0:0:0:0: [sda] tag#2 Sense Key : Medium Error [current]
[ 5466.031925] sd 0:0:0:0: [sda] tag#2 Add. Sense: Unrecovered read error -
auto reallocate failed
[ 5466.031932] sd 0:0:0:0: [sda] tag#2 CDB: Read(10) 28 00 53 f5 9b 00 00 01
00 00
[ 5466.031935] print_req_error: I/O error, dev sda, sector 1408605120
[ 5466.031994] ata1: EH complete
---
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 2 01:04:22 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 390.77, 4.15.0-36-generic, x86_64: installed
 nvidia, 390.77, 4.15.0-38-generic, x86_64: installed
DpkgLog:
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Very infrequently
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e]
(rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:382b]
   Subsystem: Lenovo GM108M [GeForce 920MX] [17aa:382b]
InstallationDate: Installed on 2018-10-04 (28 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
MachineType: LENOVO 80QQ
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic
root=UUID=b0abddd7-646b-4707-bf44-54c3fc3ea828 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/21/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: E0CN63WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Nano 5B6
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 100-15IBD
dmi.modalias:
dmi:bvnLENOVO:bvrE0CN63WW:bd10/21/2016:svnLENOVO:pn80QQ:pvrLenovoideapad100-15IBD:rvnLENOVO:rnNano5B6:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad100-15IBD:
dmi.product.family: IDEAPAD
dmi.product.name: 80QQ
dmi.product.version: Lenovo ideapad 100-15IBD
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801202/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801202] Status changed to Confirmed
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1801202
Title:
Xorg freeze
Status in linux package in Ubuntu:
Incomplete
Status in xorg-server package in Ubuntu:
New
Bug description:
The screen freezes suddenly when i'm trying to play an online video or
when i have too many tabs or folders open.
---
CurrentDmesg.txt:
[ 5465.753948] ata1.00: exception Emask 0x0 SAct 0x1c04 SErr 0x0 action 0x0
[ 5465.753954] ata1.00: irq_stat 0x4008
[ 5465.753959] ata1.00: failed command: READ FPDMA QUEUED
[ 5465.753969] ata1.00: cmd 60/00:10:00:9b:f5/01:00:53:00:00/40 tag 2 ncq dma
131072 in
res 41/40:00:c0:9b:f5/00:01:53:00:00/00 Emask 0x409
(media error)
[ 5465.753973] ata1.00: status: { DRDY ERR }
[ 5465.753976] ata1.00: error: { UNC }
[ 5466.031887] ata1.00: configured for UDMA/133
[ 5466.031915] sd 0:0:0:0: [sda] tag#2 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[ 5466.031921] sd 0:0:0:0: [sda] tag#2 Sense Key : Medium Error [current]
[ 5466.031925] sd 0:0:0:0: [sda] tag#2 Add. Sense: Unrecovered read error -
auto reallocate failed
[ 5466.031932] sd 0:0:0:0: [sda] tag#2 CDB: Read(10) 28 00 53 f5 9b 00 00 01
00 00
[ 5466.031935] print_req_error: I/O error, dev sda, sector 1408605120
[ 5466.031994] ata1: EH complete
---
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 2 01:04:22 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 390.77, 4.15.0-36-generic, x86_64: installed
 nvidia, 390.77, 4.15.0-38-generic, x86_64: installed
DpkgLog:
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Very infrequently
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e]
(rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:382b]
   Subsystem: Lenovo GM108M [GeForce 920MX] [17aa:382b]
InstallationDate: Installed on 2018-10-04 (28 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
MachineType: LENOVO 80QQ
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic
root=UUID=b0abddd7-646b-4707-bf44-54c3fc3ea828 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/21/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: E0CN63WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Nano 5B6
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 100-15IBD
dmi.modalias:
dmi:bvnLENOVO:bvrE0CN63WW:bd10/21/2016:svnLENOVO:pn80QQ:pvrLenovoideapad100-15IBD:rvnLENOVO:rnNano5B6:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad100-15IBD:
dmi.product.family: IDEAPAD
dmi.product.name: 80QQ
dmi.product.version: Lenovo ideapad 100-15IBD
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801202/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801202] Re: Xorg freeze
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".
Thanks in advance.
[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Description changed:
The screen freezes suddenly when i'm trying to play an online video or
when i have too many tabs or folders open.
+
+ ---
+
+ CurrentDmesg.txt:
+ [ 5465.753948] ata1.00: exception Emask 0x0 SAct 0x1c04 SErr 0x0 action 0x0
+ [ 5465.753954] ata1.00: irq_stat 0x4008
+ [ 5465.753959] ata1.00: failed command: READ FPDMA QUEUED
+ [ 5465.753969] ata1.00: cmd 60/00:10:00:9b:f5/01:00:53:00:00/40 tag 2 ncq dma
131072 in
+ res 41/40:00:c0:9b:f5/00:01:53:00:00/00 Emask 0x409
(media error)
+ [ 5465.753973] ata1.00: status: { DRDY ERR }
+ [ 5465.753976] ata1.00: error: { UNC }
+ [ 5466.031887] ata1.00: configured for UDMA/133
+ [ 5466.031915] sd 0:0:0:0: [sda] tag#2 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
+ [ 5466.031921] sd 0:0:0:0: [sda] tag#2 Sense Key : Medium Error [current]
+ [ 5466.031925] sd 0:0:0:0: [sda] tag#2 Add. Sense: Unrecovered read error -
auto reallocate failed
+ [ 5466.031932] sd 0:0:0:0: [sda] tag#2 CDB: Read(10) 28 00 53 f5 9b 00 00 01
00 00
+ [ 5466.031935] print_req_error: I/O error, dev sda, sector 1408605120
+ [ 5466.031994] ata1: EH complete
+
+ ---
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 2 01:04:22 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 390.77, 4.15.0-36-generic, x86_64: installed
 nvidia, 390.77, 4.15.0-38-generic, x86_64: installed
DpkgLog:
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Very infrequently
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e]
(rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:382b]
   Subsystem: Lenovo GM108M [GeForce 920MX] [17aa:382b]
InstallationDate: Installed on 2018-10-04 (28 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
MachineType: LENOVO 80QQ
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic
root=UUID=b0abddd7-646b-4707-bf44-54c3fc3ea828 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/21/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: E0CN63WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Nano 5B6
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 100-15IBD
dmi.modalias:
dmi:bvnLENOVO:bvrE0CN63WW:bd10/21/2016:svnLENOVO:pn80QQ:pvrLenovoideapad100-15IBD:rvnLENOVO:rnNano5B6:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad100-15IBD:
dmi.product.family: IDEAPAD
dmi.product.name: 80QQ
dmi.product.version: Lenovo ideapad 100-15IBD
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1801202
Title:
Xorg freeze
Status in linux package in Ubuntu:
Incomplete
Status in xorg-server package in Ubuntu:
New
Bug description:
The
[Kernel-packages] [Bug 1801181] Re: Pixelized display
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801181 Title: Pixelized display Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: New Bug description: Artefakty upgrading to 18.04 lts three iż a problem without display. I have no duch problem on 16.04 lts --- CurrentDmesg.txt: [ 29.779035] radeon :01:00.0: r600_check_texture_resource:1566 tex pitch (1680, 0x40, 1) invalid [ 29.779082] [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream ! [ 30.612745] radeon :01:00.0: r600_check_texture_resource:1566 tex pitch (1680, 0x40, 1) invalid [ 30.612804] [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream ! -- ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Thu Nov 1 22:51:23 2018 DistUpgraded: 2018-11-01 22:32:47,052 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] No such file or directory: './xorg_fix_proprietary.py') DistroCodename: bionic DistroVariant: ubuntu DkmsStatus:  bcmwl, 6.30.223.271+bdcom, 4.15.0-38-generic, x86_64: installed  bcmwl, 6.30.223.271+bdcom, 4.4.0-130-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard:  Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller])    Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:2115]  Advanced Micro Devices, Inc. [AMD/ATI] RV635/M86 [Mobility Radeon HD 3650] [1002:9591] (prog-if 00 [VGA controller])    Subsystem: Lenovo RV635/M86 [Mobility Radeon HD 3650] [17aa:2116] InstallationDate: Installed on 2015-03-10 (1332 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: LENOVO 2087A37 PccardctlIdent:  Socket 0:    no product info available PccardctlStatus:  Socket 0:    no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=76e45c9b-b94c-414a-9c7f-cfbbafb58a1a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-11-01 (0 days ago) dmi.bios.date: 10/12/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6FET93WW (3.23 ) dmi.board.name: 2087A37 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6FET93WW(3.23):bd10/12/2012:svnLENOVO:pn2087A37:pvrThinkPadT500:rvnLENOVO:rn2087A37:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T500 dmi.product.name: 2087A37 dmi.product.version: ThinkPad T500 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Nov 1 20:57:30 2018 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801181/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769480] Re: Ubuntu 18.04 - networkmanager dont show other wifi after few minutes
Is there any chance to reactivate that topic? I have the same issue on a fresh Lubuntu 18.10 installation on my Sony Vaio Notebook. After 5 minutes the tray icon (nm-tray) only shows the current wifi connection (which still works), no others anymore. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769480 Title: Ubuntu 18.04 - networkmanager dont show other wifi after few minutes Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Confirmed Bug description: how to reproduce: dd the iso to an usb drive and boot from it. List all wifi devices in live-mode and connect to one of it. Use the web for some minutes. Open up the wifi on the top right again and list the available networks - it dont show any others any more. Just the one you are connected to. How to overcome the bug: put the computer into airplane mode and go away from airplane mode again. Or: disconnect the usb wifi device and connect it again. Does this bug exist also on installed 18.04 and updated to last (apt update, apt upgrade, apt dist-upgrade)? Yes What wifi device is been used: ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3572, rev 0223 detected ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 0009 detected ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' usbcore: registered new interface driver rt2800usb ... ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2870.bin' ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.36 uname -a Linux t 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769480/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799408] Re: linux-kvm: 4.4.0-1037.43 -proposed tracker
** 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: 1799401 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: - security-signoff: Waiting for signoff verification-testing: Testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1799408 Title: linux-kvm: 4.4.0-1037.43 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released 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: 1799401 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801116] Re: linux-aws: 4.15.0-1027.27 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Invalid ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1799411 phase: Packaging reason: - prepare-package: Version not specified + prepare-package: Package not yet uploaded + prepare-package-meta: Package not yet uploaded -- 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/1801116 Title: linux-aws: 4.15.0-1027.27 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1799411 phase: Packaging reason: prepare-package: Package not yet uploaded prepare-package-meta: Package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1801116/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798182] Re: Update ENA driver to version 2.0.1K
** Changed in: linux-aws (Ubuntu Xenial) Status: In Progress => Fix Committed ** Changed in: linux-aws (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux-aws (Ubuntu Cosmic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798182 Title: Update ENA driver to version 2.0.1K Status in linux package in Ubuntu: In Progress Status in linux-aws package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux-aws source package in Xenial: Fix Committed Status in linux source package in Bionic: In Progress Status in linux-aws source package in Bionic: Fix Committed Status in linux source package in Cosmic: In Progress Status in linux-aws source package in Cosmic: Fix Committed Bug description: The following commits from mainline, linux-next, and net-next: Arthur Kiyanovski (18):   net: ena: fix warning in rmmod caused by double iounmap   net: ena: fix rare bug when failed restart/resume is followed by driver removal   net: ena: fix NULL dereference due to untimely napi initialization   net: ena: fix auto casting to boolean   net: ena: minor performance improvement   net: ena: complete host info to match latest ENA spec   net: ena: introduce Low Latency Queues data structures according to ENA spec   net: ena: add functions for handling Low Latency Queues in ena_com   net: ena: add functions for handling Low Latency Queues in ena_netdev   net: ena: use CSUM_CHECKED device indication to report skb's checksum status   net: ena: explicit casting and initialization, and clearer error handling   net: ena: limit refill Rx threshold to 256 to avoid latency issues   net: ena: change rx copybreak default to reduce kernel memory pressure   net: ena: remove redundant parameter in ena_com_admin_init()   net: ena: update driver version to 2.0.1   net: ena: fix indentations in ena_defs for better readability   net: ena: enable Low Latency Queues   net: ena: fix compilation error in xtensa architecture Eric Dumazet (1):   net: ena: remove ndo_poll_controller Netanel Belgazal (1):   net: ena: Fix Kconfig dependency on X86 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798182/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797092] Re: xenial guest on arm64 drops to busybux under openstack bionic-rocky
** Description changed: [Impact] - on openstack rocky-bionic (with patch, see 1771662), xenial guests will fail to launch as they drop to the busybox prompt after booting. + on openstack rocky-bionic (with patch, see 1771662), xenial guests will fail to launch as they drop to the busybox prompt after booting. The reason is that the EFI firmware image switched to ACPI mode by default in bionic. We knew that was happening, and backported some minimal ACPI support to keep xenial guests booting (bug 1744754). But, now we're seeing guests panic when trying to initialize PCI. [Test Case] Deploy rocky-bionic OpenStack and try to launch a xenial guest. - [Fix] Backport ACPI/PCIe support for arm64 from upstream. [ Regression Risk ] TLDR: Definitely warrants some regression testing on armhf/arm64, but regression risk seems low for other architectures. Here's a patch-by-patch risk analysis: > 0001-UBUNTU-Config-CONFIG_PCI_ECAM-y.patch Enables code that will be added in the next patch. > 0002-PCI-Provide-common-functions-for-ECAM-mapping.patch Only adds new code w/ no callers yet > 0003-PCI-generic-thunder-Use-generic-ECAM-API.patch As noted in the commit message: "The patch does not introduce any functional changes other than a very minor one: with the new code, on 64-bit platforms, we do just a single ioremap for the whole config space." > 0004-PCI-of-Move-PCI-I-O-space-management-to-PCI-core-cod.patch As noted, no functional change. > 0005-PCI-Move-ecam.h-to-linux-include-pci-ecam.h.patch As noted, no functional change. > 0006-PCI-Add-parent-device-field-to-ECAM-struct-pci_confi.patch This makes changes to the ecam code, but that was added in this series, so no regression risk there. The pci-thunder-pem changes will be regression tested on the hardware that uses that driver (Cavium ThunderX). > 0007-PCI-Add-pci_unmap_iospace-to-unmap-I-O-resources.patch Only adds new code, w/ no callers yet > 0008-PCI-ACPI-Support-I-O-resources-when-parsing-host-bri.patch Adds and calls a new function that is a no-op on !ARM (PCI_IOBASE is only defined on ARM). Also adds a call to pci_unmap_iospace(), which was added in a previous patch and is also a no-op on !ARM. > 0009-UBUNTU-Config-CONFIG_ACPI_MCFG-y.patch Enables code that will be added in the next patch. > 0010-PCI-ACPI-Add-generic-MCFG-table-handling.patch Adds parsing of a new ACPI table. A possible regression risk to platforms an MCFG table that were working fine w/ 4.4 and there's a latent bug in this parsing code. > 0011-PCI-Refactor-pci_bus_assign_domain_nr-for-CONFIG_PCI.patch As noted, no functional change intended. > 0012-PCI-Factor-DT-specific-pci_bus_find_domain_nr-code-o.patch Again, no functional change. > 0013-ARM64-PCI-Add-acpi_pci_bus_find_domain_nr.patch Only impacts ARM due to CONFIG_PCI_DOMAINS_GENERIC guard > 0014-ARM64-PCI-ACPI-support-for-legacy-IRQs-parsing-and-c.patch arm64-specific PCI initialization code - mitigate risk by regression testing on supported platforms (X-Gene, ThunderX). > 0015-ARM64-PCI-Support-ACPI-based-PCI-host-controller.patch Adds new code for arm64-ACPI support. We didn't previously support these devices, so regression risk is negligible. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797092 Title: xenial guest on arm64 drops to busybux under openstack bionic-rocky Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Triaged Status in linux source package in Bionic: Fix Released Bug description: [Impact] on openstack rocky-bionic (with patch, see 1771662), xenial guests will fail to launch as they drop to the busybox prompt after booting. The reason is that the EFI firmware image switched to ACPI mode by default in bionic. We knew that was happening, and backported some minimal ACPI support to keep xenial guests booting (bug 1744754). But, now we're seeing guests panic when trying to initialize PCI. [Test Case] Deploy rocky-bionic OpenStack and try to launch a xenial guest. [Fix] Backport ACPI/PCIe support for arm64 from upstream. [ Regression Risk ] TLDR: Definitely warrants some regression testing on armhf/arm64, but regression risk seems low for other architectures. Here's a patch-by-patch risk analysis: > 0001-UBUNTU-Config-CONFIG_PCI_ECAM-y.patch Enables code that will be added in the next patch. > 0002-PCI-Provide-common-functions-for-ECAM-mapping.patch Only adds new code w/ no callers yet > 0003-PCI-generic-thunder-Use-generic-ECAM-API.patch As noted in the commit message: "The patch does not introduce any functional changes other than a very minor one: with the new code, on 64-bit platforms, we do just a single ioremap for the whole config space." >
[Kernel-packages] [Bug 1801116] Re: linux-aws: 4.15.0-1027.27 -proposed tracker
** Summary changed: - linux-aws: -proposed tracker + linux-aws: 4.15.0-1027.27 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) -- 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/1801116 Title: linux-aws: 4.15.0-1027.27 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1799411 phase: Packaging reason: prepare-package: Version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1801116/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797092] Re: xenial guest on arm64 drops to busybux under openstack bionic-rocky
I'm not aware of any armhf hardware that has PCI and was supported by the 4.4 kernel. Calxeda gear maybe - but that was never officially released and I don't have access to it anyway. I did regression test using the virt model in QEMU. System still boots, lspci smoke tests OK: ubuntu@ubuntu:~$ lspci 00:00.0 Host bridge: Red Hat, Inc. QEMU PCIe Host bridge Kernel messages during PCI probe look identical, except we now see ECAM messages (which makes sense, that support is new): 4.4.0+arm64acpipci.dmesg:[1.269192] PCI: CLS 0 bytes, default 64 4.4.0+arm64acpipci.dmesg:[6.708312] PCI host bridge /pcie@1000 ranges: 4.4.0+arm64acpipci.dmesg:[6.747553] pci-host-generic 3f00.pcie: PCI host bridge to bus :00 4.4.0+arm64acpipci.dmesg:[6.792745] PCI: bus0: Fast back to back transfers disabled 4.4.0+arm64acpipci.dmesg:[7.012429] ehci-pci: EHCI PCI platform driver 4.4.0+arm64acpipci.dmesg:[7.037416] ohci-pci: OHCI PCI platform driver 4.4.0.dmesg:[1.309199] PCI: CLS 0 bytes, default 64 4.4.0.dmesg:[6.733705] PCI host bridge /pcie@1000 ranges: 4.4.0.dmesg:[6.760085] pci-host-generic 3f00.pcie: PCI host bridge to bus :00 4.4.0.dmesg:[6.802961] PCI: bus0: Fast back to back transfers disabled 4.4.0.dmesg:[7.016247] ehci-pci: EHCI PCI platform driver 4.4.0.dmesg:[7.040325] ohci-pci: OHCI PCI platform driver -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797092 Title: xenial guest on arm64 drops to busybux under openstack bionic-rocky Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Triaged Status in linux source package in Bionic: Fix Released Bug description: [Impact] on openstack rocky-bionic (with patch, see 1771662), xenial guests will fail to launch as they drop to the busybox prompt after booting. [Test Case] Deploy rocky-bionic OpenStack and try to launch a xenial guest. [Fix] Backport ACPI/PCIe support for arm64 from upstream. [ Regression Risk ] TLDR: Definitely warrants some regression testing on armhf/arm64, but regression risk seems low for other architectures. Here's a patch-by-patch risk analysis: > 0001-UBUNTU-Config-CONFIG_PCI_ECAM-y.patch Enables code that will be added in the next patch. > 0002-PCI-Provide-common-functions-for-ECAM-mapping.patch Only adds new code w/ no callers yet > 0003-PCI-generic-thunder-Use-generic-ECAM-API.patch As noted in the commit message: "The patch does not introduce any functional changes other than a very minor one: with the new code, on 64-bit platforms, we do just a single ioremap for the whole config space." > 0004-PCI-of-Move-PCI-I-O-space-management-to-PCI-core-cod.patch As noted, no functional change. > 0005-PCI-Move-ecam.h-to-linux-include-pci-ecam.h.patch As noted, no functional change. > 0006-PCI-Add-parent-device-field-to-ECAM-struct-pci_confi.patch This makes changes to the ecam code, but that was added in this series, so no regression risk there. The pci-thunder-pem changes will be regression tested on the hardware that uses that driver (Cavium ThunderX). > 0007-PCI-Add-pci_unmap_iospace-to-unmap-I-O-resources.patch Only adds new code, w/ no callers yet > 0008-PCI-ACPI-Support-I-O-resources-when-parsing-host-bri.patch Adds and calls a new function that is a no-op on !ARM (PCI_IOBASE is only defined on ARM). Also adds a call to pci_unmap_iospace(), which was added in a previous patch and is also a no-op on !ARM. > 0009-UBUNTU-Config-CONFIG_ACPI_MCFG-y.patch Enables code that will be added in the next patch. > 0010-PCI-ACPI-Add-generic-MCFG-table-handling.patch Adds parsing of a new ACPI table. A possible regression risk to platforms an MCFG table that were working fine w/ 4.4 and there's a latent bug in this parsing code. > 0011-PCI-Refactor-pci_bus_assign_domain_nr-for-CONFIG_PCI.patch As noted, no functional change intended. > 0012-PCI-Factor-DT-specific-pci_bus_find_domain_nr-code-o.patch Again, no functional change. > 0013-ARM64-PCI-Add-acpi_pci_bus_find_domain_nr.patch Only impacts ARM due to CONFIG_PCI_DOMAINS_GENERIC guard > 0014-ARM64-PCI-ACPI-support-for-legacy-IRQs-parsing-and-c.patch arm64-specific PCI initialization code - mitigate risk by regression testing on supported platforms (X-Gene, ThunderX). > 0015-ARM64-PCI-Support-ACPI-based-PCI-host-controller.patch Adds new code for arm64-ACPI support. We didn't previously support these devices, so regression risk is negligible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797092/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800963] Re: Changing Primary DIsplay Flips Which Display Has The Dock
This behavior is also encountered when using the nouveau display driver on a fresh install that hasn't had nvidia drivers installed. -- 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/1800963 Title: Changing Primary DIsplay Flips Which Display Has The Dock Status in gnome-control-center package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in xorg-server package in Ubuntu: Confirmed Bug description: On a fresh install from at least Ubuntu 17.04 up to 18.10, when I change Settings->Dock->Show on to a specific monitor on a dual monitor setup, this setting gets flipped if I change the primary display in Settings->Devices->Displays->Primary Display. For Example I have Monitor A and Monitor B After a fresh install Monitor A is primary with title bar, clock, etc. and the dock. If I change the dock to Show on Monitor B it moves as desired. But when I change Primary Display to Monitor B also, the dock immediately goes to Monitor A again. When I check the Show on setting it still displays Monitor B but it's actually on Monitor A. Selecting Monitor A will move the dock to Monitor B. Description: Ubuntu 18.04.1 LTS Release: 18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-31 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.77 Tue Jul 10 18:28:52 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: nvidia, 390.77, 4.15.0-29-generic, x86_64: installed nvidia, 390.77, 4.15.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GK104 [GeForce GTX 760] [1043:8472] InstallationDate: Installed on 2018-10-31 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUS All Series NonfreeKernelModules: nvidia_modeset nvidia Package: xorg-server (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=f29793fe-db23-4afe-a808-426f9bc10fda ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Tags: bionic ubuntu Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx 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:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
[Kernel-packages] [Bug 1799401] Re: linux: 4.4.0-139.165 -proposed tracker
** 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 1799403 (linux-aws), bug 1799404 (linux-lts-xenial) derivatives: bug 1799405 (linux-aws), bug 1799407 (linux-euclid), bug 1799408 (linux-kvm), bug 1799409 (linux-raspi2), bug 1799410 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress - security-signoff: Waiting for signoff snap-certification-testing: Ready verification-testing: Testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799401 Title: linux: 4.4.0-139.165 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Confirmed Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1799403 (linux-aws), bug 1799404 (linux-lts-xenial) derivatives: bug 1799405 (linux-aws), bug 1799407 (linux-euclid), bug 1799408 (linux-kvm), bug 1799409 (linux-raspi2), bug 1799410 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress snap-certification-testing: Ready verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799401/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799408] Re: linux-kvm: 4.4.0-1037.43 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released -- 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/1799408 Title: linux-kvm: 4.4.0-1037.43 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released 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: 1799401 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Waiting for signoff verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Also affects: unattended-upgrades (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Medium Status: Invalid ** Also affects: unattended-upgrades (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: unattended-upgrades (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Cosmic) Status: New => Invalid ** Changed in: linux (Ubuntu Bionic) Status: New => Invalid ** Changed in: unattended-upgrades (Ubuntu Cosmic) Status: New => Fix Released ** Changed in: unattended-upgrades (Ubuntu Disco) Status: New => Fix Released ** Changed in: unattended-upgrades (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796376 Title: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode Status in linux package in Ubuntu: Invalid Status in unattended-upgrades package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in unattended-upgrades source package in Bionic: Confirmed Status in linux source package in Cosmic: Invalid Status in unattended-upgrades source package in Cosmic: Fix Released Status in linux source package in Disco: Invalid Status in unattended-upgrades source package in Disco: Fix Released Bug description: Since the following linux-cloud-tools-common package versions : Xenial : 4.4.0-135.161 Bionic : 4.15.0-34.37 the Systemd service unit file for hv-kvp-daemon has been modified with new dependencies that make the package unable to be upgraded with unattended-upgrades on shutdown mode. Unattended-upgrades hangs with the linux-cloud-tools-common package during "Preparing to unpack". The server restarts after the unattended-upgrades service timeout expires. - Package state after reboot : iFR linux-cloud-tools-common 4.15.0-34.37 all Linux kernel version specific cloud tools for version 4.15.0 - Unattended-upgrades dpkg logs : Log started: 2018-10-05 17:59:04 (Reading database ... 52043 files and directories currently installed.) Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ... Log ended: 2018-10-05 18:00:54 - Impact : The current impact is very important as all security updates are blocked until you manually fix each server with : dpkg --configure -a apt install --only-upgrade linux-cloud-tools-common - Workaround/Fix : As a simple straightforward fix, replacing : Before=shutdown.target cloud-init-local.service walinuxagent.service with : Before=shutdown.target walinuxagent.service makes the package upgradable during shutdown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799401] Re: linux: 4.4.0-139.165 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff 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/1799401 Title: linux: 4.4.0-139.165 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Confirmed Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1799403 (linux-aws), bug 1799404 (linux-lts-xenial) derivatives: bug 1799405 (linux-aws), bug 1799407 (linux-euclid), bug 1799408 (linux-kvm), bug 1799409 (linux-raspi2), bug 1799410 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress snap-certification-testing: Ready verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799401/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792100] Re: Boot hangs at "loading initial ramdisk..."
What's interesting is the test kernel in comment #28 was tested as good. That was built with commit 19e56be2af5 as the tip of the tree. That commit is only one commit behind 22df1539aed9, which is the version tag. However, the bug exists when commit 22df1539aed9 is the tip. I built a v2 version of 4.15.0-33. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1792100 Can you test that kernel and report back if it has the bug or not? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792100 Title: Boot hangs at "loading initial ramdisk..." Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: I cannot load a kernel beyond 4.15.0-32-generic on my machine. Both 4.15.0-33-generic and 4.15.0-34-generic hang at "loading initial ramdisk...". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kms2233 F pulseaudio /dev/snd/controlC1: kms2233 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Sep 12 10:52:00 2018 HibernationDevice: RESUME=UUID=c3d34d19-9e9e-4967-ac45-f1d699cf5eef InstallationDate: Installed on 2018-01-05 (249 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Dell Inc. Precision Tower 7810 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=90d43be7-a2f7-4500-8b88-9bd7a549d96d ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-05-02 (132 days ago) dmi.bios.date: 06/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A27 dmi.board.name: 0KJCC5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA27:bd06/25/2018:svnDellInc.:pnPrecisionTower7810:pvr:rvnDellInc.:rn0KJCC5:rvrA00:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 7810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792100/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798208] Re: smartpqi updates for ubuntu 18.04.2
I built a test kernel with the five commits posed in comment #5. The test
kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1798208
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic) you need to install the
linux-image and linux-image-extra .deb packages.
• If the test kernel is 4.15(Bionic) or newer, you need to install the
linux-modules, linux-modules-extra and linux-image-unsigned .deb packages.
Thanks in advance!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1798208
Title:
smartpqi updates for ubuntu 18.04.2
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Cosmic:
In Progress
Bug description:
== SRU Justification ==
Microsemi is requesting these five patches to be added to 18.04.2 to bring
the driver up to date with kernel.org and to correct issues seen
particularly on ARM systems. The 18.04.2 kernel will be 4.18 bases, so
this SRU request is for Cosmic.
All five of these commits cherry pick cleanly and are in mainline as of
v4.19-rc1.
== Fixes ==
957c5ab108c7 ("scsi: smartpqi: improve handling for sync requests")
26b390aba2a8 ("scsi: smartpqi: improve error checking for sync requests")
9f8d05fa9844 ("scsi: smartpqi: add inspur advantech ids")
dac12fbc7b0a ("scsi: smartpqi: fix critical ARM issue reading PQI index
registers")
4ae5e9d159f8 ("scsi: smartpqi: bump driver version to 1.1.4-130")
== Regression Potential ==
Low. These five patches are limited to scsi/smartpqi.
This is a request to update the SmartPQI driver in Ubuntu kernel 18.04.2 by
pulling the following patches from upstream kernel version 4.19-rc7.
Microsemi would like added to Ubuntu 18.04.2 to bring the driver up to date
with kernel.org and to
correct issues seen particularly on ARM systems.
These patches cherry-pick cleanly from:
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
0001-scsi-smartpqi-add-in-new-supported-controllers.patch
 commit b0f9408b14838566b2a9b26434fab667c2afb0ea
 No functionality change.
 Add in more supported controllers.
0002-scsi-smartpqi-workaround-fw-bug-for-oq-deletion.patch
 commit 339faa8150fd56891105bc69fc18f5d51b8a63dd
 Correct PQI operational queue deletion.
 Operational queues are deleted during resets.
0003-scsi-smartpqi-update-driver-version.patch
 commit 61c187e46ebb27f51b52bd0eb68b7f534a300184
 No functionality change.
 Need context for the next version change patch below.
0004-scsi-smartpqi-improve-handling-for-sync-requests.patch
 commit 957c5ab108c7d98369b7524daea532c0ebbcf845
 Correct driver active thread count when submitting internal commands.
0005-scsi-smartpqi-improve-error-checking-for-sync-reques.patch
 commit 26b390aba2a8f7b9dd5ce4e3ada9431de327da6d
 Retry INQUIRY operations.
0006-scsi-smartpqi-add-inspur-advantech-ids.patch
 commit 9f8d05fa98442de78d1ab30235b0cc656ed7aff0
 No functionality change.
 Add in more supported controllers.
0007-scsi-smartpqi-fix-critical-ARM-issue-reading-PQI-ind.patch
 commit dac12fbc7b0a433a160b89212a56e155c94f3a80
 Critical bug fix for ARM.
 ARM does not handle volatile variables.
0008-scsi-smartpqi-bump-driver-version-to-1.1.4-130.patch
 commit 4ae5e9d159f83392c98c4ed88dfc63f19745be38
 No functionality change.
There are some other patches but they are kernel-wide patches that affect
other modules:
blk-mq-Allow-PCI-vector-offset-for-mapping-queues.patch
 commit f23f5bece686a76598335141a091934f7eb0998c
 This is a kernel-wide patch that affects multiple modules:
   block/blk-mq-pci.c
   drivers/nvme/host/pci.c
   drivers/scsi/qla2xxx/qla_os.c
   drivers/scsi/smartpqi/smartpqi_init.c
   include/linux/blk-mq-pci.h
commit 6396bb221514d2876fd6dc0aa2a1f240d99b37bb
Author: Kees Cook
Date: Tue Jun 12 14:03:40 2018 -0700
treewide: kzalloc() -> kcalloc()
commit 6da2ec56059c3c7a7e5f729e6349e74ace1e5c57
Author: Kees Cook
Date: Tue Jun 12 13:55:00 2018 -0700
treewide: kmalloc() -> kmalloc_array()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798208/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1650337] Re: unknown filesystem efivarfs
Alkis, please add yourself to "This bug affects you". -- 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/1650337 Title: unknown filesystem efivarfs Status in linux-signed package in Ubuntu: Confirmed Bug description: Please add file system efivarfs to 32-bit Linux kernel, so on EFI machine following command could be executed: sudo mount -t efivarfs efivarfs /sys/firmware/efi/efivars See also: bug 1648278 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1650337/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798208] Re: smartpqi updates for ubuntu 18.04.2
SRU Request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-November/096402.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1798208
Title:
smartpqi updates for ubuntu 18.04.2
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Cosmic:
In Progress
Bug description:
== SRU Justification ==
Microsemi is requesting these five patches to be added to 18.04.2 to bring
the driver up to date with kernel.org and to correct issues seen
particularly on ARM systems. The 18.04.2 kernel will be 4.18 bases, so
this SRU request is for Cosmic.
All five of these commits cherry pick cleanly and are in mainline as of
v4.19-rc1.
== Fixes ==
957c5ab108c7 ("scsi: smartpqi: improve handling for sync requests")
26b390aba2a8 ("scsi: smartpqi: improve error checking for sync requests")
9f8d05fa9844 ("scsi: smartpqi: add inspur advantech ids")
dac12fbc7b0a ("scsi: smartpqi: fix critical ARM issue reading PQI index
registers")
4ae5e9d159f8 ("scsi: smartpqi: bump driver version to 1.1.4-130")
== Regression Potential ==
Low. These five patches are limited to scsi/smartpqi.
This is a request to update the SmartPQI driver in Ubuntu kernel 18.04.2 by
pulling the following patches from upstream kernel version 4.19-rc7.
Microsemi would like added to Ubuntu 18.04.2 to bring the driver up to date
with kernel.org and to
correct issues seen particularly on ARM systems.
These patches cherry-pick cleanly from:
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
0001-scsi-smartpqi-add-in-new-supported-controllers.patch
 commit b0f9408b14838566b2a9b26434fab667c2afb0ea
 No functionality change.
 Add in more supported controllers.
0002-scsi-smartpqi-workaround-fw-bug-for-oq-deletion.patch
 commit 339faa8150fd56891105bc69fc18f5d51b8a63dd
 Correct PQI operational queue deletion.
 Operational queues are deleted during resets.
0003-scsi-smartpqi-update-driver-version.patch
 commit 61c187e46ebb27f51b52bd0eb68b7f534a300184
 No functionality change.
 Need context for the next version change patch below.
0004-scsi-smartpqi-improve-handling-for-sync-requests.patch
 commit 957c5ab108c7d98369b7524daea532c0ebbcf845
 Correct driver active thread count when submitting internal commands.
0005-scsi-smartpqi-improve-error-checking-for-sync-reques.patch
 commit 26b390aba2a8f7b9dd5ce4e3ada9431de327da6d
 Retry INQUIRY operations.
0006-scsi-smartpqi-add-inspur-advantech-ids.patch
 commit 9f8d05fa98442de78d1ab30235b0cc656ed7aff0
 No functionality change.
 Add in more supported controllers.
0007-scsi-smartpqi-fix-critical-ARM-issue-reading-PQI-ind.patch
 commit dac12fbc7b0a433a160b89212a56e155c94f3a80
 Critical bug fix for ARM.
 ARM does not handle volatile variables.
0008-scsi-smartpqi-bump-driver-version-to-1.1.4-130.patch
 commit 4ae5e9d159f83392c98c4ed88dfc63f19745be38
 No functionality change.
There are some other patches but they are kernel-wide patches that affect
other modules:
blk-mq-Allow-PCI-vector-offset-for-mapping-queues.patch
 commit f23f5bece686a76598335141a091934f7eb0998c
 This is a kernel-wide patch that affects multiple modules:
   block/blk-mq-pci.c
   drivers/nvme/host/pci.c
   drivers/scsi/qla2xxx/qla_os.c
   drivers/scsi/smartpqi/smartpqi_init.c
   include/linux/blk-mq-pci.h
commit 6396bb221514d2876fd6dc0aa2a1f240d99b37bb
Author: Kees Cook
Date: Tue Jun 12 14:03:40 2018 -0700
treewide: kzalloc() -> kcalloc()
commit 6da2ec56059c3c7a7e5f729e6349e74ace1e5c57
Author: Kees Cook
Date: Tue Jun 12 13:55:00 2018 -0700
treewide: kmalloc() -> kmalloc_array()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798208/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798208] Re: smartpqi updates for ubuntu 18.04.2
The following five commits are the only patches needed, since 18.04.2
will be based on the upstream 4.18 kernel, which already contains the
other requested commits:
957c5ab108c7 ("scsi: smartpqi: improve handling for sync requests")
26b390aba2a8 ("scsi: smartpqi: improve error checking for sync requests")
9f8d05fa9844 ("scsi: smartpqi: add inspur advantech ids")
dac12fbc7b0a ("scsi: smartpqi: fix critical ARM issue reading PQI index
registers")
4ae5e9d159f8 ("scsi: smartpqi: bump driver version to 1.1.4-130")
** Description changed:
+
+ == SRU Justification ==
+ Microsemi is requesting these five patches to be added to 18.04.2 to bring
+ the driver up to date with kernel.org and to correct issues seen
+ particularly on ARM systems. The 18.04.2 kernel will be 4.18 bases, so
+ this SRU request is for Cosmic.
+
+ All five of these commits cherry pick cleanly and are in mainline as of
+ v4.19-rc1.
+
+ == Fixes ==
+ 957c5ab108c7 ("scsi: smartpqi: improve handling for sync requests")
+ 26b390aba2a8 ("scsi: smartpqi: improve error checking for sync requests")
+ 9f8d05fa9844 ("scsi: smartpqi: add inspur advantech ids")
+ dac12fbc7b0a ("scsi: smartpqi: fix critical ARM issue reading PQI index
registers")
+ 4ae5e9d159f8 ("scsi: smartpqi: bump driver version to 1.1.4-130")
+
+ == Regression Potential ==
+ Low. These five patches are limited to scsi/smartpqi.
+
+
This is a request to update the SmartPQI driver in Ubuntu kernel 18.04.2 by
pulling the following patches from upstream kernel version 4.19-rc7.
- Microsemi would like added to Ubuntu 18.04.2 to bring the driver up to date
with kernel.org and to
+ Microsemi would like added to Ubuntu 18.04.2 to bring the driver up to date
with kernel.org and to
correct issues seen particularly on ARM systems.
These patches cherry-pick cleanly from:
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
0001-scsi-smartpqi-add-in-new-supported-controllers.patch
- commit b0f9408b14838566b2a9b26434fab667c2afb0ea
- No functionality change.
- Add in more supported controllers.
+ Â commit b0f9408b14838566b2a9b26434fab667c2afb0ea
+ Â No functionality change.
+ Â Add in more supported controllers.
0002-scsi-smartpqi-workaround-fw-bug-for-oq-deletion.patch
- commit 339faa8150fd56891105bc69fc18f5d51b8a63dd
- Correct PQI operational queue deletion.
- Operational queues are deleted during resets.
+ Â commit 339faa8150fd56891105bc69fc18f5d51b8a63dd
+ Â Correct PQI operational queue deletion.
+ Â Operational queues are deleted during resets.
0003-scsi-smartpqi-update-driver-version.patch
- commit 61c187e46ebb27f51b52bd0eb68b7f534a300184
- No functionality change.
- Need context for the next version change patch below.
+ Â commit 61c187e46ebb27f51b52bd0eb68b7f534a300184
+ Â No functionality change.
+ Â Need context for the next version change patch below.
0004-scsi-smartpqi-improve-handling-for-sync-requests.patch
- commit 957c5ab108c7d98369b7524daea532c0ebbcf845
- Correct driver active thread count when submitting internal commands.
+ Â commit 957c5ab108c7d98369b7524daea532c0ebbcf845
+ Â Correct driver active thread count when submitting internal commands.
0005-scsi-smartpqi-improve-error-checking-for-sync-reques.patch
- commit 26b390aba2a8f7b9dd5ce4e3ada9431de327da6d
- Retry INQUIRY operations.
+ Â commit 26b390aba2a8f7b9dd5ce4e3ada9431de327da6d
+ Â Retry INQUIRY operations.
0006-scsi-smartpqi-add-inspur-advantech-ids.patch
- commit 9f8d05fa98442de78d1ab30235b0cc656ed7aff0
- No functionality change.
- Add in more supported controllers.
+ Â commit 9f8d05fa98442de78d1ab30235b0cc656ed7aff0
+ Â No functionality change.
+ Â Add in more supported controllers.
0007-scsi-smartpqi-fix-critical-ARM-issue-reading-PQI-ind.patch
- commit dac12fbc7b0a433a160b89212a56e155c94f3a80
- Critical bug fix for ARM.
- ARM does not handle volatile variables.
+ Â commit dac12fbc7b0a433a160b89212a56e155c94f3a80
+ Â Critical bug fix for ARM.
+ Â ARM does not handle volatile variables.
0008-scsi-smartpqi-bump-driver-version-to-1.1.4-130.patch
- commit 4ae5e9d159f83392c98c4ed88dfc63f19745be38
- No functionality change.
+ Â commit 4ae5e9d159f83392c98c4ed88dfc63f19745be38
+ Â No functionality change.
There are some other patches but they are kernel-wide patches that affect
other modules:
blk-mq-Allow-PCI-vector-offset-for-mapping-queues.patch
- commit f23f5bece686a76598335141a091934f7eb0998c
- This is a kernel-wide patch that affects multiple modules:
-block/blk-mq-pci.c
-drivers/nvme/host/pci.c
-drivers/scsi/qla2xxx/qla_os.c
-drivers/scsi/smartpqi/smartpqi_init.c
-include/linux/blk-mq-pci.h
+ Â commit f23f5bece686a76598335141a091934f7eb0998c
+ Â This is a kernel-wide patch that affects multiple modules:
+ Â Â
[Kernel-packages] [Bug 1801181] Re: Pixelized display
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19 ** Description changed: Artefakty upgrading to 18.04 lts three iż a problem without display. I have no duch problem on 16.04 lts + + --- + + CurrentDmesg.txt: + [ 29.779035] radeon :01:00.0: r600_check_texture_resource:1566 tex pitch (1680, 0x40, 1) invalid + [ 29.779082] [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream ! + [ 30.612745] radeon :01:00.0: r600_check_texture_resource:1566 tex pitch (1680, 0x40, 1) invalid + [ 30.612804] [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream ! + + -- + ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Thu Nov 1 22:51:23 2018 DistUpgraded: 2018-11-01 22:32:47,052 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] No such file or directory: './xorg_fix_proprietary.py') DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: - bcmwl, 6.30.223.271+bdcom, 4.15.0-38-generic, x86_64: installed - bcmwl, 6.30.223.271+bdcom, 4.4.0-130-generic, x86_64: installed +  bcmwl, 6.30.223.271+bdcom, 4.15.0-38-generic, x86_64: installed +  bcmwl, 6.30.223.271+bdcom, 4.4.0-130-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: - Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) -Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:2115] - Advanced Micro Devices, Inc. [AMD/ATI] RV635/M86 [Mobility Radeon HD 3650] [1002:9591] (prog-if 00 [VGA controller]) -Subsystem: Lenovo RV635/M86 [Mobility Radeon HD 3650] [17aa:2116] +  Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) +    Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:2115] +  Advanced Micro Devices, Inc. [AMD/ATI] RV635/M86 [Mobility Radeon HD 3650] [1002:9591] (prog-if 00 [VGA controller]) +    Subsystem: Lenovo RV635/M86 [Mobility Radeon HD 3650] [17aa:2116] InstallationDate: Installed on 2015-03-10 (1332 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: LENOVO 2087A37 PccardctlIdent: - Socket 0: -no product info available +  Socket 0: +    no product info available PccardctlStatus: - Socket 0: -no card +  Socket 0: +    no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=76e45c9b-b94c-414a-9c7f-cfbbafb58a1a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-11-01 (0 days ago) dmi.bios.date: 10/12/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6FET93WW (3.23 ) dmi.board.name: 2087A37 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6FET93WW(3.23):bd10/12/2012:svnLENOVO:pn2087A37:pvrThinkPadT500:rvnLENOVO:rn2087A37:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T500 dmi.product.name: 2087A37 dmi.product.version: ThinkPad T500 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Nov 1 20:57:30 2018 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 ** Also affects: linux (Ubuntu) Importance: Undecided
[Kernel-packages] [Bug 1798208] Re: smartpqi updates for ubuntu 18.04.2
** Tags added: cosmic kernel-da-key ** No longer affects: linux (Ubuntu Bionic) ** Changed in: linux (Ubuntu Cosmic) Status: Triaged => In Progress ** Changed in: linux (Ubuntu) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Cosmic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798208 Title: smartpqi updates for ubuntu 18.04.2 Status in linux package in Ubuntu: In Progress Status in linux source package in Cosmic: In Progress Bug description: This is a request to update the SmartPQI driver in Ubuntu kernel 18.04.2 by pulling the following patches from upstream kernel version 4.19-rc7. Microsemi would like added to Ubuntu 18.04.2 to bring the driver up to date with kernel.org and to correct issues seen particularly on ARM systems. These patches cherry-pick cleanly from: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 0001-scsi-smartpqi-add-in-new-supported-controllers.patch commit b0f9408b14838566b2a9b26434fab667c2afb0ea No functionality change. Add in more supported controllers. 0002-scsi-smartpqi-workaround-fw-bug-for-oq-deletion.patch commit 339faa8150fd56891105bc69fc18f5d51b8a63dd Correct PQI operational queue deletion. Operational queues are deleted during resets. 0003-scsi-smartpqi-update-driver-version.patch commit 61c187e46ebb27f51b52bd0eb68b7f534a300184 No functionality change. Need context for the next version change patch below. 0004-scsi-smartpqi-improve-handling-for-sync-requests.patch commit 957c5ab108c7d98369b7524daea532c0ebbcf845 Correct driver active thread count when submitting internal commands. 0005-scsi-smartpqi-improve-error-checking-for-sync-reques.patch commit 26b390aba2a8f7b9dd5ce4e3ada9431de327da6d Retry INQUIRY operations. 0006-scsi-smartpqi-add-inspur-advantech-ids.patch commit 9f8d05fa98442de78d1ab30235b0cc656ed7aff0 No functionality change. Add in more supported controllers. 0007-scsi-smartpqi-fix-critical-ARM-issue-reading-PQI-ind.patch commit dac12fbc7b0a433a160b89212a56e155c94f3a80 Critical bug fix for ARM. ARM does not handle volatile variables. 0008-scsi-smartpqi-bump-driver-version-to-1.1.4-130.patch commit 4ae5e9d159f83392c98c4ed88dfc63f19745be38 No functionality change. There are some other patches but they are kernel-wide patches that affect other modules: blk-mq-Allow-PCI-vector-offset-for-mapping-queues.patch commit f23f5bece686a76598335141a091934f7eb0998c This is a kernel-wide patch that affects multiple modules: block/blk-mq-pci.c drivers/nvme/host/pci.c drivers/scsi/qla2xxx/qla_os.c drivers/scsi/smartpqi/smartpqi_init.c include/linux/blk-mq-pci.h commit 6396bb221514d2876fd6dc0aa2a1f240d99b37bb Author: Kees Cook Date: Tue Jun 12 14:03:40 2018 -0700 treewide: kzalloc() -> kcalloc() commit 6da2ec56059c3c7a7e5f729e6349e74ace1e5c57 Author: Kees Cook Date: Tue Jun 12 13:55:00 2018 -0700 treewide: kmalloc() -> kmalloc_array() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798208/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801124] Re: linux-aws: 4.4.0-1072.82 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Invalid ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1799401 phase: Packaging reason: - prepare-package: Version not specified + prepare-package: Package not yet uploaded + prepare-package-meta: Package not yet uploaded -- 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/1801124 Title: linux-aws: 4.4.0-1072.82 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-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 -- kernel-stable-master-bug: 1799401 phase: Packaging reason: prepare-package: Package not yet uploaded prepare-package-meta: Package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1801124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798208] Re: smartpqi updates for ubuntu 18.04.2
** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu Cosmic) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Cosmic) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798208 Title: smartpqi updates for ubuntu 18.04.2 Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Bug description: This is a request to update the SmartPQI driver in Ubuntu kernel 18.04.2 by pulling the following patches from upstream kernel version 4.19-rc7. Microsemi would like added to Ubuntu 18.04.2 to bring the driver up to date with kernel.org and to correct issues seen particularly on ARM systems. These patches cherry-pick cleanly from: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 0001-scsi-smartpqi-add-in-new-supported-controllers.patch commit b0f9408b14838566b2a9b26434fab667c2afb0ea No functionality change. Add in more supported controllers. 0002-scsi-smartpqi-workaround-fw-bug-for-oq-deletion.patch commit 339faa8150fd56891105bc69fc18f5d51b8a63dd Correct PQI operational queue deletion. Operational queues are deleted during resets. 0003-scsi-smartpqi-update-driver-version.patch commit 61c187e46ebb27f51b52bd0eb68b7f534a300184 No functionality change. Need context for the next version change patch below. 0004-scsi-smartpqi-improve-handling-for-sync-requests.patch commit 957c5ab108c7d98369b7524daea532c0ebbcf845 Correct driver active thread count when submitting internal commands. 0005-scsi-smartpqi-improve-error-checking-for-sync-reques.patch commit 26b390aba2a8f7b9dd5ce4e3ada9431de327da6d Retry INQUIRY operations. 0006-scsi-smartpqi-add-inspur-advantech-ids.patch commit 9f8d05fa98442de78d1ab30235b0cc656ed7aff0 No functionality change. Add in more supported controllers. 0007-scsi-smartpqi-fix-critical-ARM-issue-reading-PQI-ind.patch commit dac12fbc7b0a433a160b89212a56e155c94f3a80 Critical bug fix for ARM. ARM does not handle volatile variables. 0008-scsi-smartpqi-bump-driver-version-to-1.1.4-130.patch commit 4ae5e9d159f83392c98c4ed88dfc63f19745be38 No functionality change. There are some other patches but they are kernel-wide patches that affect other modules: blk-mq-Allow-PCI-vector-offset-for-mapping-queues.patch commit f23f5bece686a76598335141a091934f7eb0998c This is a kernel-wide patch that affects multiple modules: block/blk-mq-pci.c drivers/nvme/host/pci.c drivers/scsi/qla2xxx/qla_os.c drivers/scsi/smartpqi/smartpqi_init.c include/linux/blk-mq-pci.h commit 6396bb221514d2876fd6dc0aa2a1f240d99b37bb Author: Kees Cook Date: Tue Jun 12 14:03:40 2018 -0700 treewide: kzalloc() -> kcalloc() commit 6da2ec56059c3c7a7e5f729e6349e74ace1e5c57 Author: Kees Cook Date: Tue Jun 12 13:55:00 2018 -0700 treewide: kmalloc() -> kmalloc_array() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798208/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801124] Re: linux-aws: 4.4.0-1072.82 -proposed tracker
** Summary changed: - linux-aws: -proposed tracker + linux-aws: 4.4.0-1072.82 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) -- 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/1801124 Title: linux-aws: 4.4.0-1072.82 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1799401 phase: Packaging reason: prepare-package: Version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1801124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode
The package include the following upstream fix : https://github.com/mvo5/unattended-upgrades/commit/cda637b0d89973fd46382418893a23bef4195a2f ** Also affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796376 Title: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode Status in linux package in Ubuntu: Confirmed Status in unattended-upgrades package in Ubuntu: New Bug description: Since the following linux-cloud-tools-common package versions : Xenial : 4.4.0-135.161 Bionic : 4.15.0-34.37 the Systemd service unit file for hv-kvp-daemon has been modified with new dependencies that make the package unable to be upgraded with unattended-upgrades on shutdown mode. Unattended-upgrades hangs with the linux-cloud-tools-common package during "Preparing to unpack". The server restarts after the unattended-upgrades service timeout expires. - Package state after reboot : iFR linux-cloud-tools-common 4.15.0-34.37 all Linux kernel version specific cloud tools for version 4.15.0 - Unattended-upgrades dpkg logs : Log started: 2018-10-05 17:59:04 (Reading database ... 52043 files and directories currently installed.) Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ... Log ended: 2018-10-05 18:00:54 - Impact : The current impact is very important as all security updates are blocked until you manually fix each server with : dpkg --configure -a apt install --only-upgrade linux-cloud-tools-common - Workaround/Fix : As a simple straightforward fix, replacing : Before=shutdown.target cloud-init-local.service walinuxagent.service with : Before=shutdown.target walinuxagent.service makes the package upgradable during shutdown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode
Guillaume can you use your protocol but this time using this test package[1] I wasn't able to reproduce with the change I made based on a bug fixed in Cosmic: https://bugs.launchpad.net/bugs/1778219 -- sudo add-apt-repository ppa:slashd/uu2 sudo apt-get update sudo apt-get install unattended-upgrades -- Let me know the outcome. Regards, Eric -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796376 Title: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode Status in linux package in Ubuntu: Confirmed Status in unattended-upgrades package in Ubuntu: New Bug description: Since the following linux-cloud-tools-common package versions : Xenial : 4.4.0-135.161 Bionic : 4.15.0-34.37 the Systemd service unit file for hv-kvp-daemon has been modified with new dependencies that make the package unable to be upgraded with unattended-upgrades on shutdown mode. Unattended-upgrades hangs with the linux-cloud-tools-common package during "Preparing to unpack". The server restarts after the unattended-upgrades service timeout expires. - Package state after reboot : iFR linux-cloud-tools-common 4.15.0-34.37 all Linux kernel version specific cloud tools for version 4.15.0 - Unattended-upgrades dpkg logs : Log started: 2018-10-05 17:59:04 (Reading database ... 52043 files and directories currently installed.) Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ... Log ended: 2018-10-05 18:00:54 - Impact : The current impact is very important as all security updates are blocked until you manually fix each server with : dpkg --configure -a apt install --only-upgrade linux-cloud-tools-common - Workaround/Fix : As a simple straightforward fix, replacing : Before=shutdown.target cloud-init-local.service walinuxagent.service with : Before=shutdown.target walinuxagent.service makes the package upgradable during shutdown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799399] Re: linux: 3.13.0-162.212 -proposed tracker
** 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 1799400 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED certification-testing: Testing in progress regression-testing: Testing in progress - security-signoff: Waiting for signoff verification-testing: Testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799399 Title: linux: 3.13.0-162.212 -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: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1799400 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED certification-testing: Testing in progress regression-testing: Testing in progress verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799399/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic
I also tested last kernel from mainline (following #25 & #26 ,just for confirmation...) [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19 modinfo rtl8723be says: filename: /lib/modules/4.19.0-041900-generic/kernel/drivers/net/wireless/realtek/rtlwifi/rtl8723be/rtl8723be.ko firmware: rtlwifi/rtl8723befw_36.bin firmware: rtlwifi/rtl8723befw.bin srcversion: CF0CBB2F4446A615D0ABCBE similarily with comment #58 wifi works out of the box (no ant_sel) it works also fine with ant_sel=0 (supposed to be equivalent) it works also fine with ant_sel=1 does not work with ant_sel=2 like for comment #53, the working ant_sel changed compared to reference kernel 4.15.0-32 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1234 F pulseaudio /dev/snd/controlC0: al 1234 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Notebook Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8137 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.02 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800693] Re: linux-azure: 4.15.0-1030.31~14.04.1 -proposed tracker
The package has been published and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow/promote-to-updates Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1797061 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Packages not yet published + kernel-stable-phase:Released + kernel-stable-phase-changed:Thursday, 01. November 2018 20: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-master-bug: 1797061 - phase: Promoted to proposed + phase: Released proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-updates: Packages not yet published - kernel-stable-phase:Released - kernel-stable-phase-changed:Thursday, 01. November 2018 20:05 UTC ** Tags removed: kernel-release-tracking-bug-live -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1800693 Title: linux-azure: 4.15.0-1030.31~14.04.1 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Fix Released 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: 1797061 phase: Released proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1800693/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800692] Re: linux-azure: 4.15.0-1030.31 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: Fix Committed => 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: 1797061 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Ready to copy + kernel-stable-phase:Promoted to updates + kernel-stable-phase-changed:Thursday, 01. November 2018 20:01 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1797061 - phase: Promoted to proposed + phase: Promoted to updates proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Ready to copy - kernel-stable-phase:Promoted to updates - kernel-stable-phase-changed:Thursday, 01. November 2018 20:01 UTC + promote-to-updates: snap-release-to-candidate is neither "Fix Released" nor "Invalid" + (New) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1800692 Title: linux-azure: 4.15.0-1030.31 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Invalid Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Invalid Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Fix Released 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: 1797061 phase: Promoted to updates proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: snap-release-to-candidate is neither "Fix Released" nor "Invalid" (New) To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1800692/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800804] Re: linux-azure: 4.15.0-1031.32~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-trusty ** Tags added: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1799411 phase: Uploaded reason: - promote-to-proposed: Another kernel is currently pending in proposed + promote-to-proposed: Ready for review -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1800804 Title: linux-azure: 4.15.0-1031.32~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1799411 phase: Uploaded reason: promote-to-proposed: Ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1800804/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799400] Re: linux-lts-trusty: 3.13.0-162.212~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1799400 Title: linux-lts-trusty: 3.13.0-162.212~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1799399 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800803] Re: linux-azure: 4.15.0-1031.32 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug 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: 1799411 phase: Uploaded reason: - promote-to-proposed: Another kernel is currently pending in proposed + promote-to-proposed: Ready for review -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1800803 Title: linux-azure: 4.15.0-1031.32 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1799411 phase: Uploaded reason: promote-to-proposed: Ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1800803/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799400] Re: linux-lts-trusty: 3.13.0-162.212~precise1 -proposed tracker
** 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: 1799399 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress - security-signoff: Waiting for signoff verification-testing: Testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1799400 Title: linux-lts-trusty: 3.13.0-162.212~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1799399 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799399] Re: linux: 3.13.0-162.212 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff 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/1799399 Title: linux: 3.13.0-162.212 -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: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1799400 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED certification-testing: Testing in progress regression-testing: Testing in progress verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799399/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800694] Re: linux-azure: 4.15.0-1030.31~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: Fix Committed => 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: 1797061 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Ready to copy + kernel-stable-phase:Promoted to updates + kernel-stable-phase-changed:Thursday, 01. November 2018 20:04 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: 1797061 - phase: Promoted to proposed + phase: Promoted to updates proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Ready to copy - kernel-stable-phase:Promoted to updates - kernel-stable-phase-changed:Thursday, 01. November 2018 20:04 UTC + promote-to-updates: snap-release-to-candidate is neither "Fix Released" nor "Invalid" + (New) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1800694 Title: linux-azure: 4.15.0-1030.31~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Invalid Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Invalid Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Fix Released 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: 1797061 phase: Promoted to updates proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: snap-release-to-candidate is neither "Fix Released" nor "Invalid" (New) To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1800694/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800805] Re: linux-azure: 4.15.0-1031.32~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-xenial ** Tags added: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1799411 phase: Uploaded reason: - promote-to-proposed: Another kernel is currently pending in proposed + promote-to-proposed: Ready for review -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1800805 Title: linux-azure: 4.15.0-1031.32~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1799411 phase: Uploaded reason: promote-to-proposed: Ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1800805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798208] Re: smartpqi updates for ubuntu 18.04.2
If it helps, also, again with the caveat that I'm doing this partially for my own education, the above also matches what I found in the git tree from kernel.ubuntu.com: bladernr@galactica:~/development/git/ubuntu-kernel-git$ git checkout tags/v4.19 Previous HEAD position was 35a7f35ad1b1 Linux 4.19-rc8 HEAD is now at 84df9525b0c2 Linux 4.19 bladernr@galactica:~/development/git/ubuntu-kernel-git$ for x in `cat commits`; do if git log | grep -q $x; then echo "Commit $x: FOUND"; else echo "Commit $x: NOT FOUND"; fi; done Commit b0f9408b14838566b2a9b26434fab667c2afb0ea: FOUND Commit 339faa8150fd56891105bc69fc18f5d51b8a63dd: FOUND Commit 61c187e46ebb27f51b52bd0eb68b7f534a300184: FOUND Commit 957c5ab108c7d98369b7524daea532c0ebbcf845: FOUND Commit 26b390aba2a8f7b9dd5ce4e3ada9431de327da6d: FOUND Commit 9f8d05fa98442de78d1ab30235b0cc656ed7aff0: FOUND Commit dac12fbc7b0a433a160b89212a56e155c94f3a80: FOUND Commit 4ae5e9d159f83392c98c4ed88dfc63f19745be38: FOUND Commit f23f5bece686a76598335141a091934f7eb0998c: FOUND Commit 6396bb221514d2876fd6dc0aa2a1f240d99b37bb: FOUND Commit 6da2ec56059c3c7a7e5f729e6349e74ace1e5c57: FOUND bladernr@galactica:~/development/git/ubuntu-kernel-git$ git checkout tags/v4.18 Checking out files: 100% (11699/11699), done. Previous HEAD position was 84df9525b0c2 Linux 4.19 HEAD is now at 94710cac0ef4 Linux 4.18 bladernr@galactica:~/development/git/ubuntu-kernel-git$ for x in `cat commits`; do if git log | grep -q $x; then echo "Commit $x: FOUND"; else echo "Commit $x: NOT FOUND"; fi; done Commit b0f9408b14838566b2a9b26434fab667c2afb0ea: FOUND Commit 339faa8150fd56891105bc69fc18f5d51b8a63dd: FOUND Commit 61c187e46ebb27f51b52bd0eb68b7f534a300184: FOUND Commit 957c5ab108c7d98369b7524daea532c0ebbcf845: NOT FOUND Commit 26b390aba2a8f7b9dd5ce4e3ada9431de327da6d: NOT FOUND Commit 9f8d05fa98442de78d1ab30235b0cc656ed7aff0: NOT FOUND Commit dac12fbc7b0a433a160b89212a56e155c94f3a80: NOT FOUND Commit 4ae5e9d159f83392c98c4ed88dfc63f19745be38: NOT FOUND Commit f23f5bece686a76598335141a091934f7eb0998c: FOUND Commit 6396bb221514d2876fd6dc0aa2a1f240d99b37bb: FOUND Commit 6da2ec56059c3c7a7e5f729e6349e74ace1e5c57: FOUND -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798208 Title: smartpqi updates for ubuntu 18.04.2 Status in linux package in Ubuntu: Triaged Bug description: This is a request to update the SmartPQI driver in Ubuntu kernel 18.04.2 by pulling the following patches from upstream kernel version 4.19-rc7. Microsemi would like added to Ubuntu 18.04.2 to bring the driver up to date with kernel.org and to correct issues seen particularly on ARM systems. These patches cherry-pick cleanly from: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 0001-scsi-smartpqi-add-in-new-supported-controllers.patch commit b0f9408b14838566b2a9b26434fab667c2afb0ea No functionality change. Add in more supported controllers. 0002-scsi-smartpqi-workaround-fw-bug-for-oq-deletion.patch commit 339faa8150fd56891105bc69fc18f5d51b8a63dd Correct PQI operational queue deletion. Operational queues are deleted during resets. 0003-scsi-smartpqi-update-driver-version.patch commit 61c187e46ebb27f51b52bd0eb68b7f534a300184 No functionality change. Need context for the next version change patch below. 0004-scsi-smartpqi-improve-handling-for-sync-requests.patch commit 957c5ab108c7d98369b7524daea532c0ebbcf845 Correct driver active thread count when submitting internal commands. 0005-scsi-smartpqi-improve-error-checking-for-sync-reques.patch commit 26b390aba2a8f7b9dd5ce4e3ada9431de327da6d Retry INQUIRY operations. 0006-scsi-smartpqi-add-inspur-advantech-ids.patch commit 9f8d05fa98442de78d1ab30235b0cc656ed7aff0 No functionality change. Add in more supported controllers. 0007-scsi-smartpqi-fix-critical-ARM-issue-reading-PQI-ind.patch commit dac12fbc7b0a433a160b89212a56e155c94f3a80 Critical bug fix for ARM. ARM does not handle volatile variables. 0008-scsi-smartpqi-bump-driver-version-to-1.1.4-130.patch commit 4ae5e9d159f83392c98c4ed88dfc63f19745be38 No functionality change. There are some other patches but they are kernel-wide patches that affect other modules: blk-mq-Allow-PCI-vector-offset-for-mapping-queues.patch commit f23f5bece686a76598335141a091934f7eb0998c This is a kernel-wide patch that affects multiple modules: block/blk-mq-pci.c drivers/nvme/host/pci.c drivers/scsi/qla2xxx/qla_os.c drivers/scsi/smartpqi/smartpqi_init.c include/linux/blk-mq-pci.h commit 6396bb221514d2876fd6dc0aa2a1f240d99b37bb Author: Kees Cook Date: Tue Jun 12 14:03:40 2018 -0700 treewide: kzalloc() -> kcalloc() commit
[Kernel-packages] [Bug 1800694] Re: linux-azure: 4.15.0-1030.31~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: Confirmed => Fix Committed ** Changed in: kernel-sru-workflow/promote-to-updates Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Steve Langasek (vorlon) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1800694 Title: linux-azure: 4.15.0-1030.31~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Fix Committed Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Invalid Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Invalid Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Fix Released 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: 1797061 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1800694/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800694] Re: linux-azure: 4.15.0-1030.31~16.04.1 -proposed tracker
This bug was fixed in the package linux-azure - 4.15.0-1030.31~16.04.1 --- linux-azure (4.15.0-1030.31~16.04.1) xenial; urgency=medium * linux-azure: 4.15.0-1030.31~16.04.1 -proposed tracker (LP: #1800694) -- Marcelo Henrique Cerri Tue, 30 Oct 2018 16:03:15 -0300 ** Changed in: linux-azure (Ubuntu Xenial) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1800694 Title: linux-azure: 4.15.0-1030.31~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Fix Committed Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Invalid Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Invalid Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Fix Released 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: 1797061 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1800694/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797074] Re: linux-azure: 4.15.0-1028.29~14.04.1 -proposed tracker
*** This bug is a duplicate of bug 1800693 *** https://bugs.launchpad.net/bugs/1800693 This bug was fixed in the package linux-azure - 4.15.0-1030.31~14.04.1 --- linux-azure (4.15.0-1030.31~14.04.1) trusty; urgency=medium * linux-azure: 4.15.0-1030.31~14.04.1 -proposed tracker (LP: #1800693) linux-azure (4.15.0-1028.29~14.04.1) trusty; urgency=medium * linux-azure: 4.15.0-1028.29~14.04.1 -proposed tracker (LP: #1797074) linux-azure (4.15.0-1027.28~14.04.1) trusty; urgency=medium * linux-azure: fix getabis information (LP: #1793462) - [Packaging] linux-azure: fix getabis * Improvements to the kernel source package preparation (LP: #1793461) - Packaging: update-from-master: allow rebase to be skipped [ Ubuntu: 4.15.0-38.41 ] * linux: 4.15.0-38.41 -proposed tracker (LP: #1797061) * Silent data corruption in Linux kernel 4.15 (LP: #1796542) - block: add a lower-level bio_add_page interface - block: bio_iov_iter_get_pages: fix size of last iovec - blkdev: __blkdev_direct_IO_simple: fix leak in error case - block: bio_iov_iter_get_pages: pin more pages for multi-segment IOs [ Ubuntu: 4.15.0-37.40 ] * linux: 4.15.0-37.40 -proposed tracker (LP: #1795564) * hns3: enable ethtool rx-vlan-filter on supported hw (LP: #1793394) - net: hns3: Add vlan filter setting by ethtool command -K * hns3: Modifying channel parameters will reset ring parameters back to defaults (LP: #1793404) - net: hns3: Fix desc num set to default when setting channel * hisi_sas: Add SATA FIX check for v3 hw (LP: #1794151) - scsi: hisi_sas: Add SATA FIS check for v3 hw * Fix potential corruption using SAS controller on HiSilicon arm64 boards (LP: #1794156) - scsi: hisi_sas: add memory barrier in task delivery function * hisi_sas: Reduce unnecessary spin lock contention (LP: #1794165) - scsi: hisi_sas: Tidy hisi_sas_task_prep() * Add functional level reset support for the SAS controller on HiSilicon D06 systems (LP: #1794166) - scsi: hisi_sas: tidy host controller reset function a bit - scsi: hisi_sas: relocate some common code for v3 hw - scsi: hisi_sas: Implement handlers of PCIe FLR for v3 hw * HiSilicon SAS controller doesn't recover from PHY STP link timeout (LP: #1794172) - scsi: hisi_sas: tidy channel interrupt handler for v3 hw - scsi: hisi_sas: Fix the failure of recovering PHY from STP link timeout * getxattr: always handle namespaced attributes (LP: #1789746) - getxattr: use correct xattr length * Fix unusable NVIDIA GPU after S3 (LP: #1793338) - PCI: Reprogram bridge prefetch registers on resume * Fails to boot under Xen PV: BUG: unable to handle kernel paging request at edc21fd9 (LP: #1789118) - x86/EISA: Don't probe EISA bus for Xen PV guests * qeth: use vzalloc for QUERY OAT buffer (LP: #1793086) - s390/qeth: use vzalloc for QUERY OAT buffer * SRU: Enable middle button of touchpad on ThinkPad P72 (LP: #1793463) - Input: elantech - enable middle button of touchpad on ThinkPad P72 * Dell new AIO requires a new uart backlight driver (LP: #1727235) - SAUCE: platform/x86: dell-uart-backlight: new backlight driver for DELL AIO - updateconfigs for Dell UART backlight driver * [Ubuntu] s390/crypto: Fix return code checking in cbc_paes_crypt. (LP: #1794294) - s390/crypto: Fix return code checking in cbc_paes_crypt() * hns3: Retrieve RoCE MSI-X config from firmware (LP: #1793221) - net: hns3: Fix MSIX allocation issue for VF - net: hns3: Refine the MSIX allocation for PF * net: hns: Avoid hang when link is changed while handling packets (LP: #1792209) - net: hns: add the code for cleaning pkt in chip - net: hns: add netif_carrier_off before change speed and duplex * Page leaking in cachefiles_read_backing_file while vmscan is active (LP: #1793430) - SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while vmscan is active * some nvidia p1000 graphic cards hang during the boot (LP: #1791569) - drm/nouveau/gr/gf100-: virtualise tpc_mask + apply fixes from traces * Error reported when creating ZFS pool with "-t" option, despite successful pool creation (LP: #1769937) - SAUCE: (noup) Update zfs to 0.7.5-1ubuntu16.4 * Fix I2C touchpanels' interrupt storms after system suspend (LP: #1792309) - HID: i2c-hid: Fix flooded incomplete report after S3 on Rayd touchscreen - HID: i2c-hid: Don't reset device upon system resume * ipmmu is always registered (LP: #1783746) - iommu/ipmmu-vmsa: Don't register as BUS IOMMU if machine doesn't have IPMMU- VMSA * Bionic update: upstream stable patchset 2018-09-27 (LP: #1794889) - clocksource/drivers/imx-tpm: Correct some registers operation flow - Input: synaptics-rmi4 - fix an unchecked out of memory error path - KVM: X86: fix incorrect reference of trace_kvm_pi_irte_update - x86: Add check for APIC access address
[Kernel-packages] [Bug 1793462] Re: linux-azure: fix getabis information
This bug was fixed in the package linux-azure - 4.15.0-1030.31~14.04.1 --- linux-azure (4.15.0-1030.31~14.04.1) trusty; urgency=medium * linux-azure: 4.15.0-1030.31~14.04.1 -proposed tracker (LP: #1800693) linux-azure (4.15.0-1028.29~14.04.1) trusty; urgency=medium * linux-azure: 4.15.0-1028.29~14.04.1 -proposed tracker (LP: #1797074) linux-azure (4.15.0-1027.28~14.04.1) trusty; urgency=medium * linux-azure: fix getabis information (LP: #1793462) - [Packaging] linux-azure: fix getabis * Improvements to the kernel source package preparation (LP: #1793461) - Packaging: update-from-master: allow rebase to be skipped [ Ubuntu: 4.15.0-38.41 ] * linux: 4.15.0-38.41 -proposed tracker (LP: #1797061) * Silent data corruption in Linux kernel 4.15 (LP: #1796542) - block: add a lower-level bio_add_page interface - block: bio_iov_iter_get_pages: fix size of last iovec - blkdev: __blkdev_direct_IO_simple: fix leak in error case - block: bio_iov_iter_get_pages: pin more pages for multi-segment IOs [ Ubuntu: 4.15.0-37.40 ] * linux: 4.15.0-37.40 -proposed tracker (LP: #1795564) * hns3: enable ethtool rx-vlan-filter on supported hw (LP: #1793394) - net: hns3: Add vlan filter setting by ethtool command -K * hns3: Modifying channel parameters will reset ring parameters back to defaults (LP: #1793404) - net: hns3: Fix desc num set to default when setting channel * hisi_sas: Add SATA FIX check for v3 hw (LP: #1794151) - scsi: hisi_sas: Add SATA FIS check for v3 hw * Fix potential corruption using SAS controller on HiSilicon arm64 boards (LP: #1794156) - scsi: hisi_sas: add memory barrier in task delivery function * hisi_sas: Reduce unnecessary spin lock contention (LP: #1794165) - scsi: hisi_sas: Tidy hisi_sas_task_prep() * Add functional level reset support for the SAS controller on HiSilicon D06 systems (LP: #1794166) - scsi: hisi_sas: tidy host controller reset function a bit - scsi: hisi_sas: relocate some common code for v3 hw - scsi: hisi_sas: Implement handlers of PCIe FLR for v3 hw * HiSilicon SAS controller doesn't recover from PHY STP link timeout (LP: #1794172) - scsi: hisi_sas: tidy channel interrupt handler for v3 hw - scsi: hisi_sas: Fix the failure of recovering PHY from STP link timeout * getxattr: always handle namespaced attributes (LP: #1789746) - getxattr: use correct xattr length * Fix unusable NVIDIA GPU after S3 (LP: #1793338) - PCI: Reprogram bridge prefetch registers on resume * Fails to boot under Xen PV: BUG: unable to handle kernel paging request at edc21fd9 (LP: #1789118) - x86/EISA: Don't probe EISA bus for Xen PV guests * qeth: use vzalloc for QUERY OAT buffer (LP: #1793086) - s390/qeth: use vzalloc for QUERY OAT buffer * SRU: Enable middle button of touchpad on ThinkPad P72 (LP: #1793463) - Input: elantech - enable middle button of touchpad on ThinkPad P72 * Dell new AIO requires a new uart backlight driver (LP: #1727235) - SAUCE: platform/x86: dell-uart-backlight: new backlight driver for DELL AIO - updateconfigs for Dell UART backlight driver * [Ubuntu] s390/crypto: Fix return code checking in cbc_paes_crypt. (LP: #1794294) - s390/crypto: Fix return code checking in cbc_paes_crypt() * hns3: Retrieve RoCE MSI-X config from firmware (LP: #1793221) - net: hns3: Fix MSIX allocation issue for VF - net: hns3: Refine the MSIX allocation for PF * net: hns: Avoid hang when link is changed while handling packets (LP: #1792209) - net: hns: add the code for cleaning pkt in chip - net: hns: add netif_carrier_off before change speed and duplex * Page leaking in cachefiles_read_backing_file while vmscan is active (LP: #1793430) - SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while vmscan is active * some nvidia p1000 graphic cards hang during the boot (LP: #1791569) - drm/nouveau/gr/gf100-: virtualise tpc_mask + apply fixes from traces * Error reported when creating ZFS pool with "-t" option, despite successful pool creation (LP: #1769937) - SAUCE: (noup) Update zfs to 0.7.5-1ubuntu16.4 * Fix I2C touchpanels' interrupt storms after system suspend (LP: #1792309) - HID: i2c-hid: Fix flooded incomplete report after S3 on Rayd touchscreen - HID: i2c-hid: Don't reset device upon system resume * ipmmu is always registered (LP: #1783746) - iommu/ipmmu-vmsa: Don't register as BUS IOMMU if machine doesn't have IPMMU- VMSA * Bionic update: upstream stable patchset 2018-09-27 (LP: #1794889) - clocksource/drivers/imx-tpm: Correct some registers operation flow - Input: synaptics-rmi4 - fix an unchecked out of memory error path - KVM: X86: fix incorrect reference of trace_kvm_pi_irte_update - x86: Add check for APIC access address for vmentry of L2 guests - MIPS: io: Prevent compiler reordering writeX() - nfp:
[Kernel-packages] [Bug 1795493] Re: netfilter: nf_conntrack: resolve clash for matching conntracks
This bug was fixed in the package linux-azure - 4.15.0-1030.31 --- linux-azure (4.15.0-1030.31) bionic; urgency=medium * linux-azure: 4.15.0-1030.31 -proposed tracker (LP: #1800692) * netfilter: nf_conntrack: resolve clash for matching conntracks (LP: #1795493) - SAUCE: netfilter: nf_conntrack: resolve clash for matching conntracks - SAUCE: netfilter: nf_nat: return the same reply tuple for matching CTs -- Marcelo Henrique Cerri Tue, 30 Oct 2018 15:00:38 -0300 ** Changed in: linux-azure (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1795493 Title: netfilter: nf_conntrack: resolve clash for matching conntracks Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Bionic: Fix Released Status in linux-azure source package in Cosmic: Fix Committed Bug description: Per https://www.weave.works/blog/racy-conntrack-and-dns-lookup- timeouts Kubernetes users are seeing DNS lookups from Pods taking 5 or more seconds. Please pick up the following patches to netfilter: http://patchwork.ozlabs.org/patch/937963/ http://patchwork.ozlabs.org/patch/952939/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1795493/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800692] Re: linux-azure: 4.15.0-1030.31 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: Confirmed => Fix Committed ** Changed in: kernel-sru-workflow/promote-to-updates Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Steve Langasek (vorlon) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1800692 Title: linux-azure: 4.15.0-1030.31 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Fix Committed Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Invalid Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Invalid Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Fix Released 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: 1797061 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1800692/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800693] Re: linux-azure: 4.15.0-1030.31~14.04.1 -proposed tracker
** 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: 1797061 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Ready to copy + promote-to-updates: Packages not yet published -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1800693 Title: linux-azure: 4.15.0-1030.31~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Fix Committed Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Fix Released 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: 1797061 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Packages not yet published To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1800693/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800693] Re: linux-azure: 4.15.0-1030.31~14.04.1 -proposed tracker
This bug was fixed in the package linux-azure - 4.15.0-1030.31~14.04.1 --- linux-azure (4.15.0-1030.31~14.04.1) trusty; urgency=medium * linux-azure: 4.15.0-1030.31~14.04.1 -proposed tracker (LP: #1800693) linux-azure (4.15.0-1028.29~14.04.1) trusty; urgency=medium * linux-azure: 4.15.0-1028.29~14.04.1 -proposed tracker (LP: #1797074) linux-azure (4.15.0-1027.28~14.04.1) trusty; urgency=medium * linux-azure: fix getabis information (LP: #1793462) - [Packaging] linux-azure: fix getabis * Improvements to the kernel source package preparation (LP: #1793461) - Packaging: update-from-master: allow rebase to be skipped [ Ubuntu: 4.15.0-38.41 ] * linux: 4.15.0-38.41 -proposed tracker (LP: #1797061) * Silent data corruption in Linux kernel 4.15 (LP: #1796542) - block: add a lower-level bio_add_page interface - block: bio_iov_iter_get_pages: fix size of last iovec - blkdev: __blkdev_direct_IO_simple: fix leak in error case - block: bio_iov_iter_get_pages: pin more pages for multi-segment IOs [ Ubuntu: 4.15.0-37.40 ] * linux: 4.15.0-37.40 -proposed tracker (LP: #1795564) * hns3: enable ethtool rx-vlan-filter on supported hw (LP: #1793394) - net: hns3: Add vlan filter setting by ethtool command -K * hns3: Modifying channel parameters will reset ring parameters back to defaults (LP: #1793404) - net: hns3: Fix desc num set to default when setting channel * hisi_sas: Add SATA FIX check for v3 hw (LP: #1794151) - scsi: hisi_sas: Add SATA FIS check for v3 hw * Fix potential corruption using SAS controller on HiSilicon arm64 boards (LP: #1794156) - scsi: hisi_sas: add memory barrier in task delivery function * hisi_sas: Reduce unnecessary spin lock contention (LP: #1794165) - scsi: hisi_sas: Tidy hisi_sas_task_prep() * Add functional level reset support for the SAS controller on HiSilicon D06 systems (LP: #1794166) - scsi: hisi_sas: tidy host controller reset function a bit - scsi: hisi_sas: relocate some common code for v3 hw - scsi: hisi_sas: Implement handlers of PCIe FLR for v3 hw * HiSilicon SAS controller doesn't recover from PHY STP link timeout (LP: #1794172) - scsi: hisi_sas: tidy channel interrupt handler for v3 hw - scsi: hisi_sas: Fix the failure of recovering PHY from STP link timeout * getxattr: always handle namespaced attributes (LP: #1789746) - getxattr: use correct xattr length * Fix unusable NVIDIA GPU after S3 (LP: #1793338) - PCI: Reprogram bridge prefetch registers on resume * Fails to boot under Xen PV: BUG: unable to handle kernel paging request at edc21fd9 (LP: #1789118) - x86/EISA: Don't probe EISA bus for Xen PV guests * qeth: use vzalloc for QUERY OAT buffer (LP: #1793086) - s390/qeth: use vzalloc for QUERY OAT buffer * SRU: Enable middle button of touchpad on ThinkPad P72 (LP: #1793463) - Input: elantech - enable middle button of touchpad on ThinkPad P72 * Dell new AIO requires a new uart backlight driver (LP: #1727235) - SAUCE: platform/x86: dell-uart-backlight: new backlight driver for DELL AIO - updateconfigs for Dell UART backlight driver * [Ubuntu] s390/crypto: Fix return code checking in cbc_paes_crypt. (LP: #1794294) - s390/crypto: Fix return code checking in cbc_paes_crypt() * hns3: Retrieve RoCE MSI-X config from firmware (LP: #1793221) - net: hns3: Fix MSIX allocation issue for VF - net: hns3: Refine the MSIX allocation for PF * net: hns: Avoid hang when link is changed while handling packets (LP: #1792209) - net: hns: add the code for cleaning pkt in chip - net: hns: add netif_carrier_off before change speed and duplex * Page leaking in cachefiles_read_backing_file while vmscan is active (LP: #1793430) - SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while vmscan is active * some nvidia p1000 graphic cards hang during the boot (LP: #1791569) - drm/nouveau/gr/gf100-: virtualise tpc_mask + apply fixes from traces * Error reported when creating ZFS pool with "-t" option, despite successful pool creation (LP: #1769937) - SAUCE: (noup) Update zfs to 0.7.5-1ubuntu16.4 * Fix I2C touchpanels' interrupt storms after system suspend (LP: #1792309) - HID: i2c-hid: Fix flooded incomplete report after S3 on Rayd touchscreen - HID: i2c-hid: Don't reset device upon system resume * ipmmu is always registered (LP: #1783746) - iommu/ipmmu-vmsa: Don't register as BUS IOMMU if machine doesn't have IPMMU- VMSA * Bionic update: upstream stable patchset 2018-09-27 (LP: #1794889) - clocksource/drivers/imx-tpm: Correct some registers operation flow - Input: synaptics-rmi4 - fix an unchecked out of memory error path - KVM: X86: fix incorrect reference of trace_kvm_pi_irte_update - x86: Add check for APIC access address for vmentry of L2 guests - MIPS: io: Prevent compiler reordering writeX() - nfp:
[Kernel-packages] [Bug 1800692] Re: linux-azure: 4.15.0-1030.31 -proposed tracker
This bug was fixed in the package linux-azure - 4.15.0-1030.31 --- linux-azure (4.15.0-1030.31) bionic; urgency=medium * linux-azure: 4.15.0-1030.31 -proposed tracker (LP: #1800692) * netfilter: nf_conntrack: resolve clash for matching conntracks (LP: #1795493) - SAUCE: netfilter: nf_conntrack: resolve clash for matching conntracks - SAUCE: netfilter: nf_nat: return the same reply tuple for matching CTs -- Marcelo Henrique Cerri Tue, 30 Oct 2018 15:00:38 -0300 ** Changed in: linux-azure (Ubuntu Bionic) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1800692 Title: linux-azure: 4.15.0-1030.31 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Fix Committed Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Invalid Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Invalid Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Fix Released 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: 1797061 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1800692/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800693] Re: linux-azure: 4.15.0-1030.31~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: Confirmed => Fix Committed ** Changed in: kernel-sru-workflow/promote-to-updates Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Steve Langasek (vorlon) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1800693 Title: linux-azure: 4.15.0-1030.31~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Fix Committed Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Fix Released 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: 1797061 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Packages not yet published To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1800693/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode
Next step, I'll compile 'uu' upstream 1.6 and test against it and the cosmic version which has more fixes. If the result is different, I'll then start a bisection. Let's see. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796376 Title: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode Status in linux package in Ubuntu: Confirmed Bug description: Since the following linux-cloud-tools-common package versions : Xenial : 4.4.0-135.161 Bionic : 4.15.0-34.37 the Systemd service unit file for hv-kvp-daemon has been modified with new dependencies that make the package unable to be upgraded with unattended-upgrades on shutdown mode. Unattended-upgrades hangs with the linux-cloud-tools-common package during "Preparing to unpack". The server restarts after the unattended-upgrades service timeout expires. - Package state after reboot : iFR linux-cloud-tools-common 4.15.0-34.37 all Linux kernel version specific cloud tools for version 4.15.0 - Unattended-upgrades dpkg logs : Log started: 2018-10-05 17:59:04 (Reading database ... 52043 files and directories currently installed.) Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ... Log ended: 2018-10-05 18:00:54 - Impact : The current impact is very important as all security updates are blocked until you manually fix each server with : dpkg --configure -a apt install --only-upgrade linux-cloud-tools-common - Workaround/Fix : As a simple straightforward fix, replacing : Before=shutdown.target cloud-init-local.service walinuxagent.service with : Before=shutdown.target walinuxagent.service makes the package upgradable during shutdown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800692] Re: linux-azure: 4.15.0-1030.31 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-bionic ** Tags removed: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1797061 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Stakeholder signoff not verified - stakeholder-signoff: Waiting for signoff + promote-to-updates: Ready to copy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1800692 Title: linux-azure: 4.15.0-1030.31 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Invalid Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Invalid Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1797061 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1800692/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode
Hi Guillaume, I seemed to only be able to reproduce the behaviour in the 'uu' context, if for instance I upgrade the pkg using apt, it goes well for me so far. Can you conclude you are experiencing the same outcome as me and you are only able to fully reproduce when 'uu' is involved ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796376 Title: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode Status in linux package in Ubuntu: Confirmed Bug description: Since the following linux-cloud-tools-common package versions : Xenial : 4.4.0-135.161 Bionic : 4.15.0-34.37 the Systemd service unit file for hv-kvp-daemon has been modified with new dependencies that make the package unable to be upgraded with unattended-upgrades on shutdown mode. Unattended-upgrades hangs with the linux-cloud-tools-common package during "Preparing to unpack". The server restarts after the unattended-upgrades service timeout expires. - Package state after reboot : iFR linux-cloud-tools-common 4.15.0-34.37 all Linux kernel version specific cloud tools for version 4.15.0 - Unattended-upgrades dpkg logs : Log started: 2018-10-05 17:59:04 (Reading database ... 52043 files and directories currently installed.) Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ... Log ended: 2018-10-05 18:00:54 - Impact : The current impact is very important as all security updates are blocked until you manually fix each server with : dpkg --configure -a apt install --only-upgrade linux-cloud-tools-common - Workaround/Fix : As a simple straightforward fix, replacing : Before=shutdown.target cloud-init-local.service walinuxagent.service with : Before=shutdown.target walinuxagent.service makes the package upgradable during shutdown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800348] Re: nvidia-kernel-source-390 (not installed): nvidia kernel module failed to build [/usr/bin/ld.bfd: Relocatable linking with relocations from format elf32-i386 (...) t
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1800348 Title: nvidia-kernel-source-390 (not installed): nvidia kernel module failed to build [/usr/bin/ld.bfd: Relocatable linking with relocations from format elf32-i386 (...) to format elf64-x86-64 (...) is not supported] Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: sudo apt upgrade /etc/kernel/header_postinst.d/dkms: Secure Boot not enabled on this system. Error! Bad return status for module build on kernel: 4.15.0-38-generic (x86_64) Consult /var/lib/dkms/nvidia/390.77/build/make.log for more information. --> make.log attached. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-kernel-source-390 (not installed) ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 DKMSKernelVersion: 4.15.0-38-generic Date: Sun Oct 28 14:04:31 2018 InstallationDate: Installed on 2018-06-30 (120 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageVersion: (not installed) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 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.6 SourcePackage: nvidia-graphics-drivers-390 Title: nvidia-kernel-source-390 (not installed): nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1800348/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode
in 'uu' context and only during the shutdown operation seems like.
I just ran 'uu' from the CLI and it went well :
$ sudo unattended-upgrade --debug
...
Log started: 2018-11-01 19:10:16
(Reading database ... 56537 files and directories currently installed.)
Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ...
Unpacking linux-cloud-tools-common (4.15.0-36.39) over (4.15.0-34.37) ...
Setting up linux-cloud-tools-common (4.15.0-36.39) ...
Processing triggers for ureadahead (0.100.0-20) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
left to upgrade {'libcurl4', 'curl'}
adjusting candidate version: linux-cloud-tools-common=4.15.0-36.39
applying set ['libcurl4', 'curl']
Log ended: 2018-11-01 19:10:20
...
ii linux-cloud-tools-common4.15.0-36.39
all Linux kernel version specific cloud tools for version
4.15.0
During the shutdown procedure, it seems like something send a SIGTERM to
'uu' which cause the installation to not complete :
2018-11-01 14:20:26,426 INFO Writing dpkg log to
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
2018-11-01 14:25:23,996 WARNING SIGTERM received, will stop
2018-11-01 14:25:24,027 WARNING SIGTERM received, will stop
2018-11-01 14:25:24,578 ERROR Installing the upgrades failed!
2018-11-01 14:25:24,579 ERROR error message: installArchives() failed
2018-11-01 14:25:24,579 ERROR dpkg returned a error! See
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log for details
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1796376
Title:
Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable
with unattended-upgrades on shutdown mode
Status in linux package in Ubuntu:
Confirmed
Bug description:
Since the following linux-cloud-tools-common package versions :
Xenial : 4.4.0-135.161
Bionic : 4.15.0-34.37
the Systemd service unit file for hv-kvp-daemon has been modified with new
dependencies that make the package unable to be upgraded with
unattended-upgrades on shutdown mode.
Unattended-upgrades hangs with the linux-cloud-tools-common package during
"Preparing to unpack". The server restarts after the unattended-upgrades
service timeout expires.
- Package state after reboot :
iFR linux-cloud-tools-common 4.15.0-34.37
all Linux kernel version specific cloud tools for version
4.15.0
- Unattended-upgrades dpkg logs :
Log started: 2018-10-05 17:59:04
(Reading database ... 52043 files and directories currently installed.)
Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ...
Log ended: 2018-10-05 18:00:54
- Impact :
The current impact is very important as all security updates are
blocked until you manually fix each server with :
dpkg --configure -a
apt install --only-upgrade linux-cloud-tools-common
- Workaround/Fix :
As a simple straightforward fix, replacing :
Before=shutdown.target cloud-init-local.service walinuxagent.service
with :
Before=shutdown.target walinuxagent.service
makes the package upgradable during shutdown.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800694] Re: linux-azure: 4.15.0-1030.31~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-xenial ** Tags removed: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1797061 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Stakeholder signoff not verified - stakeholder-signoff: Waiting for signoff + promote-to-updates: Ready to copy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1800694 Title: linux-azure: 4.15.0-1030.31~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Invalid Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Invalid Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in 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: 1797061 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1800694/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800693] Re: linux-azure: 4.15.0-1030.31~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-trusty ** Tags removed: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1797061 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Stakeholder signoff not verified - stakeholder-signoff: Waiting for signoff + promote-to-updates: Ready to copy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1800693 Title: linux-azure: 4.15.0-1030.31~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1797061 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1800693/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798208] Re: smartpqi updates for ubuntu 18.04.2
Assuming I did the git checkout correctly, these are all in 4.18 stable under the v4.18.16 tag 0001-scsi-smartpqi-add-in-new-supported-controllers.patch commit b0f9408b14838566b2a9b26434fab667c2afb0ea No functionality change. Add in more supported controllers. 0002-scsi-smartpqi-workaround-fw-bug-for-oq-deletion.patch commit 339faa8150fd56891105bc69fc18f5d51b8a63dd Correct PQI operational queue deletion. Operational queues are deleted during resets. 0003-scsi-smartpqi-update-driver-version.patch commit 61c187e46ebb27f51b52bd0eb68b7f534a300184 No functionality change. Need context for the next version change patch below. These following Microsemi patces are in 4.19 Mainline, but NOT yet in v4.18.16 0004-scsi-smartpqi-improve-handling-for-sync-requests.patch commit 957c5ab108c7d98369b7524daea532c0ebbcf845 Correct driver active thread count when submitting internal commands. 0005-scsi-smartpqi-improve-error-checking-for-sync-reques.patch commit 26b390aba2a8f7b9dd5ce4e3ada9431de327da6d Retry INQUIRY operations. 0006-scsi-smartpqi-add-inspur-advantech-ids.patch commit 9f8d05fa98442de78d1ab30235b0cc656ed7aff0 No functionality change. Add in more supported controllers. 0007-scsi-smartpqi-fix-critical-ARM-issue-reading-PQI-ind.patch commit dac12fbc7b0a433a160b89212a56e155c94f3a80 Critical bug fix for ARM. ARM does not handle volatile variables. 0008-scsi-smartpqi-bump-driver-version-to-1.1.4-130.patch commit 4ae5e9d159f83392c98c4ed88dfc63f19745be38 No functionality change. These extra ones are already in v4.18.16 stable: blk-mq-Allow-PCI-vector-offset-for-mapping-queues.patch commit f23f5bece686a76598335141a091934f7eb0998c This is a kernel-wide patch that affects multiple modules: commit 6396bb221514d2876fd6dc0aa2a1f240d99b37bb Author: Kees Cook Date: Tue Jun 12 14:03:40 2018 -0700 treewide: kzalloc() -> kcalloc() commit 6da2ec56059c3c7a7e5f729e6349e74ace1e5c57 Author: Kees Cook Date: Tue Jun 12 13:55:00 2018 -0700 treewide: kmalloc() -> kmalloc_array() NOTE: I'm digging into this a bit for my own experience/education, but hopefully it will also help someone out. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798208 Title: smartpqi updates for ubuntu 18.04.2 Status in linux package in Ubuntu: Triaged Bug description: This is a request to update the SmartPQI driver in Ubuntu kernel 18.04.2 by pulling the following patches from upstream kernel version 4.19-rc7. Microsemi would like added to Ubuntu 18.04.2 to bring the driver up to date with kernel.org and to correct issues seen particularly on ARM systems. These patches cherry-pick cleanly from: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 0001-scsi-smartpqi-add-in-new-supported-controllers.patch commit b0f9408b14838566b2a9b26434fab667c2afb0ea No functionality change. Add in more supported controllers. 0002-scsi-smartpqi-workaround-fw-bug-for-oq-deletion.patch commit 339faa8150fd56891105bc69fc18f5d51b8a63dd Correct PQI operational queue deletion. Operational queues are deleted during resets. 0003-scsi-smartpqi-update-driver-version.patch commit 61c187e46ebb27f51b52bd0eb68b7f534a300184 No functionality change. Need context for the next version change patch below. 0004-scsi-smartpqi-improve-handling-for-sync-requests.patch commit 957c5ab108c7d98369b7524daea532c0ebbcf845 Correct driver active thread count when submitting internal commands. 0005-scsi-smartpqi-improve-error-checking-for-sync-reques.patch commit 26b390aba2a8f7b9dd5ce4e3ada9431de327da6d Retry INQUIRY operations. 0006-scsi-smartpqi-add-inspur-advantech-ids.patch commit 9f8d05fa98442de78d1ab30235b0cc656ed7aff0 No functionality change. Add in more supported controllers. 0007-scsi-smartpqi-fix-critical-ARM-issue-reading-PQI-ind.patch commit dac12fbc7b0a433a160b89212a56e155c94f3a80 Critical bug fix for ARM. ARM does not handle volatile variables. 0008-scsi-smartpqi-bump-driver-version-to-1.1.4-130.patch commit 4ae5e9d159f83392c98c4ed88dfc63f19745be38 No functionality change. There are some other patches but they are kernel-wide patches that affect other modules: blk-mq-Allow-PCI-vector-offset-for-mapping-queues.patch commit f23f5bece686a76598335141a091934f7eb0998c This is a kernel-wide patch that affects multiple modules: block/blk-mq-pci.c drivers/nvme/host/pci.c drivers/scsi/qla2xxx/qla_os.c drivers/scsi/smartpqi/smartpqi_init.c include/linux/blk-mq-pci.h commit 6396bb221514d2876fd6dc0aa2a1f240d99b37bb Author: Kees Cook Date: Tue Jun 12 14:03:40 2018 -0700
[Kernel-packages] [Bug 1800694] Re: linux-azure: 4.15.0-1030.31~16.04.1 -proposed tracker
Tests show no regressions and the changes correct the customer problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1800694 Title: linux-azure: 4.15.0-1030.31~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Invalid Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Invalid Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in 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: 1797061 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Stakeholder signoff not verified stakeholder-signoff: Waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1800694/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800693] Re: linux-azure: 4.15.0-1030.31~14.04.1 -proposed tracker
Tests complete with no regression. ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1800693 Title: linux-azure: 4.15.0-1030.31~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1797061 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Stakeholder signoff not verified stakeholder-signoff: Waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1800693/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800692] Re: linux-azure: 4.15.0-1030.31 -proposed tracker
Tests complete with no regression. Customer issue fix verified ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1800692 Title: linux-azure: 4.15.0-1030.31 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Invalid Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Invalid Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1797061 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Stakeholder signoff not verified stakeholder-signoff: Waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1800692/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800694] Re: linux-azure: 4.15.0-1030.31~16.04.1 -proposed tracker
Tests show no regressions and the changes correct the customer problem. ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1800694 Title: linux-azure: 4.15.0-1030.31~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Invalid Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Invalid Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in 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: 1797061 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Stakeholder signoff not verified stakeholder-signoff: Waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1800694/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799453] Re: linux-kvm: 4.18.0-1004.4 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => 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: 1799445 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Testing FAILED certification-testing: Testing in progress regression-testing: Testing in progress security-signoff: Waiting for signoff verification-testing: Testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1799453 Title: linux-kvm: 4.18.0-1004.4 -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: In Progress 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: Confirmed Status in linux-kvm source package in Cosmic: 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: 1799445 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Testing in progress regression-testing: Testing in progress security-signoff: Waiting for signoff verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799453/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799405] Re: linux-aws: 4.4.0-1071.81 -proposed tracker
*** This bug is a duplicate of bug 1801124 *** https://bugs.launchpad.net/bugs/1801124 ** This bug has been marked a duplicate of bug 1801124 linux-aws: -proposed tracker -- 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/1799405 Title: linux-aws: 4.4.0-1071.81 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1799401 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress security-signoff: Waiting for signoff snap-release-to-candidate: Snap not in candidate channel verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799405/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799403] Re: linux-aws: 4.4.0-1033.36 -proposed tracker
*** This bug is a duplicate of bug 1801123 *** https://bugs.launchpad.net/bugs/1801123 ** This bug has been marked a duplicate of bug 1801123 linux-aws: -proposed tracker -- 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/1799403 Title: linux-aws: 4.4.0-1033.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: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1799401 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress security-signoff: Waiting for signoff verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1794169] Re: AWS ubuntu became unreachable after ssh login
** Information type changed from Public Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1794169 Title: AWS ubuntu became unreachable after ssh login Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: I've reached strange situation with Ubuntu 18.04 LTS with latest kernel on AWS m5.xlarge instance. System became unreachable after series of successful ssh logins. systemd -user became zombie and block main systemd daemon (PID 1). I've created bug https://github.com/systemd/systemd/issues/10123 but it was closed with "there's a problem with your kernel". https://github.com/systemd/systemd/issues/10123#issuecomment-423984751 Symptoms are very similar to https://github.com/systemd/systemd/issues/8598 apetren+ 26679 0.0 0.0 0 0 ?Z02:56 0:00 \_ [(sd-pam)] apetren+ 26855 0.0 0.0 76636 7816 ?Ds 02:57 0:00 /lib/systemd/systemd --user apetren+ 26856 0.0 0.0 0 0 ?Z02:57 0:00 \_ [(sd-pam)] apetren+ 26954 0.0 0.0 0 0 ?Zs 02:57 0:00 \_ [kill] apetren+ 27053 0.0 0.0 76636 7496 ?Ss 02:58 0:00 /lib/systemd/systemd --user apetren+ 27054 0.0 0.0 193972 2768 ?S02:58 0:00 \_ (sd-pam) This situation is repeatable on 7 instances 1-2 times per week. how to repeat: 1. Install ubuntu 18.04 LTS from official ubuntu image 2. update kernel and packages to latest version 3. from another instance run while `true` ;do ssh ubu...@your.instance.ip "hostname; ps -ef|grep defunc |grep -v grep" ; done By this command in couple of days I have 2->4->6->8... zombies and in a hour system is frozen... sudo reboot is not working, because systemd with PID 1 is unreachable. kill -9 1 -- not working as well. # uname -r: Linux mainframe04 4.15.0-1021-aws #21-Ubuntu SMP Tue Aug 28 10:23:07 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux # cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" # systemd --version systemd 237 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid AWS instance m5.xlarge Please let me know if you need any information. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: N/A DistroRelease: Ubuntu 18.04 Ec2AMI: ami-91caece9 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2b Ec2InstanceType: m5.xlarge Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Amazon EC2 m5.xlarge Package: systemd 237-3ubuntu10.3 PackageArchitecture: amd64 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1021-aws root=UUID=a4278387-5a07-46eb-a726-ae1e22673af4 ro console=tty1 console=ttyS0 nvme.io_timeout=4294967295 ProcVersionSignature: Ubuntu 4.15.0-1021.21-aws 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1021-aws N/A linux-backports-modules-4.15.0-1021-aws N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic ec2-images Uname: Linux 4.15.0-1021-aws x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: docker WifiSyslog: _MarkForUpload: True dmi.bios.date: 10/16/2017 dmi.bios.vendor: Amazon EC2 dmi.bios.version: 1.0 dmi.board.asset.tag: i-02cfe7fcd8a997085 dmi.board.vendor: Amazon EC2 dmi.chassis.asset.tag: Amazon EC2 dmi.chassis.type: 1 dmi.chassis.vendor: Amazon EC2 dmi.modalias: dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnm5.xlarge:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr: dmi.product.name: m5.xlarge dmi.sys.vendor: Amazon EC2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794169/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801114] Re: linux-aws: -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- - kernel-stable-master-bug: 1801113 - reason: - prepare-package: Waiting for master bug - prepare-package-meta: Waiting for master bug + kernel-stable-master-bug: 1799445 ** Tags removed: kernel-sru-derivative-of-1801113 ** Tags added: kernel-sru-derivative-of-1799445 -- 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/1801114 Title: linux-aws: -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: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1799445 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1801114/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799497] Re: 4.15 kernel hard lockup about once a week
Darn, wanted to reply earlier. So maybe at least for Luis who sounds to have multiple servers in a test environment, it would be possible to run two otherwise identical servers and only remove zram-config on one. Then one locking up and the other not would be quite good proof. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799497 Title: 4.15 kernel hard lockup about once a week Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: My main server has been running into hard lockups about once a week ever since I switched to the 4.15 Ubuntu 18.04 kernel. When this happens, nothing is printed to the console, it's effectively stuck showing a login prompt. The system is running with panic=1 on the cmdline but isn't rebooting so the kernel isn't even processing this as a kernel panic. As this felt like a potential hardware issue, I had my hosting provider give me a completely different system, different motherboard, different CPU, different RAM and different storage, I installed that system on 18.04 and moved my data over, a week later, I hit the issue again. We've since also had a LXD user reporting similar symptoms here also on varying hardware: https://github.com/lxc/lxd/issues/5197 My system doesn't have a lot of memory pressure with about 50% of free memory: root@vorash:~# free -m totalusedfree shared buff/cache available Mem: 31819 17574 402 513 13842 13292 Swap: 159092687 13222 I will now try to increase console logging as much as possible on the system in the hopes that next time it hangs we can get a better idea of what happened but I'm not too hopeful given the complete silence on the console when this occurs. System is currently on: Linux vorash 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux But I've seen this since the GA kernel on 4.15 so it's not a recent regression. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 23 16:12 seq crw-rw 1 root audio 116, 33 Oct 23 16:12 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Cannot stat file /proc/22822/fd/10: Permission denied Cannot stat file /proc/22831/fd/10: Permission denied DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=none CRYPTSETUP=n IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation S1200SP NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=575c878a-0be6-4806-9c83-28f67aedea65 ro biosdevname=0 net.ifnames=0 panic=1 verbose console=tty0 console=ttyS0,115200n8 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 01/25/2018 dmi.bios.vendor: Intel Corporation dmi.bios.version: S1200SP.86B.03.01.1029.012520180838 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: S1200SP dmi.board.vendor: Intel Corporation dmi.board.version: H57532-271 dmi.chassis.asset.tag: dmi.chassis.type: 23 dmi.chassis.vendor: ... dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorporation:bvrS1200SP.86B.03.01.1029.012520180838:bd01/25/2018:svnIntelCorporation:pnS1200SP:pvr:rvnIntelCorporation:rnS1200SP:rvrH57532-271:cvn...:ct23:cvr..: dmi.product.family: Family dmi.product.name: S1200SP dmi.product.version:
[Kernel-packages] [Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69
@grzesiekC, on my side, I quite frequently do the same (connecting / reconnecting), I will try to pay attention, to see if it's correlated. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1785964 Title: Unable to unlock the desktop session: systemd-logind: got pause for 13:69 Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Confirmed Bug description: When this issue happens, you won't be able to unlock your desktop session (VT works fine). This happened twice today for me, one is after a suspend, one is just a screen lock. Not sure what is the trigger yet. Syndrome: On the login screen after typing the correct password, you will see a small circle keep spinning and that's it. I need to restart my computer to get it back to normal. In the syslog this error message looks fishy: Aug 8 10:44:57 Leggiero gnome-shell[2118]: g_array_unref: assertion 'array' failed This is part of the syslog fetching from a VT after a GUI unlock attempt (session 24 is the desktop login attempt): Aug 8 10:44:42 Leggiero systemd[1]: Started Session 24 of user sam. Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 226:0 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) AIGLX: Resuming AIGLX clients after VT switch Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): EDID vendor "AUO", prod id 4204 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): Printing DDC gathered Modelines: Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): Modeline "1366x768"x0.0 76.20 1366 1404 1426 1590 768 771 777 798 +hsync -vsync (47.9 kHz eP) Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): Modeline "1366x768"x0.0 76.20 1366 1404 1426 1988 768 771 777 798 +hsync -vsync (38.3 kHz e) Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:78 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - Dell WMI hotkeys: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - Dell WMI hotkeys: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:66 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2 - Sleep Button: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2 - Sleep Button: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:79 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - Integrated_Webcam_HD: Integrate: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - Integrated_Webcam_HD: Integrate: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:68 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4 - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4 - AT Translated Set 2 keyboard: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:67 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3 - Power Button: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3 - Power Button: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:71 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7 - AlpsPS/2 ALPS GlidePoint: is tagged by udev as: Touchpad Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7 - AlpsPS/2 ALPS GlidePoint: device is a touchpad Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:72 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8 - DELL Wireless hotkeys: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8 - DELL Wireless hotkeys: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) libinput: PixArt Microsoft USB Optical Mouse: SetProperty on 286 called but device is disabled. Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: This driver cannot change properties on a disabled device Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:65 Aug 8 10:44:55 Leggiero
[Kernel-packages] [Bug 1801116] Re: linux-aws: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package 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 -- kernel-stable-master-bug: 1799411 + kernel-stable-phase-changed:Thursday, 01. November 2018 17:00 UTC + kernel-stable-phase:Packaging ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1799411 - kernel-stable-phase-changed:Thursday, 01. November 2018 17:00 UTC - kernel-stable-phase:Packaging + phase: Packaging + reason: + prepare-package: Version not specified -- 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/1801116 Title: linux-aws: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1799411 phase: Packaging reason: prepare-package: Version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1801116/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic
I tested last proposed kernel 4.15.0-39, but the issue is still there, no signal with either no ant_sel, ant_sel=0, ant_sel=1 or ant_sel=2. In my environment the last working kernel is 4.15.0-32 with ant_sel=2. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1234 F pulseaudio /dev/snd/controlC0: al 1234 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Notebook Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8137 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.02 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767568] Re: Console DPMS Nonfunctional in Ubuntu Server 18.04
DPMS isn't working for me too on 18.04 x64 server (on 16.04 worked with no problem). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767568 Title: Console DPMS Nonfunctional in Ubuntu Server 18.04 Status in linux package in Ubuntu: Confirmed Bug description: My console display is DPMS capable, i.e., power management functions worked before upgrading from Ubuntu Server 16.0.4.4. Currently the display stays on 24x7 with idle keyboard input. 1) My release information is as follows: Description:Ubuntu 18.04 LTS Release:18.04 2) I am not sure what package this issue is tied to. The current kernel appears to have DPMS support enabled, per the configuration file in /boot. If the kernel is responsible, below is the version I am running. linux-generic: Installed: 4.15.0.20.23 3) I expected to have DPMS support for my console as in the previous release of Ubuntu Server. 4) What happened instead is my monitor stays on all the time, without DPMS controlling it. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-20-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=ab9de6b4-cca0-4e5c-89d7-e706214c8f11 InstallationDate: Installed on 2014-07-23 (1378 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Gigabyte Technology Co., Ltd. X58A-UD5 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 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=5631d3aa-8dce-4306-a08d-4ab3753256ab ro ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic apport-hook-error Uname: Linux 4.15.0-20-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-04-26 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 03/11/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: X58A-UD5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd03/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD5:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: X58A-UD5 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767568/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801123] Re: linux-aws: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package 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 -- kernel-stable-master-bug: 1799401 + kernel-stable-phase-changed:Thursday, 01. November 2018 17:02 UTC + kernel-stable-phase:Packaging ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1799401 - kernel-stable-phase-changed:Thursday, 01. November 2018 17:02 UTC - kernel-stable-phase:Packaging + phase: Packaging + reason: + prepare-package: Version not specified -- 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/1801123 Title: linux-aws: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1799401 phase: Packaging reason: prepare-package: Version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1801123/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801114] Re: linux-aws: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package 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 -- kernel-stable-master-bug: 1799445 + kernel-stable-phase-changed:Thursday, 01. November 2018 17:06 UTC + kernel-stable-phase:Packaging ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1799445 - kernel-stable-phase-changed:Thursday, 01. November 2018 17:06 UTC - kernel-stable-phase:Packaging + phase: Packaging + reason: + prepare-package: Version not specified -- 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/1801114 Title: linux-aws: -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: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1799445 phase: Packaging reason: prepare-package: Version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1801114/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801124] Re: linux-aws: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package 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 -- kernel-stable-master-bug: 1799401 + kernel-stable-phase-changed:Thursday, 01. November 2018 17:05 UTC + kernel-stable-phase:Packaging ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1799401 - kernel-stable-phase-changed:Thursday, 01. November 2018 17:05 UTC - kernel-stable-phase:Packaging + phase: Packaging + reason: + prepare-package: Version not specified -- 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/1801124 Title: linux-aws: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1799401 phase: Packaging reason: prepare-package: Version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1801124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
