[Kernel-packages] [Bug 1830930] Re: USB 3 devices are not detected on thunderbolt 3
Yes, please test it under Windows. And don't forget to upgrade Thunderbolt firmware before switching back to Linux. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830930 Title: USB 3 devices are not detected on thunderbolt 3 Status in linux package in Ubuntu: Confirmed Bug description: I found a strange problem when trying to connect my Samsung T5 SSD. If I connect it to the Thunderbolt port on my HP EliteDesk Mini G4, with Thunderbolt at boot then the SSD is detected without issues. If I unplug it and reconnect then it's not detected. If I force the thunderbolt controller on (boltctl power -t 1) then I can see the new USB host created in lsusb but the attached device is not added. No additional events are shown in dmesg. If I connect the device using another cable then it also doesn't work I have a USB-C cable only rated to USB 2.0 speed then the device is recognized without any issues. Ubuntu 19.04, 5.0.0-15-generic 04:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 2C 2018] (rev 06) 3a:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 2C 2018] (rev 06) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: toby 1495 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-27 (31 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteDesk 800 G4 DM 65W Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=86b0f677-7a3e-4ea6-9d5c-fd7c57d1f964 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-26 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q21 Ver. 02.06.03 dmi.board.name: 845A dmi.board.vendor: HP dmi.board.version: KBC Version 07.D2.00 dmi.chassis.asset.tag: 8CC84321CJ dmi.chassis.type: 6 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ21Ver.02.06.03:bd02/15/2019:svnHP:pnHPEliteDesk800G4DM65W:pvr:rvnHP:rn845A:rvrKBCVersion07.D2.00:cvnHP:ct6:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.product.name: HP EliteDesk 800 G4 DM 65W dmi.product.sku: 5BA07US#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830905] Re: Nvidia RTX 2060 USB bus timeouts cause ~30s delay in boot
Nvidia sent a patch series [1] in linux-usb. Wonder if it helps. [1] https://patchwork.kernel.org/project/linux-usb/list/?series=124541 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830905 Title: Nvidia RTX 2060 USB bus timeouts cause ~30s delay in boot Status in linux package in Ubuntu: Confirmed Bug description: From dmesg: [0.132667] kernel: pci :07:00.1: Linked as a consumer to :07:00.0 [5.882727] kernel: pci :07:00.2: xHCI HW not ready after 5 sec (HC bug?) status = 0x801 [5.882781] kernel: pci :07:00.2: quirk_usb_early_handoff+0x0/0x6a6 took 5615333 usecs [9.984204] kernel: usb 1-7: new full-speed USB device number 4 using xhci_hcd [ 10.308689] kernel: usb 1-7: New USB device found, idVendor=8087, idProduct=0a2b, bcdDevice= 0.10 [ 10.308690] kernel: usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 34.654721] kernel: xhci_hcd :07:00.2: can't setup: -110 [ 34.654730] kernel: xhci_hcd :07:00.2: USB bus 3 deregistered [ 34.654769] kernel: xhci_hcd :07:00.2: init :07:00.2 fail, -110 [ 34.654771] kernel: xhci_hcd: probe of :07:00.2 failed with error -110 $ lspci -k -s :07:00 07:00.0 VGA compatible controller: NVIDIA Corporation TU106 [GeForce RTX 2060 Rev. A] (rev a1) Subsystem: Gigabyte Technology Co., Ltd TU106 Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia 07:00.1 Audio device: NVIDIA Corporation TU106 High Definition Audio Controller (rev a1) Subsystem: Gigabyte Technology Co., Ltd TU106 High Definition Audio Controller Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 07:00.2 USB controller: NVIDIA Corporation TU106 USB 3.1 Host Controller (rev a1) Subsystem: Gigabyte Technology Co., Ltd TU106 USB 3.1 Host Controller 07:00.3 Serial bus controller [0c80]: NVIDIA Corporation TU106 USB Type-C Port Policy Controller (rev a1) Subsystem: Gigabyte Technology Co., Ltd TU106 USB Type-C Port Policy Controller Kernel driver in use: nvidia-gpu Kernel modules: i2c_nvidia_gpu ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.0.0-15-generic 5.0.0-15.16 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 4470 F pulseaudio /dev/snd/controlC1: daniel 4470 F pulseaudio /dev/snd/controlC2: daniel 4470 F pulseaudio CurrentDesktop: i3 Date: Wed May 29 09:36:51 2019 InstallationDate: Installed on 2019-05-07 (21 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. B450M DS3H ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.179 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-05-08 (20 days ago) dmi.bios.date: 01/25/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: B450M DS3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450M DS3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830350] Re: System freezes repeatedly for several seconds; wifi driver related errors
** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- 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/1830350 Title: System freezes repeatedly for several seconds; wifi driver related errors Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Bug description: I updated my system about a month ago (Fri 26 April 2019). This was the first update in several weeks and installed fresh versions of a whole truck load of applications including a kernel update. Since this latest bunch of updates the system freezes for a few seconds at regular intervals. Not fatal, but very annoying. Output from "journalctl -f" shows the following errors occurring at the same time as these freezes: May 24 10:31:18 dellfvw wpa_supplicant[1078]: wlp3s0: CTRL-EVENT-SCAN-FAILED ret=-110 May 24 10:31:18 dellfvw kernel: ath10k_pci :03:00.0: failed to receive scan abortion completion: timed out May 24 10:31:18 dellfvw kernel: ath10k_pci :03:00.0: failed to stop scan: -110 May 24 10:31:18 dellfvw kernel: ath10k_pci :03:00.0: failed to start hw scan: -110 Corresponding lines in /var/log/syslog: May 24 10:29:16 dellfvw avahi-daemon[1053]: Registering new address record for fe80::424:c75b:2a2d:52e2 on wlp3s0.*. May 24 10:29:55 dellfvw avahi-daemon[1053]: Withdrawing address record for fe80::424:c75b:2a2d:52e2 on wlp3s0. May 24 10:31:18 dellfvw wpa_supplicant[1078]: wlp3s0: CTRL-EVENT-SCAN-FAILED ret=-110 May 24 10:31:18 dellfvw kernel: [45569.661175] ath10k_pci :03:00.0: failed to receive scan abortion completion: timed out May 24 10:31:18 dellfvw kernel: [45569.661183] ath10k_pci :03:00.0: failed to stop scan: -110 May 24 10:31:18 dellfvw kernel: [45569.661187] ath10k_pci :03:00.0: failed to start hw scan: -110 I do note the interval between the avahi-daemon entry and the subsequent errors related to the wireless network interface, but the former precede the latter consistently in syslog, suggesting they may be related, which is why I'm including it in this report. The freezes last a few seconds. Keyboard input is preserved at this time and typed input appears after the freeze is resolved. Mouse cursor continues to move during freezes but mouse clicks are only processed after the freeze is resolved, i.e. the result of the mouse click is suspended (e.g. buffered) until the system becomes responsive again. For example, clicking on a window during the freeze will focus that window after the freeze has been resolved. The system is a Dell Inspiron 15 3576. Relevant output of lspci -nnk: 03:00.0 Network controller [0280]: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter [168c:0042] (rev 31) Output of lsb_release -rd: Description: Ubuntu 18.04.2 LTS Release: 18.04 Output of uname -a: Linux dellfvw 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux As already said, this is a new issue that has began occurring only after the recent batch of updates that included a kernel update. I reported the bug (maybe in the wrong place) but so far I have received no response. I've lived with this for a month or so hoping that further updates would fix the problem but it still persists. Installing the latest firmware update (14 Mar 2019) has no effect. No other changes were made to either hardware or OS configuration. Logfile snippets attached. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: frankvw1989 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=7d4169aa-136e-4eac-bb87-bb1b63b0bb27 InstallationDate: Installed on 2018-05-10 (379 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 3576 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-50-generic root=UUID=0ce4cd7e-e0fd-4fe0-83fc-9f845405ab62 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.15.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip disk lpadmin plugdev sambashare sudo users vboxusers _MarkForUpload: True dmi.bios.date: 01/16/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0K83NX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type:
[Kernel-packages] [Bug 1828578] Re: dell xps 9570 killer wifi reconnection issue followed by freeze + Ubuntu 18.04.2 LTS
Please test latest mainline kernel [1] and latest firmware [2]. If the issue persists, please attach `dmesg` output when the issue happens. [1] https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2-rc2/ [2] https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/ -- 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/1828578 Title: dell xps 9570 killer wifi reconnection issue followed by freeze + Ubuntu 18.04.2 LTS Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Bug description: Hello Team, Env - Dell XPS 9570 Ubuntu 18.04.2 , HWE kernel We are facing intermittently wifi reconnection issue on Ubuntu 18.04. Software upgrade is up-to date. Also some time we facing freezing issue due to this hard reset required to make machine back to normal. Please let me know if there are any known issue with this particular model on 18.04 ? Please let me know. Thanks Jay --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: itops 1579 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-04-25 (17 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:5395 Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 004: ID 0c45:671d Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9570 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=c41f7762-f3a2-4b42-a019-97ca9bd85edc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-18-generic N/A linux-backports-modules-4.18.0-18-generic N/A linux-firmware 1.173.5 Tags: bionic Uname: Linux 4.18.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.1 dmi.board.name: 0HWTMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: IT-07384 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.1:bd04/26/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0HWTMH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1690085]
I think I experience the same problem as described here with my recently built Ryzen computer. After installing a fresh Linux distribution I started out with Linux kernel 4.19.45. The computer ran for two days continuously, after a short pause I came back and saw it completely froze. Screen showed the last visible image, but no input worked. Neither ping/ssh, neither mouse or keyboard worked. Not even the num lock LED. There were no log entries written, neither on screen or harddisk. Last entry was some cron job, cleaning up temporary directories. The workload was just a vim, a VNC viewer and a Firefox. The next night, the same freeze happened. That finally got my attention to dig deeper. As first measure I updated the Kernel to 5.1.4. After 2 hours running, without much load, it also froze. I dug deeper, and as first measure I set the BIOS from "Auto" to "Typical current Idle". Uptime is now 1 day, without any workload except a chat client. This is This is my System: # CPU: cpu family : 23 model : 1 model name : AMD Ryzen 5 1600 Six-Core Processor stepping: 1 microcode : 0x8001137 cpu MHz : 1646.140 # Mainboard: Gigabyte Technology Co., Ltd. B450 AORUS ELITE/B450 AORUS ELITE, BIOS F5 01/25/2019 # GPU: NVIDIA GP107 [GeForce GTX 1050 Ti] Driver/OpenGL: 4.6.0 NVIDIA 418.74 # OS: Distro: Manjaro Kernel: 5.1.4-1-MANJARO x86_64 I also see this in my bootup log: 12 times: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0) 12 times: microcode: CPU0: patch_level=0x0800113 Like said, my computer is running now for 1 day without any load with the BIOS option "Typical current Idle" set. This is so far the same "workaround" that brodyck wrote at 2019-04-01 15:40:26 UTC. Unfortunately, or fortunately for him, he has not wrote anything since then. That might mean, that the problems stopped for him at that point. I will further observe this issue with my new workstation. If you don't hear back from me, the BIOS setting very likely worked. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ?
[Kernel-packages] [Bug 1690085]
(In reply to onox from comment #607) To prevent misunderstandings, let me repeat what I previously wrote, from a different angle: ASRock X370 Taichi firmware version v5.50 is worse than previous versions in that it removes the "Power Supply Idle Control" option off the configuration screen. As a result, with Linux 4.18 (Ubuntu kernel 4.18.0-20-generic) and below the system *will* lockup unless different counter measures are taken (namely set the MSR). This said, I have been and am running this single system 24/7 without issues despite extended low load periods on Ubuntu 18.04 LTS kernel 5.0.0-15-generic with microcode level 0x08001137 since May 15 (and from May 11 to May 15 on mainline Linux 5.1.2 with the same microcode) with AsRocks' firmware configuration defaults and without setting the MSR. Summing up, the latest ASRock firmware for this mainboard takes a step in the wrong direction for Linux users, however newer Linux versions prevent this system from locking up. MCExtractor is aware of a newer microcode, 0x08001138 (seen on 2019-02-04) for CPUID 0x00800f11, which ASRock decided not to include in their firmware. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU
[Kernel-packages] [Bug 1777364] Re: coping files to cifs mounted directory causes general protection fault
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777364 Title: coping files to cifs mounted directory causes general protection fault Status in linux package in Ubuntu: Fix Released Bug description: How to reproduce: Copy some large files from local filesystem to CIFS mounted filesystem. After some gigabytes, it syslog will show "general protection fault" and mounted file system will become unresponsive. How often does it occur: Every time, after a few minutes or so. Affected kernels: Bionic 4.15.0-23-generic and forward. I also tried 4.15.18-041518-generic and 4.16.13-041613-generic from ubuntu archives an got similar GPF. 4.13.0-43-generic from ubuntu 17.10 not affected. More information: I have kerberos authenticated, autofs mounted, cifs Mounted with: type cifs (rw,relatime,vers=default,sec=krb5,cache=strict,username=root,uid=1100,forceuid,gid=0,noforcegid,addr=192.168.50.2,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mbarlow2249 F pulseaudio CurrentDesktop: GNOME Date: Sun Jun 17 23:14:02 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=25088f17-7123-46c8-bda4-362bcd9f986e InstallationDate: Installed on 2017-11-26 (203 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:670c Microdia Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=69170b9c-88cc-4e5b-83a8-c6a01d7b738b ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-04-27 (51 days ago) WifiSyslog: dmi.bios.date: 02/26/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.2 dmi.board.name: 06CC14 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.2:bd02/26/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn06CC14:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777364/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811723] Re: Samba client freeze during write when using higher than vers=1.0
According to [1] it's fixed in newer kernel version. Please try it out. [1] https://bugzilla.samba.org/show_bug.cgi?id=13647 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811723 Title: Samba client freeze during write when using higher than vers=1.0 Status in linux package in Ubuntu: Confirmed Bug description: Hello, My issue is that whenever I try to write new files (copy or move) to my file server something in the samba client freezes and I can't do anything samba until the system is rebooted. To get write access I mount with uid ie "sudo mount //server/share /mountpoint -o user=write,uid=1000". Using this command the server and client negotiates smb protocol version 3.02. When this happens the server is still happily serving files to other machines. If I just read files everything works fine. If I connect from a windows client there is no issue. If I add "vers=1.0" everything works but transfers are really slow. Specifying version 3 produces a fail. Trying the same operation (different hw) with Mint 18 Mate produces the same fault. Trying the same operation (with "vers=3.0" set) using SuSE Leap 15.0 KDE live everything works as expected. Both client and server are running fully updated, as of posting, bionic. Using 'dmesg -w' too see what's going on I can see that there is a general protection fault somehow related to cifsd. I am however unable to tell if it is relevant to my issue, from kern.log: Jan 9 21:03:49 ubnu kernel: [ 410.357213] general protection fault: [#1] SMP PTI Jan 9 21:03:49 ubnu kernel: [ 410.357224] Modules linked in: cmac arc4 md4 nls_utf8 cifs ccm fscache rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) thunderbolt bnep binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_hda_codec_realtek snd_soc_acpi snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel intel_rapl btusb x86_pkg_temp_thermal intel_powerclamp btrtl coretemp joydev btbcm snd_hda_codec kvm_intel input_leds kvm irqbypass btintel crct10dif_pclmul crc32_pclmul snd_hda_core ghash_clmulni_intel pcbc snd_hwdep snd_pcm bluetooth ecdh_generic snd_seq_midi snd_seq_midi_event aesni_intel snd_rawmidi aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf snd_seq rtsx_pci_ms snd_seq_device Jan 9 21:03:49 ubnu kernel: [ 410.357357] wmi_bmof snd_timer memstick intel_wmi_thunderbolt snd shpchp soundcore mei_me mei intel_pch_thermal acpi_pad mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 xfs libcrc32c hid_generic usbhid hid rtsx_pci_sdmmc i915 e1000e i2c_algo_bit drm_kms_helper ptp syscopyarea pps_core i2c_i801 sysfillrect sysimgblt rtsx_pci fb_sys_fops drm ahci libahci wmi video Jan 9 21:03:49 ubnu kernel: [ 410.357447] CPU: 2 PID: 1822 Comm: cifsd Tainted: G OE4.15.0-43-generic #46-Ubuntu Jan 9 21:03:49 ubnu kernel: [ 410.357453] Hardware name: /NUC7i3BNB, BIOS BNKBL357.86A.0069.2018.0920.1250 09/20/2018 Jan 9 21:03:49 ubnu kernel: [ 410.357468] RIP: 0010:prefetch_freepointer+0x15/0x30 Jan 9 21:03:49 ubnu kernel: [ 410.357474] RSP: 0018:b16201ae3da0 EFLAGS: 00010282 Jan 9 21:03:49 ubnu kernel: [ 410.357482] RAX: RBX: e90527c744fff71a RCX: 3ea9 Jan 9 21:03:49 ubnu kernel: [ 410.357488] RDX: 3ea8 RSI: e90527c744fff71a RDI: 9d7079255080 Jan 9 21:03:49 ubnu kernel: [ 410.357494] RBP: b16201ae3da0 R08: 9d707ed2b650 R09: b16201ae3db0 Jan 9 21:03:49 ubnu kernel: [ 410.357499] R10: b16201ae3de8 R11: R12: 01011200 Jan 9 21:03:49 ubnu kernel: [ 410.357505] R13: 9d7079255080 R14: 9d7016478c40 R15: 9d7079255080 Jan 9 21:03:49 ubnu kernel: [ 410.357512] FS: () GS:9d707ed0() knlGS: Jan 9 21:03:49 ubnu kernel: [ 410.357519] CS: 0010 DS: ES: CR0: 80050033 Jan 9 21:03:49 ubnu kernel: [ 410.357525] CR2: 7f0a2802d028 CR3: 3760a006 CR4: 003606e0 Jan 9 21:03:49 ubnu kernel: [ 410.357530] Call Trace: Jan 9 21:03:49 ubnu kernel: [ 410.357545] kmem_cache_alloc+0xa2/0x1b0 Jan 9 21:03:49 ubnu kernel: [ 410.357558] ? mempool_alloc_slab+0x15/0x20 Jan 9 21:03:49 ubnu kernel: [ 410.357570] ? wait_woken+0x80/0x80 Jan 9 21:03:49 ubnu kernel: [ 410.357580] mempool_alloc_slab+0x15/0x20 Jan 9 21:03:49 ubnu kernel: [ 410.357590] mempool_alloc+0x71/0x190 Jan 9 21:03:49 ubnu kernel: [ 410.357660] ? smb2_add_credits+0xb0/0x250 [cifs] Jan 9 21:03:49 ubnu kernel: [ 410.357709] cifs_small_buf_get+0x1a/0x30 [cifs] Jan 9 21:03:49 ubnu kernel: [ 410.357751] cifs_demultiplex_thread+0x5c7/0xaf0 [cifs]
[Kernel-packages] [Bug 1831123] Re: USB input devices don't work with Dell WD15 dock
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1831123 Title: USB input devices don't work with Dell WD15 dock Status in linux package in Ubuntu: Invalid Bug description: A USB keyboard and mouse attached to a Dell WD15 USB-C dock stop working after undock/redock, requiring a reboot. Occasionally they fail to work from a cold boot. This was not a problem with the previous kernel 4.15.0-48. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0p: dbakken2277 F...m pulseaudio /dev/snd/controlC2: dbakken2277 F pulseaudio CurrentDesktop: KDE Date: Thu May 30 11:31:44 2019 InstallationDate: Installed on 2018-07-20 (314 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Latitude 7490 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-50-generic root=UUID=bbf44790-b08f-4145-a990-6ae159421aa9 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.3 dmi.board.name: 0DJ6MJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.3:bd04/26/2019:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0DJ6MJ:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831123/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1761379] Re: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu
** Changed in: ubuntu-power-systems 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/1761379 Title: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: [Impact] File libperf-jvmti.so is missing in linux-tools-common deb making it impossible to use perf for the JVM JITed methods. [Test case] $ sudo perf record -k 1 -e instructions:u ./java -agentpath:/usr/lib/linux-tools-5.0.0-8/libperf-jvmti.so crc32 $ sudo perf inject -i ./perf.data -j -o ./perf.data.jitted $ sudo perf report -f -i ./perf.data.jitted [Fix] Include java build dependencies and install the library into linux-tools package. [Regression potential] Small regression potential, an extra file is distributed and is not automatically linked to anything. It could impact the build, which was tested. ---Problem Description--- File libperf-jvmti.so is missing in linux-tools-common deb making it impossible to use perf for the JVM JITed methods ---uname output--- linux-image-4.13.0-36-generic Machine Type = not relevant ---Debugger--- A debugger is not configured ---Steps to Reproduce--- File libperf-jvmti.so is missing in linux-tools-common deb provided for Ubuntu 17.10 making it impossible to use perf for the JVM JITed methods. I also checked if the file is available on launchpad (https://launchpad.net/ubuntu/+source/linux) for Bionic Beaver proposed (main) at it's also absent there: gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-common_4.15.0-13.14_all.deb | fgrep jvm gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-4.15.0-13-generic_4.15.0-13.14_ppc64el.deb | fgrep jvm I do see the file in tools/perf/jvmti dir in the source .tar.gz, but apparently it's no being packaged in any .deb file? Thanks. Userspace tool common name: perf The userspace tool has the following bit modes: 64-bit Userspace tool obtained from project website: na To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1761379/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822133] Re: Azure Instance never recovered during series of instance reboots.
@Dexuan, the error 'WARNING ExtHandler CGroup walinuxagent.service: Crossed the Memory Threshold' started when the vm was first created on May 24, persisted until I stopped/dealocated the VM, and has not returned in syslog. Nor for what it's worth has this error been seen in over six months on another Ubuntu 18.04 VM we have. -- 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/1822133 Title: Azure Instance never recovered during series of instance reboots. Status in linux-azure package in Ubuntu: In Progress Bug description: Description: During SRU Testing of various Azure Instances, there will be some cases where the instance will not respond following a system reboot. SRU Testing only restarts a giving instance once, after it preps all of the necessary files to-be-tested. Series: Disco Instance Size: Basic_A3 Region: (Default) US-WEST-2 Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I initiated a series of tests which rebooted Azure Cloud instances 50 times. During the 49th Reboot, an Instance failed to return from a reboot.. Upon grabbing the console output the following was seen scrolling endlessly. I have seen this failure in cases where the instance only restarted a handful of times >5 [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus In another test attempt I saw the following failure: ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes Both of these failures broke networking, Both of these failures were seen at least twice to three times, thus may explain why in some cases we never recover from an instance reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1822133/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825777] Re: False positive test result in run_netsocktests from net in ubuntu_kernel_selftest
** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** No longer affects: linux (Ubuntu Eoan) ** Changed in: linux (Ubuntu Cosmic) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825777 Title: False positive test result in run_netsocktests from net in ubuntu_kernel_selftest Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: == SRU Justification == The run_netsocktests from net in ubuntu_kernel_selftest will be marked as passed regardless the actual test result from the ./socket: selftests: net: run_netsocktests running socket test [FAIL] ok 1..6 selftests: net: run_netsocktests [PASS] This is because the test script itself has been successfully executed, and make it return 0. == Fix == 30c04d79 (selftests/net: correct the return value for run_netsocktests) This can be cherry-picked into all of our kernels. == Test == Patch tested and submitted to the upstream. == Regression Potential == Changes limit to the testing tool, and it's is expected to see failures from this test in the future. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825777/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1803600] Re: Elantech - Touchpad not working after upgrading to 18.10 from 18.04
Thinkpad L480, same problem, same solution, but encountered while upgrading from 18.10 to 19.04. Machine was fresh installed with 18.10 and touchpad worked out of the box. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1803600 Title: Elantech - Touchpad not working after upgrading to 18.10 from 18.04 Status in linux package in Ubuntu: Confirmed Bug description: Confirmed affected laptops: ThinkPad: L480 L580 P72 P52 When updating from 18.04 to 18.10 on a ThinkPad L480 the Elantech touchpad stopped working. This means it is not recognized at all. This problem occured after the first boot in 18.10 `dmesg | grep -i elantech` shows the following errors: [3.409043] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001) [3.427372] psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0x10. [3.447275] psmouse serio1: elantech: Elan sample query result 00, 23, c8 [3.464905] psmouse serio1: elantech: Trying to set up SMBus access [5.576149] elan_i2c 0-0015: 0-0015 supply vcc not found, using dummy regulator [5.586505] elan_i2c 0-0015: failed to get resolution: -71 [5.586527] elan_i2c: probe of 0-0015 failed with error -71 uname: $ uname -a Linux test 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux I found the following thread which solves the problem temporarly (and reports the same problem in Arch): https://bugs.archlinux.org/task/59714 Running the following command enables it again for the current session: sudo sh -c 'echo -n "elantech"> /sys/bus/serio/devices/serio1/protocol' dmesg afterwards: [ 569.522490] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001) [ 569.544584] psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0x10. [ 569.565939] psmouse serio1: elantech: Elan sample query result 00, 23, c8 Before running the fix: $ cat /sys/bus/serio/devices/serio1/protocol ETSMBus and after: $ cat /sys/bus/serio/devices/serio1/protocol ETPS/2 After reboot the command has to be run again, of course. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Thu Nov 15 20:59:36 2018 DistUpgraded: 2018-11-10 09:56:53,358 DEBUG icon theme changed, re-reading DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-38-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-10-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:506a] InstallationDate: Installed on 2018-08-06 (101 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20LS001AGE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=a1f97298-a2b8-469d-80ed-7497c6e6 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2018-11-10 (5 days ago) dmi.bios.date: 02/09/2018 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET37W (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LS001AGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0QET37W(1.14):bd02/09/2018:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L480 dmi.product.name: 20LS001AGE dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480 dmi.product.version: ThinkPad L480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.4-0~b~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.4-0~b~padoka0 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau:
[Kernel-packages] [Bug 1822133] Re: Azure Instance never recovered during series of instance reboots.
I rebooted our VM over 60 times today without any further issues. Since the VM network went down before I restarted the VM or lost access to the serial console login, I'm also thinking now it was a network issue to begin with. It could always be coincidence that I was able to get the VM back by force stopping and then starting the vm from a stopped state, when neither restarting nor redeploying helped, but there is one thing, correct me if this is wrong, that is different about force stopping and that is it deallocates the VM. If the network issue were internal to the VM I wonder if both restarting and redeploying could have with the best of intentions persisted the faulty network state to the point where the operations failed, while dealocating ended the issue and the VM was able to start over clean. -- 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/1822133 Title: Azure Instance never recovered during series of instance reboots. Status in linux-azure package in Ubuntu: In Progress Bug description: Description: During SRU Testing of various Azure Instances, there will be some cases where the instance will not respond following a system reboot. SRU Testing only restarts a giving instance once, after it preps all of the necessary files to-be-tested. Series: Disco Instance Size: Basic_A3 Region: (Default) US-WEST-2 Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I initiated a series of tests which rebooted Azure Cloud instances 50 times. During the 49th Reboot, an Instance failed to return from a reboot.. Upon grabbing the console output the following was seen scrolling endlessly. I have seen this failure in cases where the instance only restarted a handful of times >5 [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus In another test attempt I saw the following failure: ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes Both of these failures broke networking, Both of these failures were seen at least twice to three times, thus may explain why in some cases we never recover from an instance reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1822133/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830792] Re: [i915] Rotated display is overscaled and overdrawn
Thanks. Your new kernel log shows different crashes in the i915 kernel driver when using Wayland. In particular, the kernel driver seems to think the monitor has been unplugged/replugged: [2.606884] drm_fb_helper_hotplug_event.part.38+0x97/0xc0 [drm_kms_helper] [2.606887] drm_fb_helper_hotplug_event+0x1c/0x30 [drm_kms_helper] [2.606903] intel_fbdev_output_poll_changed+0x6b/0xa0 [i915] [2.606906] drm_kms_helper_hotplug_event+0x2a/0x40 [drm_kms_helper] [2.606910] output_poll_execute+0x19a/0x1c0 [drm_kms_helper] If you did not unplug/replug the monitor while the system was running then this sounds like a faulty cable or faulty connection. Please try a different cable and/or reconnecting the existing one more firmly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830792 Title: [i915] Rotated display is overscaled and overdrawn Status in gnome-shell package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: On my system I have two display: one in landscape, and one in portrait. The landscape display is fine, but the portrait display is corrupted. If I unplug the display from the computer for some time and then plug it back in it will occasionally fix the problem. Once the problem is fixed, the display works perfectly fine, indefinitely. However, as soon as I reboot the computer the display will come up corrupted again and never recovers without many rounds of plug/unplug turn off/turn on. It's extremely frustrating. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 28 15:57:02 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-04-22 (36 days ago) modified.conffile..etc.logrotate.d.apport: [modified] mtime.conffile..etc.logrotate.d.apport: 2019-01-12T15:50:59.090583 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831074] Re: In high fidelity playback, front right side of headset doesn't work
** Package changed: bluez (Ubuntu) => pulseaudio (Ubuntu) ** Summary changed: - In high fidelity playback, front right side of headset doesn't work + [JBL tune 160BT] In high fidelity playback, front right side of headset doesn't work -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1831074 Title: [JBL tune 160BT] In high fidelity playback, front right side of headset doesn't work Status in pulseaudio package in Ubuntu: New Bug description: If i connect my jbl tune 160BT headset,then on high fidelity playback configuration right side of headset doesn't produce any sound. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 29 18:10:40 2019 InstallationDate: Installed on 2019-05-28 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 1bcf:2b8a Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5577 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=84cfd91b-b197-4dea-8ed6-fe6f7cf2aade ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0MVD5F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd08/16/2018:svnDellInc.:pnInspiron5577:pvr1.1.1:rvnDellInc.:rn0MVD5F:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 5577 dmi.product.sku: 07E1 dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: AC:ED:5C:49:18:75 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING RX bytes:1391391 acl:103 sco:26301 events:5764 errors:0 TX bytes:4356927 acl:4943 sco:26284 commands:703 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1831074/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822133] Re: Azure Instance never recovered during series of instance reboots.
I tried to reproduce the bug but couldn't. My Ubuntu 18.04 VM (in West US 2, the VM size is: Basic A3 (4 vcpus, 7 GiB memory)) is still running fine, after I rebooted the VM 100 times with the below /etc/rc.local script: #!/bin/bash date >> /root/reboot.log NUM=`wc -l /root/reboot.log | cut -d' ' -f1` [ $NUM -le 100 ] && reboot In Kirk's log, it looks the VM failed to obtain an IP via DHCP (or somehow the VM's network went DOWN?), and there are a lot of lines of WARNING ExtHandler CGroup walinuxagent.service: Crossed the Memory Threshold. Current Value: 627945472 bytes, Threshold: 512 megabytes. I don't know what the line means. I don't see any issue in Linux kernel and drivers. I guess the issue may be in the waagent/cloud-init daemons, or somewhere outside the VM. Since I can not reproduce the issue, and it looks nobody can reproduce the issue now (it looks Kirk's VM works fine now, after the VM was Stopped and Started again), I can not further debug the issue. If somebody manages to repro the issue again, please check if you're still able to login the VM via Azure serial console; if yes, please check if the VM has an IP address by "ifconfig -a"; if the VM has no IP, we'll have to check the syslog (and/or the network manager's log?) to find out what goes wrong; if the VM has an IP but is unable to communicate to the outside world, something may be wrong with the Linux network device driver. -- 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/1822133 Title: Azure Instance never recovered during series of instance reboots. Status in linux-azure package in Ubuntu: In Progress Bug description: Description: During SRU Testing of various Azure Instances, there will be some cases where the instance will not respond following a system reboot. SRU Testing only restarts a giving instance once, after it preps all of the necessary files to-be-tested. Series: Disco Instance Size: Basic_A3 Region: (Default) US-WEST-2 Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I initiated a series of tests which rebooted Azure Cloud instances 50 times. During the 49th Reboot, an Instance failed to return from a reboot.. Upon grabbing the console output the following was seen scrolling endlessly. I have seen this failure in cases where the instance only restarted a handful of times >5 [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus In another test attempt I saw the following failure: ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes Both of these failures broke networking, Both of these failures were seen at least twice to three times, thus may explain why in some cases we never recover from an instance reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1822133/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1694225] Re: [Thinkpad T450s] Click lock effect on trackpoint left button when touchpad is disabled
Just want to add that in linux mint v19.1 with kernel v4.15.0-20-generic, the issue had been fixed too. Looks like linux mint kernel is different than ubuntu's. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1694225 Title: [Thinkpad T450s] Click lock effect on trackpoint left button when touchpad is disabled Status in linux package in Ubuntu: Fix Released Bug description: The disabled touchpad of my Thinkpad T450s sometimes triggers a click lock when I touch it with my palm. This is typical when I'm reaching to click the trackpoint's (red pointing stick) left button. Reproduction steps: 1. Disable the touchpad via Ubuntu's "Mouse & Touchpad" setting. 2. Place and hold two fingers in contact with the touchpad. 3. Click then release the trackpoint's left button once while the cursor is on the desktop area. Then immediately move the cursor with the pointing stick. 4. If the click lock effect gets triggered, a selection would have been made and dragged on the desktop area. If the click lock doesn't happen, repeat step 3. The evtest log on the trackpoint: $evtest /dev/input/event15 Input driver version is 1.0.1 Input device ID: bus 0x11 vendor 0x2 product 0xa version 0x0 Input device name: "TPPS/2 IBM TrackPoint" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 272 (BTN_LEFT) Event code 273 (BTN_RIGHT) Event code 274 (BTN_MIDDLE) Event type 2 (EV_REL) Event code 0 (REL_X) Event code 1 (REL_Y) Properties: Property type 0 (INPUT_PROP_POINTER) Property type 5 (INPUT_PROP_POINTING_STICK) Testing ... (interrupt to exit) Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1 Event: time 1496047216.720823, -- SYN_REPORT Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0 Event: time 1496047216.778898, -- SYN_REPORT Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1 Event: time 1496047220.234518, -- SYN_REPORT If the click lock is not triggered, you would see BTN_LEFT's value 1 & 0: Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1 Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0 But if the click lock is triggered, you would only see value 1: Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1 I am guessing "value 0" means release the button. So when click lock is happening, the button left is not released at all, thus it's producing "hold the button" effect. This issue doesn't happen with Windows. I can confirm it happens on Ubuntu v17/v16, Kubuntu, Ubuntu Mate, Xubuntu, Lubuntu, Linux Mint, Fedora, and Open Suse. Also, the issue doesn't occur on older thinkpad models which doesn't use the same clickpad, e.g. T430 or X230. WORKAROUND: Execute at a terminal: sudo rmmod psmouse && sudo modprobe psmouse proto=imps --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 3980 F pulseaudio /dev/snd/controlC0: ubuntu 3980 F pulseaudio CasperVersion: 1.387 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20BX001LUS Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/16/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET64WW (1.28 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BX001LUS dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET64WW(1.28):bd03/16/2017:svnLENOVO:pn20BX001LUS:pvrThinkPadT450s:rvnLENOVO:rn20BX001LUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BX001LUS dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage
[Kernel-packages] [Bug 1785912]
Oh well, worth a shot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1785912 Title: Horizontal screen flicker Intel UHD graphics 620 (rev 07) Lenovo Ideapad 720s 13IKB 81BV Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Horrible screen flicker from login screen and after login. 18.04.1 LTS. I have two similar laptops, both Lenovo Ideapad 720s 13IKB, model 81A8 - Core i5 7200U - Intel HD Graphics 620 Rev 02 - works fine. model 81BV - Core i5 8250U - Intel UHD Graphics 620 Rev 07 - awful screen flashing. Neither have the problem in Windows (ie hardware fine) I installed the standard Ubuntu 18.04 on each of them (same USB Key, few weeks apart) but only the 81BV / 8th gen / UHD 620 Rev 07 has the problem. Flickering visible on video here: https://photos.app.goo.gl/HCN73q1nQfgstgVBA I've used ubuntu-bug so I believe you have all the details of the machine. The install came straight from your standard 18.04 download. Any changes are due to me trying to fix this (not much prev exp of kernel params etc) Things tried but which didn't work were: - enable huc/guc (got it to load - it's now visible in the attached dmesg - but didn't help.) - enable_rc6=0 (just stopped sleep / resume working) - edp_vswing=2 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-video-intel 2:2.99.917+git20171229-1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompositorRunning: None Date: Tue Aug 7 23:09:14 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:39af] InstallationDate: Installed on 2018-08-06 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e500 Atheros Communications, Inc. Bus 001 Device 003: ID 5986:210d Acer, Inc Bus 001 Device 002: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81BV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=10eb4e00-26e4-4f42-b983-9a603a658f89 ro i915.enable_guc=3 i915.enable_guc_loading=1 SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/02/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 6MCN27WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 720S-13IKB dmi.modalias: dmi:bvnLENOVO:bvr6MCN27WW:bd05/02/2018:svnLENOVO:pn81BV:pvrLenovoideapad720S-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13IKB: dmi.product.family: ideapad 720S-13IKB dmi.product.name: 81BV dmi.product.version: Lenovo ideapad 720S-13IKB 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 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/linux/+bug/1785912/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785912] Re: Horizontal screen flicker Intel UHD graphics 620 (rev 07) Lenovo Ideapad 720s 13IKB 81BV
** Changed in: linux Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1785912 Title: Horizontal screen flicker Intel UHD graphics 620 (rev 07) Lenovo Ideapad 720s 13IKB 81BV Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Horrible screen flicker from login screen and after login. 18.04.1 LTS. I have two similar laptops, both Lenovo Ideapad 720s 13IKB, model 81A8 - Core i5 7200U - Intel HD Graphics 620 Rev 02 - works fine. model 81BV - Core i5 8250U - Intel UHD Graphics 620 Rev 07 - awful screen flashing. Neither have the problem in Windows (ie hardware fine) I installed the standard Ubuntu 18.04 on each of them (same USB Key, few weeks apart) but only the 81BV / 8th gen / UHD 620 Rev 07 has the problem. Flickering visible on video here: https://photos.app.goo.gl/HCN73q1nQfgstgVBA I've used ubuntu-bug so I believe you have all the details of the machine. The install came straight from your standard 18.04 download. Any changes are due to me trying to fix this (not much prev exp of kernel params etc) Things tried but which didn't work were: - enable huc/guc (got it to load - it's now visible in the attached dmesg - but didn't help.) - enable_rc6=0 (just stopped sleep / resume working) - edp_vswing=2 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-video-intel 2:2.99.917+git20171229-1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompositorRunning: None Date: Tue Aug 7 23:09:14 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:39af] InstallationDate: Installed on 2018-08-06 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e500 Atheros Communications, Inc. Bus 001 Device 003: ID 5986:210d Acer, Inc Bus 001 Device 002: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81BV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=10eb4e00-26e4-4f42-b983-9a603a658f89 ro i915.enable_guc=3 i915.enable_guc_loading=1 SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/02/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 6MCN27WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 720S-13IKB dmi.modalias: dmi:bvnLENOVO:bvr6MCN27WW:bd05/02/2018:svnLENOVO:pn81BV:pvrLenovoideapad720S-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13IKB: dmi.product.family: ideapad 720S-13IKB dmi.product.name: 81BV dmi.product.version: Lenovo ideapad 720S-13IKB 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 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/linux/+bug/1785912/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831157] [NEW] package linux-headers-4.4.0-124 4.4.0-124.148 failed to install/upgrade: package linux-headers-4.4.0-124 is not ready for configuration cannot configure (current
Public bug reported: updating linux ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.4.0-124 4.4.0-124.148 ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 Uname: Linux 4.4.0-146-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jim2060 F pulseaudio Date: Thu May 30 16:48:53 2019 DuplicateSignature: package:linux-headers-4.4.0-124:4.4.0-124.148 Processing triggers for fontconfig (2.11.94-0ubuntu1.1) ... dpkg: error processing package linux-headers-4.4.0-124 (--configure): package linux-headers-4.4.0-124 is not ready for configuration ErrorMessage: package linux-headers-4.4.0-124 is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=aec62113-8bf2-4fab-9d87-58cafdadae3a InstallationDate: Installed on 2016-10-23 (949 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) MachineType: LENOVO 7454CTO PackageArchitecture: all ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-146-generic root=UUID=81b0c258-a14e-47fb-9251-ca8a50481d83 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.22 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-headers-4.4.0-124 4.4.0-124.148 failed to install/upgrade: package linux-headers-4.4.0-124 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6DET72WW (3.22 ) dmi.board.name: 7454CTO 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:bvr6DET72WW(3.22):bd10/25/2012:svnLENOVO:pn7454CTO:pvrThinkPadX200:rvnLENOVO:rn7454CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 7454CTO dmi.product.version: ThinkPad X200 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1831157 Title: package linux-headers-4.4.0-124 4.4.0-124.148 failed to install/upgrade: package linux-headers-4.4.0-124 is not ready for configuration cannot configure (current status 'half-installed') Status in linux package in Ubuntu: Confirmed Bug description: updating linux ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.4.0-124 4.4.0-124.148 ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 Uname: Linux 4.4.0-146-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jim2060 F pulseaudio Date: Thu May 30 16:48:53 2019 DuplicateSignature: package:linux-headers-4.4.0-124:4.4.0-124.148 Processing triggers for fontconfig (2.11.94-0ubuntu1.1) ... dpkg: error processing package linux-headers-4.4.0-124 (--configure): package linux-headers-4.4.0-124 is not ready for configuration ErrorMessage: package linux-headers-4.4.0-124 is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=aec62113-8bf2-4fab-9d87-58cafdadae3a InstallationDate: Installed on 2016-10-23 (949 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) MachineType: LENOVO 7454CTO PackageArchitecture: all ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-146-generic root=UUID=81b0c258-a14e-47fb-9251-ca8a50481d83 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.22 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-headers-4.4.0-124 4.4.0-124.148 failed to install/upgrade: package linux-headers-4.4.0-124 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6DET72WW (3.22 ) dmi.board.name: 7454CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO
[Kernel-packages] [Bug 1831157] 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/1831157 Title: package linux-headers-4.4.0-124 4.4.0-124.148 failed to install/upgrade: package linux-headers-4.4.0-124 is not ready for configuration cannot configure (current status 'half-installed') Status in linux package in Ubuntu: Confirmed Bug description: updating linux ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.4.0-124 4.4.0-124.148 ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 Uname: Linux 4.4.0-146-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jim2060 F pulseaudio Date: Thu May 30 16:48:53 2019 DuplicateSignature: package:linux-headers-4.4.0-124:4.4.0-124.148 Processing triggers for fontconfig (2.11.94-0ubuntu1.1) ... dpkg: error processing package linux-headers-4.4.0-124 (--configure): package linux-headers-4.4.0-124 is not ready for configuration ErrorMessage: package linux-headers-4.4.0-124 is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=aec62113-8bf2-4fab-9d87-58cafdadae3a InstallationDate: Installed on 2016-10-23 (949 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) MachineType: LENOVO 7454CTO PackageArchitecture: all ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-146-generic root=UUID=81b0c258-a14e-47fb-9251-ca8a50481d83 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.22 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-headers-4.4.0-124 4.4.0-124.148 failed to install/upgrade: package linux-headers-4.4.0-124 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6DET72WW (3.22 ) dmi.board.name: 7454CTO 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:bvr6DET72WW(3.22):bd10/25/2012:svnLENOVO:pn7454CTO:pvrThinkPadX200:rvnLENOVO:rn7454CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 7454CTO dmi.product.version: ThinkPad X200 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831157/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831157] Re: package linux-headers-4.4.0-124 4.4.0-124.148 failed to install/upgrade: package linux-headers-4.4.0-124 is not ready for configuration cannot configure (current st
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1831157 Title: package linux-headers-4.4.0-124 4.4.0-124.148 failed to install/upgrade: package linux-headers-4.4.0-124 is not ready for configuration cannot configure (current status 'half-installed') Status in linux package in Ubuntu: Confirmed Bug description: updating linux ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.4.0-124 4.4.0-124.148 ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 Uname: Linux 4.4.0-146-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jim2060 F pulseaudio Date: Thu May 30 16:48:53 2019 DuplicateSignature: package:linux-headers-4.4.0-124:4.4.0-124.148 Processing triggers for fontconfig (2.11.94-0ubuntu1.1) ... dpkg: error processing package linux-headers-4.4.0-124 (--configure): package linux-headers-4.4.0-124 is not ready for configuration ErrorMessage: package linux-headers-4.4.0-124 is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=aec62113-8bf2-4fab-9d87-58cafdadae3a InstallationDate: Installed on 2016-10-23 (949 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) MachineType: LENOVO 7454CTO PackageArchitecture: all ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-146-generic root=UUID=81b0c258-a14e-47fb-9251-ca8a50481d83 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.22 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-headers-4.4.0-124 4.4.0-124.148 failed to install/upgrade: package linux-headers-4.4.0-124 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6DET72WW (3.22 ) dmi.board.name: 7454CTO 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:bvr6DET72WW(3.22):bd10/25/2012:svnLENOVO:pn7454CTO:pvrThinkPadX200:rvnLENOVO:rn7454CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 7454CTO dmi.product.version: ThinkPad X200 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831157/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831123] Re: USB input devices don't work with Dell WD15 dock
I determined that the problem was actually caused by updating the firmware on my Dell Latitude 7490 from version 1.7.2 to 1.9.3. So I believe this bug report can be closed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1831123 Title: USB input devices don't work with Dell WD15 dock Status in linux package in Ubuntu: Confirmed Bug description: A USB keyboard and mouse attached to a Dell WD15 USB-C dock stop working after undock/redock, requiring a reboot. Occasionally they fail to work from a cold boot. This was not a problem with the previous kernel 4.15.0-48. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0p: dbakken2277 F...m pulseaudio /dev/snd/controlC2: dbakken2277 F pulseaudio CurrentDesktop: KDE Date: Thu May 30 11:31:44 2019 InstallationDate: Installed on 2018-07-20 (314 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Latitude 7490 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-50-generic root=UUID=bbf44790-b08f-4145-a990-6ae159421aa9 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.3 dmi.board.name: 0DJ6MJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.3:bd04/26/2019:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0DJ6MJ:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831123/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823753] Re: arm64: cma_alloc errors at boot
Thanks Paolo and John. I've uploaded a cma.4 kernel to ppa:dannf/cma that includes the following additional fix: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=e7a647580852f90b7f9a5b940e7eaffa105f6271 I'll get some non-ARM architecture testing on that before submitting for the next SRU cycle. ** Also affects: linux (Ubuntu Eoan) Importance: High Status: Confirmed ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Disco) Status: New => In Progress ** Changed in: linux (Ubuntu Eoan) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux (Ubuntu Disco) Importance: Undecided => High ** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823753 Title: arm64: cma_alloc errors at boot Status in linux package in Ubuntu: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: In Progress Bug description: On some arm64 systems[*] we are seeing a spew of messages on the console: [ 19.534097] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534109] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534113] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534126] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534130] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534142] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534146] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534157] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534161] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534173] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534177] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 This appears to be non-fatal - impacted systems all eventually boot. But, at least in the case of the HP m400, it slows down boot enough that MAAS' default timeout will expire before completing deployment. [*] Observed on a HiSilicon D06 w/ SMMU disabled in the BIOS, as well as an HP m400 (APM X-Gene) cartridge - although, not on another one that - in theory - should be identical. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823753/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826447] Re: Azure: Backport vIOMMU driver (increase vCPU limits)
https://lists.ubuntu.com/archives/kernel-team/2019-May/101013.html -- 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/1826447 Title: Azure: Backport vIOMMU driver (increase vCPU limits) Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Cosmic: In Progress Status in linux-azure source package in Disco: Incomplete Bug description: Description: To support VM instances with >255 vCPUS, we need the patch set below backported to the Azure 4.18 kernel. These patches include - - New Hyper-V IOMMU driver. This driver will be Hyper-V specific. - Minor update to the Hyper-V specific virtual PCI code. Need to expand the size of an array to allow for a larger number of vCPUs. There are very large VM instance sizes coming to Azure in 2019, and Ubuntu will require the following patches in order to function properly: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=29217a4746835fef35279abbd12c1a1efe83bfca https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=84fdfafab849036b5aefa52824b5cb42e887ef0e https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=c8ccf7599ddac5fa48e06104c44b24709e21eed5 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/controller /pci-hyperv.c?id=9bc1174280ddf7693e8c29a8f1743809e987ac37 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1826447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826447] Re: Azure: Backport vIOMMU driver (increase vCPU limits)
Should we also include it to disco/linux-azure? ** Changed in: linux-azure (Ubuntu Cosmic) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Cosmic) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Also affects: linux-azure (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Disco) Status: New => Incomplete ** Changed in: linux-azure (Ubuntu Disco) Assignee: (unassigned) => Marcelo Cerri (mhcerri) -- 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/1826447 Title: Azure: Backport vIOMMU driver (increase vCPU limits) Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Cosmic: In Progress Status in linux-azure source package in Disco: Incomplete Bug description: Description: To support VM instances with >255 vCPUS, we need the patch set below backported to the Azure 4.18 kernel. These patches include - - New Hyper-V IOMMU driver. This driver will be Hyper-V specific. - Minor update to the Hyper-V specific virtual PCI code. Need to expand the size of an array to allow for a larger number of vCPUs. There are very large VM instance sizes coming to Azure in 2019, and Ubuntu will require the following patches in order to function properly: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=29217a4746835fef35279abbd12c1a1efe83bfca https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=84fdfafab849036b5aefa52824b5cb42e887ef0e https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=c8ccf7599ddac5fa48e06104c44b24709e21eed5 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/controller /pci-hyperv.c?id=9bc1174280ddf7693e8c29a8f1743809e987ac37 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1826447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820075] Re: [Packaging] Improve config annotations check on custom kernels
linux-azure: https://lists.ubuntu.com/archives/kernel- team/2019-May/101009.html ** Also affects: linux-azure (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Bionic) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Changed in: linux-azure (Ubuntu Cosmic) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Changed in: linux-azure (Ubuntu Disco) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Changed in: linux-gcp (Ubuntu Cosmic) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Changed in: linux-gcp (Ubuntu Bionic) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Changed in: linux-gcp (Ubuntu Disco) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Changed in: linux-azure (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Cosmic) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Disco) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1820075 Title: [Packaging] Improve config annotations check on custom kernels Status in linux-azure package in Ubuntu: New Status in linux-gcp package in Ubuntu: New Status in linux-azure source package in Bionic: In Progress Status in linux-gcp source package in Bionic: New Status in linux-azure source package in Cosmic: In Progress Status in linux-gcp source package in Cosmic: Fix Released Status in linux-azure source package in Disco: In Progress Status in linux-gcp source package in Disco: New Bug description: [Impact] Currently for custom kernels, it's necessary to keep a separate annotations file that often gets out of sync with the corresponding file in debian.master/. The "debian/scripts/config-check" script can be changed to allow additional annotations files to act as overlays over the original annotations file, allowing custom kernels to override the policies just for the relevant configs. The proposal is to add support for an include directive in the annotations file so custom kernels can include the annotations file from its base kernel and override policies on a config basis. [Test Case] A kernel build should complete successfully after the change. [Regression Potential] Low regression potential since that's a change on the build process that doesn't affect the final kernel that is built. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1820075/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1761379] Re: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Disco) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1761379 Title: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Fix Committed Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: [Impact] File libperf-jvmti.so is missing in linux-tools-common deb making it impossible to use perf for the JVM JITed methods. [Test case] $ sudo perf record -k 1 -e instructions:u ./java -agentpath:/usr/lib/linux-tools-5.0.0-8/libperf-jvmti.so crc32 $ sudo perf inject -i ./perf.data -j -o ./perf.data.jitted $ sudo perf report -f -i ./perf.data.jitted [Fix] Include java build dependencies and install the library into linux-tools package. [Regression potential] Small regression potential, an extra file is distributed and is not automatically linked to anything. It could impact the build, which was tested. ---Problem Description--- File libperf-jvmti.so is missing in linux-tools-common deb making it impossible to use perf for the JVM JITed methods ---uname output--- linux-image-4.13.0-36-generic Machine Type = not relevant ---Debugger--- A debugger is not configured ---Steps to Reproduce--- File libperf-jvmti.so is missing in linux-tools-common deb provided for Ubuntu 17.10 making it impossible to use perf for the JVM JITed methods. I also checked if the file is available on launchpad (https://launchpad.net/ubuntu/+source/linux) for Bionic Beaver proposed (main) at it's also absent there: gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-common_4.15.0-13.14_all.deb | fgrep jvm gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-4.15.0-13-generic_4.15.0-13.14_ppc64el.deb | fgrep jvm I do see the file in tools/perf/jvmti dir in the source .tar.gz, but apparently it's no being packaged in any .deb file? Thanks. Userspace tool common name: perf The userspace tool has the following bit modes: 64-bit Userspace tool obtained from project website: na To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1761379/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1761379] Re: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu
** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1761379 Title: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Fix Committed Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Status in linux source package in Disco: In Progress Bug description: [Impact] File libperf-jvmti.so is missing in linux-tools-common deb making it impossible to use perf for the JVM JITed methods. [Test case] $ sudo perf record -k 1 -e instructions:u ./java -agentpath:/usr/lib/linux-tools-5.0.0-8/libperf-jvmti.so crc32 $ sudo perf inject -i ./perf.data -j -o ./perf.data.jitted $ sudo perf report -f -i ./perf.data.jitted [Fix] Include java build dependencies and install the library into linux-tools package. [Regression potential] Small regression potential, an extra file is distributed and is not automatically linked to anything. It could impact the build, which was tested. ---Problem Description--- File libperf-jvmti.so is missing in linux-tools-common deb making it impossible to use perf for the JVM JITed methods ---uname output--- linux-image-4.13.0-36-generic Machine Type = not relevant ---Debugger--- A debugger is not configured ---Steps to Reproduce--- File libperf-jvmti.so is missing in linux-tools-common deb provided for Ubuntu 17.10 making it impossible to use perf for the JVM JITed methods. I also checked if the file is available on launchpad (https://launchpad.net/ubuntu/+source/linux) for Bionic Beaver proposed (main) at it's also absent there: gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-common_4.15.0-13.14_all.deb | fgrep jvm gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-4.15.0-13-generic_4.15.0-13.14_ppc64el.deb | fgrep jvm I do see the file in tools/perf/jvmti dir in the source .tar.gz, but apparently it's no being packaged in any .deb file? Thanks. Userspace tool common name: perf The userspace tool has the following bit modes: 64-bit Userspace tool obtained from project website: na To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1761379/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820075] Re: [Packaging] Improve config annotations check on custom kernels
** Also affects: linux-azure (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1820075 Title: [Packaging] Improve config annotations check on custom kernels Status in linux-azure package in Ubuntu: New Status in linux-gcp package in Ubuntu: New Status in linux-azure source package in Bionic: New Status in linux-gcp source package in Bionic: New Status in linux-azure source package in Cosmic: New Status in linux-gcp source package in Cosmic: Fix Released Bug description: [Impact] Currently for custom kernels, it's necessary to keep a separate annotations file that often gets out of sync with the corresponding file in debian.master/. The "debian/scripts/config-check" script can be changed to allow additional annotations files to act as overlays over the original annotations file, allowing custom kernels to override the policies just for the relevant configs. The proposal is to add support for an include directive in the annotations file so custom kernels can include the annotations file from its base kernel and override policies on a config basis. [Test Case] A kernel build should complete successfully after the change. [Regression Potential] Low regression potential since that's a change on the build process that doesn't affect the final kernel that is built. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1820075/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830941] Re: linux: 4.4.0-150.176 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830941 Title: linux: 4.4.0-150.176 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Thursday, 30. May 2019 11:31 UTC reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: 'Pending -- snap pc-kernel not in expected channel(s): arch=amd64:channel=latest/beta arch=i386:channel=latest/beta' snap-release-to-edge: 'Pending -- snap pc-kernel not in expected channel(s): arch=amd64:channel=latest/edge arch=i386:channel=latest/edge' verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1830941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830813] Re: TCP : race condition on socket ownership in tcp_close()
** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830813 Title: TCP : race condition on socket ownership in tcp_close() Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: SRU Justification Impact: WARN_ON messages casued by race condition between the close of a TCP socket and another process inspecting the same socket. The code of interest is the following; in tcp_close function : ... release_sock(sk); ... WARN_ON(sock_owned_by_user(sk)); ... While in release_sock(sk), sock_release_owner function is called which sets the sk->sk_lock.owned=0. When WARN_ON(sock_owned_by_user(sk)) is called it expects to find that the socket is not owned by anyone. According to upstream commit 8873c064d1de579ea2341, while a socket is being closed is possible that other threads find it in rtnetlink dump. tcp_get_info() function acquires the socket lock ( and sets sk_lock.owned=1 ) for a short amount of time, however long enough to trigger this warning. Fix: Fixed by upstream commit in v4.20: Commit: 8873c064d1de579ea23412a6d3eee972593f142b "tcp: do not release socket ownership in tcp_close()" Commit 8873c064d1de579ea23412a6d3eee972 fixes this bug by delegating the release of ownership (calling release_sock(sk)) to later; just before exiting tcp_close function. Testcase: Reporter has tested and verified test 4.15 test kernel for Bionic. This bug is difficult to be reproduced locally because the race condition cannot be triggered in a deterministic way. To hit this bug we need the following : a) a process closing a socket and while the execution is between release_sock(s) and WARN_ON(sock_owned_by_user(sk)) b) another process inspecting the same socket to get into tcp_get_info(), acquire ownership of the socket and not release it until the first process reaches the WARN_ON(sock_owned_by_user(sk)). This scenario is difficult to be achieved in a testing environment. Regression Potential: As far as Bionic (4.15 kernel) is concerned the reporter of the bug has tested and verified a test kernel with the fix. Concerning Cosmic (4.18 kernel) the fix has not been tested. However, given that a) this fix essentially removes the WARN_ON(sock_owned_by_user(sk)) and delegates the release of the ownership to later in the tcp_close function, and b) the relevant code paths in 4.15 and 4.18 are largely the same the regression potential should be minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830813/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security
Hi. I'm using a Ubuntu 19.04 on a Samsung NP300E5C. I noticed I couldn't sudo update and I was getting a "can't write to /tmp" error. I rebooted my PC, and now it won't go past the purple screen. I've tried the add "dis_ucode_ldr" fix but nothing happened. Please I'm fairly new at Linux, can someone explain how I can go about fixing this bug? Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829620 Title: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: Description: - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of booting, after grub) - does not even show the enter cryptsetup passphrase - affected kernels: # apt list --installed |grep linux-signed WARNING: apt does not have a stable CLI interface. Use with caution in scripts. linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 [installed] linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 4.18.0.20.70 amd64 [installed] linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 5.0.0.15.71 amd64 [installed] - the setup is not new, has been working perfectly before (about 7 days since my last restart?) System: - HW: ASUS Zenbook 14 UX433FN - Ubuntu 18.04, runing latest HWE, fully updated - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup), Suspected/possible cause?: - recent intel-microcode package update - recent kernel package updates Steps taken: - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding nosplash, noplymouth) - completely removed nvidia drivers (apt purge *nvidia*) - completely purged and reinstalled grub (grup-pc) - completely purged and reinstalled all kernels (headers, modules, image, ..) - toggle BIOS "fastboot" (now using OFF) - toggle UEFI SecureBoot (now using ON) - remove plymouth (apt remove *plymouth* , but the workaround is working with plymouth installed) Workaround: - so far, I'm only able to boot with non-Ubuntu kernel! (linux-image-liquorix-amd64) - which needs "splash" option ON - reinstall cryptsetup & update-grub (as suggested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620/comments/10 ) I am not sure how to get you more debug info, as this setup has been working before, and it's a very eary boot-process bug, so I can't even access dmesg etc. EDIT: Hypothesis: Only affects ASUS with i7-8565U Whiskey Lake Intel CPU Upstream Bug Report: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1 WORKAROUND 1: disable intel microcode updates during boot From this bug: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920 1/ add the boot parameter: dis_ucode_ldr to /etc/default/grub 2/ update-grub WORKAROUND 2: downgrade (and hold) intel-microcode to older version from bionic/main apt install --reinstall intel-microcode=3.20180312.0~ubuntu18.04.1 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2337 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge (not installed) Tags: bionic wayland-session Uname: Linux 5.0.0-17.1-liquorix-amd64 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo vboxusers video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2339 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6 Tags: third-party-packages bionic wayland-session Uname: Linux 5.0.0-15-generic x86_64 UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1829620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net
[Kernel-packages] [Bug 1777364] Re: coping files to cifs mounted directory causes general protection fault
I've filed the same bug here, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811723 . Didn't find this one because I searched for the wrong terms, sorry about the duplicate. On a personal note I'd like to add that I'm surprised this doesn't affect more people and even more so that it hasn't been fixed yet. I would have thought that being able to copy files, large and small, to and from a file-server was a pretty common usecase and a fundamental function in any OS. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777364 Title: coping files to cifs mounted directory causes general protection fault Status in linux package in Ubuntu: Confirmed Bug description: How to reproduce: Copy some large files from local filesystem to CIFS mounted filesystem. After some gigabytes, it syslog will show "general protection fault" and mounted file system will become unresponsive. How often does it occur: Every time, after a few minutes or so. Affected kernels: Bionic 4.15.0-23-generic and forward. I also tried 4.15.18-041518-generic and 4.16.13-041613-generic from ubuntu archives an got similar GPF. 4.13.0-43-generic from ubuntu 17.10 not affected. More information: I have kerberos authenticated, autofs mounted, cifs Mounted with: type cifs (rw,relatime,vers=default,sec=krb5,cache=strict,username=root,uid=1100,forceuid,gid=0,noforcegid,addr=192.168.50.2,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mbarlow2249 F pulseaudio CurrentDesktop: GNOME Date: Sun Jun 17 23:14:02 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=25088f17-7123-46c8-bda4-362bcd9f986e InstallationDate: Installed on 2017-11-26 (203 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:670c Microdia Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=69170b9c-88cc-4e5b-83a8-c6a01d7b738b ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-04-27 (51 days ago) WifiSyslog: dmi.bios.date: 02/26/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.2 dmi.board.name: 06CC14 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.2:bd02/26/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn06CC14:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777364/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775717] Re: CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: thermald (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1775717
Title:
CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
Status in linux package in Ubuntu:
Incomplete
Status in thermald package in Ubuntu:
Confirmed
Bug description:
After upgrading from Ubuntu 16.04 to 18.04, I've noticed that CPU and
GPU fans suddenly go full throttle. It doesn't seem to depend on
temperature, could happen when 32 °C reported, sometimes the laptop
can work for day or two without this issue, but eventually it happens.
The only way to stop fans is to power off the laptop, power on (fans
go 100% at this point again), power off during BIOS splash screen and
power on again. Seems to happen more often after waking up from a
sleep.
Things tried:
Upgrading BIOS to latest available on ASUS site to the date of
writing. No change.
asus-fan kernel module (https://github.com/daringer/asus-fan). Detects
both fans and shows correct speed in /sys/class/hwmon/*/fan{1,2}*, but
does not seem to control it and does not prevent going full throttle.
4.17.0 kernel from Ubuntu mainline builds. Doesn't seem to affect the
issue.
Userspace fan control software (https://github.com/hirschmann/nbfc).
Can control speed of both fans to the point where they go full
throttle, after that has no effect on them.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: whale 3068 F pulseaudio
/dev/snd/controlC0: whale 3068 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=ada9b595-bbf2-40a3-8575-5908492bb969
InstallationDate: Installed on 2014-10-20 (1333 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64+mac
(20140722.2)
MachineType: ASUSTeK COMPUTER INC. G752VT
NonfreeKernelModules: nvidia_modeset nvidia wl
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic
root=UUID=f6509d56-6183-464c-90bb-9c3be2c8abdf ro quiet splash
acpi_backlight=vendor vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-23-generic N/A
linux-backports-modules-4.15.0-23-generic N/A
linux-firmware 1.173.1
Tags: bionic
Uname: Linux 4.15.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo tty
video
_MarkForUpload: True
dmi.bios.date: 06/29/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G752VT.304
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G752VT
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrG752VT.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: G
dmi.product.name: G752VT
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775717/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831103] Re: bionic: netlink: potential shift overflow in netlink_bind()
** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1831103 Title: bionic: netlink: potential shift overflow in netlink_bind() Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] The check for correctness of netlink_bind() userspace supplied parameter is done by applying a bitmask made from ngroups shift. However if we have more than 64 groups the shift results in an overflow causing an incorrect validation of the netlink_bind() parameters. This has been fixed upstream: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=91874ecf32e41b5d86a4cb9d60e0bee50d828058 And this fix has been applied to xenial, cosmic and disco (apparently only bionic is missing it). [Test Case] I've been able to reproduce this problem using a script with acpid to handle ACPI hibernate events. The script is the following: $ cat /etc/acpi/actions/sleep.sh #!/bin/sh echo "1=$1 2=$2" >> /home/ubuntu/acpi-event.log Any kernel that has the fix (xenial and cosmic for example) are logging two events (input and netlink) when the sleep button is fired: $ cat /home/ubuntu/acpi-event.log 1=button/sleep 2=SBTN 1=button/sleep 2=LNXSLPBN:00 The bionic kernel, instead, is logging only one event (input, netlink is lost): $ cat /home/ubuntu/acpi-event.log 1=button/sleep 2=SBTN [Fix] Fix that solves this problem: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=91874ecf32e41b5d86a4cb9d60e0bee50d828058 [Regression Potential] Upsteram fix, tested on the affected platform, all other kernel releases have this fix applied already, so regression potential is minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831103/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831123] 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/1831123 Title: USB input devices don't work with Dell WD15 dock Status in linux package in Ubuntu: Confirmed Bug description: A USB keyboard and mouse attached to a Dell WD15 USB-C dock stop working after undock/redock, requiring a reboot. Occasionally they fail to work from a cold boot. This was not a problem with the previous kernel 4.15.0-48. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0p: dbakken2277 F...m pulseaudio /dev/snd/controlC2: dbakken2277 F pulseaudio CurrentDesktop: KDE Date: Thu May 30 11:31:44 2019 InstallationDate: Installed on 2018-07-20 (314 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Latitude 7490 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-50-generic root=UUID=bbf44790-b08f-4145-a990-6ae159421aa9 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.3 dmi.board.name: 0DJ6MJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.3:bd04/26/2019:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0DJ6MJ:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831123/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1268252] Re: Brightness settings stopped working after upgrade
** Changed in: linux (Ubuntu Trusty) Assignee: Satwik Bhandiwad (satwik-bhandiwad) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1268252 Title: Brightness settings stopped working after upgrade Status in linux package in Ubuntu: Incomplete Status in linux source package in Trusty: Confirmed Bug description: I upgraded from saucy to trusty on my lenovo g505s laptop. After the upgrade, both the physical key and the brightness settings in the gnome-control centre have stopped working. Whatever level of brightness i decrease it to, it always stays on maximum. I'm able to reproduce this only on kernel 3.13. Works as its supposed to on kernel 3.12 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu50 ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7 Uname: Linux 3.13.0-2-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jan 12 09:17:00 2014 ExecutablePath: /usr/bin/gnome-control-center.real InstallationDate: Installed on 2013-11-16 (56 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to trusty on 2014-01-06 (5 days ago) --- ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: krishnan 3070 F pulseaudio /dev/snd/controlC0: krishnan 3070 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c545b9da-fef4-4530-9051-29276dfd842c InstallationDate: Installed on 2013-11-16 (58 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO INVALID NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 simple ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-2-generic root=UUID=0b897d24-0c02-4f57-9596-5fcd681c5ed0 ro quiet splash nomodeset vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7 RelatedPackageVersions: linux-restricted-modules-3.13.0-2-generic N/A linux-backports-modules-3.13.0-2-generic N/A linux-firmware1.121 StagingDrivers: rts5139 Tags: trusty staging Uname: Linux 3.13.0-2-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-01-06 (6 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 04/23/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 83CN12WW(V1.01) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo G505s dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G505s dmi.modalias: dmi:bvnLENOVO:bvr83CN12WW(V1.01):bd04/23/2013:svnLENOVO:pnINVALID:pvrLenovoG505s:rvnLENOVO:rnLenovoG505s:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoG505s: dmi.product.name: INVALID dmi.product.version: Lenovo G505s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831123] [NEW] USB input devices don't work with Dell WD15 dock
Public bug reported: A USB keyboard and mouse attached to a Dell WD15 USB-C dock stop working after undock/redock, requiring a reboot. Occasionally they fail to work from a cold boot. This was not a problem with the previous kernel 4.15.0-48. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0p: dbakken2277 F...m pulseaudio /dev/snd/controlC2: dbakken2277 F pulseaudio CurrentDesktop: KDE Date: Thu May 30 11:31:44 2019 InstallationDate: Installed on 2018-07-20 (314 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Latitude 7490 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-50-generic root=UUID=bbf44790-b08f-4145-a990-6ae159421aa9 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.3 dmi.board.name: 0DJ6MJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.3:bd04/26/2019:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0DJ6MJ:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1831123 Title: USB input devices don't work with Dell WD15 dock Status in linux package in Ubuntu: New Bug description: A USB keyboard and mouse attached to a Dell WD15 USB-C dock stop working after undock/redock, requiring a reboot. Occasionally they fail to work from a cold boot. This was not a problem with the previous kernel 4.15.0-48. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0p: dbakken2277 F...m pulseaudio /dev/snd/controlC2: dbakken2277 F pulseaudio CurrentDesktop: KDE Date: Thu May 30 11:31:44 2019 InstallationDate: Installed on 2018-07-20 (314 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Latitude 7490 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-50-generic root=UUID=bbf44790-b08f-4145-a990-6ae159421aa9 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.3 dmi.board.name: 0DJ6MJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.3:bd04/26/2019:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0DJ6MJ:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831123/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829186] Re: linux: 4.18.0-21.22 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829185 (bionic/linux-hwe) derivatives: bug 1829174 (linux-raspi2), bug 1829177 (linux-aws), bug 1829180 (linux-azure), bug 1829183 (linux-gcp), bug 1829184 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true - phase: Testing - phase-changed: Monday, 20. May 2019 14:01 UTC + phase: Ready for Testing + phase-changed: Thursday, 30. May 2019 16:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829186 Title: linux: 4.18.0-21.22 -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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829185 (bionic/linux-hwe) derivatives: bug 1829174 (linux-raspi2), bug 1829177 (linux-aws), bug 1829180 (linux-azure), bug 1829183 (linux-gcp), bug 1829184 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Ready for Testing phase-changed: Thursday, 30. May 2019 16:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829186/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831121] [NEW] linux-azure cryptsetup warning upon installing linux-azure kernel
Public bug reported: Series: Cosmic Instance: Any (Basic_A2) for this example Kernel: 4.18.0-1018-azuze Disk Encryption: None configured Reproduce: 1.) Install Cosmic 2.) Add Cosmic -proposed repo to sources -list 3.) sudo apt-get update && sudo apt-get install -y linux-azure Targeted kernel is 4.18.0-1018-azure Preparing to unpack .../05-linux-headers-4.18.0-1019-azure_4.18.0-1019.19_amd64.deb ... Unpacking linux-headers-4.18.0-1019-azure (4.18.0-1019.19) ... Preparing to unpack .../06-linux-headers-azure_4.18.0.1019.20_amd64.deb ... Unpacking linux-headers-azure (4.18.0.1019.20) over (4.18.0.1018.19) ... Selecting previously unselected package linux-azure-tools-4.18.0-1019. Preparing to unpack .../07-linux-azure-tools-4.18.0-1019_4.18.0-1019.19_amd64.deb ... Unpacking linux-azure-tools-4.18.0-1019 (4.18.0-1019.19) ... Selecting previously unselected package linux-tools-4.18.0-1019-azure. Preparing to unpack .../08-linux-tools-4.18.0-1019-azure_4.18.0-1019.19_amd64.deb ... Unpacking linux-tools-4.18.0-1019-azure (4.18.0-1019.19) ... Preparing to unpack .../09-linux-tools-azure_4.18.0.1019.20_amd64.deb ... Unpacking linux-tools-azure (4.18.0.1019.20) over (4.18.0.1018.19) ... Selecting previously unselected package linux-azure-cloud-tools-4.18.0-1019. Preparing to unpack .../10-linux-azure-cloud-tools-4.18.0-1019_4.18.0-1019.19_amd64.deb ... Unpacking linux-azure-cloud-tools-4.18.0-1019 (4.18.0-1019.19) ... Selecting previously unselected package linux-cloud-tools-4.18.0-1019-azure. Preparing to unpack .../11-linux-cloud-tools-4.18.0-1019-azure_4.18.0-1019.19_amd64.deb ... Unpacking linux-cloud-tools-4.18.0-1019-azure (4.18.0-1019.19) ... Preparing to unpack .../12-linux-cloud-tools-azure_4.18.0.1019.20_amd64.deb ... Unpacking linux-cloud-tools-azure (4.18.0.1019.20) over (4.18.0.1018.19) ... Setting up linux-modules-4.18.0-1019-azure (4.18.0-1019.19) ... Setting up linux-image-4.18.0-1019-azure (4.18.0-1019.19) ... I: /vmlinuz is now a symlink to boot/vmlinuz-4.18.0-1019-azure I: /initrd.img is now a symlink to boot/initrd.img-4.18.0-1019-azure Setting up linux-azure-headers-4.18.0-1019 (4.18.0-1019.19) ... Setting up linux-azure-cloud-tools-4.18.0-1019 (4.18.0-1019.19) ... Setting up linux-image-azure (4.18.0.1019.20) ... Setting up linux-headers-4.18.0-1019-azure (4.18.0-1019.19) ... Setting up linux-azure-tools-4.18.0-1019 (4.18.0-1019.19) ... Setting up linux-tools-4.18.0-1019-azure (4.18.0-1019.19) ... Setting up linux-cloud-tools-4.18.0-1019-azure (4.18.0-1019.19) ... Setting up linux-tools-azure (4.18.0.1019.20) ... Setting up linux-headers-azure (4.18.0.1019.20) ... Setting up linux-cloud-tools-azure (4.18.0.1019.20) ... Setting up linux-azure (4.18.0.1019.20) ... Processing triggers for linux-image-4.18.0-1019-azure (4.18.0-1019.19) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.18.0-1019-azure cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries nor crypto modules. If that's on purpose, you may want to uninstall the 'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs integration and avoid this warning. /etc/kernel/postinst.d/zz-update-grub: Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/50-cloudimg-settings.cfg' Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.18.0-1019-azure Found initrd image: /boot/initrd.img-4.18.0-1019-azure Found linux image: /boot/vmlinuz-4.18.0-1018-azure Found initrd image: /boot/initrd.img-4.18.0-1018-azure done ** Affects: ubuntu-kernel-tests Importance: Undecided Status: Confirmed ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Affects: linux-azure (Ubuntu Cosmic) Importance: Undecided Status: New ** Tags: azure cosmic ** Also affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Cosmic) Importance: Undecided Status: New ** Tags added: azure cosmic ** Description changed: Series: Cosmic Instance: Any (Basic_A2) for this example Kernel: 4.18.0-1018-azuze + Disk Encryption: None configured Reproduce: - 1.) Install Cosmic + 1.) Install Cosmic 2.) Add Cosmic -proposed repo to sources -list 3.) sudo apt-get update && sudo apt-get install -y linux-azure - Targeted kernel is 4.18.0-1018-azure Preparing to unpack .../05-linux-headers-4.18.0-1019-azure_4.18.0-1019.19_amd64.deb ... Unpacking linux-headers-4.18.0-1019-azure (4.18.0-1019.19) ... Preparing to unpack .../06-linux-headers-azure_4.18.0.1019.20_amd64.deb ... Unpacking linux-headers-azure (4.18.0.1019.20) over (4.18.0.1018.19) ... Selecting previously unselected package linux-azure-tools-4.18.0-1019. Preparing to unpack .../07-linux-azure-tools-4.18.0-1019_4.18.0-1019.19_amd64.deb ... Unpacking linux-azure-tools-4.18.0-1019 (4.18.0-1019.19) ... Selecting previously
[Kernel-packages] [Bug 1830951] Re: kernel panic: stack corrupted in efivar_ssdt_iter+0xd3/0xe8
I recompiled the 4.18.0-20-general kernel and made the following
changes, and things start to work.
258c258,261
<
---
> if (limit < 1) {
> pr_err("efi: Invalid name size %ld/%d.\n", name_size, limit);
> return 0;
> }
Logs proving the fix worked:
[0.321692] Registered efivars operations
[0.330723] efi: efi: Invalid name size 0/0.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1830951
Title:
kernel panic: stack corrupted in efivar_ssdt_iter+0xd3/0xe8
Status in linux package in Ubuntu:
Confirmed
Bug description:
We have a few 2010 mac pro running 1604 LTS that are just upgraded to Ubuntu
1804 LTS. While they all worked fine with the 1604 LTS and 4.4 kernel, they can
no longer boot with the 4.15.0-50 kernel installed with 1804.
We tried various kernel flags without luck, and installed latest 4.18.0-20
from HWE and got the same result.
Unfortunately, no logs are created in /var/logs when the issue happens, and
we could only boot with the old 4.4 kernel. We had to enable earlyprintk=efi to
get a backtrace in a photo.
The issue happens consistently, i.e. the backtrace looks always the same just
happens on different cores.
Attached the boot-info output and the picture taken at the end of the kernel
loading.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: steventang 2047 F pulseaudio
/dev/snd/controlC0: steventang 2047 F pulseaudio
/dev/snd/controlC1: steventang 2047 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=a7ceb7f0-6040-4236-ad7d-35780a1dc870
InstallationDate: Installed on 2019-05-28 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
MachineType: Apple Inc. MacPro5,1
NonfreeKernelModules: wl
Package: linux (not installed)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic
root=UUID=8d18bfd8-303b-4397-9216-a0e48cb6ef54 ro quiet splash
ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177
RelatedPackageVersions:
linux-restricted-modules-4.4.0-148-generic N/A
linux-backports-modules-4.4.0-148-generic N/A
linux-firmware 1.173.6
Tags: bionic
Uname: Linux 4.4.0-148-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 08/08/17
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MP51.88Z.0084.B00.1708080528
dmi.board.asset.tag: 0
dmi.board.name: Mac-F221BEC8
dmi.board.vendor: Apple Inc.
dmi.chassis.type: 7
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F221BEC8
dmi.modalias:
dmi:bvnAppleInc.:bvrMP51.88Z.0084.B00.1708080528:bd08/08/17:svnAppleInc.:pnMacPro5,1:pvr0.0:rvnAppleInc.:rnMac-F221BEC8:rvr:cvnAppleInc.:ct7:cvrMac-F221BEC8:
dmi.product.name: MacPro5,1
dmi.product.version: 0.0
dmi.sys.vendor: Apple Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830951/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831103] Re: bionic: netlink: potential shift overflow in netlink_bind()
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1831103 Title: bionic: netlink: potential shift overflow in netlink_bind() Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: [Impact] The check for correctness of netlink_bind() userspace supplied parameter is done by applying a bitmask made from ngroups shift. However if we have more than 64 groups the shift results in an overflow causing an incorrect validation of the netlink_bind() parameters. This has been fixed upstream: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=91874ecf32e41b5d86a4cb9d60e0bee50d828058 And this fix has been applied to xenial, cosmic and disco (apparently only bionic is missing it). [Test Case] I've been able to reproduce this problem using a script with acpid to handle ACPI hibernate events. The script is the following: $ cat /etc/acpi/actions/sleep.sh #!/bin/sh echo "1=$1 2=$2" >> /home/ubuntu/acpi-event.log Any kernel that has the fix (xenial and cosmic for example) are logging two events (input and netlink) when the sleep button is fired: $ cat /home/ubuntu/acpi-event.log 1=button/sleep 2=SBTN 1=button/sleep 2=LNXSLPBN:00 The bionic kernel, instead, is logging only one event (input, netlink is lost): $ cat /home/ubuntu/acpi-event.log 1=button/sleep 2=SBTN [Fix] Fix that solves this problem: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=91874ecf32e41b5d86a4cb9d60e0bee50d828058 [Regression Potential] Upsteram fix, tested on the affected platform, all other kernel releases have this fix applied already, so regression potential is minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831103/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831103] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1831103 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Bionic) Status: New => Incomplete ** Tags added: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1831103 Title: bionic: netlink: potential shift overflow in netlink_bind() Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: [Impact] The check for correctness of netlink_bind() userspace supplied parameter is done by applying a bitmask made from ngroups shift. However if we have more than 64 groups the shift results in an overflow causing an incorrect validation of the netlink_bind() parameters. This has been fixed upstream: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=91874ecf32e41b5d86a4cb9d60e0bee50d828058 And this fix has been applied to xenial, cosmic and disco (apparently only bionic is missing it). [Test Case] I've been able to reproduce this problem using a script with acpid to handle ACPI hibernate events. The script is the following: $ cat /etc/acpi/actions/sleep.sh #!/bin/sh echo "1=$1 2=$2" >> /home/ubuntu/acpi-event.log Any kernel that has the fix (xenial and cosmic for example) are logging two events (input and netlink) when the sleep button is fired: $ cat /home/ubuntu/acpi-event.log 1=button/sleep 2=SBTN 1=button/sleep 2=LNXSLPBN:00 The bionic kernel, instead, is logging only one event (input, netlink is lost): $ cat /home/ubuntu/acpi-event.log 1=button/sleep 2=SBTN [Fix] Fix that solves this problem: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=91874ecf32e41b5d86a4cb9d60e0bee50d828058 [Regression Potential] Upsteram fix, tested on the affected platform, all other kernel releases have this fix applied already, so regression potential is minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831103/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831103] [NEW] bionic: netlink: potential shift overflow in netlink_bind()
Public bug reported: [Impact] The check for correctness of netlink_bind() userspace supplied parameter is done by applying a bitmask made from ngroups shift. However if we have more than 64 groups the shift results in an overflow causing an incorrect validation of the netlink_bind() parameters. This has been fixed upstream: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=91874ecf32e41b5d86a4cb9d60e0bee50d828058 And this fix has been applied to xenial, cosmic and disco (apparently only bionic is missing it). [Test Case] I've been able to reproduce this problem using a script with acpid to handle ACPI hibernate events. The script is the following: $ cat /etc/acpi/actions/sleep.sh #!/bin/sh echo "1=$1 2=$2" >> /home/ubuntu/acpi-event.log Any kernel that has the fix (xenial and cosmic for example) are logging two events (input and netlink) when the sleep button is fired: $ cat /home/ubuntu/acpi-event.log 1=button/sleep 2=SBTN 1=button/sleep 2=LNXSLPBN:00 The bionic kernel, instead, is logging only one event (input, netlink is lost): $ cat /home/ubuntu/acpi-event.log 1=button/sleep 2=SBTN [Fix] Fix that solves this problem: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=91874ecf32e41b5d86a4cb9d60e0bee50d828058 [Regression Potential] Upsteram fix, tested on the affected platform, all other kernel releases have this fix applied already, so regression potential is minimal. ** Affects: linux (Ubuntu) Importance: High Assignee: Andrea Righi (arighi) Status: New ** Affects: linux (Ubuntu Bionic) Importance: High Assignee: Andrea Righi (arighi) Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Andrea Righi (arighi) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Andrea Righi (arighi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1831103 Title: bionic: netlink: potential shift overflow in netlink_bind() Status in linux package in Ubuntu: New Status in linux source package in Bionic: New Bug description: [Impact] The check for correctness of netlink_bind() userspace supplied parameter is done by applying a bitmask made from ngroups shift. However if we have more than 64 groups the shift results in an overflow causing an incorrect validation of the netlink_bind() parameters. This has been fixed upstream: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=91874ecf32e41b5d86a4cb9d60e0bee50d828058 And this fix has been applied to xenial, cosmic and disco (apparently only bionic is missing it). [Test Case] I've been able to reproduce this problem using a script with acpid to handle ACPI hibernate events. The script is the following: $ cat /etc/acpi/actions/sleep.sh #!/bin/sh echo "1=$1 2=$2" >> /home/ubuntu/acpi-event.log Any kernel that has the fix (xenial and cosmic for example) are logging two events (input and netlink) when the sleep button is fired: $ cat /home/ubuntu/acpi-event.log 1=button/sleep 2=SBTN 1=button/sleep 2=LNXSLPBN:00 The bionic kernel, instead, is logging only one event (input, netlink is lost): $ cat /home/ubuntu/acpi-event.log 1=button/sleep 2=SBTN [Fix] Fix that solves this problem: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=91874ecf32e41b5d86a4cb9d60e0bee50d828058 [Regression Potential] Upsteram fix, tested on the affected platform, all other kernel releases have this fix applied already, so regression potential is minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831103/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827967] Re: There are 4 HDMI/Displayport audio output listed in sound setting without attach any HDMI/DP monitor
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827967 Title: There are 4 HDMI/Displayport audio output listed in sound setting without attach any HDMI/DP monitor Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: [Impact] In our OEM projects, we often meet this issues, there is no any monitor plugged, but in the gnome-sound-setting, there are 4 hdmi/dp audio devices. [Fix] We check the eld_valid when reporting the hdmi/dp jack event [Test Case] On the problematic machines, we do s3 test without plugging monitor, there is no hdmi audio device in the sound-setting. On the machines without this problem, we do s3 test, pluggin/unplugging monitor test, the hdmi audio work well as before. [Regression Risk] Low. We have done many tests on machines with or without this problem, there is no regression so far. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1827967/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830266] Re: [linux-azure] Please Include Mainline Commit ebaf39e6032f in the 16.04 and 18.04 linux-azure kernels
https://lists.ubuntu.com/archives/kernel-team/2019-May/100992.html https://lists.ubuntu.com/archives/kernel-team/2019-May/100993.html https://lists.ubuntu.com/archives/kernel-team/2019-May/100994.html -- 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/1830266 Title: [linux-azure] Please Include Mainline Commit ebaf39e6032f in the 16.04 and 18.04 linux-azure kernels Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Xenial: In Progress Status in linux-azure source package in Cosmic: In Progress Bug description: A team within Microsoft is running the linux-azure Ubuntu kernel on a large AI cluster. They are hitting an issue which is resolved by the following commit: https://github.com/torvalds/linux/commit/ebaf39e6032faf77218220707fc3fa22487784e0 The bug is that threads can get stuck in the kernel. This bug can happen when removing network namespaces. This is something docker swarm does anytime it removes a container. Commit ebaf39e6032f was added to the mainline kernel tree in v4.20-rc6. It was not cc’d to upstream stable, so only v4.20-rc6 and newer kernels will have it. A test kernel was built with this commit, which resolves the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1830266/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821934] Re: [Hyper-V] Enable CONFIG_HOTPLUG_CPU in linux-azure
I made a mistake on the disco patch and the buglink tag wasn't included. However the change is already released in disco/linux-azure so I'm marking it manually as "Fix Released". ** Changed in: linux-azure (Ubuntu Disco) Status: In Progress => Fix Released ** Changed in: linux-azure (Ubuntu Xenial) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Changed in: linux-azure (Ubuntu Cosmic) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Changed in: linux-azure (Ubuntu Disco) Assignee: (unassigned) => Marcelo Cerri (mhcerri) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1821934 Title: [Hyper-V] Enable CONFIG_HOTPLUG_CPU in linux-azure Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure source package in Disco: Fix Released Bug description: We requested that CONFIG_HOTPLUG_CPU be disabled in bug 1776293. However, due to a recently discovered security issue, CONFIG_HOTPLUG_CPU needs to be re-enabled. There are some patches on LKML to address this security issue, but they are not in the Azure kernel yet, and may not be accepted upstream in their current form. If your interested, those two patches are available here: https://lkml.org/lkml/2019/3/26/893 https://lkml.org/lkml/2019/3/26/894 https://lkml.org/lkml/2019/3/26/895 To mitigate this security issue, the nosmt option needs to be passed on the boot line. However, the nosmt option will not work if CONFIG_HOTPLUG_CPU is disabled, which is the primary reason it needs to be turned back on at this time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1821934/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826844] Re: nvidia-drivers-* are not on the ISO
Just to say we'd love to see this in 18.04.3. Today (like system76 ) we have to handle 2 iso because 18.04.2 iso will not boot on nvidia hardware. Fixing basic usage with nouveau could also be a solution, so user could at least install ubuntu. -- 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/1826844 Title: nvidia-drivers-* are not on the ISO Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in ubuntustudio-meta package in Ubuntu: New Status in nvidia-graphics-drivers-390 source package in Eoan: Fix Released Status in ubuntustudio-meta source package in Eoan: New Bug description: On Ubuntu desktop, without a network connection, the user can select to install 3rd party drivers (which states that it'll install graphics driver) but even if he selects this option, nVidia proprietary drivers won't be installed because they are not on the pool of the ISO. also tracked in the desktop trello board as card: https://trello.com/c/rPiwDpPe/130-bug1826844-nvidia-drivers-are-not-on-the-iso Adding both ubuntu-driver-390 and ubuntu-driver-418 to the pool, adds 114MB to the ISO. Here is the list of packages that will be added to the pool: libnvidia-cfg1-390 libnvidia-cfg1-418 libnvidia-common-390 libnvidia-common-418 libnvidia-compute-390 libnvidia-compute-418 libnvidia-decode-390 libnvidia-decode-418 libnvidia-encode-390 libnvidia-encode-418 libnvidia-fbc1-390 libnvidia-fbc1-418 libnvidia-gl-390 libnvidia-gl-418 libnvidia-ifr1-390 libnvidia-ifr1-418 libvdpau1 libxnvctrl0 mesa-vdpau-drivers nvidia-compute-utils-390 nvidia-compute-utils-418 nvidia-dkms-390 nvidia-dkms-418 nvidia-driver-390 nvidia-driver-410 nvidia-driver-418 nvidia-kernel-common-390 nvidia-kernel-common-418 nvidia-kernel-source-390 nvidia-kernel-source-418 nvidia-prime nvidia-settings nvidia-utils-390 nvidia-utils-418 vdpau-driver-all xserver-xorg-video-nvidia-390 xserver-xorg-video-nvidia-418 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nvidia-driver-390 (not installed) ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 10:22:44 2019 InstallationDate: Installed on 2014-07-15 (1749 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: Upgraded to eoan on 2018-03-24 (400 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1826844/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823753] Re: arm64: cma_alloc errors at boot
Note: We have tested https://lkml.org/lkml/2019/5/6/1221, which is now on linux-next *, and the hi162 RoCE driver single patch usage is diminished: $cat cma.disco.dmesg | grep "cma: cma_alloc(cma" | sed -r 's/.*count ([0-9]+)\,.*/\1/' | sort -n | uniq -c 129 2 3 4 206 8 32 16 2 24 4 32 256 33 39 64 2 128 2 1024 I think that we had ~11K x 1K CMA pages previously, without this patchset. * https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/log/kernel/dma?h=next-20190530 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823753 Title: arm64: cma_alloc errors at boot Status in linux package in Ubuntu: Confirmed Bug description: On some arm64 systems[*] we are seeing a spew of messages on the console: [ 19.534097] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534109] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534113] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534126] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534130] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534142] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534146] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534157] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534161] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534173] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534177] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 This appears to be non-fatal - impacted systems all eventually boot. But, at least in the case of the HP m400, it slows down boot enough that MAAS' default timeout will expire before completing deployment. [*] Observed on a HiSilicon D06 w/ SMMU disabled in the BIOS, as well as an HP m400 (APM X-Gene) cartridge - although, not on another one that - in theory - should be identical. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823753/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830266] Re: [linux-azure] Please Include Mainline Commit ebaf39e6032f in the 16.04 and 18.04 linux-azure kernels
** Also affects: linux-azure (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Xenial) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Changed in: linux-azure (Ubuntu Cosmic) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Changed in: linux-azure (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Cosmic) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1830266 Title: [linux-azure] Please Include Mainline Commit ebaf39e6032f in the 16.04 and 18.04 linux-azure kernels Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Xenial: In Progress Status in linux-azure source package in Cosmic: In Progress Bug description: A team within Microsoft is running the linux-azure Ubuntu kernel on a large AI cluster. They are hitting an issue which is resolved by the following commit: https://github.com/torvalds/linux/commit/ebaf39e6032faf77218220707fc3fa22487784e0 The bug is that threads can get stuck in the kernel. This bug can happen when removing network namespaces. This is something docker swarm does anytime it removes a container. Commit ebaf39e6032f was added to the mainline kernel tree in v4.20-rc6. It was not cc’d to upstream stable, so only v4.20-rc6 and newer kernels will have it. A test kernel was built with this commit, which resolves the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1830266/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1822133] Re: Azure Instance never recovered during series of instance reboots.
On 5/29/19 6:58 PM, Sean Feole wrote: > I revisited this particular problem today. I ran a series of restart > tests across westus2 and westus, utilizing the same instance and > series, but with the latest kernel in -proposed. I was unable to > reproduce this problem as originally reported in the bug. I also have > not seen any of our SRU testing stall due to problems of this nature, > where the instance fails to respond after a restart. > > I think it's safe to say we can close this bug and mark it resolved for > the time being. > Sean, we plan to do this in today's call. Terry -- 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/1822133 Title: Azure Instance never recovered during series of instance reboots. Status in linux-azure package in Ubuntu: In Progress Bug description: Description: During SRU Testing of various Azure Instances, there will be some cases where the instance will not respond following a system reboot. SRU Testing only restarts a giving instance once, after it preps all of the necessary files to-be-tested. Series: Disco Instance Size: Basic_A3 Region: (Default) US-WEST-2 Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I initiated a series of tests which rebooted Azure Cloud instances 50 times. During the 49th Reboot, an Instance failed to return from a reboot.. Upon grabbing the console output the following was seen scrolling endlessly. I have seen this failure in cases where the instance only restarted a handful of times >5 [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus In another test attempt I saw the following failure: ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes Both of these failures broke networking, Both of these failures were seen at least twice to three times, thus may explain why in some cases we never recover from an instance reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1822133/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772412] Re: zfs 0.7.9 fixes a bug (https://github.com/zfsonlinux/zfs/pull/7343) that hangs the system completely
Fix sent to kernel team mailing list for review:
https://lists.ubuntu.com/archives/kernel-team/2019-May/100990.html
** Description changed:
SRU Bionic
== SRU Justification ==
Intensive I/O such as performed by ZFS send/receive can cause hangs because
of monopolization of the global system_taskq. The outcome is that z_zvol hung
tasks occur and I/O gets blocked.
== Fix ==
Upstream ZFS commit 77d8a0f1a4d0b2f59cee63088f7987cb38e66538 ("Fix hung
- z_zvol tasks during 'zfs receive'" fixes this issue, it adds a dedicated
- per-pool prefetch taskq that prevents the traverse code from
+ z_zvol tasks during 'zfs receive'") fixes this issue, it adds a
+ dedicated per-pool prefetch taskq that prevents the traverse code from
monopolizing the global (and limited) system_taskq by inappropriately
scheduling long running tasks on it. This fixes the z_zvol hung tasks. A
trivial backport is required for Bionic ZFS.
== Testcase ==
Perform large send/receives. Occasionally they lock up. With the fix,
this issue is addressed and no more lockups occur. Also must pass the
full ZFS ubuntu autotest tests to prove no regressions occur.
== Regression Potential ==
This fix adds more per-pool prefetch taskq's so we have more kernel
resources being used. There is therefore a very small risk that this may
impact ZFS running on memory and CPU constrained systems. However, the
fix is small, has been upstream for a while and is in Cosmic+ releases
and has not caused any regressions, so I think this is a relatively safe
fix.
--
I have experienced the problems fixed by this commit
https://github.com/zfsonlinux/zfs/pull/7343 a few times on my NAS. The
system hangs completely when it occurs. It looks like 0.7.9 brings other
interesting bug fixes that potentially freeze the system.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1772412
Title:
zfs 0.7.9 fixes a bug (https://github.com/zfsonlinux/zfs/pull/7343)
that hangs the system completely
Status in zfs-linux package in Ubuntu:
In Progress
Bug description:
SRU Bionic
== SRU Justification ==
Intensive I/O such as performed by ZFS send/receive can cause hangs because
of monopolization of the global system_taskq. The outcome is that z_zvol hung
tasks occur and I/O gets blocked.
== Fix ==
Upstream ZFS commit 77d8a0f1a4d0b2f59cee63088f7987cb38e66538 ("Fix
hung z_zvol tasks during 'zfs receive'") fixes this issue, it adds a
dedicated per-pool prefetch taskq that prevents the traverse code from
monopolizing the global (and limited) system_taskq by inappropriately
scheduling long running tasks on it. This fixes the z_zvol hung tasks.
A trivial backport is required for Bionic ZFS.
== Testcase ==
Perform large send/receives. Occasionally they lock up. With the fix,
this issue is addressed and no more lockups occur. Also must pass the
full ZFS ubuntu autotest tests to prove no regressions occur.
== Regression Potential ==
This fix adds more per-pool prefetch taskq's so we have more kernel
resources being used. There is therefore a very small risk that this
may impact ZFS running on memory and CPU constrained systems.
However, the fix is small, has been upstream for a while and is in
Cosmic+ releases and has not caused any regressions, so I think this
is a relatively safe fix.
--
I have experienced the problems fixed by this commit
https://github.com/zfsonlinux/zfs/pull/7343 a few times on my NAS. The
system hangs completely when it occurs. It looks like 0.7.9 brings
other interesting bug fixes that potentially freeze the system.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1772412/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830792] Re: [i915] Rotated display is overscaled and overdrawn
It seems unlikely to be a cable or signal problem since I can eventually coax it into working, and it continues working until I reboot. If it were a cable problem or something about the signal I would have to physically modify the connection to create and/or correct the problem. Since the mere act of rebooting creates the problem it is much more likely to be a kernel or driver bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830792 Title: [i915] Rotated display is overscaled and overdrawn Status in gnome-shell package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: On my system I have two display: one in landscape, and one in portrait. The landscape display is fine, but the portrait display is corrupted. If I unplug the display from the computer for some time and then plug it back in it will occasionally fix the problem. Once the problem is fixed, the display works perfectly fine, indefinitely. However, as soon as I reboot the computer the display will come up corrupted again and never recovers without many rounds of plug/unplug turn off/turn on. It's extremely frustrating. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 28 15:57:02 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-04-22 (36 days ago) modified.conffile..etc.logrotate.d.apport: [modified] mtime.conffile..etc.logrotate.d.apport: 2019-01-12T15:50:59.090583 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772412] Re: zfs 0.7.9 fixes a bug (https://github.com/zfsonlinux/zfs/pull/7343) that hangs the system completely
** Description changed:
+ SRU Bionic
+
+ == SRU Justification ==
+
+ Intensive I/O such as performed by ZFS send/receive can cause hangs because
of monopolization of the global system_taskq. The outcome is that z_zvol hung
+ tasks occur and I/O gets blocked.
+
+ == Fix ==
+
+ Upstream ZFS commit 77d8a0f1a4d0b2f59cee63088f7987cb38e66538 ("Fix hung
+ z_zvol tasks during 'zfs receive'" fixes this issue, it adds a dedicated
+ per-pool prefetch taskq that prevents the traverse code from
+ monopolizing the global (and limited) system_taskq by inappropriately
+ scheduling long running tasks on it. This fixes the z_zvol hung tasks. A
+ trivial backport is required for Bionic ZFS.
+
+ == Testcase ==
+
+ Perform large send/receives. Occasionally they lock up. With the fix,
+ this issue is addressed and no more lockups occur. Also must pass the
+ full ZFS ubuntu autotest tests to prove no regressions occur.
+
+ == Regression Potential ==
+
+ This fix adds more per-pool prefetch taskq's so we have more kernel
+ resources being used. There is therefore a very small risk that this may
+ impact ZFS running on memory and CPU constrained systems. However, the
+ fix is small, has been upstream for a while and is in Cosmic+ releases
+ and has not caused any regressions, so I think this is a relatively safe
+ fix.
+
+ --
+
I have experienced the problems fixed by this commit
https://github.com/zfsonlinux/zfs/pull/7343 a few times on my NAS. The
system hangs completely when it occurs. It looks like 0.7.9 brings other
interesting bug fixes that potentially freeze the system.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1772412
Title:
zfs 0.7.9 fixes a bug (https://github.com/zfsonlinux/zfs/pull/7343)
that hangs the system completely
Status in zfs-linux package in Ubuntu:
In Progress
Bug description:
SRU Bionic
== SRU Justification ==
Intensive I/O such as performed by ZFS send/receive can cause hangs because
of monopolization of the global system_taskq. The outcome is that z_zvol hung
tasks occur and I/O gets blocked.
== Fix ==
Upstream ZFS commit 77d8a0f1a4d0b2f59cee63088f7987cb38e66538 ("Fix
hung z_zvol tasks during 'zfs receive'" fixes this issue, it adds a
dedicated per-pool prefetch taskq that prevents the traverse code from
monopolizing the global (and limited) system_taskq by inappropriately
scheduling long running tasks on it. This fixes the z_zvol hung tasks.
A trivial backport is required for Bionic ZFS.
== Testcase ==
Perform large send/receives. Occasionally they lock up. With the fix,
this issue is addressed and no more lockups occur. Also must pass the
full ZFS ubuntu autotest tests to prove no regressions occur.
== Regression Potential ==
This fix adds more per-pool prefetch taskq's so we have more kernel
resources being used. There is therefore a very small risk that this
may impact ZFS running on memory and CPU constrained systems.
However, the fix is small, has been upstream for a while and is in
Cosmic+ releases and has not caused any regressions, so I think this
is a relatively safe fix.
--
I have experienced the problems fixed by this commit
https://github.com/zfsonlinux/zfs/pull/7343 a few times on my NAS. The
system hangs completely when it occurs. It looks like 0.7.9 brings
other interesting bug fixes that potentially freeze the system.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1772412/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831074] [NEW] In high fidelity playback, front right side of headset doesn't work
Public bug reported: If i connect my jbl tune 160BT headset,then on high fidelity playback configuration right side of headset doesn't produce any sound. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 29 18:10:40 2019 InstallationDate: Installed on 2019-05-28 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 1bcf:2b8a Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5577 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=84cfd91b-b197-4dea-8ed6-fe6f7cf2aade ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0MVD5F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd08/16/2018:svnDellInc.:pnInspiron5577:pvr1.1.1:rvnDellInc.:rn0MVD5F:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 5577 dmi.product.sku: 07E1 dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. hciconfig: hci0: Type: Primary Bus: USB BD Address: AC:ED:5C:49:18:75 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING RX bytes:1391391 acl:103 sco:26301 events:5764 errors:0 TX bytes:4356927 acl:4943 sco:26284 commands:703 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1831074 Title: In high fidelity playback, front right side of headset doesn't work Status in bluez package in Ubuntu: New Bug description: If i connect my jbl tune 160BT headset,then on high fidelity playback configuration right side of headset doesn't produce any sound. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 29 18:10:40 2019 InstallationDate: Installed on 2019-05-28 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 1bcf:2b8a Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5577 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=84cfd91b-b197-4dea-8ed6-fe6f7cf2aade ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0MVD5F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd08/16/2018:svnDellInc.:pnInspiron5577:pvr1.1.1:rvnDellInc.:rn0MVD5F:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 5577 dmi.product.sku: 07E1 dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: AC:ED:5C:49:18:75 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING RX bytes:1391391 acl:103 sco:26301 events:5764 errors:0 TX bytes:4356927 acl:4943 sco:26284 commands:703 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1831074/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1811723] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1811723/+attachment/5267683/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811723 Title: Samba client freeze during write when using higher than vers=1.0 Status in linux package in Ubuntu: Confirmed Bug description: Hello, My issue is that whenever I try to write new files (copy or move) to my file server something in the samba client freezes and I can't do anything samba until the system is rebooted. To get write access I mount with uid ie "sudo mount //server/share /mountpoint -o user=write,uid=1000". Using this command the server and client negotiates smb protocol version 3.02. When this happens the server is still happily serving files to other machines. If I just read files everything works fine. If I connect from a windows client there is no issue. If I add "vers=1.0" everything works but transfers are really slow. Specifying version 3 produces a fail. Trying the same operation (different hw) with Mint 18 Mate produces the same fault. Trying the same operation (with "vers=3.0" set) using SuSE Leap 15.0 KDE live everything works as expected. Both client and server are running fully updated, as of posting, bionic. Using 'dmesg -w' too see what's going on I can see that there is a general protection fault somehow related to cifsd. I am however unable to tell if it is relevant to my issue, from kern.log: Jan 9 21:03:49 ubnu kernel: [ 410.357213] general protection fault: [#1] SMP PTI Jan 9 21:03:49 ubnu kernel: [ 410.357224] Modules linked in: cmac arc4 md4 nls_utf8 cifs ccm fscache rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) thunderbolt bnep binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_hda_codec_realtek snd_soc_acpi snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel intel_rapl btusb x86_pkg_temp_thermal intel_powerclamp btrtl coretemp joydev btbcm snd_hda_codec kvm_intel input_leds kvm irqbypass btintel crct10dif_pclmul crc32_pclmul snd_hda_core ghash_clmulni_intel pcbc snd_hwdep snd_pcm bluetooth ecdh_generic snd_seq_midi snd_seq_midi_event aesni_intel snd_rawmidi aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf snd_seq rtsx_pci_ms snd_seq_device Jan 9 21:03:49 ubnu kernel: [ 410.357357] wmi_bmof snd_timer memstick intel_wmi_thunderbolt snd shpchp soundcore mei_me mei intel_pch_thermal acpi_pad mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 xfs libcrc32c hid_generic usbhid hid rtsx_pci_sdmmc i915 e1000e i2c_algo_bit drm_kms_helper ptp syscopyarea pps_core i2c_i801 sysfillrect sysimgblt rtsx_pci fb_sys_fops drm ahci libahci wmi video Jan 9 21:03:49 ubnu kernel: [ 410.357447] CPU: 2 PID: 1822 Comm: cifsd Tainted: G OE4.15.0-43-generic #46-Ubuntu Jan 9 21:03:49 ubnu kernel: [ 410.357453] Hardware name: /NUC7i3BNB, BIOS BNKBL357.86A.0069.2018.0920.1250 09/20/2018 Jan 9 21:03:49 ubnu kernel: [ 410.357468] RIP: 0010:prefetch_freepointer+0x15/0x30 Jan 9 21:03:49 ubnu kernel: [ 410.357474] RSP: 0018:b16201ae3da0 EFLAGS: 00010282 Jan 9 21:03:49 ubnu kernel: [ 410.357482] RAX: RBX: e90527c744fff71a RCX: 3ea9 Jan 9 21:03:49 ubnu kernel: [ 410.357488] RDX: 3ea8 RSI: e90527c744fff71a RDI: 9d7079255080 Jan 9 21:03:49 ubnu kernel: [ 410.357494] RBP: b16201ae3da0 R08: 9d707ed2b650 R09: b16201ae3db0 Jan 9 21:03:49 ubnu kernel: [ 410.357499] R10: b16201ae3de8 R11: R12: 01011200 Jan 9 21:03:49 ubnu kernel: [ 410.357505] R13: 9d7079255080 R14: 9d7016478c40 R15: 9d7079255080 Jan 9 21:03:49 ubnu kernel: [ 410.357512] FS: () GS:9d707ed0() knlGS: Jan 9 21:03:49 ubnu kernel: [ 410.357519] CS: 0010 DS: ES: CR0: 80050033 Jan 9 21:03:49 ubnu kernel: [ 410.357525] CR2: 7f0a2802d028 CR3: 3760a006 CR4: 003606e0 Jan 9 21:03:49 ubnu kernel: [ 410.357530] Call Trace: Jan 9 21:03:49 ubnu kernel: [ 410.357545] kmem_cache_alloc+0xa2/0x1b0 Jan 9 21:03:49 ubnu kernel: [ 410.357558] ? mempool_alloc_slab+0x15/0x20 Jan 9 21:03:49 ubnu kernel: [ 410.357570] ? wait_woken+0x80/0x80 Jan 9 21:03:49 ubnu kernel: [ 410.357580] mempool_alloc_slab+0x15/0x20 Jan 9 21:03:49 ubnu kernel: [ 410.357590] mempool_alloc+0x71/0x190 Jan 9 21:03:49 ubnu kernel: [ 410.357660] ? smb2_add_credits+0xb0/0x250 [cifs] Jan 9 21:03:49 ubnu kernel: [ 410.357709] cifs_small_buf_get+0x1a/0x30 [cifs] Jan 9 21:03:49 ubnu kernel: [ 410.357751]
[Kernel-packages] [Bug 1830792] Re: [i915] Rotated display is overscaled and overdrawn
** Attachment added: "output of xrandr > xrandr.txt (on Wayland)" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5267692/+files/xrandr.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830792 Title: [i915] Rotated display is overscaled and overdrawn Status in gnome-shell package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: On my system I have two display: one in landscape, and one in portrait. The landscape display is fine, but the portrait display is corrupted. If I unplug the display from the computer for some time and then plug it back in it will occasionally fix the problem. Once the problem is fixed, the display works perfectly fine, indefinitely. However, as soon as I reboot the computer the display will come up corrupted again and never recovers without many rounds of plug/unplug turn off/turn on. It's extremely frustrating. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 28 15:57:02 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-04-22 (36 days ago) modified.conffile..etc.logrotate.d.apport: [modified] mtime.conffile..etc.logrotate.d.apport: 2019-01-12T15:50:59.090583 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811723] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1811723/+attachment/5267681/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811723 Title: Samba client freeze during write when using higher than vers=1.0 Status in linux package in Ubuntu: Confirmed Bug description: Hello, My issue is that whenever I try to write new files (copy or move) to my file server something in the samba client freezes and I can't do anything samba until the system is rebooted. To get write access I mount with uid ie "sudo mount //server/share /mountpoint -o user=write,uid=1000". Using this command the server and client negotiates smb protocol version 3.02. When this happens the server is still happily serving files to other machines. If I just read files everything works fine. If I connect from a windows client there is no issue. If I add "vers=1.0" everything works but transfers are really slow. Specifying version 3 produces a fail. Trying the same operation (different hw) with Mint 18 Mate produces the same fault. Trying the same operation (with "vers=3.0" set) using SuSE Leap 15.0 KDE live everything works as expected. Both client and server are running fully updated, as of posting, bionic. Using 'dmesg -w' too see what's going on I can see that there is a general protection fault somehow related to cifsd. I am however unable to tell if it is relevant to my issue, from kern.log: Jan 9 21:03:49 ubnu kernel: [ 410.357213] general protection fault: [#1] SMP PTI Jan 9 21:03:49 ubnu kernel: [ 410.357224] Modules linked in: cmac arc4 md4 nls_utf8 cifs ccm fscache rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) thunderbolt bnep binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_hda_codec_realtek snd_soc_acpi snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel intel_rapl btusb x86_pkg_temp_thermal intel_powerclamp btrtl coretemp joydev btbcm snd_hda_codec kvm_intel input_leds kvm irqbypass btintel crct10dif_pclmul crc32_pclmul snd_hda_core ghash_clmulni_intel pcbc snd_hwdep snd_pcm bluetooth ecdh_generic snd_seq_midi snd_seq_midi_event aesni_intel snd_rawmidi aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf snd_seq rtsx_pci_ms snd_seq_device Jan 9 21:03:49 ubnu kernel: [ 410.357357] wmi_bmof snd_timer memstick intel_wmi_thunderbolt snd shpchp soundcore mei_me mei intel_pch_thermal acpi_pad mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 xfs libcrc32c hid_generic usbhid hid rtsx_pci_sdmmc i915 e1000e i2c_algo_bit drm_kms_helper ptp syscopyarea pps_core i2c_i801 sysfillrect sysimgblt rtsx_pci fb_sys_fops drm ahci libahci wmi video Jan 9 21:03:49 ubnu kernel: [ 410.357447] CPU: 2 PID: 1822 Comm: cifsd Tainted: G OE4.15.0-43-generic #46-Ubuntu Jan 9 21:03:49 ubnu kernel: [ 410.357453] Hardware name: /NUC7i3BNB, BIOS BNKBL357.86A.0069.2018.0920.1250 09/20/2018 Jan 9 21:03:49 ubnu kernel: [ 410.357468] RIP: 0010:prefetch_freepointer+0x15/0x30 Jan 9 21:03:49 ubnu kernel: [ 410.357474] RSP: 0018:b16201ae3da0 EFLAGS: 00010282 Jan 9 21:03:49 ubnu kernel: [ 410.357482] RAX: RBX: e90527c744fff71a RCX: 3ea9 Jan 9 21:03:49 ubnu kernel: [ 410.357488] RDX: 3ea8 RSI: e90527c744fff71a RDI: 9d7079255080 Jan 9 21:03:49 ubnu kernel: [ 410.357494] RBP: b16201ae3da0 R08: 9d707ed2b650 R09: b16201ae3db0 Jan 9 21:03:49 ubnu kernel: [ 410.357499] R10: b16201ae3de8 R11: R12: 01011200 Jan 9 21:03:49 ubnu kernel: [ 410.357505] R13: 9d7079255080 R14: 9d7016478c40 R15: 9d7079255080 Jan 9 21:03:49 ubnu kernel: [ 410.357512] FS: () GS:9d707ed0() knlGS: Jan 9 21:03:49 ubnu kernel: [ 410.357519] CS: 0010 DS: ES: CR0: 80050033 Jan 9 21:03:49 ubnu kernel: [ 410.357525] CR2: 7f0a2802d028 CR3: 3760a006 CR4: 003606e0 Jan 9 21:03:49 ubnu kernel: [ 410.357530] Call Trace: Jan 9 21:03:49 ubnu kernel: [ 410.357545] kmem_cache_alloc+0xa2/0x1b0 Jan 9 21:03:49 ubnu kernel: [ 410.357558] ? mempool_alloc_slab+0x15/0x20 Jan 9 21:03:49 ubnu kernel: [ 410.357570] ? wait_woken+0x80/0x80 Jan 9 21:03:49 ubnu kernel: [ 410.357580] mempool_alloc_slab+0x15/0x20 Jan 9 21:03:49 ubnu kernel: [ 410.357590] mempool_alloc+0x71/0x190 Jan 9 21:03:49 ubnu kernel: [ 410.357660] ? smb2_add_credits+0xb0/0x250 [cifs] Jan 9 21:03:49 ubnu kernel: [ 410.357709] cifs_small_buf_get+0x1a/0x30 [cifs] Jan 9 21:03:49 ubnu kernel: [ 410.357751] cifs_demultiplex_thread+0x5c7/0xaf0
[Kernel-packages] [Bug 1811723] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1811723/+attachment/5267686/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811723 Title: Samba client freeze during write when using higher than vers=1.0 Status in linux package in Ubuntu: Confirmed Bug description: Hello, My issue is that whenever I try to write new files (copy or move) to my file server something in the samba client freezes and I can't do anything samba until the system is rebooted. To get write access I mount with uid ie "sudo mount //server/share /mountpoint -o user=write,uid=1000". Using this command the server and client negotiates smb protocol version 3.02. When this happens the server is still happily serving files to other machines. If I just read files everything works fine. If I connect from a windows client there is no issue. If I add "vers=1.0" everything works but transfers are really slow. Specifying version 3 produces a fail. Trying the same operation (different hw) with Mint 18 Mate produces the same fault. Trying the same operation (with "vers=3.0" set) using SuSE Leap 15.0 KDE live everything works as expected. Both client and server are running fully updated, as of posting, bionic. Using 'dmesg -w' too see what's going on I can see that there is a general protection fault somehow related to cifsd. I am however unable to tell if it is relevant to my issue, from kern.log: Jan 9 21:03:49 ubnu kernel: [ 410.357213] general protection fault: [#1] SMP PTI Jan 9 21:03:49 ubnu kernel: [ 410.357224] Modules linked in: cmac arc4 md4 nls_utf8 cifs ccm fscache rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) thunderbolt bnep binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_hda_codec_realtek snd_soc_acpi snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel intel_rapl btusb x86_pkg_temp_thermal intel_powerclamp btrtl coretemp joydev btbcm snd_hda_codec kvm_intel input_leds kvm irqbypass btintel crct10dif_pclmul crc32_pclmul snd_hda_core ghash_clmulni_intel pcbc snd_hwdep snd_pcm bluetooth ecdh_generic snd_seq_midi snd_seq_midi_event aesni_intel snd_rawmidi aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf snd_seq rtsx_pci_ms snd_seq_device Jan 9 21:03:49 ubnu kernel: [ 410.357357] wmi_bmof snd_timer memstick intel_wmi_thunderbolt snd shpchp soundcore mei_me mei intel_pch_thermal acpi_pad mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 xfs libcrc32c hid_generic usbhid hid rtsx_pci_sdmmc i915 e1000e i2c_algo_bit drm_kms_helper ptp syscopyarea pps_core i2c_i801 sysfillrect sysimgblt rtsx_pci fb_sys_fops drm ahci libahci wmi video Jan 9 21:03:49 ubnu kernel: [ 410.357447] CPU: 2 PID: 1822 Comm: cifsd Tainted: G OE4.15.0-43-generic #46-Ubuntu Jan 9 21:03:49 ubnu kernel: [ 410.357453] Hardware name: /NUC7i3BNB, BIOS BNKBL357.86A.0069.2018.0920.1250 09/20/2018 Jan 9 21:03:49 ubnu kernel: [ 410.357468] RIP: 0010:prefetch_freepointer+0x15/0x30 Jan 9 21:03:49 ubnu kernel: [ 410.357474] RSP: 0018:b16201ae3da0 EFLAGS: 00010282 Jan 9 21:03:49 ubnu kernel: [ 410.357482] RAX: RBX: e90527c744fff71a RCX: 3ea9 Jan 9 21:03:49 ubnu kernel: [ 410.357488] RDX: 3ea8 RSI: e90527c744fff71a RDI: 9d7079255080 Jan 9 21:03:49 ubnu kernel: [ 410.357494] RBP: b16201ae3da0 R08: 9d707ed2b650 R09: b16201ae3db0 Jan 9 21:03:49 ubnu kernel: [ 410.357499] R10: b16201ae3de8 R11: R12: 01011200 Jan 9 21:03:49 ubnu kernel: [ 410.357505] R13: 9d7079255080 R14: 9d7016478c40 R15: 9d7079255080 Jan 9 21:03:49 ubnu kernel: [ 410.357512] FS: () GS:9d707ed0() knlGS: Jan 9 21:03:49 ubnu kernel: [ 410.357519] CS: 0010 DS: ES: CR0: 80050033 Jan 9 21:03:49 ubnu kernel: [ 410.357525] CR2: 7f0a2802d028 CR3: 3760a006 CR4: 003606e0 Jan 9 21:03:49 ubnu kernel: [ 410.357530] Call Trace: Jan 9 21:03:49 ubnu kernel: [ 410.357545] kmem_cache_alloc+0xa2/0x1b0 Jan 9 21:03:49 ubnu kernel: [ 410.357558] ? mempool_alloc_slab+0x15/0x20 Jan 9 21:03:49 ubnu kernel: [ 410.357570] ? wait_woken+0x80/0x80 Jan 9 21:03:49 ubnu kernel: [ 410.357580] mempool_alloc_slab+0x15/0x20 Jan 9 21:03:49 ubnu kernel: [ 410.357590] mempool_alloc+0x71/0x190 Jan 9 21:03:49 ubnu kernel: [ 410.357660] ? smb2_add_credits+0xb0/0x250 [cifs] Jan 9 21:03:49 ubnu kernel: [ 410.357709] cifs_small_buf_get+0x1a/0x30 [cifs] Jan 9 21:03:49 ubnu kernel: [ 410.357751]
[Kernel-packages] [Bug 1830792] Re: [i915] Rotated display is overscaled and overdrawn
I tried that and it didn't fix the problem. I am attaching the output of some of those files again for further data. ** Attachment added: "dmesg output ( on Wayland)" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5267690/+files/dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830792 Title: [i915] Rotated display is overscaled and overdrawn Status in gnome-shell package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: On my system I have two display: one in landscape, and one in portrait. The landscape display is fine, but the portrait display is corrupted. If I unplug the display from the computer for some time and then plug it back in it will occasionally fix the problem. Once the problem is fixed, the display works perfectly fine, indefinitely. However, as soon as I reboot the computer the display will come up corrupted again and never recovers without many rounds of plug/unplug turn off/turn on. It's extremely frustrating. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 28 15:57:02 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-04-22 (36 days ago) modified.conffile..etc.logrotate.d.apport: [modified] mtime.conffile..etc.logrotate.d.apport: 2019-01-12T15:50:59.090583 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811723] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1811723/+attachment/5267685/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811723 Title: Samba client freeze during write when using higher than vers=1.0 Status in linux package in Ubuntu: Confirmed Bug description: Hello, My issue is that whenever I try to write new files (copy or move) to my file server something in the samba client freezes and I can't do anything samba until the system is rebooted. To get write access I mount with uid ie "sudo mount //server/share /mountpoint -o user=write,uid=1000". Using this command the server and client negotiates smb protocol version 3.02. When this happens the server is still happily serving files to other machines. If I just read files everything works fine. If I connect from a windows client there is no issue. If I add "vers=1.0" everything works but transfers are really slow. Specifying version 3 produces a fail. Trying the same operation (different hw) with Mint 18 Mate produces the same fault. Trying the same operation (with "vers=3.0" set) using SuSE Leap 15.0 KDE live everything works as expected. Both client and server are running fully updated, as of posting, bionic. Using 'dmesg -w' too see what's going on I can see that there is a general protection fault somehow related to cifsd. I am however unable to tell if it is relevant to my issue, from kern.log: Jan 9 21:03:49 ubnu kernel: [ 410.357213] general protection fault: [#1] SMP PTI Jan 9 21:03:49 ubnu kernel: [ 410.357224] Modules linked in: cmac arc4 md4 nls_utf8 cifs ccm fscache rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) thunderbolt bnep binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_hda_codec_realtek snd_soc_acpi snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel intel_rapl btusb x86_pkg_temp_thermal intel_powerclamp btrtl coretemp joydev btbcm snd_hda_codec kvm_intel input_leds kvm irqbypass btintel crct10dif_pclmul crc32_pclmul snd_hda_core ghash_clmulni_intel pcbc snd_hwdep snd_pcm bluetooth ecdh_generic snd_seq_midi snd_seq_midi_event aesni_intel snd_rawmidi aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf snd_seq rtsx_pci_ms snd_seq_device Jan 9 21:03:49 ubnu kernel: [ 410.357357] wmi_bmof snd_timer memstick intel_wmi_thunderbolt snd shpchp soundcore mei_me mei intel_pch_thermal acpi_pad mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 xfs libcrc32c hid_generic usbhid hid rtsx_pci_sdmmc i915 e1000e i2c_algo_bit drm_kms_helper ptp syscopyarea pps_core i2c_i801 sysfillrect sysimgblt rtsx_pci fb_sys_fops drm ahci libahci wmi video Jan 9 21:03:49 ubnu kernel: [ 410.357447] CPU: 2 PID: 1822 Comm: cifsd Tainted: G OE4.15.0-43-generic #46-Ubuntu Jan 9 21:03:49 ubnu kernel: [ 410.357453] Hardware name: /NUC7i3BNB, BIOS BNKBL357.86A.0069.2018.0920.1250 09/20/2018 Jan 9 21:03:49 ubnu kernel: [ 410.357468] RIP: 0010:prefetch_freepointer+0x15/0x30 Jan 9 21:03:49 ubnu kernel: [ 410.357474] RSP: 0018:b16201ae3da0 EFLAGS: 00010282 Jan 9 21:03:49 ubnu kernel: [ 410.357482] RAX: RBX: e90527c744fff71a RCX: 3ea9 Jan 9 21:03:49 ubnu kernel: [ 410.357488] RDX: 3ea8 RSI: e90527c744fff71a RDI: 9d7079255080 Jan 9 21:03:49 ubnu kernel: [ 410.357494] RBP: b16201ae3da0 R08: 9d707ed2b650 R09: b16201ae3db0 Jan 9 21:03:49 ubnu kernel: [ 410.357499] R10: b16201ae3de8 R11: R12: 01011200 Jan 9 21:03:49 ubnu kernel: [ 410.357505] R13: 9d7079255080 R14: 9d7016478c40 R15: 9d7079255080 Jan 9 21:03:49 ubnu kernel: [ 410.357512] FS: () GS:9d707ed0() knlGS: Jan 9 21:03:49 ubnu kernel: [ 410.357519] CS: 0010 DS: ES: CR0: 80050033 Jan 9 21:03:49 ubnu kernel: [ 410.357525] CR2: 7f0a2802d028 CR3: 3760a006 CR4: 003606e0 Jan 9 21:03:49 ubnu kernel: [ 410.357530] Call Trace: Jan 9 21:03:49 ubnu kernel: [ 410.357545] kmem_cache_alloc+0xa2/0x1b0 Jan 9 21:03:49 ubnu kernel: [ 410.357558] ? mempool_alloc_slab+0x15/0x20 Jan 9 21:03:49 ubnu kernel: [ 410.357570] ? wait_woken+0x80/0x80 Jan 9 21:03:49 ubnu kernel: [ 410.357580] mempool_alloc_slab+0x15/0x20 Jan 9 21:03:49 ubnu kernel: [ 410.357590] mempool_alloc+0x71/0x190 Jan 9 21:03:49 ubnu kernel: [ 410.357660] ? smb2_add_credits+0xb0/0x250 [cifs] Jan 9 21:03:49 ubnu kernel: [ 410.357709] cifs_small_buf_get+0x1a/0x30 [cifs] Jan 9 21:03:49 ubnu kernel: [ 410.357751]
[Kernel-packages] [Bug 1811723] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1811723/+attachment/5267680/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811723 Title: Samba client freeze during write when using higher than vers=1.0 Status in linux package in Ubuntu: Confirmed Bug description: Hello, My issue is that whenever I try to write new files (copy or move) to my file server something in the samba client freezes and I can't do anything samba until the system is rebooted. To get write access I mount with uid ie "sudo mount //server/share /mountpoint -o user=write,uid=1000". Using this command the server and client negotiates smb protocol version 3.02. When this happens the server is still happily serving files to other machines. If I just read files everything works fine. If I connect from a windows client there is no issue. If I add "vers=1.0" everything works but transfers are really slow. Specifying version 3 produces a fail. Trying the same operation (different hw) with Mint 18 Mate produces the same fault. Trying the same operation (with "vers=3.0" set) using SuSE Leap 15.0 KDE live everything works as expected. Both client and server are running fully updated, as of posting, bionic. Using 'dmesg -w' too see what's going on I can see that there is a general protection fault somehow related to cifsd. I am however unable to tell if it is relevant to my issue, from kern.log: Jan 9 21:03:49 ubnu kernel: [ 410.357213] general protection fault: [#1] SMP PTI Jan 9 21:03:49 ubnu kernel: [ 410.357224] Modules linked in: cmac arc4 md4 nls_utf8 cifs ccm fscache rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) thunderbolt bnep binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_hda_codec_realtek snd_soc_acpi snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel intel_rapl btusb x86_pkg_temp_thermal intel_powerclamp btrtl coretemp joydev btbcm snd_hda_codec kvm_intel input_leds kvm irqbypass btintel crct10dif_pclmul crc32_pclmul snd_hda_core ghash_clmulni_intel pcbc snd_hwdep snd_pcm bluetooth ecdh_generic snd_seq_midi snd_seq_midi_event aesni_intel snd_rawmidi aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf snd_seq rtsx_pci_ms snd_seq_device Jan 9 21:03:49 ubnu kernel: [ 410.357357] wmi_bmof snd_timer memstick intel_wmi_thunderbolt snd shpchp soundcore mei_me mei intel_pch_thermal acpi_pad mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 xfs libcrc32c hid_generic usbhid hid rtsx_pci_sdmmc i915 e1000e i2c_algo_bit drm_kms_helper ptp syscopyarea pps_core i2c_i801 sysfillrect sysimgblt rtsx_pci fb_sys_fops drm ahci libahci wmi video Jan 9 21:03:49 ubnu kernel: [ 410.357447] CPU: 2 PID: 1822 Comm: cifsd Tainted: G OE4.15.0-43-generic #46-Ubuntu Jan 9 21:03:49 ubnu kernel: [ 410.357453] Hardware name: /NUC7i3BNB, BIOS BNKBL357.86A.0069.2018.0920.1250 09/20/2018 Jan 9 21:03:49 ubnu kernel: [ 410.357468] RIP: 0010:prefetch_freepointer+0x15/0x30 Jan 9 21:03:49 ubnu kernel: [ 410.357474] RSP: 0018:b16201ae3da0 EFLAGS: 00010282 Jan 9 21:03:49 ubnu kernel: [ 410.357482] RAX: RBX: e90527c744fff71a RCX: 3ea9 Jan 9 21:03:49 ubnu kernel: [ 410.357488] RDX: 3ea8 RSI: e90527c744fff71a RDI: 9d7079255080 Jan 9 21:03:49 ubnu kernel: [ 410.357494] RBP: b16201ae3da0 R08: 9d707ed2b650 R09: b16201ae3db0 Jan 9 21:03:49 ubnu kernel: [ 410.357499] R10: b16201ae3de8 R11: R12: 01011200 Jan 9 21:03:49 ubnu kernel: [ 410.357505] R13: 9d7079255080 R14: 9d7016478c40 R15: 9d7079255080 Jan 9 21:03:49 ubnu kernel: [ 410.357512] FS: () GS:9d707ed0() knlGS: Jan 9 21:03:49 ubnu kernel: [ 410.357519] CS: 0010 DS: ES: CR0: 80050033 Jan 9 21:03:49 ubnu kernel: [ 410.357525] CR2: 7f0a2802d028 CR3: 3760a006 CR4: 003606e0 Jan 9 21:03:49 ubnu kernel: [ 410.357530] Call Trace: Jan 9 21:03:49 ubnu kernel: [ 410.357545] kmem_cache_alloc+0xa2/0x1b0 Jan 9 21:03:49 ubnu kernel: [ 410.357558] ? mempool_alloc_slab+0x15/0x20 Jan 9 21:03:49 ubnu kernel: [ 410.357570] ? wait_woken+0x80/0x80 Jan 9 21:03:49 ubnu kernel: [ 410.357580] mempool_alloc_slab+0x15/0x20 Jan 9 21:03:49 ubnu kernel: [ 410.357590] mempool_alloc+0x71/0x190 Jan 9 21:03:49 ubnu kernel: [ 410.357660] ? smb2_add_credits+0xb0/0x250 [cifs] Jan 9 21:03:49 ubnu kernel: [ 410.357709] cifs_small_buf_get+0x1a/0x30 [cifs] Jan 9 21:03:49 ubnu kernel: [ 410.357751] cifs_demultiplex_thread+0x5c7/0xaf0
[Kernel-packages] [Bug 1811723] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1811723/+attachment/5267689/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811723 Title: Samba client freeze during write when using higher than vers=1.0 Status in linux package in Ubuntu: Confirmed Bug description: Hello, My issue is that whenever I try to write new files (copy or move) to my file server something in the samba client freezes and I can't do anything samba until the system is rebooted. To get write access I mount with uid ie "sudo mount //server/share /mountpoint -o user=write,uid=1000". Using this command the server and client negotiates smb protocol version 3.02. When this happens the server is still happily serving files to other machines. If I just read files everything works fine. If I connect from a windows client there is no issue. If I add "vers=1.0" everything works but transfers are really slow. Specifying version 3 produces a fail. Trying the same operation (different hw) with Mint 18 Mate produces the same fault. Trying the same operation (with "vers=3.0" set) using SuSE Leap 15.0 KDE live everything works as expected. Both client and server are running fully updated, as of posting, bionic. Using 'dmesg -w' too see what's going on I can see that there is a general protection fault somehow related to cifsd. I am however unable to tell if it is relevant to my issue, from kern.log: Jan 9 21:03:49 ubnu kernel: [ 410.357213] general protection fault: [#1] SMP PTI Jan 9 21:03:49 ubnu kernel: [ 410.357224] Modules linked in: cmac arc4 md4 nls_utf8 cifs ccm fscache rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) thunderbolt bnep binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_hda_codec_realtek snd_soc_acpi snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel intel_rapl btusb x86_pkg_temp_thermal intel_powerclamp btrtl coretemp joydev btbcm snd_hda_codec kvm_intel input_leds kvm irqbypass btintel crct10dif_pclmul crc32_pclmul snd_hda_core ghash_clmulni_intel pcbc snd_hwdep snd_pcm bluetooth ecdh_generic snd_seq_midi snd_seq_midi_event aesni_intel snd_rawmidi aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf snd_seq rtsx_pci_ms snd_seq_device Jan 9 21:03:49 ubnu kernel: [ 410.357357] wmi_bmof snd_timer memstick intel_wmi_thunderbolt snd shpchp soundcore mei_me mei intel_pch_thermal acpi_pad mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 xfs libcrc32c hid_generic usbhid hid rtsx_pci_sdmmc i915 e1000e i2c_algo_bit drm_kms_helper ptp syscopyarea pps_core i2c_i801 sysfillrect sysimgblt rtsx_pci fb_sys_fops drm ahci libahci wmi video Jan 9 21:03:49 ubnu kernel: [ 410.357447] CPU: 2 PID: 1822 Comm: cifsd Tainted: G OE4.15.0-43-generic #46-Ubuntu Jan 9 21:03:49 ubnu kernel: [ 410.357453] Hardware name: /NUC7i3BNB, BIOS BNKBL357.86A.0069.2018.0920.1250 09/20/2018 Jan 9 21:03:49 ubnu kernel: [ 410.357468] RIP: 0010:prefetch_freepointer+0x15/0x30 Jan 9 21:03:49 ubnu kernel: [ 410.357474] RSP: 0018:b16201ae3da0 EFLAGS: 00010282 Jan 9 21:03:49 ubnu kernel: [ 410.357482] RAX: RBX: e90527c744fff71a RCX: 3ea9 Jan 9 21:03:49 ubnu kernel: [ 410.357488] RDX: 3ea8 RSI: e90527c744fff71a RDI: 9d7079255080 Jan 9 21:03:49 ubnu kernel: [ 410.357494] RBP: b16201ae3da0 R08: 9d707ed2b650 R09: b16201ae3db0 Jan 9 21:03:49 ubnu kernel: [ 410.357499] R10: b16201ae3de8 R11: R12: 01011200 Jan 9 21:03:49 ubnu kernel: [ 410.357505] R13: 9d7079255080 R14: 9d7016478c40 R15: 9d7079255080 Jan 9 21:03:49 ubnu kernel: [ 410.357512] FS: () GS:9d707ed0() knlGS: Jan 9 21:03:49 ubnu kernel: [ 410.357519] CS: 0010 DS: ES: CR0: 80050033 Jan 9 21:03:49 ubnu kernel: [ 410.357525] CR2: 7f0a2802d028 CR3: 3760a006 CR4: 003606e0 Jan 9 21:03:49 ubnu kernel: [ 410.357530] Call Trace: Jan 9 21:03:49 ubnu kernel: [ 410.357545] kmem_cache_alloc+0xa2/0x1b0 Jan 9 21:03:49 ubnu kernel: [ 410.357558] ? mempool_alloc_slab+0x15/0x20 Jan 9 21:03:49 ubnu kernel: [ 410.357570] ? wait_woken+0x80/0x80 Jan 9 21:03:49 ubnu kernel: [ 410.357580] mempool_alloc_slab+0x15/0x20 Jan 9 21:03:49 ubnu kernel: [ 410.357590] mempool_alloc+0x71/0x190 Jan 9 21:03:49 ubnu kernel: [ 410.357660] ? smb2_add_credits+0xb0/0x250 [cifs] Jan 9 21:03:49 ubnu kernel: [ 410.357709] cifs_small_buf_get+0x1a/0x30 [cifs] Jan
[Kernel-packages] [Bug 1811723] Re: Samba client freeze during write when using higher than vers=1.0
apport information ** Tags added: apport-collected wayland-session ** Description changed: Hello, My issue is that whenever I try to write new files (copy or move) to my file server something in the samba client freezes and I can't do anything samba until the system is rebooted. To get write access I mount with uid ie "sudo mount //server/share /mountpoint -o user=write,uid=1000". Using this command the server and client negotiates smb protocol version 3.02. When this happens the server is still happily serving files to other machines. If I just read files everything works fine. If I connect from a windows client there is no issue. If I add "vers=1.0" everything works but transfers are really slow. Specifying version 3 produces a fail. Trying the same operation (different hw) with Mint 18 Mate produces the same fault. Trying the same operation (with "vers=3.0" set) using SuSE Leap 15.0 KDE live everything works as expected. Both client and server are running fully updated, as of posting, bionic. Using 'dmesg -w' too see what's going on I can see that there is a general protection fault somehow related to cifsd. I am however unable to tell if it is relevant to my issue, from kern.log: Jan 9 21:03:49 ubnu kernel: [ 410.357213] general protection fault: [#1] SMP PTI Jan 9 21:03:49 ubnu kernel: [ 410.357224] Modules linked in: cmac arc4 md4 nls_utf8 cifs ccm fscache rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) thunderbolt bnep binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_hda_codec_realtek snd_soc_acpi snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel intel_rapl btusb x86_pkg_temp_thermal intel_powerclamp btrtl coretemp joydev btbcm snd_hda_codec kvm_intel input_leds kvm irqbypass btintel crct10dif_pclmul crc32_pclmul snd_hda_core ghash_clmulni_intel pcbc snd_hwdep snd_pcm bluetooth ecdh_generic snd_seq_midi snd_seq_midi_event aesni_intel snd_rawmidi aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf snd_seq rtsx_pci_ms snd_seq_device Jan 9 21:03:49 ubnu kernel: [ 410.357357] wmi_bmof snd_timer memstick intel_wmi_thunderbolt snd shpchp soundcore mei_me mei intel_pch_thermal acpi_pad mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 xfs libcrc32c hid_generic usbhid hid rtsx_pci_sdmmc i915 e1000e i2c_algo_bit drm_kms_helper ptp syscopyarea pps_core i2c_i801 sysfillrect sysimgblt rtsx_pci fb_sys_fops drm ahci libahci wmi video Jan 9 21:03:49 ubnu kernel: [ 410.357447] CPU: 2 PID: 1822 Comm: cifsd Tainted: G OE4.15.0-43-generic #46-Ubuntu Jan 9 21:03:49 ubnu kernel: [ 410.357453] Hardware name: /NUC7i3BNB, BIOS BNKBL357.86A.0069.2018.0920.1250 09/20/2018 Jan 9 21:03:49 ubnu kernel: [ 410.357468] RIP: 0010:prefetch_freepointer+0x15/0x30 Jan 9 21:03:49 ubnu kernel: [ 410.357474] RSP: 0018:b16201ae3da0 EFLAGS: 00010282 Jan 9 21:03:49 ubnu kernel: [ 410.357482] RAX: RBX: e90527c744fff71a RCX: 3ea9 Jan 9 21:03:49 ubnu kernel: [ 410.357488] RDX: 3ea8 RSI: e90527c744fff71a RDI: 9d7079255080 Jan 9 21:03:49 ubnu kernel: [ 410.357494] RBP: b16201ae3da0 R08: 9d707ed2b650 R09: b16201ae3db0 Jan 9 21:03:49 ubnu kernel: [ 410.357499] R10: b16201ae3de8 R11: R12: 01011200 Jan 9 21:03:49 ubnu kernel: [ 410.357505] R13: 9d7079255080 R14: 9d7016478c40 R15: 9d7079255080 Jan 9 21:03:49 ubnu kernel: [ 410.357512] FS: () GS:9d707ed0() knlGS: Jan 9 21:03:49 ubnu kernel: [ 410.357519] CS: 0010 DS: ES: CR0: 80050033 Jan 9 21:03:49 ubnu kernel: [ 410.357525] CR2: 7f0a2802d028 CR3: 3760a006 CR4: 003606e0 Jan 9 21:03:49 ubnu kernel: [ 410.357530] Call Trace: Jan 9 21:03:49 ubnu kernel: [ 410.357545] kmem_cache_alloc+0xa2/0x1b0 Jan 9 21:03:49 ubnu kernel: [ 410.357558] ? mempool_alloc_slab+0x15/0x20 Jan 9 21:03:49 ubnu kernel: [ 410.357570] ? wait_woken+0x80/0x80 Jan 9 21:03:49 ubnu kernel: [ 410.357580] mempool_alloc_slab+0x15/0x20 Jan 9 21:03:49 ubnu kernel: [ 410.357590] mempool_alloc+0x71/0x190 Jan 9 21:03:49 ubnu kernel: [ 410.357660] ? smb2_add_credits+0xb0/0x250 [cifs] Jan 9 21:03:49 ubnu kernel: [ 410.357709] cifs_small_buf_get+0x1a/0x30 [cifs] Jan 9 21:03:49 ubnu kernel: [ 410.357751] cifs_demultiplex_thread+0x5c7/0xaf0 [cifs] Jan 9 21:03:49 ubnu kernel: [ 410.357762] ? __schedule+0x299/0x8a0 Jan 9 21:03:49 ubnu kernel: [ 410.35] kthread+0x121/0x140 Jan 9 21:03:49 ubnu kernel: [ 410.357815] ? cifs_handle_standard+0x190/0x190 [cifs] Jan 9 21:03:49 ubnu kernel: [ 410.357827] ? kthread_create_worker_on_cpu+0x70/0x70 Jan 9
[Kernel-packages] [Bug 1811723] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1811723/+attachment/5267687/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811723 Title: Samba client freeze during write when using higher than vers=1.0 Status in linux package in Ubuntu: Confirmed Bug description: Hello, My issue is that whenever I try to write new files (copy or move) to my file server something in the samba client freezes and I can't do anything samba until the system is rebooted. To get write access I mount with uid ie "sudo mount //server/share /mountpoint -o user=write,uid=1000". Using this command the server and client negotiates smb protocol version 3.02. When this happens the server is still happily serving files to other machines. If I just read files everything works fine. If I connect from a windows client there is no issue. If I add "vers=1.0" everything works but transfers are really slow. Specifying version 3 produces a fail. Trying the same operation (different hw) with Mint 18 Mate produces the same fault. Trying the same operation (with "vers=3.0" set) using SuSE Leap 15.0 KDE live everything works as expected. Both client and server are running fully updated, as of posting, bionic. Using 'dmesg -w' too see what's going on I can see that there is a general protection fault somehow related to cifsd. I am however unable to tell if it is relevant to my issue, from kern.log: Jan 9 21:03:49 ubnu kernel: [ 410.357213] general protection fault: [#1] SMP PTI Jan 9 21:03:49 ubnu kernel: [ 410.357224] Modules linked in: cmac arc4 md4 nls_utf8 cifs ccm fscache rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) thunderbolt bnep binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_hda_codec_realtek snd_soc_acpi snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel intel_rapl btusb x86_pkg_temp_thermal intel_powerclamp btrtl coretemp joydev btbcm snd_hda_codec kvm_intel input_leds kvm irqbypass btintel crct10dif_pclmul crc32_pclmul snd_hda_core ghash_clmulni_intel pcbc snd_hwdep snd_pcm bluetooth ecdh_generic snd_seq_midi snd_seq_midi_event aesni_intel snd_rawmidi aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf snd_seq rtsx_pci_ms snd_seq_device Jan 9 21:03:49 ubnu kernel: [ 410.357357] wmi_bmof snd_timer memstick intel_wmi_thunderbolt snd shpchp soundcore mei_me mei intel_pch_thermal acpi_pad mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 xfs libcrc32c hid_generic usbhid hid rtsx_pci_sdmmc i915 e1000e i2c_algo_bit drm_kms_helper ptp syscopyarea pps_core i2c_i801 sysfillrect sysimgblt rtsx_pci fb_sys_fops drm ahci libahci wmi video Jan 9 21:03:49 ubnu kernel: [ 410.357447] CPU: 2 PID: 1822 Comm: cifsd Tainted: G OE4.15.0-43-generic #46-Ubuntu Jan 9 21:03:49 ubnu kernel: [ 410.357453] Hardware name: /NUC7i3BNB, BIOS BNKBL357.86A.0069.2018.0920.1250 09/20/2018 Jan 9 21:03:49 ubnu kernel: [ 410.357468] RIP: 0010:prefetch_freepointer+0x15/0x30 Jan 9 21:03:49 ubnu kernel: [ 410.357474] RSP: 0018:b16201ae3da0 EFLAGS: 00010282 Jan 9 21:03:49 ubnu kernel: [ 410.357482] RAX: RBX: e90527c744fff71a RCX: 3ea9 Jan 9 21:03:49 ubnu kernel: [ 410.357488] RDX: 3ea8 RSI: e90527c744fff71a RDI: 9d7079255080 Jan 9 21:03:49 ubnu kernel: [ 410.357494] RBP: b16201ae3da0 R08: 9d707ed2b650 R09: b16201ae3db0 Jan 9 21:03:49 ubnu kernel: [ 410.357499] R10: b16201ae3de8 R11: R12: 01011200 Jan 9 21:03:49 ubnu kernel: [ 410.357505] R13: 9d7079255080 R14: 9d7016478c40 R15: 9d7079255080 Jan 9 21:03:49 ubnu kernel: [ 410.357512] FS: () GS:9d707ed0() knlGS: Jan 9 21:03:49 ubnu kernel: [ 410.357519] CS: 0010 DS: ES: CR0: 80050033 Jan 9 21:03:49 ubnu kernel: [ 410.357525] CR2: 7f0a2802d028 CR3: 3760a006 CR4: 003606e0 Jan 9 21:03:49 ubnu kernel: [ 410.357530] Call Trace: Jan 9 21:03:49 ubnu kernel: [ 410.357545] kmem_cache_alloc+0xa2/0x1b0 Jan 9 21:03:49 ubnu kernel: [ 410.357558] ? mempool_alloc_slab+0x15/0x20 Jan 9 21:03:49 ubnu kernel: [ 410.357570] ? wait_woken+0x80/0x80 Jan 9 21:03:49 ubnu kernel: [ 410.357580] mempool_alloc_slab+0x15/0x20 Jan 9 21:03:49 ubnu kernel: [ 410.357590] mempool_alloc+0x71/0x190 Jan 9 21:03:49 ubnu kernel: [ 410.357660] ? smb2_add_credits+0xb0/0x250 [cifs] Jan 9 21:03:49 ubnu kernel: [ 410.357709] cifs_small_buf_get+0x1a/0x30 [cifs] Jan 9 21:03:49 ubnu kernel: [ 410.357751]
[Kernel-packages] [Bug 1811723] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1811723/+attachment/5267682/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811723 Title: Samba client freeze during write when using higher than vers=1.0 Status in linux package in Ubuntu: Confirmed Bug description: Hello, My issue is that whenever I try to write new files (copy or move) to my file server something in the samba client freezes and I can't do anything samba until the system is rebooted. To get write access I mount with uid ie "sudo mount //server/share /mountpoint -o user=write,uid=1000". Using this command the server and client negotiates smb protocol version 3.02. When this happens the server is still happily serving files to other machines. If I just read files everything works fine. If I connect from a windows client there is no issue. If I add "vers=1.0" everything works but transfers are really slow. Specifying version 3 produces a fail. Trying the same operation (different hw) with Mint 18 Mate produces the same fault. Trying the same operation (with "vers=3.0" set) using SuSE Leap 15.0 KDE live everything works as expected. Both client and server are running fully updated, as of posting, bionic. Using 'dmesg -w' too see what's going on I can see that there is a general protection fault somehow related to cifsd. I am however unable to tell if it is relevant to my issue, from kern.log: Jan 9 21:03:49 ubnu kernel: [ 410.357213] general protection fault: [#1] SMP PTI Jan 9 21:03:49 ubnu kernel: [ 410.357224] Modules linked in: cmac arc4 md4 nls_utf8 cifs ccm fscache rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) thunderbolt bnep binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_hda_codec_realtek snd_soc_acpi snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel intel_rapl btusb x86_pkg_temp_thermal intel_powerclamp btrtl coretemp joydev btbcm snd_hda_codec kvm_intel input_leds kvm irqbypass btintel crct10dif_pclmul crc32_pclmul snd_hda_core ghash_clmulni_intel pcbc snd_hwdep snd_pcm bluetooth ecdh_generic snd_seq_midi snd_seq_midi_event aesni_intel snd_rawmidi aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf snd_seq rtsx_pci_ms snd_seq_device Jan 9 21:03:49 ubnu kernel: [ 410.357357] wmi_bmof snd_timer memstick intel_wmi_thunderbolt snd shpchp soundcore mei_me mei intel_pch_thermal acpi_pad mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 xfs libcrc32c hid_generic usbhid hid rtsx_pci_sdmmc i915 e1000e i2c_algo_bit drm_kms_helper ptp syscopyarea pps_core i2c_i801 sysfillrect sysimgblt rtsx_pci fb_sys_fops drm ahci libahci wmi video Jan 9 21:03:49 ubnu kernel: [ 410.357447] CPU: 2 PID: 1822 Comm: cifsd Tainted: G OE4.15.0-43-generic #46-Ubuntu Jan 9 21:03:49 ubnu kernel: [ 410.357453] Hardware name: /NUC7i3BNB, BIOS BNKBL357.86A.0069.2018.0920.1250 09/20/2018 Jan 9 21:03:49 ubnu kernel: [ 410.357468] RIP: 0010:prefetch_freepointer+0x15/0x30 Jan 9 21:03:49 ubnu kernel: [ 410.357474] RSP: 0018:b16201ae3da0 EFLAGS: 00010282 Jan 9 21:03:49 ubnu kernel: [ 410.357482] RAX: RBX: e90527c744fff71a RCX: 3ea9 Jan 9 21:03:49 ubnu kernel: [ 410.357488] RDX: 3ea8 RSI: e90527c744fff71a RDI: 9d7079255080 Jan 9 21:03:49 ubnu kernel: [ 410.357494] RBP: b16201ae3da0 R08: 9d707ed2b650 R09: b16201ae3db0 Jan 9 21:03:49 ubnu kernel: [ 410.357499] R10: b16201ae3de8 R11: R12: 01011200 Jan 9 21:03:49 ubnu kernel: [ 410.357505] R13: 9d7079255080 R14: 9d7016478c40 R15: 9d7079255080 Jan 9 21:03:49 ubnu kernel: [ 410.357512] FS: () GS:9d707ed0() knlGS: Jan 9 21:03:49 ubnu kernel: [ 410.357519] CS: 0010 DS: ES: CR0: 80050033 Jan 9 21:03:49 ubnu kernel: [ 410.357525] CR2: 7f0a2802d028 CR3: 3760a006 CR4: 003606e0 Jan 9 21:03:49 ubnu kernel: [ 410.357530] Call Trace: Jan 9 21:03:49 ubnu kernel: [ 410.357545] kmem_cache_alloc+0xa2/0x1b0 Jan 9 21:03:49 ubnu kernel: [ 410.357558] ? mempool_alloc_slab+0x15/0x20 Jan 9 21:03:49 ubnu kernel: [ 410.357570] ? wait_woken+0x80/0x80 Jan 9 21:03:49 ubnu kernel: [ 410.357580] mempool_alloc_slab+0x15/0x20 Jan 9 21:03:49 ubnu kernel: [ 410.357590] mempool_alloc+0x71/0x190 Jan 9 21:03:49 ubnu kernel: [ 410.357660] ? smb2_add_credits+0xb0/0x250 [cifs] Jan 9 21:03:49 ubnu kernel: [ 410.357709] cifs_small_buf_get+0x1a/0x30 [cifs] Jan 9 21:03:49 ubnu kernel: [ 410.357751]
[Kernel-packages] [Bug 1811723] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1811723/+attachment/5267688/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811723 Title: Samba client freeze during write when using higher than vers=1.0 Status in linux package in Ubuntu: Confirmed Bug description: Hello, My issue is that whenever I try to write new files (copy or move) to my file server something in the samba client freezes and I can't do anything samba until the system is rebooted. To get write access I mount with uid ie "sudo mount //server/share /mountpoint -o user=write,uid=1000". Using this command the server and client negotiates smb protocol version 3.02. When this happens the server is still happily serving files to other machines. If I just read files everything works fine. If I connect from a windows client there is no issue. If I add "vers=1.0" everything works but transfers are really slow. Specifying version 3 produces a fail. Trying the same operation (different hw) with Mint 18 Mate produces the same fault. Trying the same operation (with "vers=3.0" set) using SuSE Leap 15.0 KDE live everything works as expected. Both client and server are running fully updated, as of posting, bionic. Using 'dmesg -w' too see what's going on I can see that there is a general protection fault somehow related to cifsd. I am however unable to tell if it is relevant to my issue, from kern.log: Jan 9 21:03:49 ubnu kernel: [ 410.357213] general protection fault: [#1] SMP PTI Jan 9 21:03:49 ubnu kernel: [ 410.357224] Modules linked in: cmac arc4 md4 nls_utf8 cifs ccm fscache rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) thunderbolt bnep binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_hda_codec_realtek snd_soc_acpi snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel intel_rapl btusb x86_pkg_temp_thermal intel_powerclamp btrtl coretemp joydev btbcm snd_hda_codec kvm_intel input_leds kvm irqbypass btintel crct10dif_pclmul crc32_pclmul snd_hda_core ghash_clmulni_intel pcbc snd_hwdep snd_pcm bluetooth ecdh_generic snd_seq_midi snd_seq_midi_event aesni_intel snd_rawmidi aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf snd_seq rtsx_pci_ms snd_seq_device Jan 9 21:03:49 ubnu kernel: [ 410.357357] wmi_bmof snd_timer memstick intel_wmi_thunderbolt snd shpchp soundcore mei_me mei intel_pch_thermal acpi_pad mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 xfs libcrc32c hid_generic usbhid hid rtsx_pci_sdmmc i915 e1000e i2c_algo_bit drm_kms_helper ptp syscopyarea pps_core i2c_i801 sysfillrect sysimgblt rtsx_pci fb_sys_fops drm ahci libahci wmi video Jan 9 21:03:49 ubnu kernel: [ 410.357447] CPU: 2 PID: 1822 Comm: cifsd Tainted: G OE4.15.0-43-generic #46-Ubuntu Jan 9 21:03:49 ubnu kernel: [ 410.357453] Hardware name: /NUC7i3BNB, BIOS BNKBL357.86A.0069.2018.0920.1250 09/20/2018 Jan 9 21:03:49 ubnu kernel: [ 410.357468] RIP: 0010:prefetch_freepointer+0x15/0x30 Jan 9 21:03:49 ubnu kernel: [ 410.357474] RSP: 0018:b16201ae3da0 EFLAGS: 00010282 Jan 9 21:03:49 ubnu kernel: [ 410.357482] RAX: RBX: e90527c744fff71a RCX: 3ea9 Jan 9 21:03:49 ubnu kernel: [ 410.357488] RDX: 3ea8 RSI: e90527c744fff71a RDI: 9d7079255080 Jan 9 21:03:49 ubnu kernel: [ 410.357494] RBP: b16201ae3da0 R08: 9d707ed2b650 R09: b16201ae3db0 Jan 9 21:03:49 ubnu kernel: [ 410.357499] R10: b16201ae3de8 R11: R12: 01011200 Jan 9 21:03:49 ubnu kernel: [ 410.357505] R13: 9d7079255080 R14: 9d7016478c40 R15: 9d7079255080 Jan 9 21:03:49 ubnu kernel: [ 410.357512] FS: () GS:9d707ed0() knlGS: Jan 9 21:03:49 ubnu kernel: [ 410.357519] CS: 0010 DS: ES: CR0: 80050033 Jan 9 21:03:49 ubnu kernel: [ 410.357525] CR2: 7f0a2802d028 CR3: 3760a006 CR4: 003606e0 Jan 9 21:03:49 ubnu kernel: [ 410.357530] Call Trace: Jan 9 21:03:49 ubnu kernel: [ 410.357545] kmem_cache_alloc+0xa2/0x1b0 Jan 9 21:03:49 ubnu kernel: [ 410.357558] ? mempool_alloc_slab+0x15/0x20 Jan 9 21:03:49 ubnu kernel: [ 410.357570] ? wait_woken+0x80/0x80 Jan 9 21:03:49 ubnu kernel: [ 410.357580] mempool_alloc_slab+0x15/0x20 Jan 9 21:03:49 ubnu kernel: [ 410.357590] mempool_alloc+0x71/0x190 Jan 9 21:03:49 ubnu kernel: [ 410.357660] ? smb2_add_credits+0xb0/0x250 [cifs] Jan 9 21:03:49 ubnu kernel: [ 410.357709] cifs_small_buf_get+0x1a/0x30 [cifs] Jan 9 21:03:49 ubnu kernel: [ 410.357751] cifs_demultiplex_thread+0x5c7/0xaf0
[Kernel-packages] [Bug 1811723] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1811723/+attachment/5267678/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811723 Title: Samba client freeze during write when using higher than vers=1.0 Status in linux package in Ubuntu: Confirmed Bug description: Hello, My issue is that whenever I try to write new files (copy or move) to my file server something in the samba client freezes and I can't do anything samba until the system is rebooted. To get write access I mount with uid ie "sudo mount //server/share /mountpoint -o user=write,uid=1000". Using this command the server and client negotiates smb protocol version 3.02. When this happens the server is still happily serving files to other machines. If I just read files everything works fine. If I connect from a windows client there is no issue. If I add "vers=1.0" everything works but transfers are really slow. Specifying version 3 produces a fail. Trying the same operation (different hw) with Mint 18 Mate produces the same fault. Trying the same operation (with "vers=3.0" set) using SuSE Leap 15.0 KDE live everything works as expected. Both client and server are running fully updated, as of posting, bionic. Using 'dmesg -w' too see what's going on I can see that there is a general protection fault somehow related to cifsd. I am however unable to tell if it is relevant to my issue, from kern.log: Jan 9 21:03:49 ubnu kernel: [ 410.357213] general protection fault: [#1] SMP PTI Jan 9 21:03:49 ubnu kernel: [ 410.357224] Modules linked in: cmac arc4 md4 nls_utf8 cifs ccm fscache rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) thunderbolt bnep binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_hda_codec_realtek snd_soc_acpi snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel intel_rapl btusb x86_pkg_temp_thermal intel_powerclamp btrtl coretemp joydev btbcm snd_hda_codec kvm_intel input_leds kvm irqbypass btintel crct10dif_pclmul crc32_pclmul snd_hda_core ghash_clmulni_intel pcbc snd_hwdep snd_pcm bluetooth ecdh_generic snd_seq_midi snd_seq_midi_event aesni_intel snd_rawmidi aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf snd_seq rtsx_pci_ms snd_seq_device Jan 9 21:03:49 ubnu kernel: [ 410.357357] wmi_bmof snd_timer memstick intel_wmi_thunderbolt snd shpchp soundcore mei_me mei intel_pch_thermal acpi_pad mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 xfs libcrc32c hid_generic usbhid hid rtsx_pci_sdmmc i915 e1000e i2c_algo_bit drm_kms_helper ptp syscopyarea pps_core i2c_i801 sysfillrect sysimgblt rtsx_pci fb_sys_fops drm ahci libahci wmi video Jan 9 21:03:49 ubnu kernel: [ 410.357447] CPU: 2 PID: 1822 Comm: cifsd Tainted: G OE4.15.0-43-generic #46-Ubuntu Jan 9 21:03:49 ubnu kernel: [ 410.357453] Hardware name: /NUC7i3BNB, BIOS BNKBL357.86A.0069.2018.0920.1250 09/20/2018 Jan 9 21:03:49 ubnu kernel: [ 410.357468] RIP: 0010:prefetch_freepointer+0x15/0x30 Jan 9 21:03:49 ubnu kernel: [ 410.357474] RSP: 0018:b16201ae3da0 EFLAGS: 00010282 Jan 9 21:03:49 ubnu kernel: [ 410.357482] RAX: RBX: e90527c744fff71a RCX: 3ea9 Jan 9 21:03:49 ubnu kernel: [ 410.357488] RDX: 3ea8 RSI: e90527c744fff71a RDI: 9d7079255080 Jan 9 21:03:49 ubnu kernel: [ 410.357494] RBP: b16201ae3da0 R08: 9d707ed2b650 R09: b16201ae3db0 Jan 9 21:03:49 ubnu kernel: [ 410.357499] R10: b16201ae3de8 R11: R12: 01011200 Jan 9 21:03:49 ubnu kernel: [ 410.357505] R13: 9d7079255080 R14: 9d7016478c40 R15: 9d7079255080 Jan 9 21:03:49 ubnu kernel: [ 410.357512] FS: () GS:9d707ed0() knlGS: Jan 9 21:03:49 ubnu kernel: [ 410.357519] CS: 0010 DS: ES: CR0: 80050033 Jan 9 21:03:49 ubnu kernel: [ 410.357525] CR2: 7f0a2802d028 CR3: 3760a006 CR4: 003606e0 Jan 9 21:03:49 ubnu kernel: [ 410.357530] Call Trace: Jan 9 21:03:49 ubnu kernel: [ 410.357545] kmem_cache_alloc+0xa2/0x1b0 Jan 9 21:03:49 ubnu kernel: [ 410.357558] ? mempool_alloc_slab+0x15/0x20 Jan 9 21:03:49 ubnu kernel: [ 410.357570] ? wait_woken+0x80/0x80 Jan 9 21:03:49 ubnu kernel: [ 410.357580] mempool_alloc_slab+0x15/0x20 Jan 9 21:03:49 ubnu kernel: [ 410.357590] mempool_alloc+0x71/0x190 Jan 9 21:03:49 ubnu kernel: [ 410.357660] ? smb2_add_credits+0xb0/0x250 [cifs] Jan 9 21:03:49 ubnu kernel: [ 410.357709] cifs_small_buf_get+0x1a/0x30 [cifs] Jan 9 21:03:49 ubnu kernel: [ 410.357751] cifs_demultiplex_thread+0x5c7/0xaf0
[Kernel-packages] [Bug 1811723] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1811723/+attachment/5267679/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811723 Title: Samba client freeze during write when using higher than vers=1.0 Status in linux package in Ubuntu: Confirmed Bug description: Hello, My issue is that whenever I try to write new files (copy or move) to my file server something in the samba client freezes and I can't do anything samba until the system is rebooted. To get write access I mount with uid ie "sudo mount //server/share /mountpoint -o user=write,uid=1000". Using this command the server and client negotiates smb protocol version 3.02. When this happens the server is still happily serving files to other machines. If I just read files everything works fine. If I connect from a windows client there is no issue. If I add "vers=1.0" everything works but transfers are really slow. Specifying version 3 produces a fail. Trying the same operation (different hw) with Mint 18 Mate produces the same fault. Trying the same operation (with "vers=3.0" set) using SuSE Leap 15.0 KDE live everything works as expected. Both client and server are running fully updated, as of posting, bionic. Using 'dmesg -w' too see what's going on I can see that there is a general protection fault somehow related to cifsd. I am however unable to tell if it is relevant to my issue, from kern.log: Jan 9 21:03:49 ubnu kernel: [ 410.357213] general protection fault: [#1] SMP PTI Jan 9 21:03:49 ubnu kernel: [ 410.357224] Modules linked in: cmac arc4 md4 nls_utf8 cifs ccm fscache rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) thunderbolt bnep binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_hda_codec_realtek snd_soc_acpi snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel intel_rapl btusb x86_pkg_temp_thermal intel_powerclamp btrtl coretemp joydev btbcm snd_hda_codec kvm_intel input_leds kvm irqbypass btintel crct10dif_pclmul crc32_pclmul snd_hda_core ghash_clmulni_intel pcbc snd_hwdep snd_pcm bluetooth ecdh_generic snd_seq_midi snd_seq_midi_event aesni_intel snd_rawmidi aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf snd_seq rtsx_pci_ms snd_seq_device Jan 9 21:03:49 ubnu kernel: [ 410.357357] wmi_bmof snd_timer memstick intel_wmi_thunderbolt snd shpchp soundcore mei_me mei intel_pch_thermal acpi_pad mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 xfs libcrc32c hid_generic usbhid hid rtsx_pci_sdmmc i915 e1000e i2c_algo_bit drm_kms_helper ptp syscopyarea pps_core i2c_i801 sysfillrect sysimgblt rtsx_pci fb_sys_fops drm ahci libahci wmi video Jan 9 21:03:49 ubnu kernel: [ 410.357447] CPU: 2 PID: 1822 Comm: cifsd Tainted: G OE4.15.0-43-generic #46-Ubuntu Jan 9 21:03:49 ubnu kernel: [ 410.357453] Hardware name: /NUC7i3BNB, BIOS BNKBL357.86A.0069.2018.0920.1250 09/20/2018 Jan 9 21:03:49 ubnu kernel: [ 410.357468] RIP: 0010:prefetch_freepointer+0x15/0x30 Jan 9 21:03:49 ubnu kernel: [ 410.357474] RSP: 0018:b16201ae3da0 EFLAGS: 00010282 Jan 9 21:03:49 ubnu kernel: [ 410.357482] RAX: RBX: e90527c744fff71a RCX: 3ea9 Jan 9 21:03:49 ubnu kernel: [ 410.357488] RDX: 3ea8 RSI: e90527c744fff71a RDI: 9d7079255080 Jan 9 21:03:49 ubnu kernel: [ 410.357494] RBP: b16201ae3da0 R08: 9d707ed2b650 R09: b16201ae3db0 Jan 9 21:03:49 ubnu kernel: [ 410.357499] R10: b16201ae3de8 R11: R12: 01011200 Jan 9 21:03:49 ubnu kernel: [ 410.357505] R13: 9d7079255080 R14: 9d7016478c40 R15: 9d7079255080 Jan 9 21:03:49 ubnu kernel: [ 410.357512] FS: () GS:9d707ed0() knlGS: Jan 9 21:03:49 ubnu kernel: [ 410.357519] CS: 0010 DS: ES: CR0: 80050033 Jan 9 21:03:49 ubnu kernel: [ 410.357525] CR2: 7f0a2802d028 CR3: 3760a006 CR4: 003606e0 Jan 9 21:03:49 ubnu kernel: [ 410.357530] Call Trace: Jan 9 21:03:49 ubnu kernel: [ 410.357545] kmem_cache_alloc+0xa2/0x1b0 Jan 9 21:03:49 ubnu kernel: [ 410.357558] ? mempool_alloc_slab+0x15/0x20 Jan 9 21:03:49 ubnu kernel: [ 410.357570] ? wait_woken+0x80/0x80 Jan 9 21:03:49 ubnu kernel: [ 410.357580] mempool_alloc_slab+0x15/0x20 Jan 9 21:03:49 ubnu kernel: [ 410.357590] mempool_alloc+0x71/0x190 Jan 9 21:03:49 ubnu kernel: [ 410.357660] ? smb2_add_credits+0xb0/0x250 [cifs] Jan 9 21:03:49 ubnu kernel: [ 410.357709] cifs_small_buf_get+0x1a/0x30 [cifs] Jan 9 21:03:49 ubnu kernel: [ 410.357751]
[Kernel-packages] [Bug 1751497] Re: Bionic daily build - nouveau: Direct firmware load for nouveau/nve7_fuc084 failed with error -2
still present in ubuntu 19.04 [ 109.576524] nouveau :01:00.0: Direct firmware load for nouveau/nve7_fuc084 failed with error -2 [ 109.576530] nouveau :01:00.0: Direct firmware load for nouveau/nve7_fuc084d failed with error -2 [ 109.576532] nouveau :01:00.0: msvld: unable to load firmware data [ 109.576534] nouveau :01:00.0: msvld: init failed, -19 and nouveau sometimes crashes (not sure if related) [10154.703755] nouveau :01:00.0: fifo: fault 01 [WRITE] at 04c56000 engine 00 [GR] client 0f [GPC0/PROP_0] reason 82 [] on channel 2 [007f8d3000 systemd-logind[961]] [10154.703766] nouveau :01:00.0: fifo: channel 2: killed [10154.703769] nouveau :01:00.0: fifo: runlist 0: scheduled for recovery [10154.703773] nouveau :01:00.0: fifo: engine 0: scheduled for recovery [10154.703779] nouveau :01:00.0: fifo: engine 7: scheduled for recovery [10154.703971] nouveau :01:00.0: systemd-logind[961]: channel 2 killed! -- 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/1751497 Title: Bionic daily build - nouveau: Direct firmware load for nouveau/nve7_fuc084 failed with error -2 Status in linux package in Ubuntu: Expired Status in linux-firmware package in Ubuntu: Won't Fix Bug description: [ 136.559610] nouveau :01:00.0: Direct firmware load for nouveau/nve7_fuc084 failed with error -2 Hello, from time to time I find this annoying messages in dmesg in various Ubuntu versions (I believe since 16.04 or 16.10 up until now, including Bionic Beaver daily build). From time to time, the gdm3 crashes. The current HW/SW setup will be described below. I cannot replicate the situation, but it happens. See the excerpt from dmesg output below. [9.386558] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready [9.399079] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input12 [9.399134] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input13 [9.399208] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input14 [9.399274] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input15 [ 12.312741] r8169 :03:00.0 enp3s0: link up [ 12.312748] IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready [ 13.439863] rfkill: input handler disabled [ 15.125569] nf_conntrack: default automatic helper assignment has been turned off for security reasons and CT-based firewall rule not found. Use the iptables CT target to attach helpers instead. [ 136.559610] nouveau :01:00.0: Direct firmware load for nouveau/nve7_fuc084 failed with error -2 [ 136.559618] nouveau :01:00.0: Direct firmware load for nouveau/nve7_fuc084d failed with error -2 [ 136.559619] nouveau :01:00.0: msvld: unable to load firmware data [ 136.559622] nouveau :01:00.0: msvld: init failed, -19 [ 1376.746130] lp: driver loaded but no devices found [ 1376.756790] st: Version 20160209, fixed bufsize 32768, s/g segs 256 [ 1381.398605] do_IRQ: 1.37 No irq handler for vector rr HW setup: Asrock Extreme 6 Z97 Intel(R) Core(TM) i3-4160 CPU @ 3.60GHz, 3563 MHz nVidia GK107 [GeForce GT 640] SW setup: Linux bionic 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@bionic:~# lsmod | grep nouveau nouveau 1716224 5 i2c_algo_bit 16384 1 nouveau ttm 106496 1 nouveau drm_kms_helper167936 1 nouveau mxm_wmi16384 1 nouveau drm 401408 8 nouveau,ttm,drm_kms_helper wmi24576 2 mxm_wmi,nouveau video 40960 1 nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751497/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811723] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1811723/+attachment/5267684/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811723 Title: Samba client freeze during write when using higher than vers=1.0 Status in linux package in Ubuntu: Confirmed Bug description: Hello, My issue is that whenever I try to write new files (copy or move) to my file server something in the samba client freezes and I can't do anything samba until the system is rebooted. To get write access I mount with uid ie "sudo mount //server/share /mountpoint -o user=write,uid=1000". Using this command the server and client negotiates smb protocol version 3.02. When this happens the server is still happily serving files to other machines. If I just read files everything works fine. If I connect from a windows client there is no issue. If I add "vers=1.0" everything works but transfers are really slow. Specifying version 3 produces a fail. Trying the same operation (different hw) with Mint 18 Mate produces the same fault. Trying the same operation (with "vers=3.0" set) using SuSE Leap 15.0 KDE live everything works as expected. Both client and server are running fully updated, as of posting, bionic. Using 'dmesg -w' too see what's going on I can see that there is a general protection fault somehow related to cifsd. I am however unable to tell if it is relevant to my issue, from kern.log: Jan 9 21:03:49 ubnu kernel: [ 410.357213] general protection fault: [#1] SMP PTI Jan 9 21:03:49 ubnu kernel: [ 410.357224] Modules linked in: cmac arc4 md4 nls_utf8 cifs ccm fscache rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) thunderbolt bnep binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_hda_codec_realtek snd_soc_acpi snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel intel_rapl btusb x86_pkg_temp_thermal intel_powerclamp btrtl coretemp joydev btbcm snd_hda_codec kvm_intel input_leds kvm irqbypass btintel crct10dif_pclmul crc32_pclmul snd_hda_core ghash_clmulni_intel pcbc snd_hwdep snd_pcm bluetooth ecdh_generic snd_seq_midi snd_seq_midi_event aesni_intel snd_rawmidi aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf snd_seq rtsx_pci_ms snd_seq_device Jan 9 21:03:49 ubnu kernel: [ 410.357357] wmi_bmof snd_timer memstick intel_wmi_thunderbolt snd shpchp soundcore mei_me mei intel_pch_thermal acpi_pad mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 xfs libcrc32c hid_generic usbhid hid rtsx_pci_sdmmc i915 e1000e i2c_algo_bit drm_kms_helper ptp syscopyarea pps_core i2c_i801 sysfillrect sysimgblt rtsx_pci fb_sys_fops drm ahci libahci wmi video Jan 9 21:03:49 ubnu kernel: [ 410.357447] CPU: 2 PID: 1822 Comm: cifsd Tainted: G OE4.15.0-43-generic #46-Ubuntu Jan 9 21:03:49 ubnu kernel: [ 410.357453] Hardware name: /NUC7i3BNB, BIOS BNKBL357.86A.0069.2018.0920.1250 09/20/2018 Jan 9 21:03:49 ubnu kernel: [ 410.357468] RIP: 0010:prefetch_freepointer+0x15/0x30 Jan 9 21:03:49 ubnu kernel: [ 410.357474] RSP: 0018:b16201ae3da0 EFLAGS: 00010282 Jan 9 21:03:49 ubnu kernel: [ 410.357482] RAX: RBX: e90527c744fff71a RCX: 3ea9 Jan 9 21:03:49 ubnu kernel: [ 410.357488] RDX: 3ea8 RSI: e90527c744fff71a RDI: 9d7079255080 Jan 9 21:03:49 ubnu kernel: [ 410.357494] RBP: b16201ae3da0 R08: 9d707ed2b650 R09: b16201ae3db0 Jan 9 21:03:49 ubnu kernel: [ 410.357499] R10: b16201ae3de8 R11: R12: 01011200 Jan 9 21:03:49 ubnu kernel: [ 410.357505] R13: 9d7079255080 R14: 9d7016478c40 R15: 9d7079255080 Jan 9 21:03:49 ubnu kernel: [ 410.357512] FS: () GS:9d707ed0() knlGS: Jan 9 21:03:49 ubnu kernel: [ 410.357519] CS: 0010 DS: ES: CR0: 80050033 Jan 9 21:03:49 ubnu kernel: [ 410.357525] CR2: 7f0a2802d028 CR3: 3760a006 CR4: 003606e0 Jan 9 21:03:49 ubnu kernel: [ 410.357530] Call Trace: Jan 9 21:03:49 ubnu kernel: [ 410.357545] kmem_cache_alloc+0xa2/0x1b0 Jan 9 21:03:49 ubnu kernel: [ 410.357558] ? mempool_alloc_slab+0x15/0x20 Jan 9 21:03:49 ubnu kernel: [ 410.357570] ? wait_woken+0x80/0x80 Jan 9 21:03:49 ubnu kernel: [ 410.357580] mempool_alloc_slab+0x15/0x20 Jan 9 21:03:49 ubnu kernel: [ 410.357590] mempool_alloc+0x71/0x190 Jan 9 21:03:49 ubnu kernel: [ 410.357660] ? smb2_add_credits+0xb0/0x250 [cifs] Jan 9 21:03:49 ubnu kernel: [ 410.357709] cifs_small_buf_get+0x1a/0x30 [cifs] Jan 9 21:03:49 ubnu kernel: [ 410.357751]
[Kernel-packages] [Bug 1830792] Re: [i915] Rotated display is overscaled and overdrawn
** Attachment added: "output of journalctl -b0 > journal.txt (on Wayland)" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5267691/+files/journal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830792 Title: [i915] Rotated display is overscaled and overdrawn Status in gnome-shell package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: On my system I have two display: one in landscape, and one in portrait. The landscape display is fine, but the portrait display is corrupted. If I unplug the display from the computer for some time and then plug it back in it will occasionally fix the problem. Once the problem is fixed, the display works perfectly fine, indefinitely. However, as soon as I reboot the computer the display will come up corrupted again and never recovers without many rounds of plug/unplug turn off/turn on. It's extremely frustrating. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 28 15:57:02 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-04-22 (36 days ago) modified.conffile..etc.logrotate.d.apport: [modified] mtime.conffile..etc.logrotate.d.apport: 2019-01-12T15:50:59.090583 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831070] Re: package nvidia-dkms-390 390.116-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status
NB: Post-upgrade upgraded to nvidia-driver-418 from restricted (didn't re-enable graphics-drivers ppa) and all so far seems well. -- 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/1831070 Title: package nvidia-dkms-390 390.116-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 1 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: Just happened trying to upgrade a machine in two immediate steps bionic->cosmic->disco. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: nvidia-dkms-390 390.116-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-20.21-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Thu May 30 12:58:24 2019 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-02-20 (463 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.6ubuntu1 apt 1.8.1 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.116-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to disco on 2019-05-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1831070/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le
** Tags removed: ddstreet-next ** Description changed: in disco proposed with new systemd and v4.19 kernel it appears that dmsetup / cryptsetup storage either got better or worse. Devices take very long to activate, and sometimes remain in use during test clean up. This leads to udisks autopkgtest failing on ppc64le and systemd's "storage" autopkgtest is also failing. I've tried to make ppc64le test more resilient, but it's still odd that it became unstable in disco, and used to be rock solid on ppc64le. + + -- + sru template for systemd upload: + + [impact] + buffer overflow can cause memory corruption; this is seen in failed autopkgtests + + [test case] + see comment 6 + + [regression potential] + the patch is minimal and clearly correct; however the regression potential is around invalid/corrupted keys read from the keyring. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814373 Title: storage / luks / dmsetup regressed (or got better) on ppc64le Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Committed Status in udisks2 package in Ubuntu: Invalid Status in linux source package in Bionic: New Status in systemd source package in Bionic: In Progress Status in udisks2 source package in Bionic: Invalid Status in linux source package in Cosmic: New Status in systemd source package in Cosmic: In Progress Status in udisks2 source package in Cosmic: Invalid Status in linux source package in Disco: New Status in systemd source package in Disco: In Progress Status in udisks2 source package in Disco: Invalid Status in linux source package in Eoan: Confirmed Status in systemd source package in Eoan: Fix Committed Status in udisks2 source package in Eoan: Invalid Status in systemd package in Debian: Unknown Bug description: in disco proposed with new systemd and v4.19 kernel it appears that dmsetup / cryptsetup storage either got better or worse. Devices take very long to activate, and sometimes remain in use during test clean up. This leads to udisks autopkgtest failing on ppc64le and systemd's "storage" autopkgtest is also failing. I've tried to make ppc64le test more resilient, but it's still odd that it became unstable in disco, and used to be rock solid on ppc64le. -- sru template for systemd upload: [impact] buffer overflow can cause memory corruption; this is seen in failed autopkgtests [test case] see comment 6 [regression potential] the patch is minimal and clearly correct; however the regression potential is around invalid/corrupted keys read from the keyring. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814373/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811723] Re: Samba client freeze during write when using higher than vers=1.0
linux-image-4.15.0-50-generic ** Package changed: linux-signed-hwe (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811723 Title: Samba client freeze during write when using higher than vers=1.0 Status in linux package in Ubuntu: Incomplete Bug description: Hello, My issue is that whenever I try to write new files (copy or move) to my file server something in the samba client freezes and I can't do anything samba until the system is rebooted. To get write access I mount with uid ie "sudo mount //server/share /mountpoint -o user=write,uid=1000". Using this command the server and client negotiates smb protocol version 3.02. When this happens the server is still happily serving files to other machines. If I just read files everything works fine. If I connect from a windows client there is no issue. If I add "vers=1.0" everything works but transfers are really slow. Specifying version 3 produces a fail. Trying the same operation (different hw) with Mint 18 Mate produces the same fault. Trying the same operation (with "vers=3.0" set) using SuSE Leap 15.0 KDE live everything works as expected. Both client and server are running fully updated, as of posting, bionic. Using 'dmesg -w' too see what's going on I can see that there is a general protection fault somehow related to cifsd. I am however unable to tell if it is relevant to my issue, from kern.log: Jan 9 21:03:49 ubnu kernel: [ 410.357213] general protection fault: [#1] SMP PTI Jan 9 21:03:49 ubnu kernel: [ 410.357224] Modules linked in: cmac arc4 md4 nls_utf8 cifs ccm fscache rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) thunderbolt bnep binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_hda_codec_realtek snd_soc_acpi snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel intel_rapl btusb x86_pkg_temp_thermal intel_powerclamp btrtl coretemp joydev btbcm snd_hda_codec kvm_intel input_leds kvm irqbypass btintel crct10dif_pclmul crc32_pclmul snd_hda_core ghash_clmulni_intel pcbc snd_hwdep snd_pcm bluetooth ecdh_generic snd_seq_midi snd_seq_midi_event aesni_intel snd_rawmidi aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf snd_seq rtsx_pci_ms snd_seq_device Jan 9 21:03:49 ubnu kernel: [ 410.357357] wmi_bmof snd_timer memstick intel_wmi_thunderbolt snd shpchp soundcore mei_me mei intel_pch_thermal acpi_pad mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 xfs libcrc32c hid_generic usbhid hid rtsx_pci_sdmmc i915 e1000e i2c_algo_bit drm_kms_helper ptp syscopyarea pps_core i2c_i801 sysfillrect sysimgblt rtsx_pci fb_sys_fops drm ahci libahci wmi video Jan 9 21:03:49 ubnu kernel: [ 410.357447] CPU: 2 PID: 1822 Comm: cifsd Tainted: G OE4.15.0-43-generic #46-Ubuntu Jan 9 21:03:49 ubnu kernel: [ 410.357453] Hardware name: /NUC7i3BNB, BIOS BNKBL357.86A.0069.2018.0920.1250 09/20/2018 Jan 9 21:03:49 ubnu kernel: [ 410.357468] RIP: 0010:prefetch_freepointer+0x15/0x30 Jan 9 21:03:49 ubnu kernel: [ 410.357474] RSP: 0018:b16201ae3da0 EFLAGS: 00010282 Jan 9 21:03:49 ubnu kernel: [ 410.357482] RAX: RBX: e90527c744fff71a RCX: 3ea9 Jan 9 21:03:49 ubnu kernel: [ 410.357488] RDX: 3ea8 RSI: e90527c744fff71a RDI: 9d7079255080 Jan 9 21:03:49 ubnu kernel: [ 410.357494] RBP: b16201ae3da0 R08: 9d707ed2b650 R09: b16201ae3db0 Jan 9 21:03:49 ubnu kernel: [ 410.357499] R10: b16201ae3de8 R11: R12: 01011200 Jan 9 21:03:49 ubnu kernel: [ 410.357505] R13: 9d7079255080 R14: 9d7016478c40 R15: 9d7079255080 Jan 9 21:03:49 ubnu kernel: [ 410.357512] FS: () GS:9d707ed0() knlGS: Jan 9 21:03:49 ubnu kernel: [ 410.357519] CS: 0010 DS: ES: CR0: 80050033 Jan 9 21:03:49 ubnu kernel: [ 410.357525] CR2: 7f0a2802d028 CR3: 3760a006 CR4: 003606e0 Jan 9 21:03:49 ubnu kernel: [ 410.357530] Call Trace: Jan 9 21:03:49 ubnu kernel: [ 410.357545] kmem_cache_alloc+0xa2/0x1b0 Jan 9 21:03:49 ubnu kernel: [ 410.357558] ? mempool_alloc_slab+0x15/0x20 Jan 9 21:03:49 ubnu kernel: [ 410.357570] ? wait_woken+0x80/0x80 Jan 9 21:03:49 ubnu kernel: [ 410.357580] mempool_alloc_slab+0x15/0x20 Jan 9 21:03:49 ubnu kernel: [ 410.357590] mempool_alloc+0x71/0x190 Jan 9 21:03:49 ubnu kernel: [ 410.357660] ? smb2_add_credits+0xb0/0x250 [cifs] Jan 9 21:03:49 ubnu kernel: [ 410.357709] cifs_small_buf_get+0x1a/0x30 [cifs] Jan 9 21:03:49 ubnu kernel: [ 410.357751] cifs_demultiplex_thread+0x5c7/0xaf0 [cifs] Jan 9 21:03:49 ubnu kernel: [
[Kernel-packages] [Bug 1811723] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1811723 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811723 Title: Samba client freeze during write when using higher than vers=1.0 Status in linux package in Ubuntu: Incomplete Bug description: Hello, My issue is that whenever I try to write new files (copy or move) to my file server something in the samba client freezes and I can't do anything samba until the system is rebooted. To get write access I mount with uid ie "sudo mount //server/share /mountpoint -o user=write,uid=1000". Using this command the server and client negotiates smb protocol version 3.02. When this happens the server is still happily serving files to other machines. If I just read files everything works fine. If I connect from a windows client there is no issue. If I add "vers=1.0" everything works but transfers are really slow. Specifying version 3 produces a fail. Trying the same operation (different hw) with Mint 18 Mate produces the same fault. Trying the same operation (with "vers=3.0" set) using SuSE Leap 15.0 KDE live everything works as expected. Both client and server are running fully updated, as of posting, bionic. Using 'dmesg -w' too see what's going on I can see that there is a general protection fault somehow related to cifsd. I am however unable to tell if it is relevant to my issue, from kern.log: Jan 9 21:03:49 ubnu kernel: [ 410.357213] general protection fault: [#1] SMP PTI Jan 9 21:03:49 ubnu kernel: [ 410.357224] Modules linked in: cmac arc4 md4 nls_utf8 cifs ccm fscache rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) thunderbolt bnep binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_hda_codec_realtek snd_soc_acpi snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel intel_rapl btusb x86_pkg_temp_thermal intel_powerclamp btrtl coretemp joydev btbcm snd_hda_codec kvm_intel input_leds kvm irqbypass btintel crct10dif_pclmul crc32_pclmul snd_hda_core ghash_clmulni_intel pcbc snd_hwdep snd_pcm bluetooth ecdh_generic snd_seq_midi snd_seq_midi_event aesni_intel snd_rawmidi aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf snd_seq rtsx_pci_ms snd_seq_device Jan 9 21:03:49 ubnu kernel: [ 410.357357] wmi_bmof snd_timer memstick intel_wmi_thunderbolt snd shpchp soundcore mei_me mei intel_pch_thermal acpi_pad mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 xfs libcrc32c hid_generic usbhid hid rtsx_pci_sdmmc i915 e1000e i2c_algo_bit drm_kms_helper ptp syscopyarea pps_core i2c_i801 sysfillrect sysimgblt rtsx_pci fb_sys_fops drm ahci libahci wmi video Jan 9 21:03:49 ubnu kernel: [ 410.357447] CPU: 2 PID: 1822 Comm: cifsd Tainted: G OE4.15.0-43-generic #46-Ubuntu Jan 9 21:03:49 ubnu kernel: [ 410.357453] Hardware name: /NUC7i3BNB, BIOS BNKBL357.86A.0069.2018.0920.1250 09/20/2018 Jan 9 21:03:49 ubnu kernel: [ 410.357468] RIP: 0010:prefetch_freepointer+0x15/0x30 Jan 9 21:03:49 ubnu kernel: [ 410.357474] RSP: 0018:b16201ae3da0 EFLAGS: 00010282 Jan 9 21:03:49 ubnu kernel: [ 410.357482] RAX: RBX: e90527c744fff71a RCX: 3ea9 Jan 9 21:03:49 ubnu kernel: [ 410.357488] RDX: 3ea8 RSI: e90527c744fff71a RDI: 9d7079255080 Jan 9 21:03:49 ubnu kernel: [ 410.357494] RBP: b16201ae3da0 R08: 9d707ed2b650 R09: b16201ae3db0 Jan 9 21:03:49 ubnu kernel: [ 410.357499] R10: b16201ae3de8 R11: R12: 01011200 Jan 9 21:03:49 ubnu kernel: [ 410.357505] R13: 9d7079255080 R14: 9d7016478c40 R15: 9d7079255080 Jan 9 21:03:49 ubnu kernel: [ 410.357512] FS: () GS:9d707ed0() knlGS: Jan 9 21:03:49 ubnu kernel: [ 410.357519] CS: 0010 DS: ES: CR0: 80050033 Jan 9 21:03:49 ubnu kernel: [ 410.357525] CR2: 7f0a2802d028 CR3: 3760a006 CR4: 003606e0 Jan 9 21:03:49 ubnu kernel: [ 410.357530] Call Trace: Jan 9 21:03:49 ubnu kernel: [ 410.357545] kmem_cache_alloc+0xa2/0x1b0 Jan 9 21:03:49 ubnu kernel: [ 410.357558] ?
[Kernel-packages] [Bug 1811723] [NEW] Samba client freeze during write when using higher than vers=1.0
You have been subscribed to a public bug: Hello, My issue is that whenever I try to write new files (copy or move) to my file server something in the samba client freezes and I can't do anything samba until the system is rebooted. To get write access I mount with uid ie "sudo mount //server/share /mountpoint -o user=write,uid=1000". Using this command the server and client negotiates smb protocol version 3.02. When this happens the server is still happily serving files to other machines. If I just read files everything works fine. If I connect from a windows client there is no issue. If I add "vers=1.0" everything works but transfers are really slow. Specifying version 3 produces a fail. Trying the same operation (different hw) with Mint 18 Mate produces the same fault. Trying the same operation (with "vers=3.0" set) using SuSE Leap 15.0 KDE live everything works as expected. Both client and server are running fully updated, as of posting, bionic. Using 'dmesg -w' too see what's going on I can see that there is a general protection fault somehow related to cifsd. I am however unable to tell if it is relevant to my issue, from kern.log: Jan 9 21:03:49 ubnu kernel: [ 410.357213] general protection fault: [#1] SMP PTI Jan 9 21:03:49 ubnu kernel: [ 410.357224] Modules linked in: cmac arc4 md4 nls_utf8 cifs ccm fscache rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) thunderbolt bnep binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_hda_codec_realtek snd_soc_acpi snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel intel_rapl btusb x86_pkg_temp_thermal intel_powerclamp btrtl coretemp joydev btbcm snd_hda_codec kvm_intel input_leds kvm irqbypass btintel crct10dif_pclmul crc32_pclmul snd_hda_core ghash_clmulni_intel pcbc snd_hwdep snd_pcm bluetooth ecdh_generic snd_seq_midi snd_seq_midi_event aesni_intel snd_rawmidi aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf snd_seq rtsx_pci_ms snd_seq_device Jan 9 21:03:49 ubnu kernel: [ 410.357357] wmi_bmof snd_timer memstick intel_wmi_thunderbolt snd shpchp soundcore mei_me mei intel_pch_thermal acpi_pad mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 xfs libcrc32c hid_generic usbhid hid rtsx_pci_sdmmc i915 e1000e i2c_algo_bit drm_kms_helper ptp syscopyarea pps_core i2c_i801 sysfillrect sysimgblt rtsx_pci fb_sys_fops drm ahci libahci wmi video Jan 9 21:03:49 ubnu kernel: [ 410.357447] CPU: 2 PID: 1822 Comm: cifsd Tainted: G OE4.15.0-43-generic #46-Ubuntu Jan 9 21:03:49 ubnu kernel: [ 410.357453] Hardware name: /NUC7i3BNB, BIOS BNKBL357.86A.0069.2018.0920.1250 09/20/2018 Jan 9 21:03:49 ubnu kernel: [ 410.357468] RIP: 0010:prefetch_freepointer+0x15/0x30 Jan 9 21:03:49 ubnu kernel: [ 410.357474] RSP: 0018:b16201ae3da0 EFLAGS: 00010282 Jan 9 21:03:49 ubnu kernel: [ 410.357482] RAX: RBX: e90527c744fff71a RCX: 3ea9 Jan 9 21:03:49 ubnu kernel: [ 410.357488] RDX: 3ea8 RSI: e90527c744fff71a RDI: 9d7079255080 Jan 9 21:03:49 ubnu kernel: [ 410.357494] RBP: b16201ae3da0 R08: 9d707ed2b650 R09: b16201ae3db0 Jan 9 21:03:49 ubnu kernel: [ 410.357499] R10: b16201ae3de8 R11: R12: 01011200 Jan 9 21:03:49 ubnu kernel: [ 410.357505] R13: 9d7079255080 R14: 9d7016478c40 R15: 9d7079255080 Jan 9 21:03:49 ubnu kernel: [ 410.357512] FS: () GS:9d707ed0() knlGS: Jan 9 21:03:49 ubnu kernel: [ 410.357519] CS: 0010 DS: ES: CR0: 80050033 Jan 9 21:03:49 ubnu kernel: [ 410.357525] CR2: 7f0a2802d028 CR3: 3760a006 CR4: 003606e0 Jan 9 21:03:49 ubnu kernel: [ 410.357530] Call Trace: Jan 9 21:03:49 ubnu kernel: [ 410.357545] kmem_cache_alloc+0xa2/0x1b0 Jan 9 21:03:49 ubnu kernel: [ 410.357558] ? mempool_alloc_slab+0x15/0x20 Jan 9 21:03:49 ubnu kernel: [ 410.357570] ? wait_woken+0x80/0x80 Jan 9 21:03:49 ubnu kernel: [ 410.357580] mempool_alloc_slab+0x15/0x20 Jan 9 21:03:49 ubnu kernel: [ 410.357590] mempool_alloc+0x71/0x190 Jan 9 21:03:49 ubnu kernel: [ 410.357660] ? smb2_add_credits+0xb0/0x250 [cifs] Jan 9 21:03:49 ubnu kernel: [ 410.357709] cifs_small_buf_get+0x1a/0x30 [cifs] Jan 9 21:03:49 ubnu kernel: [ 410.357751] cifs_demultiplex_thread+0x5c7/0xaf0 [cifs] Jan 9 21:03:49 ubnu kernel: [ 410.357762] ? __schedule+0x299/0x8a0 Jan 9 21:03:49 ubnu kernel: [ 410.35] kthread+0x121/0x140 Jan 9 21:03:49 ubnu kernel: [ 410.357815] ? cifs_handle_standard+0x190/0x190 [cifs] Jan 9 21:03:49 ubnu kernel: [ 410.357827] ? kthread_create_worker_on_cpu+0x70/0x70 Jan 9 21:03:49 ubnu kernel: [ 410.357838] ? do_syscall_64+0x73/0x130 Jan 9 21:03:49 ubnu kernel: [ 410.357847] ? SyS_exit_group+0x14/0x20 Jan 9 21:03:49
[Kernel-packages] [Bug 1831070] Re: package nvidia-dkms-390 390.116-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status
** Tags removed: need-duplicate-check -- 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/1831070 Title: package nvidia-dkms-390 390.116-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 1 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: Just happened trying to upgrade a machine in two immediate steps bionic->cosmic->disco. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: nvidia-dkms-390 390.116-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-20.21-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Thu May 30 12:58:24 2019 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-02-20 (463 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.6ubuntu1 apt 1.8.1 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.116-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to disco on 2019-05-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1831070/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829211] Re: linux-fips: 4.15.0-1008.9 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1829219 phase: Ready for Testing phase-changed: Thursday, 23. May 2019 20:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress - regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829211 Title: linux-fips: 4.15.0-1008.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1829219 phase: Ready for Testing phase-changed: Thursday, 23. May 2019 20:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829211/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831070] [NEW] package nvidia-dkms-390 390.116-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit stat
Public bug reported: Just happened trying to upgrade a machine in two immediate steps bionic->cosmic->disco. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: nvidia-dkms-390 390.116-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-20.21-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Thu May 30 12:58:24 2019 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-02-20 (463 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.6ubuntu1 apt 1.8.1 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.116-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to disco on 2019-05-30 (0 days ago) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package disco -- 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/1831070 Title: package nvidia-dkms-390 390.116-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 1 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: Just happened trying to upgrade a machine in two immediate steps bionic->cosmic->disco. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: nvidia-dkms-390 390.116-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-20.21-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Thu May 30 12:58:24 2019 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-02-20 (463 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.6ubuntu1 apt 1.8.1 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.116-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to disco on 2019-05-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1831070/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829211] Re: linux-fips: 4.15.0-1008.9 -proposed tracker
4.15.0-1008.9 - fips Regression test CMPL, RTB. Issue to note in amd64: ubuntu_kernel_selftests - global.get_metadata in seccomp (bug 1811057) raw_skew in timer (bug 1811194) ubuntu_kvm_unit_tests - proxy issue for Intel Cloud (bug 1828786) ubuntu_ltp - binfmt_misc02 (bug 1822246) proc01 (bug 1829849) cpuset_base_ops (bug 1830359) cpuset_sched_domains (bug 1830361) cpuset_load_balance in controllers (bug 1830360) cpuset_memory_spread (bug 1830585) memcg_max_usage_in_bytes (bug 1829979) memcg_stat (bug 1829983) memcg_use_hierarchy (bug 1829989) memcg_usage_in_bytes (bug 1829984) getaddrinfo_01 (bug 1829995) leapsec_timer (bug 1829971) runpwtests03 (bug 1830362) mkswap01_sh (bug 1830584) zram01 (bug 1829991) zram02 (bug 1829992) getaddrinfo_01 (bug 1829995) cve-2017-17053 (bug 1830011) ubuntu_ltp_syscalls - inotify08 (bug 1775784) fanotify09-2 (bug 1804594) sync_file_range02 (bug 1819116) move_pages12 (bug 1831043) ubuntu_ramfs_stress - proxy issue for Intel Cloud (bug 1828786) ubuntu_stress_smoke_test - proxy issue for Intel Cloud (bug 1828786) ubuntu_unionmount_overlayfs_suite - proxy issue for Intel Cloud (bug 1828786) ubuntu_vfat_stress - proxy issue for Intel Cloud (bug 1828786) 42 / 49 tests were run, missing: ubuntu_boot, ubuntu_bpf, ubuntu_bpf_jit, ubuntu_btrfs_kernel_fixes, ubuntu_cts_kernel, ubuntu_zfs_fstest, ubuntu_zfs_xfs_generic Issue to note in s390x: ubuntu_kernel_selftests - reuseport_dualstack in net (bug 1812843) TRACE_syscall in seccomp (bug 1812824) global.get_metadata in seccomp (bug 1811057) ubuntu_ltp_syscalls - msgstress03 (bug 1797341) inotify08 (bug 1775784) fanotify09-2 (bug 1804594) sync_file_range02 (bug 1819116) settimeofday01 Note: Missing ubuntu_btrfs_kernel_fixes for s390x (bug 1809860) Note: Missing tests in s390x is caused by the test list in CKCT ** 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 in Ubuntu. https://bugs.launchpad.net/bugs/1829211 Title: linux-fips: 4.15.0-1008.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1829219 phase: Ready for Testing phase-changed: Thursday, 23. May 2019 20:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829211/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831065] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1831065 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1831065 Title: does not detect headphone when there is no other output devices Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: These two patches are already in the kernel-v5.0, so only B and C need these two patches. [Impact] On a Dell machine, there is no other output devices but a headphone on it, when plugging headset, the headset-mic can't work. [Fix] The headphone detection method is buggy, the driver can't detect the headphone, then the driver will not initialize for headset-mic, after applying these patches, the problem is fixed. [Test Case] Plug headset and record the sound from headset-mic, it works well. [Regression Risk] Low. the patch just change the headphone detection function, and the function is already in the kernel from 5.0-rc, no bug is reported. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1831065/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831065] Re: does not detect headphone when there is no other output devices
** Description changed: - Headset doesn't work + These two patches are already in the kernel-v5.0, so only B and C need + these two patches. + + [Impact] + On a Dell machine, there is no other output devices but a headphone + on it, when plugging headset, the headset-mic can't work. + + [Fix] + The headphone detection method is buggy, the driver can't detect + the headphone, then the driver will not initialize for headset-mic, + after applying these patches, the problem is fixed. + + [Test Case] + Plug headset and record the sound from headset-mic, it works well. + + [Regression Risk] + Low. the patch just change the headphone detection function, and the + function is already in the kernel from 5.0-rc, no bug is reported. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1831065 Title: does not detect headphone when there is no other output devices Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: These two patches are already in the kernel-v5.0, so only B and C need these two patches. [Impact] On a Dell machine, there is no other output devices but a headphone on it, when plugging headset, the headset-mic can't work. [Fix] The headphone detection method is buggy, the driver can't detect the headphone, then the driver will not initialize for headset-mic, after applying these patches, the problem is fixed. [Test Case] Plug headset and record the sound from headset-mic, it works well. [Regression Risk] Low. the patch just change the headphone detection function, and the function is already in the kernel from 5.0-rc, no bug is reported. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1831065/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831065] [NEW] does not detect headphone when there is no other output devices
Public bug reported: Headset doesn't work ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: High Assignee: Hui Wang (hui.wang) Status: New ** Tags: originate-from-1830004 somerville ** Tags added: originate-from-1830004 somerville ** Changed in: linux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1831065 Title: does not detect headphone when there is no other output devices Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: Headset doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1831065/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830941] Re: linux: 4.4.0-150.176 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- boot-testing-requested: true - phase: Promote to Proposed - phase-changed: Thursday, 30. May 2019 08:32 UTC + bugs-spammed: true + phase: Testing + phase-changed: Thursday, 30. May 2019 11:31 UTC reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + certification-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + snap-release-to-beta: 'Pending -- snap pc-kernel not in expected channel(s): arch=amd64:channel=latest/beta + arch=i386:channel=latest/beta' + snap-release-to-edge: 'Pending -- snap pc-kernel not in expected channel(s): arch=amd64:channel=latest/edge + arch=i386:channel=latest/edge' + verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830941 Title: linux: 4.4.0-150.176 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Thursday, 30. May 2019 11:31 UTC reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: 'Pending -- snap pc-kernel not in expected channel(s): arch=amd64:channel=latest/beta arch=i386:channel=latest/beta' snap-release-to-edge: 'Pending -- snap pc-kernel not in expected channel(s): arch=amd64:channel=latest/edge arch=i386:channel=latest/edge' verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1830941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830941] Re: linux: 4.4.0-150.176 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830941 Title: linux: 4.4.0-150.176 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- boot-testing-requested: true phase: Promote to Proposed phase-changed: Thursday, 30. May 2019 08:32 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1830941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830890] Re: glibc 2.23-0ubuntu11 ADT test failure with linux 4.4.0-149.175
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830890 Title: glibc 2.23-0ubuntu11 ADT test failure with linux 4.4.0-149.175 Status in glibc package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in glibc source package in Xenial: Invalid Status in linux source package in Xenial: Fix Committed Bug description: [Impact] Some glibc testcases are regressing on i386 after the following commit was applied to xenial/linux as part of upstream stable update 4.4.179: commit 379d98ddf41344273d9718556f761420f4dc80b3 Author: Alistair Strachan Date: Fri Aug 3 10:39:31 2018 -0700 x86: vdso: Use $LD instead of $CC to link which accidentally broke unwinding from userspace, because ld would strip the .eh_frame sections when linking. Test logs: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/g/glibc/20190528_085308_d03ca@/log.gz [Fix] The following commit fixes the issue: commit cd01544a268ad8ee5b1dfe42c4393f1095f86879 Author: Alistair Strachan Date: Fri Dec 14 14:36:37 2018 -0800 x86/vdso: Pass --eh-frame-hdr to the linker It was applied to 4.4.180, but we need to apply it before otherwise xenial/linux will be released with a regression. [Test] ADT tests for glibc. [Regression Potential] Low. One line patch to Makefile which fixes a known regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1830890/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831043] Re: move_pages12 test from ubuntu_ltp_syscalls failed on B
** Description changed: - This is a new test case landed 8 days ago: + This is a new test case landed 8 days ago, but we already have the patch in B, and it looks like this is not failing across all the nodes: + move_pages12.c:114: FAIL: move_pages failed: ENOMEM + <<>> tag=move_pages12 stime=1559209337 cmdline="move_pages12" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s move_pages12.c:235: INFO: Free RAM 31883452 kB move_pages12.c:253: INFO: Increasing 2048kB hugepages pool on node 0 to 4 move_pages12.c:263: INFO: Increasing 2048kB hugepages pool on node 1 to 4 move_pages12.c:179: INFO: Allocating and freeing 4 hugepages on node 0 move_pages12.c:179: INFO: Allocating and freeing 4 hugepages on node 1 move_pages12.c:169: PASS: Bug not reproduced move_pages12.c:114: FAIL: move_pages failed: ENOMEM move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS Summary: passed 1 failed 998 skipped 0 warnings 0 <<>> initiation_status="ok" duration=4 termination_type=exited termination_id=1 corefile=no cutime=93 cstime=474 <<>> ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: - total 0 - crw-rw 1 root audio 116, 1 May 30 09:29 seq - crw-rw 1 root audio 116, 33 May 30 09:29 timer + total 0 + crw-rw 1 root audio 116, 1 May 30 09:29 seq + crw-rw 1 root audio 116, 33 May 30 09:29 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu May 30 09:42:46 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: - + ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro RelatedPackageVersions: - linux-restricted-modules-4.15.0-50-generic N/A - linux-backports-modules-4.15.0-50-generic N/A - linux-firmware 1.173.6 + linux-restricted-modules-4.15.0-50-generic N/A + linux-backports-modules-4.15.0-50-generic N/A + linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1831043 Title: move_pages12 test from ubuntu_ltp_syscalls failed on B Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: This is a new test case landed 8 days ago, but we already have the patch in B, and it looks like this is not failing across all the nodes: move_pages12.c:114: FAIL: move_pages failed: ENOMEM <<>> tag=move_pages12 stime=1559209337 cmdline="move_pages12" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s move_pages12.c:235: INFO: Free RAM 31883452 kB move_pages12.c:253: INFO: Increasing 2048kB hugepages pool on node 0 to 4 move_pages12.c:263: INFO: Increasing 2048kB hugepages pool on node 1 to 4 move_pages12.c:179: INFO: Allocating and freeing 4 hugepages on node 0 move_pages12.c:179: INFO: Allocating and freeing 4 hugepages on node 1 move_pages12.c:169: PASS: Bug not reproduced move_pages12.c:114: FAIL: move_pages failed: ENOMEM move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS Summary: passed 1 failed 998 skipped 0 warnings 0 <<>> initiation_status="ok" duration=4 termination_type=exited termination_id=1 corefile=no cutime=93 cstime=474 <<>> ProblemType: Bug DistroRelease: Ubuntu 18.04 Package:
[Kernel-packages] [Bug 1791405] Re: bluetooth always in discoverable mode (security issue)
** No longer affects: bluez (Ubuntu Bionic) ** No longer affects: bluez (Ubuntu Cosmic) ** No longer affects: bluez (Ubuntu Disco) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1791405 Title: bluetooth always in discoverable mode (security issue) Status in bluez package in Ubuntu: New Status in gnome-bluetooth package in Ubuntu: Fix Released Status in gnome-bluetooth source package in Bionic: Fix Released Status in gnome-bluetooth source package in Cosmic: Fix Released Status in gnome-bluetooth source package in Disco: Fix Released Status in bluez source package in Eoan: Fix Committed Status in gnome-bluetooth package in Fedora: Won't Fix Bug description: Excerpt from a similar report (https://bugzilla.redhat.com/show_bug.cgi?id=1602985) : Opening the Bluetooth settings will make the device discoverable again, but does not make the device undiscoverable after the settings are closed (this is not intended behavior; devices should only be discoverable when the bluetooth settings UI is open). There seem to be a merge request : https://gitlab.gnome.org/GNOME/gnome-bluetooth/merge_requests/1 Could you please merge it asap, it should be treated as a security issue IMHO. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1791405/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831043] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux (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/1831043 Title: move_pages12 test from ubuntu_ltp_syscalls failed on B Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: This is a new test case landed 8 days ago: <<>> tag=move_pages12 stime=1559209337 cmdline="move_pages12" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s move_pages12.c:235: INFO: Free RAM 31883452 kB move_pages12.c:253: INFO: Increasing 2048kB hugepages pool on node 0 to 4 move_pages12.c:263: INFO: Increasing 2048kB hugepages pool on node 1 to 4 move_pages12.c:179: INFO: Allocating and freeing 4 hugepages on node 0 move_pages12.c:179: INFO: Allocating and freeing 4 hugepages on node 1 move_pages12.c:169: PASS: Bug not reproduced move_pages12.c:114: FAIL: move_pages failed: ENOMEM move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS Summary: passed 1 failed 998 skipped 0 warnings 0 <<>> initiation_status="ok" duration=4 termination_type=exited termination_id=1 corefile=no cutime=93 cstime=474 <<>> ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 30 09:29 seq crw-rw 1 root audio 116, 33 May 30 09:29 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu May 30 09:42:46 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1831043/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831043] Re: move_pages12 test from ubuntu_ltp_syscalls failed on B
Test passed on Cosmic. ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1831043 Title: move_pages12 test from ubuntu_ltp_syscalls failed on B Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: This is a new test case landed 8 days ago: <<>> tag=move_pages12 stime=1559209337 cmdline="move_pages12" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s move_pages12.c:235: INFO: Free RAM 31883452 kB move_pages12.c:253: INFO: Increasing 2048kB hugepages pool on node 0 to 4 move_pages12.c:263: INFO: Increasing 2048kB hugepages pool on node 1 to 4 move_pages12.c:179: INFO: Allocating and freeing 4 hugepages on node 0 move_pages12.c:179: INFO: Allocating and freeing 4 hugepages on node 1 move_pages12.c:169: PASS: Bug not reproduced move_pages12.c:114: FAIL: move_pages failed: ENOMEM move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS Summary: passed 1 failed 998 skipped 0 warnings 0 <<>> initiation_status="ok" duration=4 termination_type=exited termination_id=1 corefile=no cutime=93 cstime=474 <<>> ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 30 09:29 seq crw-rw 1 root audio 116, 33 May 30 09:29 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu May 30 09:42:46 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1831043/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831043] [NEW] move_pages12 test from ubuntu_ltp_syscalls failed on B
Public bug reported: This is a new test case landed 8 days ago: <<>> tag=move_pages12 stime=1559209337 cmdline="move_pages12" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s move_pages12.c:235: INFO: Free RAM 31883452 kB move_pages12.c:253: INFO: Increasing 2048kB hugepages pool on node 0 to 4 move_pages12.c:263: INFO: Increasing 2048kB hugepages pool on node 1 to 4 move_pages12.c:179: INFO: Allocating and freeing 4 hugepages on node 0 move_pages12.c:179: INFO: Allocating and freeing 4 hugepages on node 1 move_pages12.c:169: PASS: Bug not reproduced move_pages12.c:114: FAIL: move_pages failed: ENOMEM move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS Summary: passed 1 failed 998 skipped 0 warnings 0 <<>> initiation_status="ok" duration=4 termination_type=exited termination_id=1 corefile=no cutime=93 cstime=474 <<>> ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 30 09:29 seq crw-rw 1 root audio 116, 33 May 30 09:29 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu May 30 09:42:46 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic uec-images ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1831043 Title: move_pages12 test from ubuntu_ltp_syscalls failed on B Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Bionic: New Bug description: This is a new test case landed 8 days ago: <<>> tag=move_pages12 stime=1559209337 cmdline="move_pages12" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s move_pages12.c:235: INFO: Free RAM 31883452 kB move_pages12.c:253: INFO: Increasing 2048kB hugepages pool on node 0 to 4 move_pages12.c:263: INFO: Increasing 2048kB hugepages pool on node 1 to 4 move_pages12.c:179: INFO: Allocating and freeing 4 hugepages on node 0 move_pages12.c:179: INFO: Allocating and freeing 4 hugepages on node 1 move_pages12.c:169: PASS: Bug not reproduced move_pages12.c:114: FAIL: move_pages failed: ENOMEM move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS Summary: passed 1 failed 998 skipped 0 warnings 0 <<>> initiation_status="ok" duration=4 termination_type=exited termination_id=1 corefile=no cutime=93 cstime=474 <<>> ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 30 09:29 seq crw-rw 1 root audio 116, 33 May 30 09:29 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error:
[Kernel-packages] [Bug 1830941] Re: linux: 4.4.0-150.176 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- boot-testing-requested: true phase: Promote to Proposed phase-changed: Thursday, 30. May 2019 08:32 UTC reason: - promote-to-proposed: Pending -- packages copied to Proposed signed:building + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830941 Title: linux: 4.4.0-150.176 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing 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 verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- boot-testing-requested: true phase: Promote to Proposed phase-changed: Thursday, 30. May 2019 08:32 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1830941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1809704] Re: efivarfs test in ubuntu_kernel_selftest failed on the second run
** No longer affects: linux (Ubuntu Eoan) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1809704 Title: efivarfs test in ubuntu_kernel_selftest failed on the second run Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: New Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Status in linux source package in Disco: New Bug description: This seems to be an issue to the test case, if you run the test suite twice, it will fail on the second run. The first run will create the test file: $ ll /sys/firmware/efi/efivars/test_create_read-210be57c-9849-4fc7-a635-e6382d1aec27 -rw--- 1 root root 0 Dec 24 07:16 /sys/firmware/efi/efivars/test_create_read-210be57c-9849-4fc7-a635-e6382d1aec27 This is cause the open(O_WRONLY) test in test_create_read failed with premission denied on the second run. This issue can be reproduced with upstream kernel tree on Xenial as well. $ sudo make -C linux/tools/testing/selftests TARGETS=efivarfs run_tests make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' for TARGET in efivarfs; do \ make -C $TARGET; \ done; make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/efivarfs' make[1]: Nothing to be done for 'all'. make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/efivarfs' for TARGET in efivarfs; do \ make -C $TARGET run_tests; \ done; make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/efivarfs' running test_create ./efivarfs.sh: line 48: /sys/firmware/efi/efivars/test_create-210be57c-9849-4fc7-a635-e6382d1aec27: Permission denied [PASS] running test_create_empty ./efivarfs.sh: line 65: /sys/firmware/efi/efivars/test_create_empty-210be57c-9849-4fc7-a635-e6382d1aec27: Permission denied [PASS] running test_create_read open(O_WRONLY): Permission denied [FAIL] running test_delete [PASS] running test_zero_size_delete [PASS] running test_open_unlink [PASS] running test_valid_filenames [PASS] running test_invalid_filenames [PASS] selftests: efivarfs.sh [FAIL] make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/efivarfs' make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-141-generic 4.4.0-141.167 ProcVersionSignature: User Name 4.4.0-141.167-generic 4.4.162 Uname: Linux 4.4.0-141-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 24 05:10 seq crw-rw 1 root audio 116, 33 Dec 24 05:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: [92859.670497] smpboot: CPU 111 is now offline [92859.723040] kvm: disabled by bios [92859.750562] smpboot: Booting Node 1 Processor 111 APIC 0x7d [92859.821706] kvm: disabled by bios Date: Tue Dec 25 06:30:01 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b1f:03e9 Insyde Software Corp. Bus 001 Device 002: ID :0001 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation S2600WFT PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-141-generic.efi.signed root=UUID=e93f24ed-4e90-4ccb-ba6d-f3b97fe0436f ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-141-generic N/A linux-backports-modules-4.4.0-141-generic N/A linux-firmware 1.157.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2016 dmi.bios.vendor: Intel Corporation dmi.bios.version:
[Kernel-packages] [Bug 1763323] Re: ubuntu_fan_smoke_test failed on 4.4/4.15/4.18 kvm & azure kernel
Test disabled in ACT for KVM kernels https://kernel.ubuntu.com/git/ubuntu/autotest-client- tests.git/commit/?id=be027ae34aa565fb640697b56d862fb087a0ad0b -- 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/1763323 Title: ubuntu_fan_smoke_test failed on 4.4/4.15/4.18 kvm & azure kernel Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Triaged Status in linux-kvm package in Ubuntu: New Status in linux source package in Xenial: Triaged Status in linux-kvm source package in Xenial: New Status in linux source package in Bionic: New Status in linux-kvm source package in Bionic: New Status in linux source package in Cosmic: New Status in linux-kvm source package in Cosmic: New Bug description: The "enable disable fan test" will fail with Xenial KVM kernel Error message: RTNETLINK answers: Operation not supported /usr/sbin/fanctl: ip link add ftun0 type vxlan id 16384000 dev ens4 dstport 0 local 10.246.72.56 fan-map 250.0.0.0/8:10.246.0.0/16 /usr/sbin/fanctl: WARNING: ftun0: failed to configure address translation RTNETLINK answers: Cannot assign requested address iptables v1.6.0: Couldn't load target `fan-egress':No such file or directory Try `iptables -h' or 'iptables --help' for more information. iptables: Bad rule (does a matching rule exist in that chain?). iptables: Bad rule (does a matching rule exist in that chain?). iptables: No chain/target/match by that name. rm: cannot remove '/run/ubuntu-fan/nat-core': No such file or directory /usr/sbin/fanatic: unable to bring fan up, unable to configure ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1021-kvm 4.4.0-1021.26 ProcVersionSignature: User Name 4.4.0-1021.26-kvm 4.4.117 Uname: Linux 4.4.0-1021-kvm x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Thu Apr 12 10:22:57 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1763323/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828989] Re: ftrace in ubuntu_kernel_selftests complains "Illegal number" because of the absence of tput
https://lists.ubuntu.com/archives/kernel-team/2019-May/100983.html ** No longer affects: linux (Ubuntu Eoan) ** Description changed: == Justification == Issue found in Disco, the ftrace test will complain about: ./ftracetest: 163: [: Illegal number: This is because the tput command failed and returns nothing for the shell script comparison. == Fix == * 0e27ded1 (selftests/ftrace: Handle the absence of tput) - This patches can be cherry-picked into Disco and Eoan after the patch - for bug 1828995 has landed (4ce55a9c). + This patches can be cherry-picked into Disco after the patch for bug + 1828995 has landed (4ce55a9c). == Test == Tested with a P8 box, problem can be solved with this patch. == Regression Potential == No regression is expected. It's just fixing the testing tool. ** Tags added: disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828989 Title: ftrace in ubuntu_kernel_selftests complains "Illegal number" because of the absence of tput Status in linux package in Ubuntu: In Progress Status in linux source package in Disco: In Progress Bug description: == Justification == Issue found in Disco, the ftrace test will complain about: ./ftracetest: 163: [: Illegal number: This is because the tput command failed and returns nothing for the shell script comparison. == Fix == * 0e27ded1 (selftests/ftrace: Handle the absence of tput) This patches can be cherry-picked into Disco after the patch for bug 1828995 has landed (4ce55a9c). == Test == Tested with a P8 box, problem can be solved with this patch. == Regression Potential == No regression is expected. It's just fixing the testing tool. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828989/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830941] Re: linux: 4.4.0-150.176 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- boot-testing-requested: true - phase: Ready for Promote to Proposed - phase-changed: Thursday, 30. May 2019 03:32 UTC + phase: Promote to Proposed + phase-changed: Thursday, 30. May 2019 08:32 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Pending -- packages copied to Proposed signed:building -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830941 Title: linux: 4.4.0-150.176 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing 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 verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- boot-testing-requested: true phase: Promote to Proposed phase-changed: Thursday, 30. May 2019 08:32 UTC reason: promote-to-proposed: Pending -- packages copied to Proposed signed:building To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1830941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830941] Re: linux: 4.4.0-150.176 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830941 Title: linux: 4.4.0-150.176 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing 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 verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- boot-testing-requested: true phase: Promote to Proposed phase-changed: Thursday, 30. May 2019 08:32 UTC reason: promote-to-proposed: Pending -- packages copied to Proposed signed:building To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1830941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
