[Kernel-packages] [Bug 1839214] Re: Setting vm.overcommit_kbytes = 0 made the entire system explode.
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839214 Title: Setting vm.overcommit_kbytes = 0 made the entire system explode. Status in linux package in Ubuntu: Expired Bug description: On Ubuntu 16.04 LTS and the newest kernel 4.4.0-157, I tried the following command: echo "vm.overcommit_memory = 2" >> /etc/sysctl.conf echo "vm.overcommit_kbytes = 0" >> /etc/sysctl.conf sysctl -p Then I can't reboot, all the commands are invalid, the system explodes. After a forced restart, I can't even connect it with ssh. #reboot reboot -bash: fork: Cannot allocate memory After some searching and inspection, I find the default value of vm.overcommit_kbytes is 0, so why set it to 0 again will get such a result? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839214/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839216] Re: xenial VM hangs copying block device
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839216 Title: xenial VM hangs copying block device Status in linux package in Ubuntu: Expired Bug description: With a Xenial kernel running in a VM (32 cores and 65536 MB RAM), the following script hangs in the dd command: == #!/bin/bash dd if=/dev/zero of=in.bin bs=1 seek=6442506751 count=1 cp in.bin out.bin IN=$(losetup --show -f in.bin) OUT=$(losetup --show -f out.bin) typeset -i i=1 while true; do echo $i $(date) dd if=$IN of=$OUT bs=128k i=i+1 done == The trace (sorry, I don't have the exact kernel version... I found this mid-June 2019) looks like: # cat /proc/5230/stack [<0>] io_schedule+0x16/0x40 [<0>] wbt_wait+0x234/0x390 [<0>] blk_mq_make_request+0x103/0x590 [<0>] generic_make_request+0x122/0x2f0 [<0>] submit_bio+0x73/0x150 [<0>] submit_bh_wbc+0x17a/0x1b0 [<0>] __block_write_full_page+0x15b/0x400 [<0>] block_write_full_page+0x10c/0x130 [<0>] blkdev_writepage+0x18/0x20 [<0>] __writepage+0x1d/0x50 [<0>] write_cache_pages+0x228/0x4b0 [<0>] generic_writepages+0x5c/0x90 [<0>] blkdev_writepages+0x2f/0x40 [<0>] do_writepages+0x1f/0x70 [<0>] __filemap_fdatawrite_range+0xc6/0x100 [<0>] filemap_write_and_wait+0x31/0x90 [<0>] __blkdev_put+0x7a/0x210 [<0>] blkdev_put+0x4c/0xd0 [<0>] blkdev_close+0x34/0x70 [<0>] __fput+0xea/0x220 [<0>] fput+0xe/0x10 [<0>] task_work_run+0x9a/0xc0 [<0>] exit_to_usermode_loop+0xce/0xd0 [<0>] do_syscall_64+0x116/0x150 [<0>] entry_SYSCALL_64_after_hwframe+0x42/0xb7 [<0>] 0x If we have used strace on the process, we find that dd is inside "close(1)" as it closes the output file. I don't know if this would reproduce on actual hardware, as I don't have a machine that large to play with. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839216/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581088] Re: Middle mouse (wheel-click) button stopped working after upgrade to 16.04
My M185 didn't register middle-click (bottom 2) neither, after trick #91, sometimes middle-click registered as bottom 4, mostly 2, and sometimes nothing, with a similar experience to #99. So I repeated #91 and ran `xinput set-button-map 4 1 2 3 2 2` and for now everything is working and solid. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1581088 Title: Middle mouse (wheel-click) button stopped working after upgrade to 16.04 Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to 16.04 clicking the middle mouse button (scroll wheel) on my Logitech M185 stopped working. xev does not even show the event for clicking the wheel, while it shows other button clicks and scroll wheel up/down events. xinput list shows the USB receiver 2 times: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=9[slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=10 [slave pointer (2)] ⎜ ↳ HID 046a:0023 id=13 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=16 [slave pointer (2)] ⎜ ↳ TPPS/2 IBM TrackPoint id=17 [slave pointer (2)] Listing the capabilities looks like this: $ xinput list 9 Logitech USB Receiver id=9[slave pointer (2)] Reporting 7 classes: Class originated from: 9. Type: XIButtonClass Buttons supported: 24 Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" "Button Side" "Button Extra" "Button Forward" "Button Back" "Button Task" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" Button state: Class originated from: 9. Type: XIValuatorClass Detail for Valuator 0: Label: Rel X Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 1: Label: Rel Y Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 2: Label: Rel Horiz Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 3: Label: Rel Vert Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIScrollClass Scroll info for Valuator 2 type: 2 (horizontal) increment: 1.00 flags: 0x0 Class originated from: 9. Type: XIScrollClass Scroll info for Valuator 3 type: 1 (vertical) increment: -1.00 flags: 0x2 ( preferred ) $ xinput list 10 Logitech USB Receiver id=10 [slave pointer (2)] Reporting 6 classes: Class originated from: 10. Type: XIButtonClass Buttons supported: 7 Button labels: "Button 0" "Button Unknown" "Button Unknown" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" Button state: Class originated from: 10. Type: XIKeyClass Keycodes supported: 248 Class originated from: 10. Type: XIValuatorClass Detail for Valuator 0: Label: Rel X Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 10. Type: XIValuatorClass Detail for Valuator 1: Label: Rel Y Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 10. Type: XIValuatorClass Detail for Valuator 2: Label: Rel Horiz Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 10. Type: XIScrollClass Scroll info for Valuator 2 type: 2 (horizontal) increment: 1.00 flags: 0x0 Does anyone have an idea how I can attempt to further debug that issue? Or maybe even a solution? Should I consider this issue a bug? Can I provide more info? --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: toby 11625 F pulseaudio /dev/snd/controlC0: toby 11625 F pulseaudio /dev/snd/pcmC1D0p: toby 11625 F...m pulseaudio /dev/snd/controlC1: toby 11625 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04
[Kernel-packages] [Bug 1845704] Re: HDMI monitor is not detected as sound output device starting from kernel 4.18.0-21 and above, Ubuntu 18.10 and 19.04
This isn't x86 specific, ppc64el is similarly affected ** Tags removed: amd64 cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845704 Title: HDMI monitor is not detected as sound output device starting from kernel 4.18.0-21 and above, Ubuntu 18.10 and 19.04 Status in linux package in Ubuntu: Confirmed Bug description: After upgrading Ubuntu 18.10 from kernel 4.18.0-20-generic to 4.18.0-21-generic, HDMI Audio stopped working, system does not detect it at all as a sound output device. Downgrading to 4.18.0-20 helped on Ubuntu 18.10, but currently I'm using Ubuntu 19.04 with kernel 5.0.0-29-generic, and HDMI sound still does not work and system cannot detect it. Adding the following parameters to GRUB didn't helped (): - amdgpu.dc=1 - radeon.audio=1 Video card: Radeon HD 4850 with 2 DVI ports with ability to output sound thru DVI (DVI-HDMI cable or DVI-HDMI adapter). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-29-generic 5.0.0-29.31 ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oshmyrko 2595 F pulseaudio /dev/snd/controlC2: oshmyrko 2595 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 27 22:14:27 2019 InstallationDate: Installed on 2019-04-13 (166 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic root=UUID=a88b1763-5d14-4204-ba95-d6718c22158d ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-29-generic N/A linux-backports-modules-5.0.0-29-generic N/A linux-firmware1.178.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-07-09 (80 days ago) dmi.bios.date: 02/12/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 EVO R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2603:bd02/12/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97EVOR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: SKU dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827822] Re: kernel null pointer dereference
A month or so after reporting this, amid a frustrating series of unpredictable lockups, I figured out how to run memtest which indicated I had a bad memory card. Since replacing it, I have had no further problems. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827822 Title: kernel null pointer dereference Status in linux package in Ubuntu: Confirmed Bug description: System started freezing up a couple days ago. After the latest one, I looked at the syslog file and found what appears to be a kernel bug report. May 5 18:06:03 corbin-goul kernel: [ 4650.769677] BUG: unable to handle kernel NULL pointer dereference at 0008 May 5 18:06:03 corbin-goul kernel: [ 4650.769694] IP: rm_hole+0x19/0x70 [drm] May 5 18:06:03 corbin-goul kernel: [ 4650.769696] PGD 0 P4D 0 May 5 18:06:03 corbin-goul kernel: [ 4650.769698] Oops: 0002 [#1] SMP PTI May 5 18:06:03 corbin-goul kernel: [ 4650.769700] Modules linked in: nls_iso8859_1 snd_hda_codec_realtek snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_codec_generic snd_hda_intel snd _hda_codec kvm snd_hda_core snd_hwdep snd_pcm irqbypass mei_me intel_cstate mei intel_rapl_perf snd_seq_midi input_leds snd_seq_midi_event serio_raw snd_rawmidi snd_seq snd_seq_device snd_timer lpc_ich snd shpchp soundcore mac_hid s ch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq a sync_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear raid1 hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 May 5 18:06:03 corbin-goul kernel: [ 4650.769733] aesni_intel i2c_algo_bit aes_x86_64 crypto_simd drm_kms_helper glue_helper cryptd syscopyarea sysfillrect sysimgblt r8169 fb_sys_fops ahci mii drm libahci sata_inic162x video May 5 18:06:03 corbin-goul kernel: [ 4650.769743] CPU: 0 PID: 8713 Comm: kworker/0:0 Not tainted 4.15.0-48-generic #51-Ubuntu May 5 18:06:03 corbin-goul kernel: [ 4650.769744] Hardware name: Gigabyte Technology Co., Ltd. H87M-D3H/H87M-D3H, BIOS F3 04/24/2013 May 5 18:06:03 corbin-goul kernel: [ 4650.769770] Workqueue: events __i915_gem_free_work [i915] May 5 18:06:03 corbin-goul kernel: [ 4650.769778] RIP: 0010:rm_hole+0x19/0x70 [drm] May 5 18:06:03 corbin-goul kernel: [ 4650.769779] RSP: 0018:95fb81f2bd20 EFLAGS: 00010202 May 5 18:06:03 corbin-goul kernel: [ 4650.769780] RAX: RBX: 89d51f1382c0 RCX: May 5 18:06:03 corbin-goul kernel: [ 4650.769781] RDX: RSI: 89d765cf8b40 RDI: 89d51f138318 May 5 18:06:03 corbin-goul kernel: [ 4650.769782] RBP: 95fb81f2bd28 R08: 89d5e7b71bc0 R09: May 5 18:06:03 corbin-goul kernel: [ 4650.769783] R10: 95fb81f2bde0 R11: 0001 R12: 89d765cf8b00 May 5 18:06:03 corbin-goul kernel: [ 4650.769784] R13: R14: 89d51f1382e0 R15: 89d75f6c37c8 May 5 18:06:03 corbin-goul kernel: [ 4650.769786] FS: () GS:89d77e20() knlGS: May 5 18:06:03 corbin-goul kernel: [ 4650.769787] CS: 0010 DS: ES: CR0: 80050033 May 5 18:06:03 corbin-goul kernel: [ 4650.769788] CR2: 0008 CR3: 0002eac0a002 CR4: 001606f0 May 5 18:06:03 corbin-goul kernel: [ 4650.769789] Call Trace: May 5 18:06:03 corbin-goul kernel: [ 4650.769797] drm_mm_remove_node+0x29d/0x360 [drm] May 5 18:06:03 corbin-goul kernel: [ 4650.769801] ? __internal_add_timer+0x1f/0x60 May 5 18:06:03 corbin-goul kernel: [ 4650.769816] i915_vma_remove+0x3a/0x100 [i915] May 5 18:06:03 corbin-goul kernel: [ 4650.769830] i915_vma_unbind+0x1cd/0x370 [i915] May 5 18:06:03 corbin-goul kernel: [ 4650.769843] i915_vma_close+0x7d/0xa0 [i915] May 5 18:06:03 corbin-goul kernel: [ 4650.769856] __i915_gem_free_objects+0xa3/0x2c0 [i915] May 5 18:06:03 corbin-goul kernel: [ 4650.769867] __i915_gem_free_work+0x60/0x90 [i915] May 5 18:06:03 corbin-goul kernel: [ 4650.769870] process_one_work+0x1de/0x410 May 5 18:06:03 corbin-goul kernel: [ 4650.769872] worker_thread+0x32/0x410 May 5 18:06:03 corbin-goul kernel: [ 4650.769874] kthread+0x121/0x140 May 5 18:06:03 corbin-goul kernel: [ 4650.769876] ? process_one_work+0x410/0x410 May 5 18:06:03 corbin-goul kernel: [ 4650.769878] ? kthread_create_worker_on_cpu+0x70/0x70 May 5 18:06:03 corbin-goul kernel: [ 4650.769881] ret_from_fork+0x35/0x40 May 5 18:06:03 corbin-goul kernel: [ 4650.769882] Code: 00 00 00 45 31 d2 eb bb 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 48 8b 57 30 48 8b 47 38 48 89 fb 48 8d 7f 58 <48>
[Kernel-packages] [Bug 1844021] Re: Suspend stopped working from 4.4.0-157 onwards
Thanks, but when I went to test it couldn't get this installed. Is it possibly a corrupted deb file? When I tried the linux-modules deb, I got this (Reading database ... 221473 files and directories currently installed.) Preparing to unpack linux-modules-4.15.0-66-generic_4.15.0-66.75~lp1844021_amd64.deb ... Unpacking linux-modules-4.15.0-66-generic (4.15.0-66.75~lp1844021) ... dpkg-deb (subprocess): cannot copy archive member from 'linux-modules-4.15.0-66-generic_4.15.0-66.75~lp1844021_amd64.deb' to decompressor pipe: unexpected end of file or stream dpkg-deb (subprocess): decompressing archive member: lzma error: unexpected end of input dpkg-deb: error: subprocess returned error exit status 2 dpkg: error processing archive linux-modules-4.15.0-66-generic_4.15.0-66.75~lp1844021_amd64.deb (--install): cannot copy extracted data for './lib/modules/4.15.0-66-generic/kernel/drivers/scsi/qla2xxx/qla2xxx.ko' to '/lib/modules/4.15.0-66-generic/kernel/drivers/scsi/qla2xxx/qla2xxx.ko.dpkg-new': unexpected end of file or stream Errors were encountered while processing: linux-modules-4.15.0-66-generic_4.15.0-66.75~lp1844021_amd64.deb -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844021 Title: Suspend stopped working from 4.4.0-157 onwards Status in linux package in Ubuntu: Incomplete Bug description: Since upgrading the kernel above 4.4.0-154, starting with 4.4.0-157, suspend does not work for me anymore. Never had such an issue in the last 6 years. This is the relevant output when suspend fails: [ 328.25] PM: Suspending system (mem) [ 328.288902] Suspending console(s) (use no_console_suspend to debug) [ 328.289118] wlp1s0: deauthenticating from xx:xx:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING) [ 328.289209] sd 1:0:0:0: [sdb] Synchronizing SCSI cache [ 328.289570] sd 0:0:0:0: [sda] Synchronizing SCSI cache [ 328.289600] sd 0:0:0:0: [sda] Stopping disk [ 328.291700] sd 1:0:0:0: [sdb] Stopping disk [ 328.312413] xhci_hcd :03:00.0: WARN: xHC save state timeout [ 328.312456] suspend_common(): xhci_pci_suspend+0x0/0x70 returns -110 [ 328.312461] pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -110 [ 328.312465] dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -110 [ 328.312483] PM: Device :03:00.0 failed to suspend async: error -110 [ 328.848109] PM: Some devices failed to suspend, or early wake event detected This is my relevant lspci -v output: 03:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller (prog-if 30 [XHCI]) Subsystem: Samsung Electronics Co Ltd ASM1042 SuperSpeed USB Host Controller Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at f050 (64-bit, non-prefetchable) [size=32K] Capabilities: Kernel driver in use: xhci_hcd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844021/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846123] Re: xenial/linux-azure: 4.15.0-1061.66 -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: 1846131 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Signoff phase-changed: Thursday, 03. October 2019 23:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1846122 xenial/linux-azure-edge: bug 1846121 xenial/linux-azure/azure-kernel: bug 1846120 variant: debs -- 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/1846123 Title: xenial/linux-azure: 4.15.0-1061.66 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed 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: 1846131 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Signoff phase-changed: Thursday, 03. October 2019 23:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1846122 xenial/linux-azure-edge: bug 1846121 xenial/linux-azure/azure-kernel: bug 1846120 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846123/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846910] [NEW] nvidia-384 384.130-0ubuntu0.16.04.2: nvidia-384 kernel module failed to build
Public bug reported: upgrade reported an error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-384 384.130-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 DKMSKernelVersion: 4.4.0-165-generic Date: Sat Oct 5 15:51:17 2019 InstallationDate: Installed on 2016-09-05 (1125 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageVersion: 384.130-0ubuntu0.16.04.2 RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: nvidia-graphics-drivers-384 Title: nvidia-384 384.130-0ubuntu0.16.04.2: nvidia-384 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-384 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-384 in Ubuntu. https://bugs.launchpad.net/bugs/1846910 Title: nvidia-384 384.130-0ubuntu0.16.04.2: nvidia-384 kernel module failed to build Status in nvidia-graphics-drivers-384 package in Ubuntu: New Bug description: upgrade reported an error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-384 384.130-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 DKMSKernelVersion: 4.4.0-165-generic Date: Sat Oct 5 15:51:17 2019 InstallationDate: Installed on 2016-09-05 (1125 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageVersion: 384.130-0ubuntu0.16.04.2 RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: nvidia-graphics-drivers-384 Title: nvidia-384 384.130-0ubuntu0.16.04.2: nvidia-384 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-384/+bug/1846910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827822] Re: kernel null pointer dereference
I just had this happen to me. I'll attach the relevant part of the syslog. If there's any more info that I could give that would help just let me know. Using Kernel 5.3.0-10-generic from Eoan. Oct 5 18:02:26 kernel: [493310.092229] BUG: kernel NULL pointer dereference, address: 02ac Oct 5 18:02:26 kernel: [493310.092235] #PF: supervisor read access in kernel mode Oct 5 18:02:26 kernel: [493310.092237] #PF: error_code(0x) - not-present page Oct 5 18:02:26 kernel: [493310.092239] PGD 0 P4D 0 Oct 5 18:02:26 kernel: [493310.092244] Oops: [#1] SMP NOPTI Oct 5 18:02:26 kernel: [493310.092248] CPU: 0 PID: 2063 Comm: kworker/u32:3 Not tainted 5.3.0-10-generic #11-Ubuntu Oct 5 18:02:26 kernel: [493310.092250] Hardware name: Micro-Star International Co., Ltd MS-7C02/B450 TOMAHAWK (MS-7C02), BIOS 1.50 01/25/2019 Oct 5 18:02:26 kernel: [493310.092266] Workqueue: events_unbound commit_work [drm_kms_helper] Oct 5 18:02:26 kernel: [493310.092409] RIP: 0010:dc_stream_log+0x12/0xc0 [amdgpu] Oct 5 18:02:26 kernel: [493310.092414] Code: 83 f1 01 0f b6 c9 e8 8d 92 35 d3 e9 71 ff ff ff 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 f2 bf 04 00 00 00 48 89 e5 53 <8b> 86 ac 02 00 00 48 89 f3 8b 8e 0c 01 00 00 50 8b 86 28 01 00 00 Oct 5 18:02:26 kernel: [493310.092418] RSP: 0018:b81e08617b80 EFLAGS: 00010202 Oct 5 18:02:26 kernel: [493310.092422] RAX: RBX: 0001 RCX: 0002 Oct 5 18:02:26 kernel: [493310.092424] RDX: RSI: RDI: 0004 Oct 5 18:02:26 kernel: [493310.092427] RBP: b81e08617b88 R08: R09: 0001 Oct 5 18:02:26 kernel: [493310.092430] R10: 9c49fea173c8 R11: R12: 9c43047a Oct 5 18:02:26 kernel: [493310.092432] R13: 9c49f2e0 R14: 9c43047a R15: 9c49e90c Oct 5 18:02:26 kernel: [493310.092436] FS: () GS:9c49fea0() knlGS: Oct 5 18:02:26 kernel: [493310.092439] CS: 0010 DS: ES: CR0: 80050033 Oct 5 18:02:26 kernel: [493310.092441] CR2: 02ac CR3: 0007ecba CR4: 003406f0 Oct 5 18:02:26 kernel: [493310.092445] DR0: 1004c7c0 DR1: 10183c60 DR2: 100f14a0 Oct 5 18:02:26 kernel: [493310.092447] DR3: 100efd10 DR6: 0ff0 DR7: 0600 Oct 5 18:02:26 kernel: [493310.092449] Call Trace: Oct 5 18:02:26 kernel: [493310.092611] dc_commit_state+0x7e/0xb0 [amdgpu] Oct 5 18:02:26 kernel: [493310.092745] amdgpu_dm_atomic_commit_tail+0x3bf/0xfb0 [amdgpu] Oct 5 18:02:26 kernel: [493310.092753] ? cpumask_next_and+0x1e/0x20 Oct 5 18:02:26 kernel: [493310.092759] ? free_one_page+0xb7/0x4b0 Oct 5 18:02:26 kernel: [493310.092764] ? __switch_to_asm+0x40/0x70 Oct 5 18:02:26 kernel: [493310.092767] ? __switch_to_asm+0x34/0x70 Oct 5 18:02:26 kernel: [493310.092770] ? __switch_to_asm+0x40/0x70 Oct 5 18:02:26 kernel: [493310.092773] ? __switch_to_asm+0x34/0x70 Oct 5 18:02:26 kernel: [493310.092776] ? __switch_to_asm+0x40/0x70 Oct 5 18:02:26 kernel: [493310.092779] ? __switch_to_asm+0x34/0x70 Oct 5 18:02:26 kernel: [493310.092782] ? __switch_to_asm+0x40/0x70 Oct 5 18:02:26 kernel: [493310.092785] ? __switch_to_asm+0x34/0x70 Oct 5 18:02:26 kernel: [493310.092788] ? __switch_to_asm+0x40/0x70 Oct 5 18:02:26 kernel: [493310.092791] ? __switch_to_asm+0x34/0x70 Oct 5 18:02:26 kernel: [493310.092794] ? __switch_to_asm+0x40/0x70 Oct 5 18:02:26 kernel: [493310.092797] ? __switch_to_asm+0x34/0x70 Oct 5 18:02:26 kernel: [493310.092801] ? select_idle_sibling+0x1f/0x70 Oct 5 18:02:26 kernel: [493310.092804] ? select_task_rq_fair+0x379/0x5c0 Oct 5 18:02:26 kernel: [493310.092807] ? _cond_resched+0x19/0x30 Oct 5 18:02:26 kernel: [493310.092810] ? wait_for_completion_timeout+0x3a/0x120 Oct 5 18:02:26 kernel: [493310.092824] commit_tail+0x41/0x70 [drm_kms_helper] Oct 5 18:02:26 kernel: [493310.092836] ? commit_tail+0x41/0x70 [drm_kms_helper] Oct 5 18:02:26 kernel: [493310.092848] commit_work+0x12/0x20 [drm_kms_helper] Oct 5 18:02:26 kernel: [493310.092852] process_one_work+0x1db/0x380 Oct 5 18:02:26 kernel: [493310.092855] worker_thread+0x4d/0x400 Oct 5 18:02:26 kernel: [493310.092860] kthread+0x104/0x140 Oct 5 18:02:26 kernel: [493310.092863] ? process_one_work+0x380/0x380 Oct 5 18:02:26 kernel: [493310.092866] ? kthread_park+0x80/0x80 Oct 5 18:02:26 kernel: [493310.092870] ret_from_fork+0x22/0x40 Oct 5 18:02:26 kernel: [493310.092873] Modules linked in: ppp_mppe ppp_async nf_conntrack_pptp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c snd_seq_dummy ccm binfmt_misc edac_mce_amd kvm_amd snd_hda_codec_realtek snd_hda_codec_generic kvm ledtrig_audio irqbypass snd_hda_codec_hdmi snd_hda_intel snd_usb_audio snd_hda_codec snd_usbmidi_lib snd_hda_core mc snd_hwdep snd_pcm ath9k_htc
[Kernel-packages] [Bug 1846103] Re: bionic/linux-raspi2: 4.15.0-1049.53 -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: 1846131 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Signoff phase-changed: Friday, 04. October 2019 01:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-raspi2/pi-kernel: bug 1846101 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1846103 Title: bionic/linux-raspi2: 4.15.0-1049.53 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Bionic: Confirmed 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: 1846131 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Signoff phase-changed: Friday, 04. October 2019 01:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-raspi2/pi-kernel: bug 1846101 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846103/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846641] Re: eoan/linux: 5.3.0-17.18 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => In Progress ** 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Saturday, 05. October 2019 01:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED + automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe-edge: bug 1846636 eoan/linux-aws: bug 1846613 eoan/linux-azure: bug 1846616 eoan/linux-gcp: bug 1846623 eoan/linux-kvm: bug 1846628 eoan/linux-oracle: bug 1846630 eoan/linux-raspi2: bug 1846611 eoan/linux-snapdragon: bug 1846634 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1846641 Title: eoan/linux: 5.3.0-17.18 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress 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-release series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Confirmed 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Saturday, 05. October 2019 01:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe-edge: bug 1846636 eoan/linux-aws: bug 1846613 eoan/linux-azure: bug 1846616 eoan/linux-gcp: bug 1846623 eoan/linux-kvm: bug 1846628 eoan/linux-oracle: bug 1846630 eoan/linux-raspi2: bug 1846611 eoan/linux-snapdragon: bug 1846634 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846641/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846016] Re: iwlwifi regular scan timed out error sending statistics_cmd queue 0 is inactive
In one of the latest boots i've found red lines with some gdm3 error, so i gave gnome-shell a purge and reinstall and it worked. With the backport of iwlwifi i didn't have internet, but i uninstalled it and then was able to reinstall gnome-shell. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1846016 Title: iwlwifi regular scan timed out error sending statistics_cmd queue 0 is inactive Status in Linux: Fix Released Status in linux package in Ubuntu: In Progress Status in linux source package in Eoan: In Progress Bug description: I have ubuntu 19.10 Eoan Ermine development version. Cannot boot since yesterday. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-firmware 1.182 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Mon Sep 30 20:57:08 2019 Dependencies: InstallationDate: Installed on 2019-07-23 (68 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: Upgraded to eoan on 2019-09-27 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1846016/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg
Jeremy Soller's fix to edit Xwrapper seems to be good. The edits to the gdm service cause a crash to happen on boot. Currently using an HP Laptop with an Intel CPU and Nvidia GPU that I believe is Optimus. I have the proprietary Nvidia driver running on nvidia-driver-430 as of this comment's date. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg Status in gdm3 package in Ubuntu: Opinion Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846064] Re: xenial/linux-snapdragon: 4.4.0-1128.136 -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: 1846069 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Signoff phase-changed: Thursday, 03. October 2019 18:27 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1846063 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1846064 Title: xenial/linux-snapdragon: 4.4.0-1128.136 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: Confirmed 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: 1846069 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Signoff phase-changed: Thursday, 03. October 2019 18:27 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1846063 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846064/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846062] Re: xenial/linux-raspi2: 4.4.0-1124.133 -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: 1846069 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Signoff phase-changed: Thursday, 03. October 2019 18:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-raspi2/pi2-kernel: bug 1846061 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1846062 Title: xenial/linux-raspi2: 4.4.0-1124.133 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: Confirmed 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: 1846069 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Signoff phase-changed: Thursday, 03. October 2019 18:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-raspi2/pi2-kernel: bug 1846061 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846059] Re: xenial/linux-aws: 4.4.0-1096.107 -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: 1846069 packages: main: linux-aws meta: linux-meta-aws phase: Signoff phase-changed: Thursday, 03. October 2019 19:50 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-aws/aws-kernel: bug 1846058 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1846059 Title: xenial/linux-aws: 4.4.0-1096.107 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug 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: 1846069 packages: main: linux-aws meta: linux-meta-aws phase: Signoff phase-changed: Thursday, 03. October 2019 19:50 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-aws/aws-kernel: bug 1846058 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846059/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846069] Re: xenial/linux: 4.4.0-166.195 -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 bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 03. October 2019 14:51 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-aws: bug 1846066 trusty/linux-lts-xenial: bug 1846067 xenial/linux-aws: bug 1846059 xenial/linux-fips: bug 1846065 xenial/linux-kvm: bug 1846060 xenial/linux-raspi2: bug 1846062 xenial/linux-snapdragon: bug 1846064 xenial/linux/caracalla-kernel: bug 1846054 xenial/linux/pc-kernel: bug 1846055 xenial/linux/stlouis-kernel: bug 1846057 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1846069 Title: xenial/linux: 4.4.0-166.195 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed 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 bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 03. October 2019 14:51 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-aws: bug 1846066 trusty/linux-lts-xenial: bug 1846067 xenial/linux-aws: bug 1846059 xenial/linux-fips: bug 1846065 xenial/linux-kvm: bug 1846060 xenial/linux-raspi2: bug 1846062 xenial/linux-snapdragon: bug 1846064 xenial/linux/caracalla-kernel: bug 1846054 xenial/linux/pc-kernel: bug 1846055 xenial/linux/stlouis-kernel: bug 1846057 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846271] Re: Full video freeze kernel 4.15.0-65
It's not enabled on 16.04 but it's default enabled on 18.04. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1846271 Title: Full video freeze kernel 4.15.0-65 Status in linux package in Ubuntu: Incomplete Bug description: Must restart PC to recover. Everything else seems to continue to work, like music/video playing continues even though I can no longer see any updates to video, no mouse movement and no keyboard entries seem to work. Reverted back to 4.15.0-64 for stability. Unable to provide the ubuntu-bug linux due to inability to make any entries on frozen desktop. --- ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lmcor 3039 F pulseaudio /dev/snd/controlC0: lmcor 3039 F pulseaudio CurrentDesktop: KDE DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=bf754a96-f70b-4964-bdbb-b7ab12e42018 InstallationDate: Installed on 2018-09-30 (366 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171127 MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-64-generic root=UUID=7663b459-8677-4afe-85fb-12424af45024 ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-64.73~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-64-generic N/A linux-backports-modules-4.15.0-64-generic N/A linux-firmware 1.157.22 Tags: sylvia Uname: Linux 4.15.0-64-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev root sambashare sudo _MarkForUpload: True dmi.bios.date: 01/22/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3803 dmi.board.asset.tag: Default string dmi.board.name: PRIME X370-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3803:bd01/22/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX370-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846271/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846271] Re: Full video freeze kernel 4.15.0-65
I am in the process of evaluating a replacement for Mint/Ubuntu. I have used many distros, but Mint/Ubuntu is the ONLY Linux distro to ever freeze-up and to require a restart (who do you think you are...MS?). It has happened on 2 different desktop PCs, the only similarity is AMD processors. If you need the journal for instances like this, then why isn't it enabled by default? Do what you want with what I have reported to you as I am done with this back and forth messaging getting absolutely nowhere. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1846271 Title: Full video freeze kernel 4.15.0-65 Status in linux package in Ubuntu: Incomplete Bug description: Must restart PC to recover. Everything else seems to continue to work, like music/video playing continues even though I can no longer see any updates to video, no mouse movement and no keyboard entries seem to work. Reverted back to 4.15.0-64 for stability. Unable to provide the ubuntu-bug linux due to inability to make any entries on frozen desktop. --- ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lmcor 3039 F pulseaudio /dev/snd/controlC0: lmcor 3039 F pulseaudio CurrentDesktop: KDE DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=bf754a96-f70b-4964-bdbb-b7ab12e42018 InstallationDate: Installed on 2018-09-30 (366 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171127 MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-64-generic root=UUID=7663b459-8677-4afe-85fb-12424af45024 ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-64.73~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-64-generic N/A linux-backports-modules-4.15.0-64-generic N/A linux-firmware 1.157.22 Tags: sylvia Uname: Linux 4.15.0-64-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev root sambashare sudo _MarkForUpload: True dmi.bios.date: 01/22/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3803 dmi.board.asset.tag: Default string dmi.board.name: PRIME X370-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3803:bd01/22/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX370-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846271/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774640] Re: Bluetooth turns off automatically Ubuntu 18.04 LTS
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1774640 Title: Bluetooth turns off automatically Ubuntu 18.04 LTS Status in bluez package in Ubuntu: Confirmed Bug description: Whenever I start up my laptop and connect my JBL-speaker, the device stays connected. However, when I turn de speaker off, and try to reconnect to the speaker, the Bluetooth automatically turns off. I then need to restart my laptop and then only Bluetooth works again. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-27 (39 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 003: ID 0bda:57b5 Realtek Semiconductor Corp. Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X555LAB Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=2c696fdd-83b4-4daf-b864-3c9a68f8c2dc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-22-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/04/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LAB.503 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LAB 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.:bvrX555LAB.503:bd08/04/2015:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555LAB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:1A:7D:DA:71:0A ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:55347 acl:67 sco:0 events:7591 errors:0 TX bytes:4599486 acl:14880 sco:0 commands:100 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1774640/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1841485] Re: Unbearable whistling in headphones
Thank you and good luck for trying to solve this very annoying bug. Regards. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1841485 Title: Unbearable whistling in headphones Status in linux package in Ubuntu: Confirmed Bug description: Unbearable whistling in headphones plugged into 3.5 mm audio jack port. My Dell XPS 9570 with the kernel 4.15.0-58 (LTS) & 5.0.0-25 are impacted by this bug ;( --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: philippe 2233 F...m pulseaudio /dev/snd/controlC0: philippe 2233 F pulseaudio DistroRelease: Linux Mint 19.2 InstallationDate: Installed on 2019-08-26 (0 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 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 8087:0025 Intel Corp. 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.15.0-58-generic root=UUID=620f2477-363c-44a5-828d-b6d70149d781 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.9 Tags: tina Uname: Linux 4.15.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/27/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd06/27/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1584475] Re: No input events for FutureMax Dance Mat
I also have FutureMax Dance Mat. I think the main problem is with Stepmania, however. I've been using the following patch for Stepmania. It works most of the time. https://github.com/stepmania/stepmania/pull/1745 Sometimes (after resuming from suspend and such) there are some intermittent failures to recognize the dance mat though. I haven't quite managed to track the cause of those down. But the patch definitely works. The reason that "vanilla" Stepmania doesn't work on Linux is because it expects analog inputs. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1584475 Title: No input events for FutureMax Dance Mat Status in linux package in Ubuntu: Triaged Bug description: On my ubuntu booth of my FutureMax Dance Mats does not generate any input events. So they can not be used. The hardware is working, i verified this with a windows PC. The missing events were checked with cat /dev/input/eventX, evtest, xev. On ubuntu the device is set up (udevadm has it, dmesg has it, evtest sees it), module joydev is loaded but no input is recognized/ visible and /dev/input/eventX Expected behavior: Plug and Play with the usb Dance Mat Acutal behavior: No play possible as no input events appear and so the game can not use it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xar2249 F pulseaudio /dev/snd/controlC0: xar2249 F pulseaudio CurrentDesktop: MATE Date: Sun May 22 15:29:57 2016 HibernationDevice: RESUME=UUID=d68a39e5-b419-4307-9af9-6eeda8990336 MachineType: Sony Corporation VPCZ12C5E ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=18e98aae-17c4-4d7d-80db-421236684825 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-05-17 (4 days ago) dmi.bios.date: 07/30/2010 dmi.bios.vendor: INSYDE dmi.bios.version: R3030C3 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDE:bvrR3030C3:bd07/30/2010:svnSonyCorporation:pnVPCZ12C5E:pvrJ004B4UH:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VPCZ12C5E dmi.product.version: J004B4UH dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584475/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846108] Re: bionic/linux-aws-fips: 4.15.0-2002.2 -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: 1846110 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips phase: Ready for Promote to Proposed phase-changed: Friday, 04. October 2019 23:17 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Stalled -- ready for review variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1846108 Title: bionic/linux-aws-fips: 4.15.0-2002.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm 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: New Status in Kernel SRU Workflow promote-to-proposed series: Confirmed 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: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid 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: 1846110 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips phase: Ready for Promote to Proposed phase-changed: Friday, 04. October 2019 23:17 UTC reason: promote-to-proposed: Stalled -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846108/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836912] Re: ipv4: enable route flushing in network namespaces
** Tags removed: verification-needed-disco ** Tags added: verification-done-disco ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Christian Brauner (cbrauner) ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => Christian Brauner (cbrauner) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836912 Title: ipv4: enable route flushing in network namespaces Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Committed Bug description: SRU Justification Impact: Tools such as vpnc try to flush routes when run inside network namespaces by writing 1 into /proc/sys/net/ipv4/route/flush. This currently does not work because flush is not enabled in non-initial network namespaces. Users have complained about this at various times (cf. Link: https://github.com/lxc/lxd/issues/4257). Fix: Enable /proc/sys/net/ipv4/route/flush inside non-initial network namespaces. Regression Potential: None, since this didn't use to work before. Since routes are per network namespace it is safe to enable /proc/sys/net/ipv4/route/flush in there. Test Case: Tested with LXD on a kernel with the patch applied and by running vpnc successfully. Target Kernels: All LTS kernels starting from 4.15. Kernel 5.3 has the patchset upstream. Patches: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5cdda5f1d6adde02da591ca2196f20289977dc56 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836912/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1841977] Re: shiftfs: drop entries from cache on unlink
** Tags removed: verification-needed-disco ** Tags added: verification-done-disco ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => Christian Brauner (cbrauner) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1841977 Title: shiftfs: drop entries from cache on unlink Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Committed Bug description: SRU Justification Impact: LXD on Ubuntu runs on top of zfs by defaults. Users that make use of shiftfs for efficient id-shifting currently hit a bug where zfs is confused about the amount of space that is used in a dataset. For example, creating a file with 1GB of random data will increase the space used by the dataset by 1GB. When the file is removed via rm the space is not freed for zfs. This leads to zfs running out of space pretty quickly. This bug has been observed, described, and reproduced here https://discuss.linuxcontainers.org/t/trying-out-shiftfs/5155/9 . Stéphane Graber observed related issues. Regression Potential: Limited to shiftfs. This patch has been tested on various backends btrfs, dir, zfs to verify that it doesn't regress other workloads. Shiftfs now also aligns more closely with overlayfs on file deletion. Test Case: sudo snap install lxd sudo snap set lxd shiftfs.enable=true sudo systemctl restart snap.lxd.daemon sudo lxd init # make sure to select zfs as backend sudo lxc launch images:ubuntu/bionic b1 sudo lxc exec b1 -- dd if=/dev/urandom bs=1M count=1000 of=dummy.file sudo zfs list default/containers/b1 # will show +1GB sudo lxc exec b1 -- rm dummy.file sudo zfs list default/containers/b1 # will show +1GB on a non-fixed kernel and -1GB on a fixed kernel Target Kernels: All LTS kernels with shiftfs support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841977/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842059] Re: shiftfs: mark kmem_cache as reclaimable
** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => Christian Brauner (cbrauner) ** Tags removed: verification-needed-disco ** Tags added: verification-done-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/1842059 Title: shiftfs: mark kmem_cache as reclaimable Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Committed Bug description: SRU Justification Impact: Shiftfs does not mark it's slab cache as reclaimable. While this is not a big deal it is not nice to the kernel in general. The shiftfs cache is not so important that it can't be reclaimed. Regression Potential: Limited to shiftfs. This patch has been tested for multiple days and has not caused any regressions. Test Case: Open a lot of files in shiftfs to get them into the cache and then cause memory pressure via e.g. stress-ng and see if the shiftfs cache shrinks. Target Kernels: All LTS kernels with shiftfs support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842059/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838886] Re: New ID in ums-realtek module breaks cardreader
For confirmation that my auto_delink_en setting was kept by the default after rebooting (so I made sure that initramfs was containing correct settings): root@sirius:~# cat /sys/module/ums_realtek/parameters/auto_delink_en 1 So it looks like the module boots correctly and having the default auto_delink_en setting, but for the specific device it's not using the setting. So fix 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/1838886 Title: New ID in ums-realtek module breaks cardreader Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Confirmed Bug description: === SRU Justification === [Impact] Some ums-realtek card readers may dropped from USB bus after using ums-realtek driver instead of usb-storage generic driver. [Fix] Disable auto-delink on new ums-realtek devices, only whitelist three oldest IDs. [Test] Affected user and myself confirmed disabling auto-delink works. [Regression Potential] Minimal. Limited to one specific driver and this also restore the old behavior. === Original Bug Report === When installing the latest HWE stack (Linux 5.0) to Ubuntu 18.04, the Realtek cardreader in my ZOTAC ZBOX-CI323NANO stops working correctly. Previously it accepted SD cards all the time. Now it looks like you have to insert the card on booting or shortly after booting to access it. If you wait longer, it no longer detects the card. The reason for this can be found in the kernel log (dmes). On boot it seems to detect a card in the reader, although there is none. After a while it says "Read capacity failed" and "scsi 2:0:0:0: rejecting I/O to dead device" and then resets the device. It tries this 3 times and then gives up completely. After that any real device plugged is no longer detected. The device is: idVendor=0bda, idProduct=0153, bcdDevice=57.13 Support for this was added in mainline kernel: https://github.com/torvalds/linux/commit/1a6dd3fea131276a4fc44ae77b0f471b0b473577 And this seems to be backported to 5.0 kernel in Ubuntu 18.04 HWE stack. Full log on boot (no card inserted): [3.689559] usb 1-5.1: new high-speed USB device number 4 using xhci_hcd [3.898312] usb 1-5.1: New USB device found, idVendor=0bda, idProduct=0153, bcdDevice=57.13 [3.898316] usb 1-5.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [3.898319] usb 1-5.1: Product: USB2.0-CRW [3.898322] usb 1-5.1: Manufacturer: Generic [3.898324] usb 1-5.1: SerialNumber: 2012092657120 [3.911571] usbcore: registered new interface driver usb-storage [3.914796] usbcore: registered new interface driver uas [3.917676] ums-realtek 1-5.1:1.0: USB Mass Storage device detected [3.924478] scsi host2: usb-storage 1-5.1:1.0 [3.924649] usbcore: registered new interface driver ums-realtek [...] [ 13.477360] ums-realtek 1-5.1:1.0: USB Mass Storage device detected [ 13.509592] scsi host2: usb-storage 1-5.1:1.0 [ 14.544213] scsi 2:0:0:0: Direct-Access Generic- SD/MMC/MS PRO1.00 PQ: 0 ANSI: 4 [ 14.545237] sd 2:0:0:0: Attached scsi generic sg1 type 0 [ 14.549430] sd 2:0:0:0: [sdb] Attached SCSI removable disk [ 170.961728] scsi 2:0:0:0: rejecting I/O to dead device [ 170.962069] scsi 2:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_ERROR [ 170.962073] scsi 2:0:0:0: [sdb] Sense not available. [ 171.985846] usb 1-5.1: new high-speed USB device number 8 using xhci_hcd [ 172.194299] usb 1-5.1: New USB device found, idVendor=0bda, idProduct=0153, bcdDevice=57.13 [ 172.194317] usb 1-5.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 172.194327] usb 1-5.1: Product: USB2.0-CRW [ 172.194338] usb 1-5.1: Manufacturer: Generic [ 172.194346] usb 1-5.1: SerialNumber: 2012092657120 [ 172.200625] ums-realtek 1-5.1:1.0: USB Mass Storage device detected [ 172.212503] scsi host2: usb-storage 1-5.1:1.0 [ 173.233036] scsi 2:0:0:0: Direct-Access Generic- SD/MMC/MS PRO1.00 PQ: 0 ANSI: 4 [ 173.233796] sd 2:0:0:0: Attached scsi generic sg1 type 0 [ 173.239620] sd 2:0:0:0: [sdb] Attached SCSI removable disk [ 329.654468] usb 1-5.1: USB disconnect, device number 8 [ 329.665905] scsi 2:0:0:0: rejecting I/O to dead device [ 329.665970] scsi 2:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_ERROR [ 329.665976] scsi 2:0:0:0: [sdb] Sense not available. [ 330.701685] usb 1-5.1: new high-speed USB device number 9 using xhci_hcd [ 330.910415] usb 1-5.1: New USB device found, idVendor=0bda, idProduct=0153, bcdDevice=57.13 [ 330.910433] usb 1-5.1: New USB device strings: Mfr=1, Product=2,
[Kernel-packages] [Bug 1838886] Re: New ID in ums-realtek module breaks cardreader
It would be good that somebody else adds the correct tags so this fix gets delivered to all distributions using the 5.x kernels. I am not sure if 4.x needs the fix at all, as according to the latest non-hwe kernel I used in bionic, the bad realtek IDs were not added to the unusual devices. But maybe that changed in the meantime. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838886 Title: New ID in ums-realtek module breaks cardreader Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Confirmed Bug description: === SRU Justification === [Impact] Some ums-realtek card readers may dropped from USB bus after using ums-realtek driver instead of usb-storage generic driver. [Fix] Disable auto-delink on new ums-realtek devices, only whitelist three oldest IDs. [Test] Affected user and myself confirmed disabling auto-delink works. [Regression Potential] Minimal. Limited to one specific driver and this also restore the old behavior. === Original Bug Report === When installing the latest HWE stack (Linux 5.0) to Ubuntu 18.04, the Realtek cardreader in my ZOTAC ZBOX-CI323NANO stops working correctly. Previously it accepted SD cards all the time. Now it looks like you have to insert the card on booting or shortly after booting to access it. If you wait longer, it no longer detects the card. The reason for this can be found in the kernel log (dmes). On boot it seems to detect a card in the reader, although there is none. After a while it says "Read capacity failed" and "scsi 2:0:0:0: rejecting I/O to dead device" and then resets the device. It tries this 3 times and then gives up completely. After that any real device plugged is no longer detected. The device is: idVendor=0bda, idProduct=0153, bcdDevice=57.13 Support for this was added in mainline kernel: https://github.com/torvalds/linux/commit/1a6dd3fea131276a4fc44ae77b0f471b0b473577 And this seems to be backported to 5.0 kernel in Ubuntu 18.04 HWE stack. Full log on boot (no card inserted): [3.689559] usb 1-5.1: new high-speed USB device number 4 using xhci_hcd [3.898312] usb 1-5.1: New USB device found, idVendor=0bda, idProduct=0153, bcdDevice=57.13 [3.898316] usb 1-5.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [3.898319] usb 1-5.1: Product: USB2.0-CRW [3.898322] usb 1-5.1: Manufacturer: Generic [3.898324] usb 1-5.1: SerialNumber: 2012092657120 [3.911571] usbcore: registered new interface driver usb-storage [3.914796] usbcore: registered new interface driver uas [3.917676] ums-realtek 1-5.1:1.0: USB Mass Storage device detected [3.924478] scsi host2: usb-storage 1-5.1:1.0 [3.924649] usbcore: registered new interface driver ums-realtek [...] [ 13.477360] ums-realtek 1-5.1:1.0: USB Mass Storage device detected [ 13.509592] scsi host2: usb-storage 1-5.1:1.0 [ 14.544213] scsi 2:0:0:0: Direct-Access Generic- SD/MMC/MS PRO1.00 PQ: 0 ANSI: 4 [ 14.545237] sd 2:0:0:0: Attached scsi generic sg1 type 0 [ 14.549430] sd 2:0:0:0: [sdb] Attached SCSI removable disk [ 170.961728] scsi 2:0:0:0: rejecting I/O to dead device [ 170.962069] scsi 2:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_ERROR [ 170.962073] scsi 2:0:0:0: [sdb] Sense not available. [ 171.985846] usb 1-5.1: new high-speed USB device number 8 using xhci_hcd [ 172.194299] usb 1-5.1: New USB device found, idVendor=0bda, idProduct=0153, bcdDevice=57.13 [ 172.194317] usb 1-5.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 172.194327] usb 1-5.1: Product: USB2.0-CRW [ 172.194338] usb 1-5.1: Manufacturer: Generic [ 172.194346] usb 1-5.1: SerialNumber: 2012092657120 [ 172.200625] ums-realtek 1-5.1:1.0: USB Mass Storage device detected [ 172.212503] scsi host2: usb-storage 1-5.1:1.0 [ 173.233036] scsi 2:0:0:0: Direct-Access Generic- SD/MMC/MS PRO1.00 PQ: 0 ANSI: 4 [ 173.233796] sd 2:0:0:0: Attached scsi generic sg1 type 0 [ 173.239620] sd 2:0:0:0: [sdb] Attached SCSI removable disk [ 329.654468] usb 1-5.1: USB disconnect, device number 8 [ 329.665905] scsi 2:0:0:0: rejecting I/O to dead device [ 329.665970] scsi 2:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_ERROR [ 329.665976] scsi 2:0:0:0: [sdb] Sense not available. [ 330.701685] usb 1-5.1: new high-speed USB device number 9 using xhci_hcd [ 330.910415] usb 1-5.1: New USB device found, idVendor=0bda, idProduct=0153, bcdDevice=57.13 [ 330.910433] usb 1-5.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 330.910444] usb 1-5.1: Product: USB2.0-CRW
[Kernel-packages] [Bug 1838886] Re: New ID in ums-realtek module breaks cardreader
Hi, using the "-proposed" thingie in Bionic with the HWE kernel did not work even after the last query. So I did it the hard way (without any PPA used with APT/APT-GET). I downloaded the kernel manually and installed the following files: root@sirius:~/kernel-pkg# ls -l total 66160 -rw-r--r-- 1 root root 10758372 Oct 4 13:58 linux-headers-5.0.0-32_5.0.0-32.34_all.deb -rw-r--r-- 1 root root 1245844 Oct 4 13:58 linux-headers-5.0.0-32-generic_5.0.0-32.34_amd64.deb -rw-r--r-- 1 root root 8424200 Oct 4 16:18 linux-image-5.0.0-32-generic_5.0.0-32.34_amd64.deb -rw-r--r-- 1 root root 13831532 Oct 4 13:58 linux-modules-5.0.0-32-generic_5.0.0-32.34_amd64.deb -rw-r--r-- 1 root root 33478212 Oct 4 13:58 linux-modules-extra-5.0.0-32-generic_5.0.0-32.34_amd64.deb After removing the special module params and rebuilding initramfs, the kernel booted perfectly and ums-realtek worked. The module-info was correct: root@sirius:~# modinfo ums-realtek filename: /lib/modules/5.0.0-32-generic/kernel/drivers/usb/storage/ums-realtek.ko license:GPL author: wwang description:Driver for Realtek USB Card Reader srcversion: EA294247A6C868AE3685D12 alias: usb:v0BDAp0184d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v0BDAp0177d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v0BDAp0159d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v0BDAp0158d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v0BDAp0153d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v0BDAp0138d*dc*dsc*dp*ic*isc*ip*in* depends:usb-storage retpoline: Y intree: Y name: ums_realtek vermagic: 5.0.0-32-generic SMP mod_unload signat: PKCS#7 signer: sig_key: sig_hashalgo: md4 parm: auto_delink_en:auto delink mode (0=firmware, 1=software [default]) (int) parm: enable_mmc:enable mmc support (int) parm: ss_en:enable selective suspend (int) parm: ss_delay:seconds to delay before entering selective suspend (int) So I can confirm the HWE kernel in 18.04 is fine, too. Nevertheless, I have no idea if or why the bionic default kernel was affected at all. I opened the issue only on the HWE kernel, so maybe the kernel bot should be improved to actually understand before sending stupid messages to me about stuff I can't check. I will add the disco verification. I will keep the bionic verification and set it back to the default, although I can't test it. I will remove the bionic-verification failed tag. Uwe ** Tags removed: verification-failed-bionic verification-needed-disco ** Tags added: verification-done-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/1838886 Title: New ID in ums-realtek module breaks cardreader Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Confirmed Bug description: === SRU Justification === [Impact] Some ums-realtek card readers may dropped from USB bus after using ums-realtek driver instead of usb-storage generic driver. [Fix] Disable auto-delink on new ums-realtek devices, only whitelist three oldest IDs. [Test] Affected user and myself confirmed disabling auto-delink works. [Regression Potential] Minimal. Limited to one specific driver and this also restore the old behavior. === Original Bug Report === When installing the latest HWE stack (Linux 5.0) to Ubuntu 18.04, the Realtek cardreader in my ZOTAC ZBOX-CI323NANO stops working correctly. Previously it accepted SD cards all the time. Now it looks like you have to insert the card on booting or shortly after booting to access it. If you wait longer, it no longer detects the card. The reason for this can be found in the kernel log (dmes). On boot it seems to detect a card in the reader, although there is none. After a while it says "Read capacity failed" and "scsi 2:0:0:0: rejecting I/O to dead device" and then resets the device. It tries this 3 times and then gives up completely. After that any real device plugged is no longer detected. The device is: idVendor=0bda, idProduct=0153, bcdDevice=57.13 Support for this was added in mainline kernel: https://github.com/torvalds/linux/commit/1a6dd3fea131276a4fc44ae77b0f471b0b473577 And this seems to be backported to 5.0 kernel in Ubuntu 18.04 HWE stack. Full log on boot (no card inserted): [3.689559] usb 1-5.1: new high-speed USB device number 4 using xhci_hcd [3.898312] usb 1-5.1: New USB device found, idVendor=0bda, idProduct=0153, bcdDevice=57.13 [3.898316] usb 1-5.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [3.898319] usb 1-5.1: Product: USB2.0-CRW [3.898322] usb 1-5.1: Manufacturer: Generic [3.898324] usb 1-5.1: SerialNumber:
[Kernel-packages] [Bug 1834558] Re: intel_idle enable in ICL
still under investigation some issues. keep tune. cpu_idle will be still default. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834558 Title: intel_idle enable in ICL Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: Description: Support for intel_idle on Ice Lake (client) Target Release: 19.10 Target Kernel: 5.3 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1834558/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1754052] Re: Dell Latitude 7480 press shift keys triggers random mouseclick when `Tap to click` enabled on touchpad.
My Dell Latitude 7480 also has this problem. Is there any fix? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1754052 Title: Dell Latitude 7480 press shift keys triggers random mouseclick when `Tap to click` enabled on touchpad. Status in linux package in Ubuntu: Invalid Bug description: In Ubuntu 16.04.3 and 17.10.1 holding down either shift key on a Dell Latitude 7480 causes random mouse clicks to occur without being nowhere near the touchpad with palms. No external mouse/keyboard connected. Disabling `Tap to click` in `Mouse & Touchpad` settings makes the problem go away. The problem is not present in 14.04.5, whether installed or live CD. How to reproduce: 1. On a Dell Latitude 7480 live boot (or install) one of the following images: - ubuntu-16.04.3-desktop-amd64.iso - ubuntu-17.10.1-desktop-amd64.iso 2. Open `Mouse & Touchpad` and make sure `Tap to click` is enabled. 3. Click `Test Your Settings` and make sure window has focus. 4. Hold down either shift key and after a few seconds single/double clicks start registering. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Mar 7 13:00:21 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07a0] LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Dell Inc. Latitude 7480 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/30/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 00F6D3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd01/30/2018:svnDellInc.:pnLatitude7480:pvr:rvnDellInc.:rn00F6D3:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Latitude 7480 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754052/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1841485] Re: Unbearable whistling in headphones
I only have Precision 5530 to test with but let's see if I can reproduce the issue. ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1841485 Title: Unbearable whistling in headphones Status in linux package in Ubuntu: Confirmed Bug description: Unbearable whistling in headphones plugged into 3.5 mm audio jack port. My Dell XPS 9570 with the kernel 4.15.0-58 (LTS) & 5.0.0-25 are impacted by this bug ;( --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: philippe 2233 F...m pulseaudio /dev/snd/controlC0: philippe 2233 F pulseaudio DistroRelease: Linux Mint 19.2 InstallationDate: Installed on 2019-08-26 (0 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729 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 8087:0025 Intel Corp. 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.15.0-58-generic root=UUID=620f2477-363c-44a5-828d-b6d70149d781 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.9 Tags: tina Uname: Linux 4.15.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/27/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd06/27/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845719] Re: eoan/linux-raspi2: 5.3.0-1006.7 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** 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: 1846204 packages: main: linux-raspi2 meta: linux-meta-raspi2 - phase: Promote to Proposed - phase-changed: Saturday, 05. October 2019 06:45 UTC + phase: Testing + phase-changed: Saturday, 05. October 2019 08:17 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1845719 Title: eoan/linux-raspi2: 5.3.0-1006.7 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 source package in Eoan: Confirmed 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: 1846204 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Saturday, 05. October 2019 08:17 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1845719/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846073] Re: disco/linux-raspi2: 5.0.0-1020.20 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1846073 Title: disco/linux-raspi2: 5.0.0-1020.20 -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 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: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Disco: Confirmed 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: 1846097 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Friday, 04. October 2019 14:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846073/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846079] Re: disco/linux-azure: 5.0.0-1023.24 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => 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/1846079 Title: disco/linux-azure: 5.0.0-1023.24 -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: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Disco: Confirmed 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: 1846097 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Friday, 04. October 2019 15:58 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure: bug 1846078 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846079/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846075] Re: disco/linux-aws: 5.0.0-1019.21 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1846075 Title: disco/linux-aws: 5.0.0-1019.21 -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: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Disco: Confirmed 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: 1846097 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Friday, 04. October 2019 14:22 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-edge: bug 1846074 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846075/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846091] Re: disco/linux-snapdragon: 5.0.0-1024.25 -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-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1846091 Title: disco/linux-snapdragon: 5.0.0-1024.25 -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 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: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Disco: Confirmed 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: 1846097 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Friday, 04. October 2019 15:46 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846091/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846087] Re: disco/linux-kvm: 5.0.0-1020.21 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1846087 Title: disco/linux-kvm: 5.0.0-1020.21 -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: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Disco: Confirmed 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: 1846097 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Friday, 04. October 2019 15:46 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846086] Re: disco/linux-gcp: 5.0.0-1021.21 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1846086 Title: disco/linux-gcp: 5.0.0-1021.21 -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: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: Confirmed 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: 1846097 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Friday, 04. October 2019 15:58 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp: bug 1846082 bionic/linux-gke-5.0: bug 1846085 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846086/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846097] Re: disco/linux: 5.0.0-32.34 -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/1846097 Title: disco/linux: 5.0.0-32.34 -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-lrm 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 verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Confirmed 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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Friday, 04. October 2019 15:56 UTC proposed-announcement-sent: true proposed-testing-requested: true 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 verification-testing: Ongoing -- testing in progress trackers: bionic/linux-bluefield: bug 1846096 bionic/linux-hwe: bug 1846092 bionic/linux-oem-osp1: bug 1846095 disco/linux-aws: bug 1846075 disco/linux-azure: bug 1846079 disco/linux-gcp: bug 1846086 disco/linux-kvm: bug 1846087 disco/linux-oracle: bug 1846089 disco/linux-raspi2: bug 1846073 disco/linux-snapdragon: bug 1846091 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846097/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1841098] Re: PCI-passthrough instance creation problem RTX2080Ti
My suggestion is to try 16.10, 17.04 etc to find out which userspace regressed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1841098 Title: PCI-passthrough instance creation problem RTX2080Ti Status in linux package in Ubuntu: Incomplete Bug description: I am running Openstack Ansible Rocky 18.1.8 on Ubuntu 18.04 nodes. I use PCI-passthrough (IOMMU vfio) on GTX1080Tis and and RTX2080Tis. The 1080s work fine, but 2080 instances take anywhere from 3 minutes to over 3 hours to start with qemu/KVM and the amount of time varies randomly, with the averaging being around 1.5hrs. I tried upgrading the kernel to 5.0.0 and it did not fix the issue. Downgrading the GPU hosts to Ubuntu 16.04 fixed the issue, they now start in 30 seconds or less. Sorry, but I do not have any logs. I couldn't find any errors in any system logs including enabling debugging on libvirtd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841098/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846641] Re: eoan/linux: 5.3.0-17.18 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Saturday, 05. October 2019 01:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe-edge: bug 1846636 eoan/linux-aws: bug 1846613 eoan/linux-azure: bug 1846616 eoan/linux-gcp: bug 1846623 eoan/linux-kvm: bug 1846628 eoan/linux-oracle: bug 1846630 eoan/linux-raspi2: bug 1846611 eoan/linux-snapdragon: bug 1846634 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1846641 Title: eoan/linux: 5.3.0-17.18 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete 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-release series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Confirmed 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Saturday, 05. October 2019 01:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe-edge: bug 1846636 eoan/linux-aws: bug 1846613 eoan/linux-azure: bug 1846616 eoan/linux-gcp: bug 1846623 eoan/linux-kvm: bug 1846628 eoan/linux-oracle: bug 1846630 eoan/linux-raspi2: bug 1846611 eoan/linux-snapdragon: bug 1846634 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846641/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822363] Re: Booting hangs when USB 3.0 Etron EJ168 PCI card is detected
** 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/1822363 Title: Booting hangs when USB 3.0 Etron EJ168 PCI card is detected Status in linux package in Ubuntu: Fix Released Bug description: I have installed Etron EJ168 PCI USB 3.0 [1B6F:7023] which briliantly works in any Windows OS (I use multiboot PC) on my Conroe865PE AGP/PCI Intel Kentsfield QX6800 system with classic BIOS (non UEFI). There are no devices connected to PCI USB card during boot. The desktop Ubuntu 18.04 kernel 4.15.0-46-generic freezes with this card during boot (see attached "photo log" with boot and grub options). I can't access/login Ubuntu or console. It was checked and confirmed on ubuntu-18.04.1-desktop-amd64.iso LIVE CD desktop (with acpi=off option too). Previously I was used and removed USB 3.0 NEC Renesas upd720200 PCI card [1033:0194], which was partially workable under my installation of Ubuntu 18.04 and Windows. It had problems from time to time with FW load from card on start and not detecting USB devices connected even if FW present. I tried and also removed USB 3.0 NEC Renesas upd720202 PCI card [1912:0015] which also was partially workable in the same way (other card bios and newer NEC chip). System was fully bootable with NEC cards. The Etron EJ168 works superb on Windows OS's with directly or with hub connections with USB devices. I can assist in any way to solve this bug as IT Professional. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822363/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845719] Re: eoan/linux-raspi2: 5.3.0-1006.7 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => Fix Committed ** 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: 1846204 packages: main: linux-raspi2 meta: linux-meta-raspi2 - phase: Ready for Promote to Proposed - phase-changed: Thursday, 03. October 2019 15:07 UTC + phase: Promote to Proposed + phase-changed: Saturday, 05. October 2019 06:45 UTC reason: - promote-to-proposed: Stalled -- ready for review + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1845719 Title: eoan/linux-raspi2: 5.3.0-1006.7 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 source package in Eoan: Confirmed 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: 1846204 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Promote to Proposed phase-changed: Saturday, 05. October 2019 06:45 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1845719/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823076] Re: System wakes up immediately after suspend if Bluetooth is still enabled
"Same result" here means it doesn't wake up anymore? -- 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/1823076 Title: System wakes up immediately after suspend if Bluetooth is still enabled Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: After replacing my USB mouse with a BT mouse, I noticed my machine would no longer suspend without immediately waking up. i.e. I suspend and see the light go into the slow fade in and out for one cycle and then goes solid and the display wakes up again. If I disable BT (via blueman applet) suspend works fine. I've fixed this by shutting down the BT service before suspend, and starting it back up on wake, as indicated here: https://askubuntu.com/questions/797590/ubuntu-wakes-up-immediately- after-suspend Perhaps this script should be included in blueZ as suspend issues seem very hard to debug and the immediate wake after suspend could be caused many any number of things. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 [modified: lib/systemd/system/bluetooth.service] ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Apr 3 13:16:14 2019 InstallationDate: Installed on 2019-02-09 (53 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Intel(R) Client Systems NUC8i3BEH ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0051.2018.1015.1513 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0051.2018.1015.1513:bd10/15/2018:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.version: J72753-303 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:BB:60:50:92:5D ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1912660 acl:106009 sco:0 events:337 errors:0 TX bytes:12331 acl:74 sco:0 commands:204 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1823076/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846271] Re: Full video freeze kernel 4.15.0-65
Set "Storage=persistent" in journald.conf [1]. [1] https://www.freedesktop.org/software/systemd/man/journald.conf.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1846271 Title: Full video freeze kernel 4.15.0-65 Status in linux package in Ubuntu: Incomplete Bug description: Must restart PC to recover. Everything else seems to continue to work, like music/video playing continues even though I can no longer see any updates to video, no mouse movement and no keyboard entries seem to work. Reverted back to 4.15.0-64 for stability. Unable to provide the ubuntu-bug linux due to inability to make any entries on frozen desktop. --- ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lmcor 3039 F pulseaudio /dev/snd/controlC0: lmcor 3039 F pulseaudio CurrentDesktop: KDE DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=bf754a96-f70b-4964-bdbb-b7ab12e42018 InstallationDate: Installed on 2018-09-30 (366 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171127 MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-64-generic root=UUID=7663b459-8677-4afe-85fb-12424af45024 ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-64.73~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-64-generic N/A linux-backports-modules-4.15.0-64-generic N/A linux-firmware 1.157.22 Tags: sylvia Uname: Linux 4.15.0-64-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev root sambashare sudo _MarkForUpload: True dmi.bios.date: 01/22/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3803 dmi.board.asset.tag: Default string dmi.board.name: PRIME X370-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3803:bd01/22/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX370-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846271/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846248] Re: precise/linux-lts-trusty: 3.13.0-174.225~12.04.1 -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: 1846250 packages: main: linux-lts-trusty meta: linux-meta-lts-trusty signed: linux-signed-lts-trusty phase: Ready for Promote to Proposed phase-changed: Friday, 04. October 2019 17:41 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Stalled -- ready for review variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1846248 Title: precise/linux-lts-trusty: 3.13.0-174.225~12.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Confirmed 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: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Confirmed Bug description: This bug 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: 1846250 packages: main: linux-lts-trusty meta: linux-meta-lts-trusty signed: linux-signed-lts-trusty phase: Ready for Promote to Proposed phase-changed: Friday, 04. October 2019 17:41 UTC reason: promote-to-proposed: Stalled -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846248/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
