[Kernel-packages] [Bug 1776242] Re: CONFIG_CC_STACKPROTECTOR is now defined on Makefile
This was not an issue in the kernel; rather the qa-regression-testing script needed to take into account the auto-detection of the compiler's ability to perform stack protection and the restructuring of the config option due to that. I have fixed this in https://git.launchpad.net/qa- regression-testing/commit/?id=69b1392a208985e90857facbe367e3af635c8228 . Unfortunately, it looks to change a bit again in the 4.18 kernel, but I think I have the checks set up to work properly when that lands as well. ** Changed in: linux (Ubuntu Cosmic) Status: Confirmed => Invalid ** Also affects: qa-regression-testing Importance: Undecided Status: New ** Changed in: qa-regression-testing Assignee: (unassigned) => Steve Beattie (sbeattie) ** Changed in: qa-regression-testing Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776242 Title: CONFIG_CC_STACKPROTECTOR is now defined on Makefile Status in QA Regression Testing: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Cosmic: Invalid Bug description: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-cosmic-canonical-kernel-team- bootstrap/cosmic/amd64/l/linux/20180524_171024_2701c@/log.gz 15:41:48 ERROR| [stderr] CONFIG_CC_STACKPROTECTOR set ... FAIL commit 2bc2f688fdf8808de4f36be563ccdb0bde7c0c54 Makefile: move stack-protector availability out of Kconfig + ifndef stackp-broken +# If the stack protector is functional, enable code that depends on it. +KBUILD_CPPFLAGS += -DCONFIG_CC_STACKPROTECTOR + endif To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1776242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781433] Re: linux: 4.15.0-28.30 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/bionic/4.15.0-28.30 /bionic-proposed-published.html ** Tags added: certification-testing-passed ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781433 Title: linux: 4.15.0-28.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1781437 (linux-hwe), bug 1781438 (linux-hwe-edge), bug 1781072 (azure), bug 1781074 (azure-edge), bug 1781115 (gcp) derivatives: bug 1781435 (linux-aws), bug 1781066 (azure), bug 1781067 (gcp), bug 1781068 (kvm), bug 1781063 (raspi2), bug 1781064 (oem) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1781433/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782085] [NEW] Kernel panic, iSCSI, Unable to handle kernel pointer dereference in virtual kernel address space
You have been subscribed to a public bug: Description will follow ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-169770 severity-high targetmilestone-inin1804 -- Kernel panic,iSCSI,Unable to handle kernel pointer dereference in virtual kernel address space https://bugs.launchpad.net/bugs/1782085 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782085] [NEW] Kernel panic, iSCSI, Unable to handle kernel pointer dereference in virtual kernel address space
Public bug reported: Description will follow ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-169770 severity-high targetmilestone-inin1804 ** Tags added: architecture-s39064 bugnameltc-169770 severity-high targetmilestone-inin1804 ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782085 Title: Kernel panic,iSCSI,Unable to handle kernel pointer dereference in virtual kernel address space Status in linux package in Ubuntu: New Bug description: Description will follow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782085/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782085] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2018-07-17 03:53 EDT--- ---Problem Description--- Kernel panic,Unable to handle kernel pointer dereference in virtual kernel address space Contact Information = Michael Finnegan/finne...@us.ibm.com ---uname output--- Linux ilzlnx4 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:57:26 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1 - IO running to iscsi luns 2 - Error inject running was storage side switch port bounce (off/on) Stack trace output: "ilzlnx4 login:" "[551709.743278] Unable to handle kernel pointer dereference in virtual kernel ad" "dress space" "[551709.743952] Failing address: TEID: 0483" "[551709.743955] Fault in home space mode while using kernel ASCE." "[551709.743959] AS:00eb0007 R3:0001f3bd0007 S:0001f3bd4000 P:000" 0013d "[551709.743990] Oops: 0004 ilc:3 [#1] SMP" "[551709.743994] Modules linked in: iptable_filter binfmt_misc rpcsec_gss_krb5 au" "th_rpcgss nfsv4 nfs lockd grace fscache dm_round_robin dm_service_time dm_multip" "ath scsi_dh_rdac scsi_dh_emc scsi_dh_alua qeth_l2 s390_trng ghash_s390 prng aes_" "s390 des_s390 des_generic sha512_s390 sha256_s390 sha1_s390 sha_common chsc_sch" "eadm_sch qeth qdio ccwgroup vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq" "_codel ib_iser rdma_cm iw_cm sunrpc ib_cm ib_core iscsi_tcp libiscsi_tcp libiscs" "i scsi_transport_iscsi ip_tables x_tables crc32_vx_s390 dasd_eckd_mod dasd_mod" "[551709.744079] CPU: 2 PID: 39417 Comm: kworker/u512:1 Not tainted 4.15.0-15-gen" "eric #16-Ubuntu" "[551709.744083] Hardware name: IBM 3906 M05 7G4 (LPAR)" "[551709.744099] Workqueue: iscsi_q_3 iscsi_xmitworker [libiscsi]" "[551709.744104] Krnl PSW : 06270506 152bbcbd (__iscsi_get_task+0" "x6/0x18 [libiscsi])" "[551709.744148]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 RI" ":0 EA:3" "[551709.744154] Krnl GPRS: 0008 0001e0e3fce0 00" 008400 "[551709.744339]03ff80126640 0001e4f0e400 00" 0003ff801267cc "[551709.744342]03ff8012669c 00" 01e161ab10 "[551709.744937]0001f3a93000 0001e161aba2 03ff80121e8e 00" 01e0e3fc90 "[551709.745123] Krnl Code: 03ff80121624: c0f4fcf6 brcl 15,3ff80" 121010 "[551709.745123]03ff8012162a: c0f4377b brcl 15,3ff80" 128520 "[551709.745123] #03ff80121630: c004 brcl 0,3ff801" 21630 "[551709.745123] >03ff80121636: eb012078006a asi 120(%r2)" ",1" "[551709.745123]03ff8012163c: c0f43772 brcl 15,3ff80" 128520 "[551709.745123]03ff80121642: 0707 bcr 0,%r7" "[551709.745123]03ff80121644: 0707 bcr 0,%r7" "[551709.745123]03ff80121646: 0707 bcr 0,%r7" "[551709.745246] Call Trace:" "[551709.745441] ([<03ff80121ec6>] iscsi_xmit_task+0x86/0x138 [libiscsi])" "[551709.745450] [<03ff8012669c>] iscsi_data_xmit+0x44c/0x548 [libiscsi]" "[551709.745478] [<03ff801267cc>] iscsi_xmitworker+0x34/0x58 [libiscsi]" "[551709.745488] [<001911c2>] process_one_work+0x262/0x4d8" "[551709.745492] [<00191490>] worker_thread+0x58/0x4e8" "[551709.745497] [<001985f4>] kthread+0x14c/0x168" "[551709.745503] [<008ee45a>] kernel_thread_starter+0xa/0x10" "[551709.745506] [<008ee450>] kernel_thread_starter+0x0/0x10" "[551709.745509] Last Breaking-Event-Address:" "[551709.745516] [<03ff80121e88>] iscsi_xmit_task+0x48/0x138 [libiscsi]" [551709.745565] "[551709.745566] Kernel panic - not syncing: Fatal exception in interrupt" Oops output: Oops: 0004 ilc:3 [#1] SMP System Dump Info: The system is not configured to capture a system dump. -Post a private note with access information to the machine that the bug is occuring on. -Attach sysctl -a output output to the bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782085 Title: Kernel panic,iSCSI,Unable to handle kernel pointer dereference in virtual kernel address space Status in linux package in Ubuntu: New Bug description: Description will follow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782085/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781763] Re: HP ProBook 455 G5 needs mute-led-gpio fixup
Patch applied upstream [1], thanks for the report and the patch. It will be cherry-picked to Ubuntu kernel in the future. [1] http://mailman.alsa-project.org/pipermail/alsa- devel/2018-July/138153.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/1781763 Title: HP ProBook 455 G5 needs mute-led-gpio fixup Status in linux package in Ubuntu: In Progress Bug description: I noticed that the audio LEDs on this model's keyboard were not functioning. After a great deal of research, I found I needed to patch the kernel to apply an existing fixup for my particular model. I built a custom kernel to test it, and it does indeed fix my problem. I would appreciate it if this patch could be included in a future kernel build. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781763/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782091] [NEW] msgctl02 in ubuntu_ltp_syscalls failed with X
Public bug reported: Steps as root: 1. git clone --depth=1 https://github.com/linux-test-project/ltp.git 2. cd ltp; make autotools 3. ./configure 4. make 5. make install $ cat /tmp/test.txt msgctl01 msgctl01 msgctl02 msgctl02 msgctl03 msgctl03 msgctl04 msgctl04 msgstress01 msgstress01 msgstress02 msgstress02 msgstress03 msgstress03 msgstress04 msgstress04 msgctl12 msgctl12 $ sudo /opt/ltp/runltp -f /tmp/test.txt Test output: <<>> tag=msgctl02 stime=1531815429 cmdline="msgctl02" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s tst_safe_sysv_ipc.c:51: BROK: msgctl02.c:68: msgget(1627521041, 7b0) failed: EEXIST Summary: passed 0 failed 0 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=2 corefile=no cutime=0 cstime=0 <<>> This failure can be reproduced with the kernel in -release 4.4.0-130-generic, therefore it should not be considered as a regression. There is a recent change for msgctl02 (79eac0a) in the ltp repo. It's worthy to revert it to see if it's the tool change that cause this. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-130-generic 4.4.0-130.156 ProcVersionSignature: User Name 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 17 07:55 seq crw-rw 1 root audio 116, 33 Jul 17 07:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jul 17 08:15:58 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic.efi.signed root=UUID=051b34ce-dfed-4e36-aa78-851c5a284ee4 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-130-generic N/A linux-backports-modules-4.4.0-130-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2015 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd12/27/2015:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug uec-images xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782091 Title: msgctl02 in ubuntu_ltp_syscalls failed with X Status in linux package in Ubuntu: Confirmed Bug description: Steps as root: 1. git clone --depth=1 https://github.com/linux-test-project/ltp.git 2. cd ltp; make autotools 3. ./configure 4. make 5. make install $ cat /tmp/test.txt msgctl01 msgctl01 msgctl02 msgctl02 msgctl03 msgctl03 msgctl04 msgctl04 msgstress01 msgstress01 msgstress02 msgstress02 msgstress03 msgstress03 msgstress04 msgstress04 msgctl12 msgctl12 $ sudo /opt/ltp/runltp -f /tmp/test.txt Test output: <<>> tag=msgctl02 stime=1531815429 cmdline="msgctl02" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s tst_safe_sysv_ipc.c:51: BROK: msgctl02.c:68: msgget(1627521041, 7b0) failed: EEXIST Summary: passed 0 failed 0 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=2 corefile=no cutime=0 cstime=0 <<>> This failure can be reproduced with the kernel in -release 4.4.0-130-generic, therefore it should not be considered as a regression. There is a recent change for msgctl02 (79eac0a) in the ltp repo. It's worthy to revert it to see if it's the tool change that cause this. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-130-generic 4.4.0-130.156 ProcVersionSignature: User Name 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 17 07:55 seq crw-rw 1 root audio 116, 33 Jul 17 07:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/
[Kernel-packages] [Bug 1654517] Re: ZFS I/O hangs for minutes
This stack trace is similar to one in https://github.com/zfsonlinux/zfs/issues/2934 - the suspected issue is that one of the devices is taking a long time to complete and ZFS is blocked waiting for this. I suggest installing sysstat sudo apt install sysstat and when the lockup happens run: iostat -mx so that we can see if it is a long device delay or not. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1654517 Title: ZFS I/O hangs for minutes Status in Native ZFS for Linux: Fix Released Status in zfs-linux package in Ubuntu: Incomplete Bug description: I/O for multiple programs, like `thunderbird`, `firefox`, etc., hangs for minutes and approx. 100 `z_rd_int_[n]` and `z_wr_int_[n]` kernel threads are created, `dmesg` contains [ 9184.451606] INFO: task txg_sync:11471 blocked for more than 120 seconds. [ 9184.451610] Tainted: P OE 4.8.0-32-generic #34-Ubuntu [ 9184.451611] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 9184.451612] txg_syncD a240ab3a7aa8 0 11471 2 0x [ 9184.451616] a240ab3a7aa8 00ffbb6ade1f a24095148000 a240e5ca5580 [ 9184.451618] 0046 a240ab3a8000 a240ff359200 7fff [ 9184.451620] a23d36cf9050 0001 a240ab3a7ac0 bbe96b15 [ 9184.451621] Call Trace: [ 9184.451627] [] schedule+0x35/0x80 [ 9184.451628] [] schedule_timeout+0x22a/0x3f0 [ 9184.451631] [] ? __switch_to+0x2ce/0x6c0 [ 9184.451633] [] ? pick_next_task_fair+0x48c/0x4c0 [ 9184.451635] [] ? ktime_get+0x41/0xb0 [ 9184.451636] [] io_schedule_timeout+0xa4/0x110 [ 9184.451644] [] cv_wait_common+0xb2/0x130 [spl] [ 9184.451646] [] ? wake_atomic_t_function+0x60/0x60 [ 9184.451650] [] __cv_wait_io+0x18/0x20 [spl] [ 9184.451689] [] zio_wait+0xfd/0x1d0 [zfs] [ 9184.451716] [] dsl_pool_sync+0xb8/0x480 [zfs] [ 9184.451745] [] spa_sync+0x37f/0xb30 [zfs] [ 9184.451747] [] ? default_wake_function+0x12/0x20 [ 9184.451779] [] txg_sync_thread+0x3a5/0x600 [zfs] [ 9184.451807] [] ? txg_delay+0x160/0x160 [zfs] [ 9184.451811] [] thread_generic_wrapper+0x71/0x80 [spl] [ 9184.451815] [] ? __thread_exit+0x20/0x20 [spl] [ 9184.451817] [] kthread+0xd8/0xf0 [ 9184.451819] [] ret_from_fork+0x1f/0x40 [ 9184.451821] [] ? kthread_create_on_node+0x1e0/0x1e0 [ 9184.451849] INFO: task mozStorage #2:21607 blocked for more than 120 seconds. [ 9184.451851] Tainted: P OE 4.8.0-32-generic #34-Ubuntu [ 9184.451852] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 9184.451853] mozStorage #2 D a23fe8a5bd38 0 21607 19750 0x0004 [ 9184.451855] a23fe8a5bd38 00ffa240ee8feb40 a240ecf72ac0 a2403803b900 [ 9184.451857] bc2c02f7 a23fe8a5c000 a240aa940828 a240aa940800 [ 9184.451858] a240aa940980 a23fe8a5bd50 bbe96b15 [ 9184.451860] Call Trace: [ 9184.451861] [] schedule+0x35/0x80 [ 9184.451866] [] cv_wait_common+0x110/0x130 [spl] [ 9184.451868] [] ? wake_atomic_t_function+0x60/0x60 [ 9184.451872] [] __cv_wait+0x15/0x20 [spl] [ 9184.451904] [] zil_commit.part.11+0x79/0x7a0 [zfs] [ 9184.451909] [] ? tsd_hash_search.isra.0+0x46/0xa0 [spl] [ 9184.451913] [] ? tsd_set+0x2b4/0x500 [spl] [ 9184.451914] [] ? mutex_lock+0x12/0x30 [ 9184.451945] [] zil_commit+0x17/0x20 [zfs] [ 9184.451975] [] zfs_fsync+0x7a/0xf0 [zfs] [ 9184.452005] [] zpl_fsync+0x68/0xa0 [zfs] [ 9184.452008] [] vfs_fsync_range+0x4b/0xb0 [ 9184.452010] [] do_fsync+0x3d/0x70 [ 9184.452011] [] SyS_fsync+0x10/0x20 [ 9184.452013] [] entry_SYSCALL_64_fastpath+0x1e/0xa8 [ 9184.452023] INFO: task bitcoin-msghand:663 blocked for more than 120 seconds. [ 9184.452024] Tainted: P OE 4.8.0-32-generic #34-Ubuntu [ 9184.452025] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 9184.452026] bitcoin-msghand D a23eeb23bd38 0 663 26994 0x [ 9184.452028] a23eeb23bd38 00ffa23eab434000 a240ecf7 a24095148000 [ 9184.452030] a23eeb23bd20 a23eeb23c000 a240aa940828 a240aa940800 [ 9184.452031] a240aa940980 a23eeb23bd50 bbe96b15 [ 9184.452033] Call Trace: [ 9184.452034] [] schedule+0x35/0x80 [ 9184.452039] [] cv_wait_common+0x110/0x130 [spl] [ 9184.452041] [] ? wake_atomic_t_function+0x60/0x60 [ 9184.452044] [] __cv_wait+0x15/0x20 [spl] [ 9184.452074] [] zil_commit.part.11+0x79/0x7a0 [zfs]
[Kernel-packages] [Bug 1782093] [NEW] msgctl04 in ubuntu_ltp_syscalls failed with X
Public bug reported: Steps as root: 1. git clone --depth=1 https://github.com/linux-test-project/ltp.git 2. cd ltp; make autotools 3. ./configure 4. make 5. make install $ sudo /opt/ltp/runltp -s msgctl02 Test output: <<>> tag=msgctl04 stime=1531753902 cmdline="msgctl04" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s tst_safe_sysv_ipc.c:51: BROK: msgctl04.c:93: msgget(1627521048, 600) failed: EEXIST Summary: passed 0 failed 0 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=2 corefile=no cutime=0 cstime=0 <<>> This failure can be reproduced with the kernel in -release 4.4.0-130-generic, therefore it should not be considered as a regression. There is a recent change for msgctl02 (79eac0a) in the ltp repo. It's worthy to revert it to see if it's the tool change that cause this. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-130-generic 4.4.0-130.156 ProcVersionSignature: User Name 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 17 07:55 seq crw-rw 1 root audio 116, 33 Jul 17 07:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jul 17 08:25:57 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic.efi.signed root=UUID=051b34ce-dfed-4e36-aa78-851c5a284ee4 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-130-generic N/A linux-backports-modules-4.4.0-130-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2015 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd12/27/2015:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug uec-images xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782093 Title: msgctl04 in ubuntu_ltp_syscalls failed with X Status in linux package in Ubuntu: New Bug description: Steps as root: 1. git clone --depth=1 https://github.com/linux-test-project/ltp.git 2. cd ltp; make autotools 3. ./configure 4. make 5. make install $ sudo /opt/ltp/runltp -s msgctl02 Test output: <<>> tag=msgctl04 stime=1531753902 cmdline="msgctl04" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s tst_safe_sysv_ipc.c:51: BROK: msgctl04.c:93: msgget(1627521048, 600) failed: EEXIST Summary: passed 0 failed 0 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=2 corefile=no cutime=0 cstime=0 <<>> This failure can be reproduced with the kernel in -release 4.4.0-130-generic, therefore it should not be considered as a regression. There is a recent change for msgctl02 (79eac0a) in the ltp repo. It's worthy to revert it to see if it's the tool change that cause this. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-130-generic 4.4.0-130.156 ProcVersionSignature: User Name 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 17 07:55 seq crw-rw 1 root audio 116, 33 Jul 17 07:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jul 17 08:25:57 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic.efi.signed root=UUID=051b34ce-dfed-4e36-aa78-851c5a284ee
[Kernel-packages] [Bug 1782091] Re: msgctl02 in ubuntu_ltp_syscalls failed with X
** Description changed: Steps as root: - 1. git clone --depth=1 https://github.com/linux-test-project/ltp.git - 2. cd ltp; make autotools - 3. ./configure - 4. make - 5. make install + 1. git clone --depth=1 https://github.com/linux-test-project/ltp.git + 2. cd ltp; make autotools + 3. ./configure + 4. make + 5. make install - $ cat /tmp/test.txt - msgctl01 msgctl01 - msgctl02 msgctl02 - msgctl03 msgctl03 - msgctl04 msgctl04 - msgstress01 msgstress01 - msgstress02 msgstress02 - msgstress03 msgstress03 - msgstress04 msgstress04 - msgctl12 msgctl12 - - $ sudo /opt/ltp/runltp -f /tmp/test.txt - + $ sudo /opt/ltp/runltp -s msgctl02 Test output: <<>> tag=msgctl02 stime=1531815429 cmdline="msgctl02" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s tst_safe_sysv_ipc.c:51: BROK: msgctl02.c:68: msgget(1627521041, 7b0) failed: EEXIST Summary: passed 0 failed 0 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=2 corefile=no cutime=0 cstime=0 <<>> - - This failure can be reproduced with the kernel in -release 4.4.0-130-generic, therefore it should not be considered as a regression. + This failure can be reproduced with the kernel in -release + 4.4.0-130-generic, therefore it should not be considered as a + regression. There is a recent change for msgctl02 (79eac0a) in the ltp repo. It's worthy to revert it to see if it's the tool change that cause this. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-130-generic 4.4.0-130.156 ProcVersionSignature: User Name 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic x86_64 AlsaDevices: - total 0 - crw-rw 1 root audio 116, 1 Jul 17 07:55 seq - crw-rw 1 root audio 116, 33 Jul 17 07:55 timer + total 0 + crw-rw 1 root audio 116, 1 Jul 17 07:55 seq + crw-rw 1 root audio 116, 33 Jul 17 07:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jul 17 08:15:58 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: - + ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic.efi.signed root=UUID=051b34ce-dfed-4e36-aa78-851c5a284ee4 ro RelatedPackageVersions: - linux-restricted-modules-4.4.0-130-generic N/A - linux-backports-modules-4.4.0-130-generic N/A - linux-firmware 1.157.20 + linux-restricted-modules-4.4.0-130-generic N/A + linux-backports-modules-4.4.0-130-generic N/A + linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2015 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd12/27/2015:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782091 Title: msgctl02 in ubuntu_ltp_syscalls failed with X Status in linux package in Ubuntu: Confirmed Bug description: Steps as root: 1. git clone --depth=1 https://github.com/linux-test-project/ltp.git 2. cd ltp; make autotools 3. ./configure 4. make 5. make install $ sudo /opt/ltp/runltp -s msgctl02 Test output: <<>> tag=msgctl02 stime=1531815429 cmdline="msgctl02" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s tst_safe_sysv_ipc.c:51: BROK: msgctl02.c:68: msgget(1627521041, 7b0) failed: EEXIST Summary: passed 0 failed 0 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=2 corefile=no cutime=0 cstime=0 <<>> This failure can be reproduced with the kernel in -release 4.4.0-130-generic, therefore it should not be considered as a regression. There is a recent change for msgctl02 (79eac0a) in the ltp repo. It's worthy to revert it to see if it's the tool change that cause this. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.
[Kernel-packages] [Bug 1782091] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782091 Title: msgctl02 in ubuntu_ltp_syscalls failed with X Status in linux package in Ubuntu: Confirmed Bug description: Steps as root: 1. git clone --depth=1 https://github.com/linux-test-project/ltp.git 2. cd ltp; make autotools 3. ./configure 4. make 5. make install $ sudo /opt/ltp/runltp -s msgctl02 Test output: <<>> tag=msgctl02 stime=1531815429 cmdline="msgctl02" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s tst_safe_sysv_ipc.c:51: BROK: msgctl02.c:68: msgget(1627521041, 7b0) failed: EEXIST Summary: passed 0 failed 0 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=2 corefile=no cutime=0 cstime=0 <<>> This failure can be reproduced with the kernel in -release 4.4.0-130-generic, therefore it should not be considered as a regression. There is a recent change for msgctl02 (79eac0a) in the ltp repo. It's worthy to revert it to see if it's the tool change that cause this. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-130-generic 4.4.0-130.156 ProcVersionSignature: User Name 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 17 07:55 seq crw-rw 1 root audio 116, 33 Jul 17 07:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jul 17 08:15:58 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic.efi.signed root=UUID=051b34ce-dfed-4e36-aa78-851c5a284ee4 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-130-generic N/A linux-backports-modules-4.4.0-130-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2015 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd12/27/2015:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782091/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU
Got the same problem on a Dell E6400 Laptop. Systemd-udevd climbs to 100% cpu usage in minutes, making it verify difficult and horrible to install, if one can manage to find the patience, only to find out that this problem persists after the installation. I could install after: systemctl disable systemd-udevd.service systemctl disable systemd-udevd-control.socket systemctl disable systemd-udevd-kernel.socket systemctl stop systemd-udevd.service systemctl stop systemd-udevd-control.socket systemctl stop systemd-udevd-kernel.socket then kill -9 any systemd-udevd process that remained active After this the installation went fine and fast. Disabling bluetooth in the bios did not work for me. Disabling wireless in the bios works to some extend, systemd-udevd takes around ~50% cpu instead of 100% Downgrade to 4.13 kernel worked like a charm, no problems after that. I had some problems switching to the nvidia driver, so i had to stick with nouveau (which works great) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1759836 Title: systemd-udevd consumes 100% of CPU Status in Bluez Utilities: Confirmed Status in linux: Confirmed Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1759836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1778476] Re: [bionic] high cpu load HP probook iio-sensor-proxy
Bug reported upstream: https://github.com/hadess/iio-sensor-proxy/issues/231 ** Bug watch added: github.com/hadess/iio-sensor-proxy/issues #231 https://github.com/hadess/iio-sensor-proxy/issues/231 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1778476 Title: [bionic] high cpu load HP probook iio-sensor-proxy Status in linux package in Ubuntu: Confirmed Bug description: I have a many HP ProBook 450 G1 and HP ProBook 650 G3 with fresh install of Ubuntu Desktop. They all have a load average of 1.0 when idle (no graphical session opened). vmstat shows idle =~ 100% The process which uses most CPU time is iio-sensor-proxy (about 1%) and it's constantly in D state (uninterruptible sleep). Manually starting this command shows that the sensor (lis3lv02d on both products) is constantly sending garbage informations (see attachment). With iio-sensor-proxy service stopped, the CPU load is ~ 0% As the service is 'static' and can not be disabled, the only workaround is to remove the 'iios-sensor-proxy' package. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1371 F pulseaudio ljanvier 2104 F pulseaudio /dev/snd/controlC0: gdm1371 F pulseaudio ljanvier 2104 F pulseaudio DistroRelease: Ubuntu 18.04 MachineType: Hewlett-Packard HP ProBook 650 G1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=e375b9cb-3776-455a-bb2e-24f826528047 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UnreportableReason: Ce rapport concerne un paquet qui n'est pas installé. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 12/24/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L77 Ver. 01.31 dmi.board.name: 1993 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 16.3A dmi.chassis.asset.tag: 5CG5124FWZ dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL77Ver.01.31:bd12/24/2014:svnHewlett-Packard:pnHPProBook650G1:pvrA3009DD10303:rvnHewlett-Packard:rn1993:rvrKBCVersion16.3A:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP ProBook 650 G1 dmi.product.version: A3009DD10303 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782085] Re: Kernel panic, iSCSI, Unable to handle kernel pointer dereference in virtual kernel address space
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Status: New => Triaged ** Changed in: ubuntu-z-systems Importance: Undecided => High ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782085 Title: Kernel panic,iSCSI,Unable to handle kernel pointer dereference in virtual kernel address space Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: New Bug description: Description will follow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1782085/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782093] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782093 Title: msgctl04 in ubuntu_ltp_syscalls failed with X Status in linux package in Ubuntu: Confirmed Bug description: Steps as root: 1. git clone --depth=1 https://github.com/linux-test-project/ltp.git 2. cd ltp; make autotools 3. ./configure 4. make 5. make install $ sudo /opt/ltp/runltp -s msgctl02 Test output: <<>> tag=msgctl04 stime=1531753902 cmdline="msgctl04" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s tst_safe_sysv_ipc.c:51: BROK: msgctl04.c:93: msgget(1627521048, 600) failed: EEXIST Summary: passed 0 failed 0 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=2 corefile=no cutime=0 cstime=0 <<>> This failure can be reproduced with the kernel in -release 4.4.0-130-generic, therefore it should not be considered as a regression. There is a recent change for msgctl02 (79eac0a) in the ltp repo. It's worthy to revert it to see if it's the tool change that cause this. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-130-generic 4.4.0-130.156 ProcVersionSignature: User Name 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 17 07:55 seq crw-rw 1 root audio 116, 33 Jul 17 07:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jul 17 08:25:57 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic.efi.signed root=UUID=051b34ce-dfed-4e36-aa78-851c5a284ee4 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-130-generic N/A linux-backports-modules-4.4.0-130-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2015 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd12/27/2015:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782093/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782085] Re: Kernel panic, iSCSI, Unable to handle kernel pointer dereference in virtual kernel address space
I'm wondering why a pre-GA bionic (according to the tags) kernel was used? ==> 4.15.0-15 The GA kernel was 4.15.0.20 and we are now in between on an even higher level: linux-generic | 4.15.0.20.23 | bionic | s390x linux-generic | 4.15.0.23.25 | bionic-security | s390x linux-generic | 4.15.0.23.25 | bionic-updates | s390x ( linux-generic | 4.15.0.28.30 | bionic-proposed | s390x) Please always make sure that you are on the latest kernel level! (Of course not necessarily on the proposed level ...) Does that also happen with the current/latest kernel? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782085 Title: Kernel panic,iSCSI,Unable to handle kernel pointer dereference in virtual kernel address space Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: New Bug description: Description will follow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1782085/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782091] Re: msgctl02 in ubuntu_ltp_syscalls failed with X/B
Can be reproduced with Bionic. ** Summary changed: - msgctl02 in ubuntu_ltp_syscalls failed with X + msgctl02 in ubuntu_ltp_syscalls failed with X/B ** Description changed: Steps as root: 1. git clone --depth=1 https://github.com/linux-test-project/ltp.git 2. cd ltp; make autotools 3. ./configure 4. make 5. make install - $ sudo /opt/ltp/runltp -s msgctl02 + $ cat /tmp/test.txt + msgctl01 msgctl01 + msgctl02 msgctl02 + msgctl03 msgctl03 + msgctl04 msgctl04 + msgstress01 msgstress01 + msgstress02 msgstress02 + msgstress03 msgstress03 + msgstress04 msgstress04 + msgctl12 msgctl12 + + $ sudo /opt/ltp/runltp -f /tmp/test.txt Test output: <<>> tag=msgctl02 stime=1531815429 cmdline="msgctl02" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s tst_safe_sysv_ipc.c:51: BROK: msgctl02.c:68: msgget(1627521041, 7b0) failed: EEXIST Summary: passed 0 failed 0 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=2 corefile=no cutime=0 cstime=0 <<>> This failure can be reproduced with the kernel in -release 4.4.0-130-generic, therefore it should not be considered as a regression. - There is a recent change for msgctl02 (79eac0a) in the ltp repo. It's - worthy to revert it to see if it's the tool change that cause this. + If you run only this test after a reboot, it will pass for the first time. + tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s + msgctl02.c:47: PASS: msgctl(IPC_SET) msg_qbytes - 1 + msgctl02.c:54: PASS: msg_qbytes = 16383 + + + There is a recent change for msgctl02 (79eac0a) in the ltp repo. This test can pass with with commit revert back to 1a11467414 + ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-130-generic 4.4.0-130.156 ProcVersionSignature: User Name 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 17 07:55 seq crw-rw 1 root audio 116, 33 Jul 17 07:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jul 17 08:15:58 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic.efi.signed root=UUID=051b34ce-dfed-4e36-aa78-851c5a284ee4 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-130-generic N/A linux-backports-modules-4.4.0-130-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2015 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd12/27/2015:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782091 Title: msgctl02 in ubuntu_ltp_syscalls failed with X/B Status in linux package in Ubuntu: Confirmed Bug description: Steps as root: 1. git clone --depth=1 https://github.com/linux-test-project/ltp.git 2. cd ltp; make autotools 3. ./configure 4. make 5. make install $ cat /tmp/test.txt msgctl01 msgctl01 msgctl02 msgctl02 msgctl03 msgctl03 msgctl04 msgctl04 msgstress01 msgstress01 msgstress02 msgstress02 msgstress03 msgstress03 msgstress04 msgstress04 msgctl12 msgctl12 $ sudo /opt/ltp/runltp -f /tmp/test.txt Test output: <<>> tag=msgctl02 stime=1531815429 cmdline="msgctl02" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s tst_safe_sysv_ipc.c:51: BROK: msgctl02.c:68: msgget(1627521041, 7b0) failed: EEXIST Summary: passed 0 failed 0 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=2 corefile=no cutime=0 cstime=0 <<>> This failure can be reproduced with the kernel in -release 4.4.0-130-generic, therefore it should not be considered as a regression. If you run only this test after a reboot, it will pass for the first time. tst_test.c:1015: INFO: Timeout per run is 0h 05m
[Kernel-packages] [Bug 1781924] Re: Kernel wrong temperature reporting
Seems like shutdowns disappeared after disabling thermald service. Could it be a broken package problem? Package: thermald Architecture: amd64 Version: 1.7.0-5ubuntu1 Priority: optional Section: admin Origin: Ubuntu Maintainer: Colin King Original-Maintainer: Colin King Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 583 Depends: libc6 (>= 2.16), libdbus-1-3 (>= 1.9.14), libdbus-glib-1-2 (>= 0.88), libgcc1 (>= 1:3.0), libglib2.0-0 (>= 2.37.3), libstdc++6 (>= 5.2), libxml2 (>= 2.7.4), lsb-base (>= 3.0-6) Filename: pool/main/t/thermald/thermald_1.7.0-5ubuntu1_amd64.deb Size: 185220 MD5sum: 842c83b5d474d8366bdc4ffdf201db21 SHA1: 5cdfc914bc11e37bdd47620874e015fb10387ab8 SHA256: 9734e7700262f4b9a03dfd3e0f59044871228339452edb7aa11afd6cfc9743c1 Homepage: https://github.com/01org/thermal_daemon Description-en: Thermal monitoring and controlling daemon Thermal Daemon is a Linux daemon for monitoring and controlling platform temperatures. Once the system temperature reaches a certain threshold, the Linux daemon activates various cooling methods to try to cool the system. Description-md5: b3957326598bfd50927c3294bfbabcc9 Task: ubuntu-budgie-desktop Supported: 5y -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781924 Title: Kernel wrong temperature reporting Status in linux package in Ubuntu: Confirmed Bug description: I'm having some thermal trouble since I've started using kernel >4.0.x with my new laptop. According to psensor and sensord, CPU temperature jumps above the 90C, stays there for around 1second, and goes back to 50C. All transitions happen in around 100ms. I've cleaned and re- applied thermal paste and checked the connections twice. More interestingly, this doesn't happen when the CPU is under heavy-load, but when it is waiting idly. Sometimes sensord reports the CPU temp has gone over the critical threshold of the CPU and device shuts down itself immediately. There is also Windows 10 installed as a dual boot and didn't see this problem on it when idle or under heavy load. Dmesg output is full of following warnings; [ 1282.296247] CPU0: Core temperature above threshold, cpu clock throttled (total events = 109)[ 1282.296267] CPU4: Core temperature above threshold, cpu clock throttled (total events = 109) [ 1282.296269] CPU5: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296269] CPU1: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296271] CPU4: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296272] CPU6: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296273] CPU2: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296274] CPU7: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296275] CPU3: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296281] CPU0: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.297226] CPU4: Core temperature/speed normal [ 1282.297227] CPU5: Package temperature/speed normal [ 1282.297228] CPU0: Core temperature/speed normal [ 1282.297229] CPU1: Package temperature/speed normal [ 1282.297229] CPU0: Package temperature/speed normal [ 1282.297230] CPU4: Package temperature/speed normal [ 1282.297233] CPU3: Package temperature/speed normal [ 1282.297233] CPU7: Package temperature/speed normal [ 1282.297269] CPU2: Package temperature/speed normal [ 1282.297269] CPU6: Package temperature/speed normal Because of wrong temperature reporting, kernel throttles the CPU and reduces overall performance, which results in frustrating user experience. I've tried followings and find a temporary solution; - intel_pstate enabled, turbo-boost enabled > problem exists - intel_pstate enabled, turbo-boost disabled > problem frequency reduced - intel_pstate disabled, governor set to anythig other than powersave > problem exists - intel_pstate disabled, governor set to powersave > problem frequency reduced I'm suspicious about a kernel bug such as; - https://bugzilla.redhat.com/show_bug.cgi?id=924570 - https://bugzilla.redhat.com/show_bug.cgi?id=1317190 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D7p: burak 1547 F...m pulseaudio /dev/snd/controlC0: burak 1547 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19 HibernationDevice: RESUME=UUID=60a9fd7e-ec69-448a-b19a-93efaa6035ed Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. Bus 001
[Kernel-packages] [Bug 1782091] Re: msgctl02 in ubuntu_ltp_syscalls failed with X/B
Verified with 4.18.0-041800rc5-generic, the bug still exists. ** Tags added: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782091 Title: msgctl02 in ubuntu_ltp_syscalls failed with X/B Status in linux package in Ubuntu: Confirmed Bug description: Steps as root: 1. git clone --depth=1 https://github.com/linux-test-project/ltp.git 2. cd ltp; make autotools 3. ./configure 4. make 5. make install $ cat /tmp/test.txt msgctl01 msgctl01 msgctl02 msgctl02 msgctl03 msgctl03 msgctl04 msgctl04 msgstress01 msgstress01 msgstress02 msgstress02 msgstress03 msgstress03 msgstress04 msgstress04 msgctl12 msgctl12 $ sudo /opt/ltp/runltp -f /tmp/test.txt Test output: <<>> tag=msgctl02 stime=1531815429 cmdline="msgctl02" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s tst_safe_sysv_ipc.c:51: BROK: msgctl02.c:68: msgget(1627521041, 7b0) failed: EEXIST Summary: passed 0 failed 0 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=2 corefile=no cutime=0 cstime=0 <<>> This failure can be reproduced with the kernel in -release 4.4.0-130-generic, therefore it should not be considered as a regression. If you run only this test after a reboot, it will pass for the first time. tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s msgctl02.c:47: PASS: msgctl(IPC_SET) msg_qbytes - 1 msgctl02.c:54: PASS: msg_qbytes = 16383 There is a recent change for msgctl02 (79eac0a) in the ltp repo. This test can pass with with commit revert back to 1a11467414 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-130-generic 4.4.0-130.156 ProcVersionSignature: User Name 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 17 07:55 seq crw-rw 1 root audio 116, 33 Jul 17 07:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jul 17 08:15:58 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic.efi.signed root=UUID=051b34ce-dfed-4e36-aa78-851c5a284ee4 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-130-generic N/A linux-backports-modules-4.4.0-130-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2015 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd12/27/2015:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782091/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782093] Re: msgctl04 in ubuntu_ltp_syscalls failed with X
Bug can be found on Bionic. Verified with 4.18.0-041800rc5-generic, the bug still exists. ** Description changed: Steps as root: - 1. git clone --depth=1 https://github.com/linux-test-project/ltp.git - 2. cd ltp; make autotools - 3. ./configure - 4. make - 5. make install + 1. git clone --depth=1 https://github.com/linux-test-project/ltp.git + 2. cd ltp; make autotools + 3. ./configure + 4. make + 5. make install $ sudo /opt/ltp/runltp -s msgctl02 Test output: <<>> tag=msgctl04 stime=1531753902 cmdline="msgctl04" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s tst_safe_sysv_ipc.c:51: BROK: msgctl04.c:93: msgget(1627521048, 600) failed: EEXIST Summary: passed 0 failed 0 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=2 corefile=no cutime=0 cstime=0 <<>> This failure can be reproduced with the kernel in -release 4.4.0-130-generic, therefore it should not be considered as a regression. - There is a recent change for msgctl02 (79eac0a) in the ltp repo. It's - worthy to revert it to see if it's the tool change that cause this. + If you run only this test after a reboot, it will pass: + incrementing stop + tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s + msgctl04.c:72: PASS: msgctl(458754, 2, 0x55d59a243980): EACCES + msgctl04.c:72: PASS: msgctl(491523, 2, 0x): EFAULT + msgctl04.c:72: PASS: msgctl(491523, 1, 0x): EFAULT + msgctl04.c:72: PASS: msgctl(491523, -1, 0x55d59a243980): EINVAL + msgctl04.c:72: PASS: msgctl(-1, 2, 0x55d59a243980): EINVAL + msgctl04.c:72: PASS: msgctl(-1, 1, 0x55d59a243980): EINVAL + msgctl04.c:72: PASS: msgctl(425985, 0, (nil)): EPERM + (Also the msgctl02 test can pass multiple times after this) + + There is a recent change for msgctl in the ltp repo. This test can pass + with with commit revert back to 1a11467414 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-130-generic 4.4.0-130.156 ProcVersionSignature: User Name 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic x86_64 AlsaDevices: - total 0 - crw-rw 1 root audio 116, 1 Jul 17 07:55 seq - crw-rw 1 root audio 116, 33 Jul 17 07:55 timer + total 0 + crw-rw 1 root audio 116, 1 Jul 17 07:55 seq + crw-rw 1 root audio 116, 33 Jul 17 07:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jul 17 08:25:57 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: - + ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic.efi.signed root=UUID=051b34ce-dfed-4e36-aa78-851c5a284ee4 ro RelatedPackageVersions: - linux-restricted-modules-4.4.0-130-generic N/A - linux-backports-modules-4.4.0-130-generic N/A - linux-firmware 1.157.20 + linux-restricted-modules-4.4.0-130-generic N/A + linux-backports-modules-4.4.0-130-generic N/A + linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2015 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd12/27/2015:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782093 Title: msgctl04 in ubuntu_ltp_syscalls failed with X Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Bug description: Steps as root: 1. git clone --depth=1 https://github.com/linux-test-project/ltp.git 2. cd ltp; make autotools 3. ./configure 4. make 5. make install $ sudo /opt/ltp/runltp -s msgctl02 Test output: <<>> tag=msgctl04 stime=1531753902 cmdline="msgctl04" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s tst_safe_sysv_ipc.c:51: BROK: msgc
[Kernel-packages] [Bug 1782091] Re: msgctl02 in ubuntu_ltp_syscalls failed with X/B
** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782091 Title: msgctl02 in ubuntu_ltp_syscalls failed with X/B Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Bug description: Steps as root: 1. git clone --depth=1 https://github.com/linux-test-project/ltp.git 2. cd ltp; make autotools 3. ./configure 4. make 5. make install $ cat /tmp/test.txt msgctl01 msgctl01 msgctl02 msgctl02 msgctl03 msgctl03 msgctl04 msgctl04 msgstress01 msgstress01 msgstress02 msgstress02 msgstress03 msgstress03 msgstress04 msgstress04 msgctl12 msgctl12 $ sudo /opt/ltp/runltp -f /tmp/test.txt Test output: <<>> tag=msgctl02 stime=1531815429 cmdline="msgctl02" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s tst_safe_sysv_ipc.c:51: BROK: msgctl02.c:68: msgget(1627521041, 7b0) failed: EEXIST Summary: passed 0 failed 0 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=2 corefile=no cutime=0 cstime=0 <<>> This failure can be reproduced with the kernel in -release 4.4.0-130-generic, therefore it should not be considered as a regression. If you run only this test after a reboot, it will pass for the first time. tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s msgctl02.c:47: PASS: msgctl(IPC_SET) msg_qbytes - 1 msgctl02.c:54: PASS: msg_qbytes = 16383 There is a recent change for msgctl02 (79eac0a) in the ltp repo. This test can pass with with commit revert back to 1a11467414 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-130-generic 4.4.0-130.156 ProcVersionSignature: User Name 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 17 07:55 seq crw-rw 1 root audio 116, 33 Jul 17 07:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jul 17 08:15:58 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic.efi.signed root=UUID=051b34ce-dfed-4e36-aa78-851c5a284ee4 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-130-generic N/A linux-backports-modules-4.4.0-130-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2015 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd12/27/2015:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1782091/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766964] Re: zpool status -v aborts with SIGABRT with and without arguments
I've not heard back on any feedback for information from comment #1, so I'm going to mark this as "Won't Fix". If this is still and issue, please re-open the bug and provide debugging feedback as requested. ** Changed in: zfs-linux (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1766964 Title: zpool status -v aborts with SIGABRT with and without arguments Status in zfs-linux package in Ubuntu: Won't Fix Bug description: I am currently running Ubuntu 16.04 with ZFS 0.6.5. Distributor ID: Ubuntu Description:Ubuntu 16.04.4 LTS Release:16.04 Codename: xenial christian@kepler ~ $ apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.6.5.6-0ubuntu20 Candidate: 0.6.5.6-0ubuntu20 Version table: *** 0.6.5.6-0ubuntu20 500 500 http://mirror.math.ucdavis.edu/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.6.5.6-0ubuntu8 500 500 http://mirror.math.ucdavis.edu/ubuntu xenial/universe amd64 Packages Here is the package listing: (standard input):ii libzfs2linux 0.6.5.6-0ubuntu20 amd64Native OpenZFS filesystem library for Linux (standard input):ii zfs-dkms 0.6.5.6-0ubuntu20 amd64Native OpenZFS filesystem kernel modules for Linux (standard input):ii zfs-doc 0.6.5.6-0ubuntu20 all Native OpenZFS filesystem documentation and examples. (standard input):ii zfs-zed 0.6.5.6-0ubuntu20 amd64OpenZFS Event Daemon (zed) (standard input):ii zfsutils-linux0.6.5.6-0ubuntu20 amd64Native OpenZFS management utilities for Linux I try to run status on my zpool using the command `zpool status zkepler` and get this result: pool: zkepler state: ONLINE scan: scrub in progress since Wed Apr 25 13:10:24 2018 802G scanned out of 2.28T at 217M/s, 2h0m to go 0 repaired, 34.32% done Aborted I would expect an extended report of status but it just aborts with SIGABRT when run through gdb. (gdb) run status -v Starting program: /sbin/zpool status -v [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". pool: zkepler state: ONLINE scan: scrub in progress since Wed Apr 25 13:10:24 2018 825G scanned out of 2.28T at 211M/s, 2h2m to go 0 repaired, 35.32% done Program received signal SIGABRT, Aborted. 0x768d6428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 54 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory. I have upgraded this machine from 14.04 LTS within the last few months but I purged all the ZFS packages and the ZFS PPA and reinstalled all the packages. My kernel version is 4.4.0-121-generic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1766964/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722261] Re: deadlock in mount umount and sync
I'm going to mark this as "Won't Fix" as this issue is not occurring with the zil_slog_limit change and I've not fixed anything. If this problem re-occurs please re-open this bug. ** Changed in: zfs-linux (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1722261 Title: deadlock in mount umount and sync Status in zfs-linux package in Ubuntu: Won't Fix Bug description: I use zfs vesion 0.6.5.6 on Ubuntu 16.04.2 LTS . I have many zombie process on auto-mount of snapshot and on sync ! 903 process are in deadlock. i can't mount a new file system or snapshot . Partial output of ps alx |grep 'call_r D' below . what is the cause? what can I do ? 0 0 2371 1 20 0 6016 752 call_r D? 0:00 /bin/sync 0 0 15290 1 20 0 6016 676 call_r D? 0:00 /bin/sync 0 0 18919 1 20 0 6016 708 call_r D? 0:00 /bin/sync 0 0 27076 1 20 0 6016 808 call_r D? 0:00 /bin/sync 4 0 31976 1 20 0 22084 1344 call_r D? 0:00 umount -t zfs -n /samba/shares/Aat/.zfs/snapshot/2017-10-04_09.00.05--5d error in kern.log: 9 13:20:28 zfs-cis kernel: [5368563.592834] WARNING: Unable to automount /samba/shares/Trapianti/.zfs/snapshot/2017-10-03_08.00.03--5d/pool_z2_samba/shares/Trapianti@2017-10-03_08.00.03--5d: 256 Oct 9 13:20:28 zfs-cis kernel: [5368563.597868] WARNING: Unable to automount /samba/shares/Trapianti/.zfs/snapshot/2017-10-03_08.00.03--5d/pool_z2_samba/shares/Trapianti@2017-10-03_08.00.03--5d: 256 Oct 9 13:20:28 zfs-cis kernel: [5368563.601730] WARNING: Unable to automount /samba/shares/Trapianti/.zfs/snapshot/2017-10-03_08.00.03--5d/pool_z2_samba/shares/Trapianti@2017-10-03_08.00.03--5d: 256 Oct 9 13:22:57 zfs-cis kernel: [5368713.187001] WARNING: Unable to automount /samba/shares/Trapianti/.zfs/snapshot/2017-10-03_10.00.03--5d/pool_z2_samba/shares/Trapianti@2017-10-03_10.00.03--5d: 256 Oct 9 13:22:57 zfs-cis kernel: [5368713.13] WARNING: Unable to automount /samba/shares/Cardiologia2/.zfs/snapshot/2017-10-03_12.00.03--5d/pool_z2_samba/shares/Cardiologia2@2017-10-03_12.00.03--5d: 256 Oct 9 13:22:57 zfs-cis kernel: [5368713.15] WARNING: Unable to automount /samba/shares/Trapianti/.zfs/snapshot/2017-10-03_14.00.04--5d/pool_z2_samba/shares/Trapianti@2017-10-03_14.00.04--5d: 256 Oct 9 13:22:57 zfs-cis kernel: [5368713.189005] WARNING: Unable to automount /samba/shares/Aat/.zfs/snapshot/2017-10-03_20.00.04--5d/pool_z2_samba/shares/Aat@2017-10-03_20.00.04--5d: 256 Oct 9 13:22:57 zfs-cis kernel: [5368713.190105] WARNING: Unable to automount /samba/shares/Trapianti/.zfs/snapshot/2017-10-03_10.00.03--5d/pool_z2_samba/shares/Trapianti@2017-10-03_10.00.03--5d: 256 Oct 9 13:22:57 zfs-cis kernel: [5368713.192847] WARNING: Unable to automount /samba/shares/Trapianti/.zfs/snapshot/2017-10-03_10.00.03--5d/pool_z2_samba/shares/Trapianti@2017-10-03_10.00.03--5d: 256 Oct 9 13:22:57 zfs-cis kernel: [5368713.193617] WARNING: Unable to automount /samba/shares/Trapianti/.zfs/snapshot/2017-10-03_14.00.04--5d/pool_z2_samba/shares/Trapianti@2017-10-03_14.00.04--5d: 256 Oct 9 13:22:57 zfs-cis kernel: [5368713.198096] WARNING: Unable to automount /samba/shares/Trapianti/.zfs/snapshot/2017-10-03_14.00.04--5d/pool_z2_samba/shares/Trapianti@2017-10-03_14.00.04--5d: 256 in syslog : Oct 9 12:22:12 zfs-cis systemd[1]: Got message type=method_call sender=n/a destination=org.freedesktop.systemd1 object=/org/freedesktop/systemd1/unit/samba_2dshares_2dChtrapianti_2emount interface=org.freedesktop.DBus.Properties member=GetAll cookie=155 reply_cookie=0 error=n/a Oct 9 12:22:12 zfs-cis systemd[1]: Got message type=method_call sender=n/a destination=org.freedesktop.systemd1 object=/org/freedesktop/systemd1/unit/samba_2dshares_2dLaboratorio_5fTrapianti_2emount interface=org.freedesktop.DBus.Properties member=GetAll cookie=202 reply_cookie=0 error=n/a Oct 9 12:22:12 zfs-cis systemd[1]: Got message type=method_call sender=n/a destination=org.freedesktop.systemd1 object=/org/freedesktop/systemd1/unit/samba_2dshares_2dProgettoTrapianti_2emount interface=org.freedesktop.DBus.Properties member=GetAll cookie=260 reply_cookie=0 error=n/a Oct 9 12:22:12 zfs-cis systemd[1]: Got message type=method_call sender=n/a destination=org.freedesktop.systemd1 object=/org/freedesktop/systemd1/unit/samba_2dshares_2dTrapianti_2emount interface=org.freedesktop.DBus.Properties member=GetAll cookie=291 reply_cookie=0 error=n/a Oct 9 12:22:13 zfs-cis systemd[1]: Got message type=method_call sender=n/a destination=org.freedesktop.systemd1 object=/org/freedesktop/systemd1/unit/samba_2dshares_2dChtrapianti_2emount interface=org.freedesktop.DBus.Properties member=GetAll c
[Kernel-packages] [Bug 1782114] [NEW] ubuntu_ramfs_stress OOM on 4.15 KVM kernel
Public bug reported: This test will fail with the 4.15 kvm kernel in -release. Therefore this might not be a kernel regression but a tool issue. Complete syslog output can be found here: https://pastebin.ubuntu.com/p/tYTf8gh5ft/ Test output: 10:13:57 DEBUG| [stdout] Stress test: /home/ubuntu/autotest/client/tmp/ubuntu_ramfs_stress/src/stress-ng/stress-ng --verify --times --metrics-brief --syslog --keep-name -t 15s --hdd 4 --hdd-opts sync,wr-rnd,rd-rnd,fadv-willneed,fadv-rnd --link 4 --symlink 4 --lockf 4 --seek 4 --aio 4 --aio-requests 32 --dentry 4 --dir 4 --dentry-order stride --fallocate 4 --fstat 4 --dentries 65536 --io 1 --lease 4 --mmap 0 --mmap-file --mmap-async --open 4 --rename 4 --hdd-bytes 32M --fallocate-bytes 32M --chdir 4 --chmod 4 --filename 4 --rename 4 --mmap-bytes 32M --hdd-write-size 512 10:13:57 DEBUG| [stdout] Mount point: /mnt/ramfs-test-1002 10:13:57 DEBUG| [stdout] Date: Tue Jul 17 10:13:57 UTC 2018 10:13:57 DEBUG| [stdout] Host: harpo 10:13:57 DEBUG| [stdout] Kernel:4.15.0-1011-kvm #11-Ubuntu SMP Fri May 25 08:24:07 UTC 2018 10:13:57 DEBUG| [stdout] Machine: harpo x86_64 x86_64 10:13:57 DEBUG| [stdout] CPUs online: 2 10:13:57 DEBUG| [stdout] CPUs total:2 10:13:57 DEBUG| [stdout] Page size: 4096 10:13:57 DEBUG| [stdout] Pages avail: 216098 10:13:57 DEBUG| [stdout] Pages total: 255157 10:13:57 DEBUG| [stdout] 10:13:57 DEBUG| [stdout] 10:13:57 DEBUG| [stdout] 10:13:57 DEBUG| [stdout] stress-ng: info: [1024] dispatching hogs: 4 hdd, 4 link, 4 symlink, 4 lockf, 4 seek, 4 aio, 4 dentry, 4 dir, 4 fallocate, 4 fstat, 1 io, 4 lease, 2 mmap, 4 open, 4 rename, 4 chdir, 4 chmod, 4 filename, 4 rename 10:14:13 ERROR| Exception escaping from test: Traceback (most recent call last): File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function return func(*args, **dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute postprocess_profiled_run, args, dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once self.run_once(*args, **dargs) File "/home/ubuntu/autotest/client/tests/ubuntu_ramfs_stress/ubuntu_ramfs_stress.py", line 70, in run_once self.results = utils.system_output(cmd, retain_output=True) File "/home/ubuntu/autotest/client/shared/utils.py", line 1267, in system_output verbose=verbose, args=args).stdout File "/home/ubuntu/autotest/client/shared/utils.py", line 918, in run "Command returned non-zero exit status") CmdError: Command &1> failed, rc=-9, Command returned non-zero exit status * Command: LOG=/tmp/ramfs-falure.log STRESS_NG=/home/ubuntu/autotest/client/tmp/ubuntu_ramfs_stress/src/stress- ng/stress-ng DURATION=15s bash -c /home/ubuntu/autotest/client/tests/ubunt u_ramfs_stress/ubuntu_ramfs_stress.sh /home/ubuntu/autotest/client/tmp/ubuntu_ramfs_stress/src 2>&1 Exit status: -9 Duration: 15.3993020058 stdout: Stress test: /home/ubuntu/autotest/client/tmp/ubuntu_ramfs_stress/src/stress-ng/stress-ng --verify --times --metrics-brief --syslog --keep-name -t 15s --hdd 4 --hdd-opts sync,wr-rnd,rd-rnd,fadv-willneed,fadv-rnd --link 4 --symlink 4 --lockf 4 --seek 4 --aio 4 --aio-requests 32 --dentry 4 --dir 4 --dentry-order stride --fallocate 4 --fstat 4 --dentries 65536 --io 1 --lease 4 --mmap 0 --mmap-file --mmap-async --open 4 --rename 4 --hdd-bytes 32M --fallocate-bytes 32M --chdir 4 --chmod 4 --filename 4 --rename 4 --mmap-bytes 32M --hdd-write-size 512 Mount point: /mnt/ramfs-test-1002 Date: Tue Jul 17 10:13:57 UTC 2018 Host: harpo Kernel:4.15.0-1011-kvm #11-Ubuntu SMP Fri May 25 08:24:07 UTC 2018 Machine: harpo x86_64 x86_64 CPUs online: 2 CPUs total:2 Page size: 4096 Pages avail: 216098 Pages total: 255157 stress-ng: info: [1024] dispatching hogs: 4 hdd, 4 link, 4 symlink, 4 lockf, 4 seek, 4 aio, 4 dentry, 4 dir, 4 fallocate, 4 fstat, 1 io, 4 lease, 2 mmap, 4 open, 4 rename, 4 chdir, 4 chmod, 4 filename, 4 rename 10:14:14 ERROR| child process failed 10:14:14 DEBUG| Traceback (most recent call last): 10:14:14 DEBUG| File "/home/ubuntu/autotest/client/parallel.py", line 25, in fork_start 10:14:14 DEBUG| l() 10:14:14 DEBUG| File "/home/ubuntu/autotest/client/job.py", line 505, in 10:14:14 DEBUG| l = lambda: test.runtest(self, url, tag, args, dargs) 10:14:14 DEBUG| File "/home/ubuntu/autotest/client/test.py", line 125, in runtest 10:14:14 DEBUG| job.sysinfo.log_after_each_iteration) 10:14:14 DEBUG| File "/home/ubuntu/autotest/
[Kernel-packages] [Bug 1782116] [NEW] snapcraft.yaml: missing ubuntu-retpoline-extract-one script breaks the build
Public bug reported: Impact: On a generic amd64 environment, check out the Xenia/generic or Bionic/generic tree, cd into it and execute snapcraft - it should build the corresponding kernel snap. linux $ snapcraft ... HOSTCC scripts/mod/mk_elfconfig /bin/bash: ./scripts/ubuntu-retpoline-extract-one: No such file or directory scripts/Makefile.build:332: recipe for target 'scripts/mod/empty.o' failed make[2]: *** [scripts/mod/empty.o] Error 127 make[2]: *** Waiting for unfinished jobs HOSTLD arch/x86/tools/relocs HOSTCC scripts/selinux/genheaders/genheaders HOSTCC scripts/selinux/mdp/mdp scripts/Makefile.build:606: recipe for target 'scripts/mod' failed make[1]: *** [scripts/mod] Error 2 make[1]: *** Waiting for unfinished jobs CC arch/x86/purgatory/purgatory.o Makefile:589: recipe for target 'scripts' failed make: *** [scripts] Error 2 make: *** Waiting for unfinished jobs AS arch/x86/purgatory/stack.o /bin/bash: ./scripts/ubuntu-retpoline-extract-one: No such file or directory scripts/Makefile.build:332: recipe for target 'arch/x86/purgatory/purgatory.o' failed make[1]: *** [arch/x86/purgatory/purgatory.o] Error 127 make[1]: *** Waiting for unfinished jobs AS arch/x86/purgatory/setup-x86_64.o /bin/bash: ./scripts/ubuntu-retpoline-extract-one: No such file or directory scripts/Makefile.build:435: recipe for target 'arch/x86/purgatory/stack.o' failed make[1]: *** [arch/x86/purgatory/stack.o] Error 127 /bin/bash: ./scripts/ubuntu-retpoline-extract-one: No such file or directory scripts/Makefile.build:435: recipe for target 'arch/x86/purgatory/setup-x86_64.o' failed make[1]: *** [arch/x86/purgatory/setup-x86_64.o] Error 127 arch/x86/Makefile:260: recipe for target 'archprepare' failed make: *** [archprepare] Error 2 Failed to run 'make -j4 bzImage modules' for 'kernel': Exited with code 2. Verify that the part is using the correct parameters and try again. Fix: The retpoline-extract-one should be copied to the parts/build/script directory, apply the attached patch to let snapcraft do it before starting the kernel build Regression risk: None, since we are only patching the snapcraft.yaml file (and it didn't build in the first place). --- ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782116 Title: snapcraft.yaml: missing ubuntu-retpoline-extract-one script breaks the build Status in linux package in Ubuntu: New Bug description: Impact: On a generic amd64 environment, check out the Xenia/generic or Bionic/generic tree, cd into it and execute snapcraft - it should build the corresponding kernel snap. linux $ snapcraft ... HOSTCC scripts/mod/mk_elfconfig /bin/bash: ./scripts/ubuntu-retpoline-extract-one: No such file or directory scripts/Makefile.build:332: recipe for target 'scripts/mod/empty.o' failed make[2]: *** [scripts/mod/empty.o] Error 127 make[2]: *** Waiting for unfinished jobs HOSTLD arch/x86/tools/relocs HOSTCC scripts/selinux/genheaders/genheaders HOSTCC scripts/selinux/mdp/mdp scripts/Makefile.build:606: recipe for target 'scripts/mod' failed make[1]: *** [scripts/mod] Error 2 make[1]: *** Waiting for unfinished jobs CC arch/x86/purgatory/purgatory.o Makefile:589: recipe for target 'scripts' failed make: *** [scripts] Error 2 make: *** Waiting for unfinished jobs AS arch/x86/purgatory/stack.o /bin/bash: ./scripts/ubuntu-retpoline-extract-one: No such file or directory scripts/Makefile.build:332: recipe for target 'arch/x86/purgatory/purgatory.o' failed make[1]: *** [arch/x86/purgatory/purgatory.o] Error 127 make[1]: *** Waiting for unfinished jobs AS arch/x86/purgatory/setup-x86_64.o /bin/bash: ./scripts/ubuntu-retpoline-extract-one: No such file or directory scripts/Makefile.build:435: recipe for target 'arch/x86/purgatory/stack.o' failed make[1]: *** [arch/x86/purgatory/stack.o] Error 127 /bin/bash: ./scripts/ubuntu-retpoline-extract-one: No such file or directory scripts/Makefile.build:435: recipe for target 'arch/x86/purgatory/setup-x86_64.o' failed make[1]: *** [arch/x86/purgatory/setup-x86_64.o] Error 127 arch/x86/Makefile:260: recipe for target 'archprepare' failed make: *** [archprepare] Error 2 Failed to run 'make -j4 bzImage modules' for 'kernel': Exited with code 2. Verify that the part is using the correct parameters and try again. Fix: The retpoline-extract-one should be copied to the parts/build/script directory, apply the attached patch to let snapcraft do it before starting the kernel build Regression risk: None, since we are only patching the snapcraft.yaml file (and it didn't build in the first place). --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+sour
[Kernel-packages] [Bug 1782116] Re: snapcraft.yaml: missing ubuntu-retpoline-extract-one script breaks the build
** Patch added: "0001-UBUNTU-snapcraft.yaml-copy-retpoline-extract-one-to-.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782116/+attachment/5164456/+files/0001-UBUNTU-snapcraft.yaml-copy-retpoline-extract-one-to-.patch ** Description changed: + Impact: + Check out the Xenia/generic or Bionic/generic tree, cd into it and execute: snapcraft ... - HOSTCC scripts/mod/mk_elfconfig + HOSTCC scripts/mod/mk_elfconfig /bin/bash: ./scripts/ubuntu-retpoline-extract-one: No such file or directory scripts/Makefile.build:332: recipe for target 'scripts/mod/empty.o' failed make[2]: *** [scripts/mod/empty.o] Error 127 make[2]: *** Waiting for unfinished jobs - HOSTLD arch/x86/tools/relocs - HOSTCC scripts/selinux/genheaders/genheaders - HOSTCC scripts/selinux/mdp/mdp + HOSTLD arch/x86/tools/relocs + HOSTCC scripts/selinux/genheaders/genheaders + HOSTCC scripts/selinux/mdp/mdp scripts/Makefile.build:606: recipe for target 'scripts/mod' failed make[1]: *** [scripts/mod] Error 2 make[1]: *** Waiting for unfinished jobs - CC arch/x86/purgatory/purgatory.o + CC arch/x86/purgatory/purgatory.o Makefile:589: recipe for target 'scripts' failed make: *** [scripts] Error 2 make: *** Waiting for unfinished jobs - AS arch/x86/purgatory/stack.o + AS arch/x86/purgatory/stack.o /bin/bash: ./scripts/ubuntu-retpoline-extract-one: No such file or directory scripts/Makefile.build:332: recipe for target 'arch/x86/purgatory/purgatory.o' failed make[1]: *** [arch/x86/purgatory/purgatory.o] Error 127 make[1]: *** Waiting for unfinished jobs - AS arch/x86/purgatory/setup-x86_64.o + AS arch/x86/purgatory/setup-x86_64.o /bin/bash: ./scripts/ubuntu-retpoline-extract-one: No such file or directory scripts/Makefile.build:435: recipe for target 'arch/x86/purgatory/stack.o' failed make[1]: *** [arch/x86/purgatory/stack.o] Error 127 /bin/bash: ./scripts/ubuntu-retpoline-extract-one: No such file or directory scripts/Makefile.build:435: recipe for target 'arch/x86/purgatory/setup-x86_64.o' failed make[1]: *** [arch/x86/purgatory/setup-x86_64.o] Error 127 arch/x86/Makefile:260: recipe for target 'archprepare' failed make: *** [archprepare] Error 2 Failed to run 'make -j4 bzImage modules' for 'kernel': Exited with code 2. Verify that the part is using the correct parameters and try again. + + Fix: + The retpoline-extract-one should be copied to the parts/build/script directory, apply the attached patch to let snapcraft do it before starting the kernel build + + Regression risk: + None, since we are only patching the snapcraft.yaml file (and it didn't build in the first place). + + --- ** Description changed: Impact: Check out the Xenia/generic or Bionic/generic tree, cd into it and execute: snapcraft + linux $ snapcrat ... HOSTCC scripts/mod/mk_elfconfig /bin/bash: ./scripts/ubuntu-retpoline-extract-one: No such file or directory scripts/Makefile.build:332: recipe for target 'scripts/mod/empty.o' failed make[2]: *** [scripts/mod/empty.o] Error 127 make[2]: *** Waiting for unfinished jobs HOSTLD arch/x86/tools/relocs HOSTCC scripts/selinux/genheaders/genheaders HOSTCC scripts/selinux/mdp/mdp scripts/Makefile.build:606: recipe for target 'scripts/mod' failed make[1]: *** [scripts/mod] Error 2 make[1]: *** Waiting for unfinished jobs CC arch/x86/purgatory/purgatory.o Makefile:589: recipe for target 'scripts' failed make: *** [scripts] Error 2 make: *** Waiting for unfinished jobs AS arch/x86/purgatory/stack.o /bin/bash: ./scripts/ubuntu-retpoline-extract-one: No such file or directory scripts/Makefile.build:332: recipe for target 'arch/x86/purgatory/purgatory.o' failed make[1]: *** [arch/x86/purgatory/purgatory.o] Error 127 make[1]: *** Waiting for unfinished jobs AS arch/x86/purgatory/setup-x86_64.o /bin/bash: ./scripts/ubuntu-retpoline-extract-one: No such file or directory scripts/Makefile.build:435: recipe for target 'arch/x86/purgatory/stack.o' failed make[1]: *** [arch/x86/purgatory/stack.o] Error 127 /bin/bash: ./scripts/ubuntu-retpoline-extract-one: No such file or directory scripts/Makefile.build:435: recipe for target 'arch/x86/purgatory/setup-x86_64.o' failed make[1]: *** [arch/x86/purgatory/setup-x86_64.o] Error 127 arch/x86/Makefile:260: recipe for target 'archprepare' failed make: *** [archprepare] Error 2 Failed to run 'make -j4 bzImage modules' for 'kernel': Exited with code 2. Verify that the part is using the correct parameters and try again. Fix: The retpoline-extract-one should be copied to the parts/build/script directory, apply the attached patch to let snapcraft do it before starting the kernel build Regression risk: None, since we are only patching the snapcraft.yaml file (and it didn't build in the first place). --- *
[Kernel-packages] [Bug 1723948] Re: error -lock in zfs send
Did the advice in comment #3 help? I've not heard any response from this for a couple of months, so I'm closing this bug as Won't Fix. If this is still and issue, please feel free to reopen the bug. ** Changed in: zfs-linux (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1723948 Title: error -lock in zfs send Status in Native ZFS for Linux: New Status in zfs-linux package in Ubuntu: Won't Fix Bug description: zfs send stop working. the process did not produce output. checked by mbuffer log in kernel.log: Oct 15 07:25:53 zfs-cis kernel: [479439.151281] INFO: task zfs:8708 blocked for more than 120 seconds. Oct 15 07:25:53 zfs-cis kernel: [479439.156980] Tainted: P OE 4.4.0-96-generic #119-Ubuntu Oct 15 07:25:53 zfs-cis kernel: [479439.162688] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Oct 15 07:25:53 zfs-cis kernel: [479439.173974] zfs D 88197bd77318 0 8708 8141 0x Oct 15 07:25:53 zfs-cis kernel: [479439.173981] 88197bd77318 810c3dc2 8820374cf000 881b645ff000 Oct 15 07:25:53 zfs-cis kernel: [479439.173985] 88197bd78000 00792c6d 882030aa4ac8 Oct 15 07:25:53 zfs-cis kernel: [479439.173989] 88101dac1840 88197bd77330 8183f165 882030aa4a00 Oct 15 07:25:53 zfs-cis kernel: [479439.173993] Call Trace: Oct 15 07:25:53 zfs-cis kernel: [479439.174006] [] ? __wake_up_common+0x52/0x90 Oct 15 07:25:53 zfs-cis kernel: [479439.174023] [] schedule+0x35/0x80 Oct 15 07:25:53 zfs-cis kernel: [479439.174045] [] taskq_wait_id+0x60/0xb0 [spl] Oct 15 07:25:53 zfs-cis kernel: [479439.174051] [] ? wake_atomic_t_function+0x60/0x60 Oct 15 07:25:53 zfs-cis kernel: [479439.174115] [] ? dump_write+0x230/0x230 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.174178] [] spa_taskq_dispatch_sync+0x92/0xd0 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.174223] [] dump_bytes+0x51/0x70 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.174267] [] dump_write+0x11e/0x230 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.174311] [] backup_cb+0x633/0x850 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.174356] [] traverse_visitbp+0x47a/0x960 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.174365] [] ? spl_kmem_alloc+0xaf/0x190 [spl] Oct 15 07:25:53 zfs-cis kernel: [479439.174409] [] traverse_visitbp+0x5c0/0x960 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.174462] [] traverse_visitbp+0x5c0/0x960 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.174503] [] traverse_dnode+0x7f/0xe0 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.174542] [] traverse_visitbp+0x6cc/0x960 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.174579] [] traverse_visitbp+0x5c0/0x960 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.174616] [] traverse_visitbp+0x5c0/0x960 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.174653] [] traverse_visitbp+0x5c0/0x960 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.174690] [] traverse_visitbp+0x5c0/0x960 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.174726] [] traverse_visitbp+0x5c0/0x960 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.174762] [] traverse_visitbp+0x5c0/0x960 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.174799] [] traverse_dnode+0x7f/0xe0 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.174835] [] traverse_visitbp+0x865/0x960 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.174871] [] traverse_impl+0x1ae/0x410 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.174908] [] ? dmu_recv_end_check+0x210/0x210 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.174944] [] traverse_dataset+0x52/0x60 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.174981] [] ? dmu_recv_end_check+0x210/0x210 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.175017] [] dmu_send_impl+0x409/0x560 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.175060] [] dmu_send_obj+0x172/0x1e0 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.175129] [] zfs_ioc_send+0xe9/0x2c0 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.175143] [] ? strdup+0x3b/0x60 [spl] Oct 15 07:25:53 zfs-cis kernel: [479439.175207] [] zfsdev_ioctl+0x44b/0x4e0 [zfs] Oct 15 07:25:53 zfs-cis kernel: [479439.175218] [] do_vfs_ioctl+0x29f/0x490 Oct 15 07:25:53 zfs-cis kernel: [479439.175225] [] ? _do_fork+0xec/0x360 Oct 15 07:25:53 zfs-cis kernel: [479439.175232] [] SyS_ioctl+0x79/0x90 Oct 15 07:25:53 zfs-cis kernel: [479439.175242] [] entry_SYSCALL_64_fastpath+0x16/0x71 To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1723948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.
[Kernel-packages] [Bug 1782070] Re: [Redpine] Upgrades to improve throughput and stability
** Description changed: This is a tracking bug for several improvements for the Redpine RS9113 - Wifi+BT combo-device on Dell Edge 300X gateways. Some of these upgrades - are: + Wifi+BT combo-device on Dell Edge 300X gateways using Ubuntu 18.04 + Server based image. Some of these upgrades are: 1. WoWLAN support from S3/S4 and S5. 2. Better radio throughput - 3. Stable operation -- fixes to mitigate issues during driver module loading/un-loading -- panics when resuming from hibernation + 3. Stable operation + - fixes to mitigate issues during driver module loading/un-loading + - panics when resuming from hibernation This bug is of tracking purposes only, please don't triage. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1782070 Title: [Redpine] Upgrades to improve throughput and stability Status in linux-oem package in Ubuntu: Confirmed Bug description: This is a tracking bug for several improvements for the Redpine RS9113 Wifi+BT combo-device on Dell Edge 300X gateways using Ubuntu 18.04 Server based image. Some of these upgrades are: 1. WoWLAN support from S3/S4 and S5. 2. Better radio throughput 3. Stable operation - fixes to mitigate issues during driver module loading/un-loading - panics when resuming from hibernation These changes have been verified by QA and Dell/ODM. This bug is of tracking purposes only, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem/+bug/1782070/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782116] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1782116 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782116 Title: snapcraft.yaml: missing ubuntu-retpoline-extract-one script breaks the build Status in linux package in Ubuntu: Incomplete Bug description: Impact: On a generic amd64 environment, check out the Xenia/generic or Bionic/generic tree, cd into it and execute snapcraft - it should build the corresponding kernel snap. linux $ snapcraft ... HOSTCC scripts/mod/mk_elfconfig /bin/bash: ./scripts/ubuntu-retpoline-extract-one: No such file or directory scripts/Makefile.build:332: recipe for target 'scripts/mod/empty.o' failed make[2]: *** [scripts/mod/empty.o] Error 127 make[2]: *** Waiting for unfinished jobs HOSTLD arch/x86/tools/relocs HOSTCC scripts/selinux/genheaders/genheaders HOSTCC scripts/selinux/mdp/mdp scripts/Makefile.build:606: recipe for target 'scripts/mod' failed make[1]: *** [scripts/mod] Error 2 make[1]: *** Waiting for unfinished jobs CC arch/x86/purgatory/purgatory.o Makefile:589: recipe for target 'scripts' failed make: *** [scripts] Error 2 make: *** Waiting for unfinished jobs AS arch/x86/purgatory/stack.o /bin/bash: ./scripts/ubuntu-retpoline-extract-one: No such file or directory scripts/Makefile.build:332: recipe for target 'arch/x86/purgatory/purgatory.o' failed make[1]: *** [arch/x86/purgatory/purgatory.o] Error 127 make[1]: *** Waiting for unfinished jobs AS arch/x86/purgatory/setup-x86_64.o /bin/bash: ./scripts/ubuntu-retpoline-extract-one: No such file or directory scripts/Makefile.build:435: recipe for target 'arch/x86/purgatory/stack.o' failed make[1]: *** [arch/x86/purgatory/stack.o] Error 127 /bin/bash: ./scripts/ubuntu-retpoline-extract-one: No such file or directory scripts/Makefile.build:435: recipe for target 'arch/x86/purgatory/setup-x86_64.o' failed make[1]: *** [arch/x86/purgatory/setup-x86_64.o] Error 127 arch/x86/Makefile:260: recipe for target 'archprepare' failed make: *** [archprepare] Error 2 Failed to run 'make -j4 bzImage modules' for 'kernel': Exited with code 2. Verify that the part is using the correct parameters and try again. Fix: The retpoline-extract-one should be copied to the parts/build/script directory, apply the attached patch to let snapcraft do it before starting the kernel build Regression risk: None, since we are only patching the snapcraft.yaml file (and it didn't build in the first place). --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782116/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1667838] Re: zpool export mpu1pool cannot export 'mpu1pool': pool is busy
Internally zpool export will call unshare and umount, so a "pool is busy" indicates that process(es) has/have one or more files open and so this operation fails. One can check for these processes using either: lsof -Pn or fuser -vm /poolname (where poolname is the name of your pool) and it's worth checking the status of the pool using: zpool status -v ** Changed in: zfs-linux (Ubuntu) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1667838 Title: zpool export mpu1pool cannot export 'mpu1pool': pool is busy Status in zfs-linux package in Ubuntu: Incomplete Bug description: $ lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 Linux 4.4.0-64-generic $ apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.6.5.6-0ubuntu15 # modinfo zfs |head filename: /lib/modules/4.4.0-64-generic/kernel/zfs/zfs/zfs.ko version:0.6.5.6-0ubuntu15 I was not able to unmount a ZFS pool: # zpool export mpu1pool cannot export 'mpu1pool': pool is busy The filesystems were unmounted and there was nothing that would be blocking them FS. Neither sync, echo 3 > /proc/sys/vm/drop_caches helped. The only way worked to export a ZFS pool was to turn off the SWAP: # lsof -Pn |grep -i mpu1 lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete. # free -mh totalusedfree shared buff/cache available Mem: 7.7G5.1G502M837M2.1G 1.0G Swap: 8.0G428M7.6G # swapoff -a # free -mh totalusedfree shared buff/cache available Mem: 7.7G1.5G4.8G366M1.4G 5.2G Swap:0B 0B 0B # zpool export mpu1pool # echo $? 0 # swapon -a It is not obvious that the SWAP has to be freed before one can export ZFS pool. Would it be possible to improve this situation? Kind regards, Andrey Arapov To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1667838/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782070] Re: [Redpine] Upgrades to improve throughput and stability
** Description changed: This is a tracking bug for several improvements for the Redpine RS9113 Wifi+BT combo-device on Dell Edge 300X gateways using Ubuntu 18.04 Server based image. Some of these upgrades are: 1. WoWLAN support from S3/S4 and S5. 2. Better radio throughput 3. Stable operation - fixes to mitigate issues during driver module loading/un-loading - panics when resuming from hibernation + These changes have been verified by QA and Dell/ODM. + This bug is of tracking purposes only, please don't triage. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1782070 Title: [Redpine] Upgrades to improve throughput and stability Status in linux-oem package in Ubuntu: Confirmed Bug description: This is a tracking bug for several improvements for the Redpine RS9113 Wifi+BT combo-device on Dell Edge 300X gateways using Ubuntu 18.04 Server based image. Some of these upgrades are: 1. WoWLAN support from S3/S4 and S5. 2. Better radio throughput 3. Stable operation - fixes to mitigate issues during driver module loading/un-loading - panics when resuming from hibernation These changes have been verified by QA and Dell/ODM. This bug is of tracking purposes only, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem/+bug/1782070/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode
This bug seems related with the kernel or 4.15.0-20 of d-i ISO. Please refer to #18 for test results on different kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762940 Title: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode Status in linux package in Ubuntu: Triaged Status in install-package source package in Bionic: New Status in linux source package in Bionic: Triaged Bug description: For all(as I know) Huawei servers, the vga adapter are embed in the iBMC chips. Those server can install from ISO manually for 16.04.4 and screen display normally. But for 18.04 ( tested both for daily and final beta)version, the install screen is blur. One of tested server is Huawei 2855 v5, the certification link for 16.04 are https://certification.ubuntu.com/hardware/201707-25596/. Below are key difference of dmesg. It seems might related with DRM. 18.04 install screen is blur dmesg ... [2.039009] fb0: EFI VGA frame buffer device ... [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.191435] [drm] No driver support for vblank timestamp query. [4.209338] checking generic (9000 30) vs hw (0 0) [4.209384] fbcon: hibmcdrmfb (fb1) is primary device [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63 ... [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on minor 0 ... [5.636624] vga16fb: initializing [5.636627] vga16fb: mapped to 0x48a7a1d2 [5.636630] checking generic (9000 30) vs hw (a 1) [5.636676] fb2: VGA16 VGA frame buffer device ... 16.04.4 install screen is fine (no screen blur) dmesg ... [2.000419] fb0: EFI VGA frame buffer device [8.795065] vga16fb: initializing [8.795068] vga16fb: mapped to 0x880a [8.795071] checking generic (9800 30) vs hw (a 1) [8.795121] fb1: VGA16 VGA frame buffer device ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771091] Re: zpool freezes importing older ZFS pool, blocks shotdown and system does not boot
This looks very similar to the following ZFS bug report https://github.com/zfsonlinux/zfs/issues/6881 It may indicate you have data corruption and degraded pool. It's hard to tell any further. Have you been able to resolve this issue? ** Bug watch added: Github Issue Tracker for ZFS #6881 https://github.com/zfsonlinux/zfs/issues/6881 ** Changed in: zfs-linux (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1771091 Title: zpool freezes importing older ZFS pool, blocks shotdown and system does not boot Status in zfs-linux package in Ubuntu: Incomplete Bug description: After fresh install of xubuntu 18.04 LTS 64-bit, and the installation of zfs-dkms I tried to do 'zpool import' on an older ZFS pool, consisting of on partition on the separate PATA HDD. After issuing 'sudo zpool import ' , command freezes (as to zfs commands). System then fails to shutdown properly and seems locked and needs hard reboot (actually it waits up to half an hour to shutdown). After restarting, system displays Xubuntu splash screen and does not boot anymore (it actually resets itself if given again half an hour or so). When getting to rescue options, by pressing SHIFT key on keyboard and going to shell and remounting / read-write, I could do removing of ZFS Ubuntu packages and after that system could boot. Usefull message I got when trying to continue booting in shell was: "[ 40.811792] VERIFY3(0 == remove_reference(hdr, ((void *)0), tag)) failed (0 = 0) [ 40.811856] PANIC at arc.c:3084:arc_buf_destroy()" So it points to some ZFS bug with ARC. Previously, I was able to (unlike with 17.10) upgrade from 17.10 to 18.04 and to import and use a newer ZFS pool. But this bug is about fresh 18.04 install and an older ZFS pool. (zpool import says pool can be upgraded) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1771091/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1778798] Re: zedit doesn't open file in vm mode
zfs-zed is a ZFS Event Daemon and nothing to do with an editor. I think you must be referring to another tool. Un-assigning this bug from zfsutils-linux. ** Package changed: zfs-linux (Ubuntu) => fis-gtm (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1778798 Title: zedit doesn't open file in vm mode Status in fis-gtm package in Ubuntu: New Bug description: fis-gtm installed in Ubuntu environment. zfs-zed package installed to create and edit M routines. Using zed command doesn't open file. -- Description:Ubuntu 16.04.4 LTS Release:16.04 -- Package: zfs-zed -- Expected action was the file opened in vm editor. -- Actual action was the file wasn't opened. cemberger@cemberger-PC:/$ sudo zed "usr/staff/TESTING" cemberger@cemberger-PC:/$ ls usr/staff TESTING cemberger@cemberger-PC:/$ sudo zed "cprac" cemberger@cemberger-PC:/$ sudo zed "ccc" cemberger@cemberger-PC:/$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fis-gtm/+bug/1778798/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782125] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782125 Title: sound not working but driver all set Status in linux package in Ubuntu: Confirmed Bug description: sound not working and some issue to rum kali linux packages ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-131-generic 4.4.0-131.157 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: GNOME-Flashback:Unity Date: Tue Jul 17 16:52:55 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=f8021436-59da-47fb-a06e-75f56c298fd1 InstallationDate: Installed on 2017-11-27 (232 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Vostro 15-3568 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-131-generic.efi.signed root=UUID=2b2cc385-d110-4524-aada-58e05aefbc62 ro acpi_rev_override drm.debug=0xe plymouth:debug quiet splash 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.4.0-131-generic N/A linux-backports-modules-4.4.0-131-generic N/A linux-firmware 1.157.20 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2018-05-16 (62 days ago) dmi.bios.date: 11/13/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.0.4 dmi.board.name: 06XGVW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.0.4:bd11/13/2017:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn06XGVW:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Vostro 15-3568 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782125/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782125] [NEW] sound not working but driver all set
Public bug reported: sound not working and some issue to rum kali linux packages ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-131-generic 4.4.0-131.157 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: GNOME-Flashback:Unity Date: Tue Jul 17 16:52:55 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=f8021436-59da-47fb-a06e-75f56c298fd1 InstallationDate: Installed on 2017-11-27 (232 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Vostro 15-3568 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-131-generic.efi.signed root=UUID=2b2cc385-d110-4524-aada-58e05aefbc62 ro acpi_rev_override drm.debug=0xe plymouth:debug quiet splash 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.4.0-131-generic N/A linux-backports-modules-4.4.0-131-generic N/A linux-firmware 1.157.20 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2018-05-16 (62 days ago) dmi.bios.date: 11/13/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.0.4 dmi.board.name: 06XGVW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.0.4:bd11/13/2017:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn06XGVW:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Vostro 15-3568 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug package-from-proposed xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782125 Title: sound not working but driver all set Status in linux package in Ubuntu: Confirmed Bug description: sound not working and some issue to rum kali linux packages ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-131-generic 4.4.0-131.157 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: GNOME-Flashback:Unity Date: Tue Jul 17 16:52:55 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=f8021436-59da-47fb-a06e-75f56c298fd1 InstallationDate: Installed on 2017-11-27 (232 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Vostro 15-3568 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-131-generic.efi.signed root=UUID=2b2cc385-d110-4524-aada-58e05aefbc62 ro acpi_rev_override drm.debug=0xe plymouth:debug quiet splash 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.4.0-131-generic N/A linux-backports-modules-4.4.0-131-generic N/A linux-firmware 1.157.20 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2018-05-16 (62 days ago) dmi.bios.date: 11/13/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.0.4 dmi.board.name: 06XGVW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.0.4:bd11/13/2017:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn06XGVW:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Vostro 15-3568 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782125/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe
[Kernel-packages] [Bug 1708049] Re: package zfsutils-linux 0.6.5.6-0ubuntu17 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configur
Can you try: sudo apt-get install --reinstall zfsutils-linux and see if that helps. ** Changed in: zfs-linux (Ubuntu) Assignee: (unassigned) => Colin Ian King (colin-king) ** Changed in: zfs-linux (Ubuntu) Status: New => Triaged ** Changed in: zfs-linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1708049 Title: package zfsutils-linux 0.6.5.6-0ubuntu17 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in zfs-linux package in Ubuntu: Triaged Bug description: Ubuntu 16.04 . When it trys to update ZFS it fails and then several hours later the computer crashes.Reboot still crashes. Have to go back several updates to stop crashing. thanks R ProblemType: Package DistroRelease: Ubuntu 16.04 Package: zfsutils-linux 0.6.5.6-0ubuntu17 Uname: Linux 4.9.24-040924-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Wed Aug 2 00:34:53 2017 DuplicateSignature: package:zfsutils-linux:0.6.5.6-0ubuntu17 Processing triggers for mime-support (3.59ubuntu1) ... dpkg: error processing package zfsutils-linux (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-04-14 (109 days ago) InstallationMedia: Ubuntu-Studio 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: zfs-linux Title: package zfsutils-linux 0.6.5.6-0ubuntu17 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1708049/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781891] [NEW] PCI USB card passthrough does not work any more
You have been subscribed to a public bug: System information: Ubuntu 18.04 LTS (server edition) with kernel 4.15.0-24-generic x86_64 Upgraded from Ubuntu server 17.10 Software: qemu-kvm: Installed: 1:2.11+dfsg-1ubuntu7.4 Candidate: 1:2.11+dfsg-1ubuntu7.4 Version table: *** 1:2.11+dfsg-1ubuntu7.4 500 500 http://za.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:2.11+dfsg-1ubuntu7.3 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1:2.11+dfsg-1ubuntu7 500 500 http://za.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Hardware: Motherboard: X370 Killer SLI CPU: AMD Ryzen 7 1800X PCI device: 27:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (rev 01) IOMMU Group 15 27:00.0 USB controller [0c03]: VIA Technologies, Inc. VL805 USB 3.0 Host Controller [1106:3483] (rev 01) USB controller of PCI card: Bus 003 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Loaded device drivers: Before upgrading to Ubuntu 18.04, this PCI device was added to pci-stub.ids which allowed the device to be passed to a Windows 10 VM. In turn, all USB devices connected to this card worked in the VM and drivers could successfully be installed. Since the upgrade from Ubuntu 17.10 to Ubuntu 18.04, I have tried several approaches to have this device not bound to the xhci driver but all in vain. (In every test I did, I always performed update-initramfs -u as well as update-grub) pci-stub.ids does not stop xhci from grabbing device. So passing PCI card to VM does not work Adding the device ID to /etc/modprobe.d/vfio.conf (options) does seem to load the connect the vfio driver to it, but xhci still binds to it as well, so passing PCI device to VM does not work. Adding ":27:00.0,xhci" to /etc/unbindpci also did not work. By adding the USB controller to the VM, USB devices connected to it does seem to be USB devices on the VM, but some of the drivers does not load correctly in Windows 10. For example, I need to install a device driver for a ROCKEY4 USB dongle and even though the driver installs (which must be done with device disconnected), the driver does not seem to ever bind correctly to the device because the software that uses the dongle does not recognise it. I have successfully bound a PCI graphics adapter to the VM, so in principle PCI passthrough works, bit in the case of the USB PCI card there seems to be no way to pass the device to a VM. Expected result: PCI passthrough should be available to all types of PCI devices and instructions should be available from qemu or kvm documentation even though it involves different parts of the OS (such as making use of /etc/modprobe/vfio.conf, /etc/unbindpci etc) ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- PCI USB card passthrough does not work any more https://bugs.launchpad.net/bugs/1781891 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781891] Re: PCI USB card passthrough does not work any more
Since at the time the problem occurs this is just host kernel/modules behaving not as they should I'll move that over to the kernel. You might want to share what kernel/modules you have, but until then I'll just assume the default of 18.04. ** Package changed: qemu-kvm (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781891 Title: PCI USB card passthrough does not work any more Status in linux package in Ubuntu: Incomplete Bug description: System information: Ubuntu 18.04 LTS (server edition) with kernel 4.15.0-24-generic x86_64 Upgraded from Ubuntu server 17.10 Software: qemu-kvm: Installed: 1:2.11+dfsg-1ubuntu7.4 Candidate: 1:2.11+dfsg-1ubuntu7.4 Version table: *** 1:2.11+dfsg-1ubuntu7.4 500 500 http://za.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:2.11+dfsg-1ubuntu7.3 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1:2.11+dfsg-1ubuntu7 500 500 http://za.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Hardware: Motherboard: X370 Killer SLI CPU: AMD Ryzen 7 1800X PCI device: 27:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (rev 01) IOMMU Group 15 27:00.0 USB controller [0c03]: VIA Technologies, Inc. VL805 USB 3.0 Host Controller [1106:3483] (rev 01) USB controller of PCI card: Bus 003 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Loaded device drivers: Before upgrading to Ubuntu 18.04, this PCI device was added to pci-stub.ids which allowed the device to be passed to a Windows 10 VM. In turn, all USB devices connected to this card worked in the VM and drivers could successfully be installed. Since the upgrade from Ubuntu 17.10 to Ubuntu 18.04, I have tried several approaches to have this device not bound to the xhci driver but all in vain. (In every test I did, I always performed update- initramfs -u as well as update-grub) pci-stub.ids does not stop xhci from grabbing device. So passing PCI card to VM does not work Adding the device ID to /etc/modprobe.d/vfio.conf (options) does seem to load the connect the vfio driver to it, but xhci still binds to it as well, so passing PCI device to VM does not work. Adding ":27:00.0,xhci" to /etc/unbindpci also did not work. By adding the USB controller to the VM, USB devices connected to it does seem to be USB devices on the VM, but some of the drivers does not load correctly in Windows 10. For example, I need to install a device driver for a ROCKEY4 USB dongle and even though the driver installs (which must be done with device disconnected), the driver does not seem to ever bind correctly to the device because the software that uses the dongle does not recognise it. I have successfully bound a PCI graphics adapter to the VM, so in principle PCI passthrough works, bit in the case of the USB PCI card there seems to be no way to pass the device to a VM. Expected result: PCI passthrough should be available to all types of PCI devices and instructions should be available from qemu or kvm documentation even though it involves different parts of the OS (such as making use of /etc/modprobe/vfio.conf, /etc/unbindpci etc) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781891/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781891] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1781891 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781891 Title: PCI USB card passthrough does not work any more Status in linux package in Ubuntu: Incomplete Bug description: System information: Ubuntu 18.04 LTS (server edition) with kernel 4.15.0-24-generic x86_64 Upgraded from Ubuntu server 17.10 Software: qemu-kvm: Installed: 1:2.11+dfsg-1ubuntu7.4 Candidate: 1:2.11+dfsg-1ubuntu7.4 Version table: *** 1:2.11+dfsg-1ubuntu7.4 500 500 http://za.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:2.11+dfsg-1ubuntu7.3 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1:2.11+dfsg-1ubuntu7 500 500 http://za.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Hardware: Motherboard: X370 Killer SLI CPU: AMD Ryzen 7 1800X PCI device: 27:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (rev 01) IOMMU Group 15 27:00.0 USB controller [0c03]: VIA Technologies, Inc. VL805 USB 3.0 Host Controller [1106:3483] (rev 01) USB controller of PCI card: Bus 003 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Loaded device drivers: Before upgrading to Ubuntu 18.04, this PCI device was added to pci-stub.ids which allowed the device to be passed to a Windows 10 VM. In turn, all USB devices connected to this card worked in the VM and drivers could successfully be installed. Since the upgrade from Ubuntu 17.10 to Ubuntu 18.04, I have tried several approaches to have this device not bound to the xhci driver but all in vain. (In every test I did, I always performed update- initramfs -u as well as update-grub) pci-stub.ids does not stop xhci from grabbing device. So passing PCI card to VM does not work Adding the device ID to /etc/modprobe.d/vfio.conf (options) does seem to load the connect the vfio driver to it, but xhci still binds to it as well, so passing PCI device to VM does not work. Adding ":27:00.0,xhci" to /etc/unbindpci also did not work. By adding the USB controller to the VM, USB devices connected to it does seem to be USB devices on the VM, but some of the drivers does not load correctly in Windows 10. For example, I need to install a device driver for a ROCKEY4 USB dongle and even though the driver installs (which must be done with device disconnected), the driver does not seem to ever bind correctly to the device because the software that uses the dongle does not recognise it. I have successfully bound a PCI graphics adapter to the VM, so in principle PCI passthrough works, bit in the case of the USB PCI card there seems to be no way to pass the device to a VM. Expected result: PCI passthrough should be available to all types of PCI devices and instructions should be available from qemu or kvm documentation even though it involves different parts of the OS (such as making use of /etc/modprobe/vfio.conf, /etc/unbindpci etc) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781891/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773584] Re: zfs-dkms 0.7.5-1ubuntu16: zfs kernel module failed to build
*** This bug is a duplicate of bug 1742698 *** https://bugs.launchpad.net/bugs/1742698 ** This bug has been marked a duplicate of bug 1742698 zfs-dkms 0.6.5.6-0ubuntu18: zfs kernel module failed to build -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1773584 Title: zfs-dkms 0.7.5-1ubuntu16: zfs kernel module failed to build Status in zfs-linux package in Ubuntu: Confirmed Bug description: this was reported on the first boot after upgrade to 18.04. I am not using zfs currently so my fix is just to remove from the modeule list. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: zfs-dkms 0.7.5-1ubuntu16 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 DKMSBuildLog: DKMS make.log for zfs-0.7.5 for kernel 4.15.0-23-generic (x86_64) Sat May 26 04:11:20 PDT 2018 make: *** No targets specified and no makefile found. Stop. DKMSKernelVersion: 4.15.0-23-generic Date: Sat May 26 04:11:23 2018 InstallationDate: Installed on 2018-04-04 (52 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105) PackageArchitecture: all PackageVersion: 0.7.5-1ubuntu16 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: zfs-linux Title: zfs-dkms 0.7.5-1ubuntu16: zfs kernel module failed to build UpgradeStatus: Upgraded to bionic on 2018-05-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1773584/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1714084] Re: package zfsutils-linux 0.6.5.6-0ubuntu17 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1742698 *** https://bugs.launchpad.net/bugs/1742698 ** This bug has been marked a duplicate of bug 1742698 zfs-dkms 0.6.5.6-0ubuntu18: zfs kernel module failed to build -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1714084 Title: package zfsutils-linux 0.6.5.6-0ubuntu17 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in zfs-linux package in Ubuntu: New Bug description: Attempted reinstall of zfsutils-linux ProblemType: Package DistroRelease: Ubuntu 16.04 Package: zfsutils-linux 0.6.5.6-0ubuntu17 ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76 Uname: Linux 4.4.0-92-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Wed Aug 30 15:49:18 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-07-24 (402 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: zfs-linux Title: package zfsutils-linux 0.6.5.6-0ubuntu17 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.zfs: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1714084/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742698] Re: zfs-dkms 0.6.5.6-0ubuntu18: zfs kernel module failed to build
The zfs DKMS package is no longer required as the ZFS filesystem modules are now built into the kernel package, so a quick fix is to remove the zfs-dkms packagage -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1742698 Title: zfs-dkms 0.6.5.6-0ubuntu18: zfs kernel module failed to build Status in zfs-linux package in Ubuntu: Confirmed Bug description: Ubuntu MATE 16.04 standard distro. It looks like there is a common defect across many versions that has not been addressed. If they are trying to fix this, whatever they've been doing is not effective. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: zfs-dkms 0.6.5.6-0ubuntu18 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 DKMSBuildLog: DKMS make.log for zfs-0.6.5.6 for kernel 4.13.0-26-generic (x86_64) Thu Jan 11 06:40:09 MST 2018 make: *** No targets specified and no makefile found. Stop. DKMSKernelVersion: 4.13.0-26-generic Date: Thu Jan 11 06:40:12 2018 InstallationDate: Installed on 2017-12-16 (25 days ago) InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) PackageVersion: 0.6.5.6-0ubuntu18 RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: zfs-linux Title: zfs-dkms 0.6.5.6-0ubuntu18: zfs 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/zfs-linux/+bug/1742698/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781891] Re: PCI USB card passthrough does not work any more
Trying to recreate this, I have a xhci Host controller (no extra card, but as part of the chipset). 00:14.0 USB controller: Intel Corporation C610/X99 series chipset USB xHCI Host Controller (rev 05) 00:14.0 USB controller: Intel Corporation C610/X99 series chipset USB xHCI Host Controller (rev 05) (prog-if 30 [XHCI]) Subsystem: Hewlett-Packard Company C610/X99 series chipset USB xHCI Host Controller Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: xhci_hcd First check if it can be unbound: echo :00:14.0 | sudo tee /sys/bus/pci/devices/:00:14.0/driver/unbind Works and I see: [2071597.213764] xhci_hcd :00:14.0: remove, state 4 [2071597.213778] usb usb5: USB disconnect, device number 1 [2071597.215019] xhci_hcd :00:14.0: USB bus 5 deregistered [2071597.215036] xhci_hcd :00:14.0: remove, state 4 [2071597.215046] usb usb4: USB disconnect, device number 1 [2071597.215049] usb 4-3: USB disconnect, device number 2 [2071597.218160] xhci_hcd :00:14.0: USB bus 4 deregistered FYI: Libvirt should do the unbind/bind for you at runtime if you configured it as managed hostdev Check ID $ lspci -n -s 00:14.0 00:14.0 0c03: 8086:8d31 (rev 05) Tell vfio-pci to handle that $ echo 8086 8d31 | sudo tee /sys/bus/pci/drivers/vfio-pci/new_id I get a fail to bind it like: vfio-pci: probe of :00:14.0 failed with error But then on this system I always failed to get vfio working due to FW issues (not a Linux issue). You might try the above but for your device to initially rule out all of the modprobe/boot timing that might affect it. After boot just try to: 1. unbind your device from xhci 2. make the ID known to vfio-pci (that should autoload it then) Report back the kernel you have and the success or fail when doing so, along a dmesg log of the try. That should clarify if we look at vfio-pci no more being able to load at all (above test fails) or just at how to prep cour config correctly so that it works again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781891 Title: PCI USB card passthrough does not work any more Status in linux package in Ubuntu: Incomplete Bug description: System information: Ubuntu 18.04 LTS (server edition) with kernel 4.15.0-24-generic x86_64 Upgraded from Ubuntu server 17.10 Software: qemu-kvm: Installed: 1:2.11+dfsg-1ubuntu7.4 Candidate: 1:2.11+dfsg-1ubuntu7.4 Version table: *** 1:2.11+dfsg-1ubuntu7.4 500 500 http://za.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:2.11+dfsg-1ubuntu7.3 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1:2.11+dfsg-1ubuntu7 500 500 http://za.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Hardware: Motherboard: X370 Killer SLI CPU: AMD Ryzen 7 1800X PCI device: 27:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (rev 01) IOMMU Group 15 27:00.0 USB controller [0c03]: VIA Technologies, Inc. VL805 USB 3.0 Host Controller [1106:3483] (rev 01) USB controller of PCI card: Bus 003 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Loaded device drivers: Before upgrading to Ubuntu 18.04, this PCI device was added to pci-stub.ids which allowed the device to be passed to a Windows 10 VM. In turn, all USB devices connected to this card worked in the VM and drivers could successfully be installed. Since the upgrade from Ubuntu 17.10 to Ubuntu 18.04, I have tried several approaches to have this device not bound to the xhci driver but all in vain. (In every test I did, I always performed update- initramfs -u as well as update-grub) pci-stub.ids does not stop xhci from grabbing device. So passing PCI card to VM does not work Adding the device ID to /etc/modprobe.d/vfio.conf (options) does seem to load the connect the vfio driver to it, but xhci still binds to it as well, so passing PCI device to VM does not work. Adding ":27:00.0,xhci" to /etc/unbindpci also did not work. By adding the USB controller to the VM, USB devices connected to it does seem to be USB devices on the VM, but some of the drivers does not load correctly in Windows 10. For example, I need to install a device driver for a ROCKEY4 USB dongle and even though the driver installs (which must be done with device disconnected), the driver does not seem to ever bind correctly to the device because the software that uses the dongle does not recognise it. I have successfully bound a PCI graphics adapter to the VM, so in principle PCI passthrough works, bit in the case of the USB PCI card there seems to be no way to pass the devi
[Kernel-packages] [Bug 1769937] Re: Error reported when creating ZFS pool with "-t" option, despite successful pool creation
** Changed in: zfs-linux (Ubuntu) Status: Confirmed => In Progress ** Changed in: zfs-linux (Ubuntu) Importance: Undecided => High ** Changed in: zfs-linux (Ubuntu) Importance: High => Medium ** Changed in: zfs-linux (Ubuntu) Assignee: (unassigned) => Colin Ian King (colin-king) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1769937 Title: Error reported when creating ZFS pool with "-t" option, despite successful pool creation Status in zfs-linux package in Ubuntu: In Progress Bug description: When creating a pool with the -t option on Ubuntu 18.04 LTS, it will report an error and return a non-zero exit code, but the pool appears to be successfully created. For example: # zpool create -O canmount=off -O mountpoint=none -R /mnt/rpool-25582 -t rpool-25582 rpool /dev/mapper/loop2p1 cannot create 'rpool': no such pool or dataset # zpool list NAME SIZE ALLOC FREE EXPANDSZ FRAGCAP DEDUP HEALTH ALTROOT rpool-25582 69.5G 92.5K 69.5G - 0% 0% 1.00x ONLINE /mnt/rpool-25582 # zpool export rpool-25582 # zpool import rpool # zpool list NAMESIZE ALLOC FREE EXPANDSZ FRAGCAP DEDUP HEALTH ALTROOT rpool 69.5G 134K 69.5G - 0% 0% 1.00x ONLINE - I opened an upstream bug against ZFS on Linux, here: https://github.com/zfsonlinux/zfs/issues/7502 And it has been recently fixed, here: https://github.com/zfsonlinux/zfs/pull/7509 Can this upstream fix be pulled into the Ubuntu 18.04 LTS packages? Thanks, Prakash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1769937/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779815] Re: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device
** Tags added: id-5b4cdabed3976614e2bd033d -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1779815 Title: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device Status in The Ubuntu-power-systems project: Triaged Status in debian-installer package in Ubuntu: New Status in linux package in Ubuntu: Invalid Bug description: == Comment: #0 - ABDUL HALEEM - 2018-07-02 03:55:33 == ---Problem Description--- Ubuntu 18.04.01 ppc64el installer does not detect LSI3008 base SAS disks / MD RAID devices Used 20101020ubuntu543 version to install http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/ Contact Information = abdha...@in.ibm.com ---uname output--- Linux ltc-boston21 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = BostonLC ---boot type--- Network boot Installer fails to detect the LSI SAS disks / RAID MD device ===console error log=== ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ? /dev/nvme0n1 - 491.5 GB NVMe Device ? ? /dev/nvme1n1 - 98.3 GB NVMe Device ? ? ? ?? ? ? ??? moves; selects; activates buttons To make sure it detects the disks I had to Detect disks-->Guided partitioning--> Guided - use entire disk ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ? /dev/nvme0n1 - 491.5 GB NVMe Device? ? /dev/nvme1n1 - 98.3 GB NVMe Device ? ? SCSI3 (0,0,0) (sda) - 4.0 TB SEAGATE ST4000NM0075 ? ? SCSI3 (1,0,0) (sdb) - 199.9 GB LSI Logical Volume ? ? SCSI3 (0,2,0) (sdc) - 2.0 TB ATA ST2000NM0125-1YZ ? ? ? ?? ? ? ??? IPR had similar issue reported #164932 and fixed with 4.15.0-20, looks installer need a fix for LSI (mpt3sas) devices too == Comment: #2 - SEETEENA THOUFEEK - 2018-07-03 02:01:47 == 164932 - refers LP1751813 == Comment: #3 - SEETEENA THOUFEEK - 2018-07-03 02:02:51 == Jul 2 08:49:52 anna-install: Installing mdadm-udeb Jul 2 08:49:52 disk-detect: No Intel/DDF RAID disks detected. Jul 2 08:49:52 anna-install: Installing dmraid-udeb Jul 2 08:49:52 disk-detect: No Serial ATA RAID disks detected Jul 2 08:49:53 check-missing-firmware: looking at dmesg again, restarting from \[ 330.659712\] Jul 2 08:49:53 check-missing-firmware: timestamp found, truncating dmesg accordingly Jul 2 08:49:53 check-missing-firmware: saving timestamp for a later use: Jul 2 08:49:53 check-missing-firmware: /dev/.udev/firmware-missing does not exist, skipping Jul 2 08:49:53 check-missing-firmware: /run/udev/firmware-missing does not exist, skipping Jul 2 08:49:53 check-missing-firmware: no missing firmware in loaded kernel modules Jul 2 08:49:53 main-menu[1425]: (process:8933): ERROR: unsupported sector size 4096 on /dev/sda. Jul 2 08:49:53 main-menu[1425]: (process:8933): File descriptor 3 (pipe:[38926]) leaked on pvs invocation. Parent PID 8940: /bin/sh Jul 2 08:49:53 main-m
[Kernel-packages] [Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode
The daily build is still use 4.15.0-20 kernel. http://cdimage.ubuntu.com/ubuntu-server/bionic/daily/current/bionic-server-amd64.iso Anyone can confirm that the 18.04.1 d-i install iso would update the kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762940 Title: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode Status in linux package in Ubuntu: Triaged Status in install-package source package in Bionic: New Status in linux source package in Bionic: Triaged Bug description: For all(as I know) Huawei servers, the vga adapter are embed in the iBMC chips. Those server can install from ISO manually for 16.04.4 and screen display normally. But for 18.04 ( tested both for daily and final beta)version, the install screen is blur. One of tested server is Huawei 2855 v5, the certification link for 16.04 are https://certification.ubuntu.com/hardware/201707-25596/. Below are key difference of dmesg. It seems might related with DRM. 18.04 install screen is blur dmesg ... [2.039009] fb0: EFI VGA frame buffer device ... [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.191435] [drm] No driver support for vblank timestamp query. [4.209338] checking generic (9000 30) vs hw (0 0) [4.209384] fbcon: hibmcdrmfb (fb1) is primary device [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63 ... [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on minor 0 ... [5.636624] vga16fb: initializing [5.636627] vga16fb: mapped to 0x48a7a1d2 [5.636630] checking generic (9000 30) vs hw (a 1) [5.636676] fb2: VGA16 VGA frame buffer device ... 16.04.4 install screen is fine (no screen blur) dmesg ... [2.000419] fb0: EFI VGA frame buffer device [8.795065] vga16fb: initializing [8.795068] vga16fb: mapped to 0x880a [8.795071] checking generic (9800 30) vs hw (a 1) [8.795121] fb1: VGA16 VGA frame buffer device ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781838] Re: linux: 4.15.0-29.31 -proposed tracker
** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Invalid ** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781838 Title: linux: 4.15.0-29.31 -proposed tracker Status in Kernel SRU Workflow: Invalid 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: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-certification-testing series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Invalid Status in Kernel SRU Workflow snap-release-to-candidate series: Invalid Status in Kernel SRU Workflow snap-release-to-edge series: Invalid Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1781838/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782150] [NEW] linux: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Confirmed ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/snap-certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/snap-release-to-beta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-candidate Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-edge Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-stable Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Status: Invalid ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Bionic) Importance: Medium Status: Confirmed ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2018.07.02-5 kernel-sru-master-kernel ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: bionic ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-beta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-candidate Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-edge Importan
[Kernel-packages] [Bug 1782158] [NEW] linux-kvm: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1782150 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-kvm (Ubuntu Bionic) Importance: Medium Status: Confirmed ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2018.07.02-5 kernel-sru-derivative-of-1782150 ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux-kvm (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: bionic ** Changed in: linux-kvm (Ubuntu Bionic) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assig
[Kernel-packages] [Bug 1782157] [NEW] linux-aws: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1782150 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/snap-release-to-beta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-candidate Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-edge Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-stable Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-aws (Ubuntu Bionic) Importance: Medium Status: Confirmed ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2018.07.02-5 kernel-sru-derivative-of-1782150 ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux-aws (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: bionic ** Changed in: linux-aws (Ubuntu Bionic) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-beta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-candidate Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-edge Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-stable Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecide
[Kernel-packages] [Bug 1782154] [NEW] linux-gcp: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1782150 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/snap-release-to-beta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-candidate Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-edge Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-stable Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-gcp (Ubuntu Bionic) Importance: Medium Status: Confirmed ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2018.07.02-5 kernel-sru-derivative-of-1782150 ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux-gcp (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: bionic ** Changed in: linux-gcp (Ubuntu Bionic) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-beta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-candidate Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-edge Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-stable Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecide
[Kernel-packages] [Bug 1782153] [NEW] linux-oem: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1782150 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-oem (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem (Ubuntu Bionic) Importance: Medium Status: Confirmed ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2018.07.02-5 kernel-sru-derivative-of-1782150 ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux-oem (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: bionic ** Changed in: linux-oem (Ubuntu Bionic) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canon
[Kernel-packages] [Bug 1782151] [NEW] linux-azure: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1782150 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/snap-release-to-beta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-candidate Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-edge Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-stable Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/stakeholder-signoff Importance: Medium Assignee: Joshua R. Poulson (jrp) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-azure (Ubuntu Bionic) Importance: Medium Status: Confirmed ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2018.07.02-5 kernel-sru-derivative-of-1782150 ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux-azure (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: bionic ** Changed in: linux-azure (Ubuntu Bionic) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-beta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-candidate Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-edge Importance
[Kernel-packages] [Bug 1782162] [NEW] linux-gcp: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1782150 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/snap-release-to-beta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-candidate Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-edge Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-stable Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-gcp (Ubuntu Xenial) Importance: Medium Status: Confirmed ** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-backport-of-1782150 kernel-sru-cycle-2018.07.02-5 xenial ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux-gcp (Ubuntu Xenial) Importance: Undecided Status: New ** Tags added: xenial ** Changed in: linux-gcp (Ubuntu Xenial) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-beta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-candidate Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-edge Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-stable Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided
[Kernel-packages] [Bug 1782159] [NEW] linux-azure: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1782150 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/snap-release-to-beta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-candidate Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-edge Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-stable Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/stakeholder-signoff Importance: Medium Assignee: Joshua R. Poulson (jrp) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-azure (Ubuntu Xenial) Importance: Medium Status: Confirmed ** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-backport-of-1782150 kernel-sru-cycle-2018.07.02-5 xenial ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux-azure (Ubuntu Xenial) Importance: Undecided Status: New ** Tags added: xenial ** Changed in: linux-azure (Ubuntu Xenial) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-beta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-candidate Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-edge Importance:
[Kernel-packages] [Bug 1782162] Re: linux-gcp: -proposed tracker
** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Invalid ** Changed in: kernel-sru-workflow/upload-to-ppa Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Invalid ** Changed in: linux-gcp (Ubuntu Xenial) Status: Confirmed => Invalid -- 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/1782162 Title: linux-gcp: -proposed tracker Status in Kernel SRU Workflow: Invalid 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: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Invalid Status in Kernel SRU Workflow snap-release-to-candidate series: Invalid Status in Kernel SRU Workflow snap-release-to-edge series: Invalid Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Invalid Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1782150 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1782162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782159] Re: linux-azure: -proposed tracker
** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Invalid ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/upload-to-ppa Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Invalid ** Changed in: linux-azure (Ubuntu Xenial) Status: Confirmed => Invalid -- 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/1782159 Title: linux-azure: -proposed tracker Status in Kernel SRU Workflow: Invalid 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: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Invalid Status in Kernel SRU Workflow snap-release-to-candidate series: Invalid Status in Kernel SRU Workflow snap-release-to-edge series: Invalid Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Invalid Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1782150 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1782159/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782158] Re: linux-kvm: -proposed tracker
** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/upload-to-ppa Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Invalid ** Changed in: linux-kvm (Ubuntu Bionic) Status: Confirmed => Invalid -- 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/1782158 Title: linux-kvm: -proposed tracker Status in Kernel SRU Workflow: Invalid 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: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: Invalid Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1782150 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1782158/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782157] Re: linux-aws: -proposed tracker
** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Invalid ** Changed in: kernel-sru-workflow/upload-to-ppa Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Invalid ** Changed in: linux-aws (Ubuntu Bionic) Status: Confirmed => Invalid -- 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/1782157 Title: linux-aws: -proposed tracker Status in Kernel SRU Workflow: Invalid 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: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Invalid Status in Kernel SRU Workflow snap-release-to-candidate series: Invalid Status in Kernel SRU Workflow snap-release-to-edge series: Invalid Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Invalid Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1782150 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1782157/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782154] Re: linux-gcp: -proposed tracker
** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Invalid ** Changed in: kernel-sru-workflow/upload-to-ppa Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Invalid ** Changed in: linux-gcp (Ubuntu Bionic) Status: Confirmed => Invalid -- 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/1782154 Title: linux-gcp: -proposed tracker Status in Kernel SRU Workflow: Invalid 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: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Invalid Status in Kernel SRU Workflow snap-release-to-candidate series: Invalid Status in Kernel SRU Workflow snap-release-to-edge series: Invalid Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Invalid Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1782150 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1782154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782153] Re: linux-oem: -proposed tracker
** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/upload-to-ppa Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Invalid ** Changed in: linux-oem (Ubuntu Bionic) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1782153 Title: linux-oem: -proposed tracker Status in Kernel SRU Workflow: Invalid 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: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Invalid Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1782150 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1782153/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782151] Re: linux-azure: -proposed tracker
** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Invalid ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/upload-to-ppa Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Invalid ** Changed in: linux-azure (Ubuntu Bionic) Status: Confirmed => Invalid -- 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/1782151 Title: linux-azure: -proposed tracker Status in Kernel SRU Workflow: Invalid 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: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Invalid Status in Kernel SRU Workflow snap-release-to-candidate series: Invalid Status in Kernel SRU Workflow snap-release-to-edge series: Invalid Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Invalid Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1782150 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1782151/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782150] Re: linux: -proposed tracker
** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Invalid ** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782150 Title: linux: -proposed tracker Status in Kernel SRU Workflow: Invalid 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: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-certification-testing series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Invalid Status in Kernel SRU Workflow snap-release-to-candidate series: Invalid Status in Kernel SRU Workflow snap-release-to-edge series: Invalid Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1782150/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782166] [NEW] Invoking obsolete 'firmware_install' target breaks snap build
Public bug reported: Impact: The snapcraft.yaml in bionic/master still invokes the obsolete 'firmware_install' target that was removed in 5620a0d1aacd554ebebcff373e31107bb1ef7769 ("firmware: delete in-kernel firmware"), and by invoking a non existin target, snap build fails. On a generic amd64 environment, check out the Bionic/generic tree, cd into it and execute snapcraft: linux $ snapcraft ... make -j4 bzImage modules ... LD [M] virt/lib/irqbypass.ko make: *** No rule to make target 'firmware_install'. Stop. make: *** Waiting for unfinished jobs INSTALL arch/x86/crypto/blowfish-x86_64.ko ... make -j4 CONFIG_PREFIX=/home/flag/canonical/linux/parts/kernel/install modules_install INSTALL_MOD_PATH=/home/flag/canonical/linux/parts/kernel/install firmware_install INSTALL_FW_PATH=/home/flag/canonical/linux/parts/kernel/install/lib/firmware Failed to run 'make -j4 CONFIG_PREFIX=/home/flag/canonical/linux/parts/kernel/install modules_install INSTALL_MOD_PATH=/home/flag/canonical/linux/parts/kernel/install firmware_install INSTALL_FW_PATH=/home/flag/canonical/linux/parts/kernel/install/lib/firmware' for 'kernel': Exited with code 2. Verify that the part is using the correct parameters and try again. Fix: Stop invoking a non existing target by applying the attached patch. $ snapcraft ... Regression risk: None since the patch only modifies the snapcraft.yaml file. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782166 Title: Invoking obsolete 'firmware_install' target breaks snap build Status in linux package in Ubuntu: New Bug description: Impact: The snapcraft.yaml in bionic/master still invokes the obsolete 'firmware_install' target that was removed in 5620a0d1aacd554ebebcff373e31107bb1ef7769 ("firmware: delete in-kernel firmware"), and by invoking a non existin target, snap build fails. On a generic amd64 environment, check out the Bionic/generic tree, cd into it and execute snapcraft: linux $ snapcraft ... make -j4 bzImage modules ... LD [M] virt/lib/irqbypass.ko make: *** No rule to make target 'firmware_install'. Stop. make: *** Waiting for unfinished jobs INSTALL arch/x86/crypto/blowfish-x86_64.ko ... make -j4 CONFIG_PREFIX=/home/flag/canonical/linux/parts/kernel/install modules_install INSTALL_MOD_PATH=/home/flag/canonical/linux/parts/kernel/install firmware_install INSTALL_FW_PATH=/home/flag/canonical/linux/parts/kernel/install/lib/firmware Failed to run 'make -j4 CONFIG_PREFIX=/home/flag/canonical/linux/parts/kernel/install modules_install INSTALL_MOD_PATH=/home/flag/canonical/linux/parts/kernel/install firmware_install INSTALL_FW_PATH=/home/flag/canonical/linux/parts/kernel/install/lib/firmware' for 'kernel': Exited with code 2. Verify that the part is using the correct parameters and try again. Fix: Stop invoking a non existing target by applying the attached patch. $ snapcraft ... Regression risk: None since the patch only modifies the snapcraft.yaml file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781839] Re: linux: 4.4.0-132.158 -proposed tracker
** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Won't Fix => Invalid ** Changed in: linux (Ubuntu Xenial) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781839 Title: linux: 4.4.0-132.158 -proposed tracker Status in Kernel SRU Workflow: Invalid 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: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-certification-testing series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Invalid Status in Kernel SRU Workflow snap-release-to-candidate series: Invalid Status in Kernel SRU Workflow snap-release-to-edge series: Invalid Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1781839/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782166] Re: Invoking obsolete 'firmware_install' target breaks snap build
** Patch added: "0001-UBUNTU-snapcraft.yaml-stop-invoking-the-obsolete-and.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782166/+attachment/5164548/+files/0001-UBUNTU-snapcraft.yaml-stop-invoking-the-obsolete-and.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782166 Title: Invoking obsolete 'firmware_install' target breaks snap build Status in linux package in Ubuntu: New Bug description: Impact: The snapcraft.yaml in bionic/master still invokes the obsolete 'firmware_install' target that was removed in 5620a0d1aacd554ebebcff373e31107bb1ef7769 ("firmware: delete in-kernel firmware"), and by invoking a non existin target, snap build fails. On a generic amd64 environment, check out the Bionic/generic tree, cd into it and execute snapcraft: linux $ snapcraft ... make -j4 bzImage modules ... LD [M] virt/lib/irqbypass.ko make: *** No rule to make target 'firmware_install'. Stop. make: *** Waiting for unfinished jobs INSTALL arch/x86/crypto/blowfish-x86_64.ko ... make -j4 CONFIG_PREFIX=/home/flag/canonical/linux/parts/kernel/install modules_install INSTALL_MOD_PATH=/home/flag/canonical/linux/parts/kernel/install firmware_install INSTALL_FW_PATH=/home/flag/canonical/linux/parts/kernel/install/lib/firmware Failed to run 'make -j4 CONFIG_PREFIX=/home/flag/canonical/linux/parts/kernel/install modules_install INSTALL_MOD_PATH=/home/flag/canonical/linux/parts/kernel/install firmware_install INSTALL_FW_PATH=/home/flag/canonical/linux/parts/kernel/install/lib/firmware' for 'kernel': Exited with code 2. Verify that the part is using the correct parameters and try again. Fix: Stop invoking a non existing target by applying the attached patch. $ snapcraft ... Regression risk: None since the patch only modifies the snapcraft.yaml file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782166] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1782166 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782166 Title: Invoking obsolete 'firmware_install' target breaks snap build Status in linux package in Ubuntu: Incomplete Bug description: Impact: The snapcraft.yaml in bionic/master still invokes the obsolete 'firmware_install' target that was removed in 5620a0d1aacd554ebebcff373e31107bb1ef7769 ("firmware: delete in-kernel firmware"), and by invoking a non existin target, snap build fails. On a generic amd64 environment, check out the Bionic/generic tree, cd into it and execute snapcraft: linux $ snapcraft ... make -j4 bzImage modules ... LD [M] virt/lib/irqbypass.ko make: *** No rule to make target 'firmware_install'. Stop. make: *** Waiting for unfinished jobs INSTALL arch/x86/crypto/blowfish-x86_64.ko ... make -j4 CONFIG_PREFIX=/home/flag/canonical/linux/parts/kernel/install modules_install INSTALL_MOD_PATH=/home/flag/canonical/linux/parts/kernel/install firmware_install INSTALL_FW_PATH=/home/flag/canonical/linux/parts/kernel/install/lib/firmware Failed to run 'make -j4 CONFIG_PREFIX=/home/flag/canonical/linux/parts/kernel/install modules_install INSTALL_MOD_PATH=/home/flag/canonical/linux/parts/kernel/install firmware_install INSTALL_FW_PATH=/home/flag/canonical/linux/parts/kernel/install/lib/firmware' for 'kernel': Exited with code 2. Verify that the part is using the correct parameters and try again. Fix: Stop invoking a non existing target by applying the attached patch. $ snapcraft ... Regression risk: None since the patch only modifies the snapcraft.yaml file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779376] Re: linux: 4.4.0-131.157 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/xenial/4.4.0-131.157 /xenial-proposed-published.html ** Tags added: certification-testing-passed ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1779376 Title: linux: 4.4.0-131.157 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1779377 (linux-aws), bug 1779378 (linux-lts-xenial) derivatives: bug 1779379 (linux-aws), bug 1779380 (linux-euclid), bug 1779381 (linux-kvm), bug 1779382 (linux-raspi2), bug 1779383 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1779376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782173] [NEW] linux: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Confirmed ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/snap-certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/snap-release-to-beta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-candidate Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-edge Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-stable Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Status: Invalid ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Bionic) Importance: Medium Status: Confirmed ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2018.07.02-5 kernel-sru-master-kernel ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: bionic ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-beta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-candidate Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-edge Importan
[Kernel-packages] [Bug 1782166] Re: Invoking obsolete 'firmware_install' target breaks snap build
** Description changed: Impact: - The snapcraft.yaml in bionic/master still invokes the obsolete + The snapcraft.yaml in bionic/master invokes the now obsolete 'firmware_install' target that was removed in 5620a0d1aacd554ebebcff373e31107bb1ef7769 ("firmware: delete in-kernel - firmware"), and by invoking a non existin target, snap build fails. + firmware"), and by invoking a non existing target, it fails to build. On a generic amd64 environment, check out the Bionic/generic tree, cd into it and execute snapcraft: linux $ snapcraft ... make -j4 bzImage modules ... - LD [M] virt/lib/irqbypass.ko + LD [M] virt/lib/irqbypass.ko make: *** No rule to make target 'firmware_install'. Stop. make: *** Waiting for unfinished jobs - INSTALL arch/x86/crypto/blowfish-x86_64.ko + INSTALL arch/x86/crypto/blowfish-x86_64.ko ... make -j4 CONFIG_PREFIX=/home/flag/canonical/linux/parts/kernel/install modules_install INSTALL_MOD_PATH=/home/flag/canonical/linux/parts/kernel/install firmware_install INSTALL_FW_PATH=/home/flag/canonical/linux/parts/kernel/install/lib/firmware Failed to run 'make -j4 CONFIG_PREFIX=/home/flag/canonical/linux/parts/kernel/install modules_install INSTALL_MOD_PATH=/home/flag/canonical/linux/parts/kernel/install firmware_install INSTALL_FW_PATH=/home/flag/canonical/linux/parts/kernel/install/lib/firmware' for 'kernel': Exited with code 2. Verify that the part is using the correct parameters and try again. Fix: - Stop invoking a non existing target by applying the attached patch. + Since firmware files were removed from the Linux source code, and we + rely on files provided by the linux-firmware package, skip invoking + 'firmware_install' altogether and fix the build. - $ snapcraft + linux $ snapcraft ... - + Staging kernel + Staging firmware + Priming kernel + Priming firmware + Determining the version from the project repo (version-script). + The version has been set to '4.15.0-24.26' + Snapping 'pc-kernel' | + Snapped pc-kernel_4.15.0-24.26_amd64.snap + linux $ Regression risk: None since the patch only modifies the snapcraft.yaml file. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782166 Title: Invoking obsolete 'firmware_install' target breaks snap build Status in linux package in Ubuntu: Incomplete Bug description: Impact: The snapcraft.yaml in bionic/master invokes the now obsolete 'firmware_install' target that was removed in 5620a0d1aacd554ebebcff373e31107bb1ef7769 ("firmware: delete in-kernel firmware"), and by invoking a non existing target, it fails to build. On a generic amd64 environment, check out the Bionic/generic tree, cd into it and execute snapcraft: linux $ snapcraft ... make -j4 bzImage modules ... LD [M] virt/lib/irqbypass.ko make: *** No rule to make target 'firmware_install'. Stop. make: *** Waiting for unfinished jobs INSTALL arch/x86/crypto/blowfish-x86_64.ko ... make -j4 CONFIG_PREFIX=/home/flag/canonical/linux/parts/kernel/install modules_install INSTALL_MOD_PATH=/home/flag/canonical/linux/parts/kernel/install firmware_install INSTALL_FW_PATH=/home/flag/canonical/linux/parts/kernel/install/lib/firmware Failed to run 'make -j4 CONFIG_PREFIX=/home/flag/canonical/linux/parts/kernel/install modules_install INSTALL_MOD_PATH=/home/flag/canonical/linux/parts/kernel/install firmware_install INSTALL_FW_PATH=/home/flag/canonical/linux/parts/kernel/install/lib/firmware' for 'kernel': Exited with code 2. Verify that the part is using the correct parameters and try again. Fix: Since firmware files were removed from the Linux source code, and we rely on files provided by the linux-firmware package, skip invoking 'firmware_install' altogether and fix the build. linux $ snapcraft ... Staging kernel Staging firmware Priming kernel Priming firmware Determining the version from the project repo (version-script). The version has been set to '4.15.0-24.26' Snapping 'pc-kernel' | Snapped pc-kernel_4.15.0-24.26_amd64.snap linux $ Regression risk: None since the patch only modifies the snapcraft.yaml file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782181] [NEW] linux-oem: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1782173 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-oem (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem (Ubuntu Bionic) Importance: Medium Status: Confirmed ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2018.07.02-5 kernel-sru-derivative-of-1782173 ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux-oem (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: bionic ** Changed in: linux-oem (Ubuntu Bionic) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canon
[Kernel-packages] [Bug 1782180] [NEW] linux-kvm: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1782173 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-kvm (Ubuntu Bionic) Importance: Medium Status: Confirmed ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2018.07.02-5 kernel-sru-derivative-of-1782173 ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux-kvm (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: bionic ** Changed in: linux-kvm (Ubuntu Bionic) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assig
[Kernel-packages] [Bug 1782178] [NEW] linux-azure: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1782173 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/snap-release-to-beta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-candidate Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-edge Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-stable Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/stakeholder-signoff Importance: Medium Assignee: Joshua R. Poulson (jrp) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-azure (Ubuntu Bionic) Importance: Medium Status: Confirmed ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2018.07.02-5 kernel-sru-derivative-of-1782173 ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux-azure (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: bionic ** Changed in: linux-azure (Ubuntu Bionic) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-beta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-candidate Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-edge Importance
[Kernel-packages] [Bug 1782176] [NEW] linux-aws: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1782173 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/snap-release-to-beta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-candidate Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-edge Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-stable Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-aws (Ubuntu Bionic) Importance: Medium Status: Confirmed ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2018.07.02-5 kernel-sru-derivative-of-1782173 ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux-aws (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: bionic ** Changed in: linux-aws (Ubuntu Bionic) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-beta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-candidate Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-edge Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-stable Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecide
[Kernel-packages] [Bug 1782174] [NEW] linux-gcp: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1782173 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/snap-release-to-beta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-candidate Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-edge Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-stable Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-gcp (Ubuntu Bionic) Importance: Medium Status: Confirmed ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2018.07.02-5 kernel-sru-derivative-of-1782173 ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux-gcp (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: bionic ** Changed in: linux-gcp (Ubuntu Bionic) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-beta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-candidate Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-edge Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-stable Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecide
[Kernel-packages] [Bug 1782186] [NEW] linux-azure: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1782173 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/snap-release-to-beta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-candidate Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-edge Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-stable Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/stakeholder-signoff Importance: Medium Assignee: Joshua R. Poulson (jrp) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-azure (Ubuntu Xenial) Importance: Medium Status: Confirmed ** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-backport-of-1782173 kernel-sru-cycle-2018.07.02-5 xenial ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux-azure (Ubuntu Xenial) Importance: Undecided Status: New ** Tags added: xenial ** Changed in: linux-azure (Ubuntu Xenial) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-beta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-candidate Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-edge Importance:
[Kernel-packages] [Bug 1782184] [NEW] linux-gcp: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1782173 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/snap-release-to-beta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-candidate Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-edge Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-stable Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-gcp (Ubuntu Xenial) Importance: Medium Status: Confirmed ** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-backport-of-1782173 kernel-sru-cycle-2018.07.02-5 xenial ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux-gcp (Ubuntu Xenial) Importance: Undecided Status: New ** Tags added: xenial ** Changed in: linux-gcp (Ubuntu Xenial) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-beta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-candidate Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-edge Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-stable Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided
[Kernel-packages] [Bug 1782166] Re: Invoking obsolete 'firmware_install' target breaks snap build
** Description changed: Impact: The snapcraft.yaml in bionic/master invokes the now obsolete 'firmware_install' target that was removed in 5620a0d1aacd554ebebcff373e31107bb1ef7769 ("firmware: delete in-kernel - firmware"), and by invoking a non existing target, it fails to build. + firmware"), and by invoking a non existing target, it breaks the build + process. On a generic amd64 environment, check out the Bionic/generic tree, cd into it and execute snapcraft: linux $ snapcraft ... make -j4 bzImage modules ... LD [M] virt/lib/irqbypass.ko make: *** No rule to make target 'firmware_install'. Stop. make: *** Waiting for unfinished jobs INSTALL arch/x86/crypto/blowfish-x86_64.ko ... make -j4 CONFIG_PREFIX=/home/flag/canonical/linux/parts/kernel/install modules_install INSTALL_MOD_PATH=/home/flag/canonical/linux/parts/kernel/install firmware_install INSTALL_FW_PATH=/home/flag/canonical/linux/parts/kernel/install/lib/firmware Failed to run 'make -j4 CONFIG_PREFIX=/home/flag/canonical/linux/parts/kernel/install modules_install INSTALL_MOD_PATH=/home/flag/canonical/linux/parts/kernel/install firmware_install INSTALL_FW_PATH=/home/flag/canonical/linux/parts/kernel/install/lib/firmware' for 'kernel': Exited with code 2. Verify that the part is using the correct parameters and try again. Fix: Since firmware files were removed from the Linux source code, and we rely on files provided by the linux-firmware package, skip invoking 'firmware_install' altogether and fix the build. linux $ snapcraft ... - Staging kernel - Staging firmware - Priming kernel - Priming firmware + Staging kernel + Staging firmware + Priming kernel + Priming firmware Determining the version from the project repo (version-script). The version has been set to '4.15.0-24.26' - Snapping 'pc-kernel' | + Snapping 'pc-kernel' | Snapped pc-kernel_4.15.0-24.26_amd64.snap linux $ Regression risk: None since the patch only modifies the snapcraft.yaml file. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782166 Title: Invoking obsolete 'firmware_install' target breaks snap build Status in linux package in Ubuntu: Incomplete Bug description: Impact: The snapcraft.yaml in bionic/master invokes the now obsolete 'firmware_install' target that was removed in 5620a0d1aacd554ebebcff373e31107bb1ef7769 ("firmware: delete in-kernel firmware"), and by invoking a non existing target, it breaks the build process. On a generic amd64 environment, check out the Bionic/generic tree, cd into it and execute snapcraft: linux $ snapcraft ... make -j4 bzImage modules ... LD [M] virt/lib/irqbypass.ko make: *** No rule to make target 'firmware_install'. Stop. make: *** Waiting for unfinished jobs INSTALL arch/x86/crypto/blowfish-x86_64.ko ... make -j4 CONFIG_PREFIX=/home/flag/canonical/linux/parts/kernel/install modules_install INSTALL_MOD_PATH=/home/flag/canonical/linux/parts/kernel/install firmware_install INSTALL_FW_PATH=/home/flag/canonical/linux/parts/kernel/install/lib/firmware Failed to run 'make -j4 CONFIG_PREFIX=/home/flag/canonical/linux/parts/kernel/install modules_install INSTALL_MOD_PATH=/home/flag/canonical/linux/parts/kernel/install firmware_install INSTALL_FW_PATH=/home/flag/canonical/linux/parts/kernel/install/lib/firmware' for 'kernel': Exited with code 2. Verify that the part is using the correct parameters and try again. Fix: Since firmware files were removed from the Linux source code, and we rely on files provided by the linux-firmware package, skip invoking 'firmware_install' altogether and fix the build. linux $ snapcraft ... Staging kernel Staging firmware Priming kernel Priming firmware Determining the version from the project repo (version-script). The version has been set to '4.15.0-24.26' Snapping 'pc-kernel' | Snapped pc-kernel_4.15.0-24.26_amd64.snap linux $ Regression risk: None since the patch only modifies the snapcraft.yaml file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781891] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1781891/+attachment/5164569/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781891 Title: PCI USB card passthrough does not work any more Status in linux package in Ubuntu: Confirmed Bug description: System information: Ubuntu 18.04 LTS (server edition) with kernel 4.15.0-24-generic x86_64 Upgraded from Ubuntu server 17.10 Software: qemu-kvm: Installed: 1:2.11+dfsg-1ubuntu7.4 Candidate: 1:2.11+dfsg-1ubuntu7.4 Version table: *** 1:2.11+dfsg-1ubuntu7.4 500 500 http://za.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:2.11+dfsg-1ubuntu7.3 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1:2.11+dfsg-1ubuntu7 500 500 http://za.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Hardware: Motherboard: X370 Killer SLI CPU: AMD Ryzen 7 1800X PCI device: 27:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (rev 01) IOMMU Group 15 27:00.0 USB controller [0c03]: VIA Technologies, Inc. VL805 USB 3.0 Host Controller [1106:3483] (rev 01) USB controller of PCI card: Bus 003 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Loaded device drivers: Before upgrading to Ubuntu 18.04, this PCI device was added to pci-stub.ids which allowed the device to be passed to a Windows 10 VM. In turn, all USB devices connected to this card worked in the VM and drivers could successfully be installed. Since the upgrade from Ubuntu 17.10 to Ubuntu 18.04, I have tried several approaches to have this device not bound to the xhci driver but all in vain. (In every test I did, I always performed update- initramfs -u as well as update-grub) pci-stub.ids does not stop xhci from grabbing device. So passing PCI card to VM does not work Adding the device ID to /etc/modprobe.d/vfio.conf (options) does seem to load the connect the vfio driver to it, but xhci still binds to it as well, so passing PCI device to VM does not work. Adding ":27:00.0,xhci" to /etc/unbindpci also did not work. By adding the USB controller to the VM, USB devices connected to it does seem to be USB devices on the VM, but some of the drivers does not load correctly in Windows 10. For example, I need to install a device driver for a ROCKEY4 USB dongle and even though the driver installs (which must be done with device disconnected), the driver does not seem to ever bind correctly to the device because the software that uses the dongle does not recognise it. I have successfully bound a PCI graphics adapter to the VM, so in principle PCI passthrough works, bit in the case of the USB PCI card there seems to be no way to pass the device to a VM. Expected result: PCI passthrough should be available to all types of PCI devices and instructions should be available from qemu or kvm documentation even though it involves different parts of the OS (such as making use of /etc/modprobe/vfio.conf, /etc/unbindpci etc) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-24-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=087ca1e6-4fd0-4a4b-a323-8b8ce733b3c7 InstallationDate: Installed on 2018-03-14 (124 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=0286b7bc-6ce2-494c-89aa-6c4402876bad ro ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-generic N/A lin
[Kernel-packages] [Bug 1781891] Re: PCI USB card passthrough does not work any more
apport information ** Tags added: apport-collected ** Description changed: System information: Ubuntu 18.04 LTS (server edition) with kernel 4.15.0-24-generic x86_64 Upgraded from Ubuntu server 17.10 Software: qemu-kvm: Installed: 1:2.11+dfsg-1ubuntu7.4 Candidate: 1:2.11+dfsg-1ubuntu7.4 Version table: *** 1:2.11+dfsg-1ubuntu7.4 500 500 http://za.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:2.11+dfsg-1ubuntu7.3 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1:2.11+dfsg-1ubuntu7 500 500 http://za.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Hardware: Motherboard: X370 Killer SLI CPU: AMD Ryzen 7 1800X PCI device: 27:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (rev 01) IOMMU Group 15 27:00.0 USB controller [0c03]: VIA Technologies, Inc. VL805 USB 3.0 Host Controller [1106:3483] (rev 01) USB controller of PCI card: Bus 003 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Loaded device drivers: Before upgrading to Ubuntu 18.04, this PCI device was added to pci-stub.ids which allowed the device to be passed to a Windows 10 VM. In turn, all USB devices connected to this card worked in the VM and drivers could successfully be installed. Since the upgrade from Ubuntu 17.10 to Ubuntu 18.04, I have tried several approaches to have this device not bound to the xhci driver but all in vain. (In every test I did, I always performed update-initramfs -u as well as update-grub) pci-stub.ids does not stop xhci from grabbing device. So passing PCI card to VM does not work Adding the device ID to /etc/modprobe.d/vfio.conf (options) does seem to load the connect the vfio driver to it, but xhci still binds to it as well, so passing PCI device to VM does not work. Adding ":27:00.0,xhci" to /etc/unbindpci also did not work. By adding the USB controller to the VM, USB devices connected to it does seem to be USB devices on the VM, but some of the drivers does not load correctly in Windows 10. For example, I need to install a device driver for a ROCKEY4 USB dongle and even though the driver installs (which must be done with device disconnected), the driver does not seem to ever bind correctly to the device because the software that uses the dongle does not recognise it. I have successfully bound a PCI graphics adapter to the VM, so in principle PCI passthrough works, bit in the case of the USB PCI card there seems to be no way to pass the device to a VM. Expected result: - PCI passthrough should be available to all types of PCI devices and - instructions should be available from qemu or kvm documentation even - though it involves different parts of the OS (such as making use of - /etc/modprobe/vfio.conf, /etc/unbindpci etc) + PCI passthrough should be available to all types of PCI devices and instructions should be available from qemu or kvm documentation even though it involves different parts of the OS (such as making use of /etc/modprobe/vfio.conf, /etc/unbindpci etc) + --- + AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-24-generic. + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' + ApportVersion: 2.20.9-0ubuntu7.1 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' + Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' + DistroRelease: Ubuntu 18.04 + HibernationDevice: RESUME=UUID=087ca1e6-4fd0-4a4b-a323-8b8ce733b3c7 + InstallationDate: Installed on 2018-03-14 (124 days ago) + InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' + Lsusb: + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + MachineType: QEMU Standard PC (i440FX + PIIX, 1996) + Package: linux (not installed) + ProcFB: 0 qxldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=0286b7bc-6ce2-494c-89aa-6c4402876bad ro + ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-24-generic N/A + linux-backports-modules-4.15.0-24-generic N/A + linux-firmware 1.173 + RfKill: Error: [Errno 2] N
[Kernel-packages] [Bug 1781891] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1781891/+attachment/5164567/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781891 Title: PCI USB card passthrough does not work any more Status in linux package in Ubuntu: Confirmed Bug description: System information: Ubuntu 18.04 LTS (server edition) with kernel 4.15.0-24-generic x86_64 Upgraded from Ubuntu server 17.10 Software: qemu-kvm: Installed: 1:2.11+dfsg-1ubuntu7.4 Candidate: 1:2.11+dfsg-1ubuntu7.4 Version table: *** 1:2.11+dfsg-1ubuntu7.4 500 500 http://za.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:2.11+dfsg-1ubuntu7.3 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1:2.11+dfsg-1ubuntu7 500 500 http://za.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Hardware: Motherboard: X370 Killer SLI CPU: AMD Ryzen 7 1800X PCI device: 27:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (rev 01) IOMMU Group 15 27:00.0 USB controller [0c03]: VIA Technologies, Inc. VL805 USB 3.0 Host Controller [1106:3483] (rev 01) USB controller of PCI card: Bus 003 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Loaded device drivers: Before upgrading to Ubuntu 18.04, this PCI device was added to pci-stub.ids which allowed the device to be passed to a Windows 10 VM. In turn, all USB devices connected to this card worked in the VM and drivers could successfully be installed. Since the upgrade from Ubuntu 17.10 to Ubuntu 18.04, I have tried several approaches to have this device not bound to the xhci driver but all in vain. (In every test I did, I always performed update- initramfs -u as well as update-grub) pci-stub.ids does not stop xhci from grabbing device. So passing PCI card to VM does not work Adding the device ID to /etc/modprobe.d/vfio.conf (options) does seem to load the connect the vfio driver to it, but xhci still binds to it as well, so passing PCI device to VM does not work. Adding ":27:00.0,xhci" to /etc/unbindpci also did not work. By adding the USB controller to the VM, USB devices connected to it does seem to be USB devices on the VM, but some of the drivers does not load correctly in Windows 10. For example, I need to install a device driver for a ROCKEY4 USB dongle and even though the driver installs (which must be done with device disconnected), the driver does not seem to ever bind correctly to the device because the software that uses the dongle does not recognise it. I have successfully bound a PCI graphics adapter to the VM, so in principle PCI passthrough works, bit in the case of the USB PCI card there seems to be no way to pass the device to a VM. Expected result: PCI passthrough should be available to all types of PCI devices and instructions should be available from qemu or kvm documentation even though it involves different parts of the OS (such as making use of /etc/modprobe/vfio.conf, /etc/unbindpci etc) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-24-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=087ca1e6-4fd0-4a4b-a323-8b8ce733b3c7 InstallationDate: Installed on 2018-03-14 (124 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=0286b7bc-6ce2-494c-89aa-6c4402876bad ro ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-generic N/A linux-firmware
[Kernel-packages] [Bug 1782173] Re: linux: -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow + + backports: bug 1782182 (linux-hwe-edge), bug 1782183 (linux-hwe), bug 1782184 (linux-gcp), bug 1782185 (linux-azure-edge), bug 1782186 (linux-azure) + derivatives: bug 1782174 (linux-gcp), bug 1782175 (linux-raspi2), bug 1782176 (linux-aws), bug 1782178 (linux-azure), bug 1782180 (linux-kvm), bug 1782181 (linux-oem) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782173 Title: linux: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1782182 (linux-hwe-edge), bug 1782183 (linux-hwe), bug 1782184 (linux-gcp), bug 1782185 (linux-azure-edge), bug 1782186 (linux-azure) derivatives: bug 1782174 (linux-gcp), bug 1782175 (linux-raspi2), bug 1782176 (linux-aws), bug 1782178 (linux-azure), bug 1782180 (linux-kvm), bug 1782181 (linux-oem) To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1782173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781891] Card0.Codecs.codec.0.txt
apport information ** Attachment added: "Card0.Codecs.codec.0.txt" https://bugs.launchpad.net/bugs/1781891/+attachment/5164568/+files/Card0.Codecs.codec.0.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781891 Title: PCI USB card passthrough does not work any more Status in linux package in Ubuntu: Confirmed Bug description: System information: Ubuntu 18.04 LTS (server edition) with kernel 4.15.0-24-generic x86_64 Upgraded from Ubuntu server 17.10 Software: qemu-kvm: Installed: 1:2.11+dfsg-1ubuntu7.4 Candidate: 1:2.11+dfsg-1ubuntu7.4 Version table: *** 1:2.11+dfsg-1ubuntu7.4 500 500 http://za.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:2.11+dfsg-1ubuntu7.3 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1:2.11+dfsg-1ubuntu7 500 500 http://za.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Hardware: Motherboard: X370 Killer SLI CPU: AMD Ryzen 7 1800X PCI device: 27:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (rev 01) IOMMU Group 15 27:00.0 USB controller [0c03]: VIA Technologies, Inc. VL805 USB 3.0 Host Controller [1106:3483] (rev 01) USB controller of PCI card: Bus 003 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Loaded device drivers: Before upgrading to Ubuntu 18.04, this PCI device was added to pci-stub.ids which allowed the device to be passed to a Windows 10 VM. In turn, all USB devices connected to this card worked in the VM and drivers could successfully be installed. Since the upgrade from Ubuntu 17.10 to Ubuntu 18.04, I have tried several approaches to have this device not bound to the xhci driver but all in vain. (In every test I did, I always performed update- initramfs -u as well as update-grub) pci-stub.ids does not stop xhci from grabbing device. So passing PCI card to VM does not work Adding the device ID to /etc/modprobe.d/vfio.conf (options) does seem to load the connect the vfio driver to it, but xhci still binds to it as well, so passing PCI device to VM does not work. Adding ":27:00.0,xhci" to /etc/unbindpci also did not work. By adding the USB controller to the VM, USB devices connected to it does seem to be USB devices on the VM, but some of the drivers does not load correctly in Windows 10. For example, I need to install a device driver for a ROCKEY4 USB dongle and even though the driver installs (which must be done with device disconnected), the driver does not seem to ever bind correctly to the device because the software that uses the dongle does not recognise it. I have successfully bound a PCI graphics adapter to the VM, so in principle PCI passthrough works, bit in the case of the USB PCI card there seems to be no way to pass the device to a VM. Expected result: PCI passthrough should be available to all types of PCI devices and instructions should be available from qemu or kvm documentation even though it involves different parts of the OS (such as making use of /etc/modprobe/vfio.conf, /etc/unbindpci etc) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-24-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=087ca1e6-4fd0-4a4b-a323-8b8ce733b3c7 InstallationDate: Installed on 2018-03-14 (124 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=0286b7bc-6ce2-494c-89aa-6c4402876bad ro ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-gen
[Kernel-packages] [Bug 1781891] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1781891/+attachment/5164570/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781891 Title: PCI USB card passthrough does not work any more Status in linux package in Ubuntu: Confirmed Bug description: System information: Ubuntu 18.04 LTS (server edition) with kernel 4.15.0-24-generic x86_64 Upgraded from Ubuntu server 17.10 Software: qemu-kvm: Installed: 1:2.11+dfsg-1ubuntu7.4 Candidate: 1:2.11+dfsg-1ubuntu7.4 Version table: *** 1:2.11+dfsg-1ubuntu7.4 500 500 http://za.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:2.11+dfsg-1ubuntu7.3 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1:2.11+dfsg-1ubuntu7 500 500 http://za.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Hardware: Motherboard: X370 Killer SLI CPU: AMD Ryzen 7 1800X PCI device: 27:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (rev 01) IOMMU Group 15 27:00.0 USB controller [0c03]: VIA Technologies, Inc. VL805 USB 3.0 Host Controller [1106:3483] (rev 01) USB controller of PCI card: Bus 003 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Loaded device drivers: Before upgrading to Ubuntu 18.04, this PCI device was added to pci-stub.ids which allowed the device to be passed to a Windows 10 VM. In turn, all USB devices connected to this card worked in the VM and drivers could successfully be installed. Since the upgrade from Ubuntu 17.10 to Ubuntu 18.04, I have tried several approaches to have this device not bound to the xhci driver but all in vain. (In every test I did, I always performed update- initramfs -u as well as update-grub) pci-stub.ids does not stop xhci from grabbing device. So passing PCI card to VM does not work Adding the device ID to /etc/modprobe.d/vfio.conf (options) does seem to load the connect the vfio driver to it, but xhci still binds to it as well, so passing PCI device to VM does not work. Adding ":27:00.0,xhci" to /etc/unbindpci also did not work. By adding the USB controller to the VM, USB devices connected to it does seem to be USB devices on the VM, but some of the drivers does not load correctly in Windows 10. For example, I need to install a device driver for a ROCKEY4 USB dongle and even though the driver installs (which must be done with device disconnected), the driver does not seem to ever bind correctly to the device because the software that uses the dongle does not recognise it. I have successfully bound a PCI graphics adapter to the VM, so in principle PCI passthrough works, bit in the case of the USB PCI card there seems to be no way to pass the device to a VM. Expected result: PCI passthrough should be available to all types of PCI devices and instructions should be available from qemu or kvm documentation even though it involves different parts of the OS (such as making use of /etc/modprobe/vfio.conf, /etc/unbindpci etc) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-24-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=087ca1e6-4fd0-4a4b-a323-8b8ce733b3c7 InstallationDate: Installed on 2018-03-14 (124 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=0286b7bc-6ce2-494c-89aa-6c4402876bad ro ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-generic N/A linux-firmware
[Kernel-packages] [Bug 1781891] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1781891/+attachment/5164575/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781891 Title: PCI USB card passthrough does not work any more Status in linux package in Ubuntu: Confirmed Bug description: System information: Ubuntu 18.04 LTS (server edition) with kernel 4.15.0-24-generic x86_64 Upgraded from Ubuntu server 17.10 Software: qemu-kvm: Installed: 1:2.11+dfsg-1ubuntu7.4 Candidate: 1:2.11+dfsg-1ubuntu7.4 Version table: *** 1:2.11+dfsg-1ubuntu7.4 500 500 http://za.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:2.11+dfsg-1ubuntu7.3 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1:2.11+dfsg-1ubuntu7 500 500 http://za.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Hardware: Motherboard: X370 Killer SLI CPU: AMD Ryzen 7 1800X PCI device: 27:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (rev 01) IOMMU Group 15 27:00.0 USB controller [0c03]: VIA Technologies, Inc. VL805 USB 3.0 Host Controller [1106:3483] (rev 01) USB controller of PCI card: Bus 003 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Loaded device drivers: Before upgrading to Ubuntu 18.04, this PCI device was added to pci-stub.ids which allowed the device to be passed to a Windows 10 VM. In turn, all USB devices connected to this card worked in the VM and drivers could successfully be installed. Since the upgrade from Ubuntu 17.10 to Ubuntu 18.04, I have tried several approaches to have this device not bound to the xhci driver but all in vain. (In every test I did, I always performed update- initramfs -u as well as update-grub) pci-stub.ids does not stop xhci from grabbing device. So passing PCI card to VM does not work Adding the device ID to /etc/modprobe.d/vfio.conf (options) does seem to load the connect the vfio driver to it, but xhci still binds to it as well, so passing PCI device to VM does not work. Adding ":27:00.0,xhci" to /etc/unbindpci also did not work. By adding the USB controller to the VM, USB devices connected to it does seem to be USB devices on the VM, but some of the drivers does not load correctly in Windows 10. For example, I need to install a device driver for a ROCKEY4 USB dongle and even though the driver installs (which must be done with device disconnected), the driver does not seem to ever bind correctly to the device because the software that uses the dongle does not recognise it. I have successfully bound a PCI graphics adapter to the VM, so in principle PCI passthrough works, bit in the case of the USB PCI card there seems to be no way to pass the device to a VM. Expected result: PCI passthrough should be available to all types of PCI devices and instructions should be available from qemu or kvm documentation even though it involves different parts of the OS (such as making use of /etc/modprobe/vfio.conf, /etc/unbindpci etc) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-24-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=087ca1e6-4fd0-4a4b-a323-8b8ce733b3c7 InstallationDate: Installed on 2018-03-14 (124 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=0286b7bc-6ce2-494c-89aa-6c4402876bad ro ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-generic N/A
[Kernel-packages] [Bug 1777857] Re: [LTCTest][OPAL][OP920] INFO: rcu_sched self-detected stall on CPU
*** This bug is a duplicate of bug 1773964 *** https://bugs.launchpad.net/bugs/1773964 ** This bug has been marked a duplicate of bug 1773964 IPL: ppc64_cpu --frequency hang with INFO: rcu_sched detected stalls on CPUs/tasks on w34 and wsbmc016 with 920.1714.20170330n -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777857 Title: [LTCTest][OPAL][OP920] INFO: rcu_sched self-detected stall on CPU Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: == SRU Justification == IBM is seeing kernel traces during testing. This is due to a missing backport of some kernel fixes in the RTC driver, which is commit 682e6b4da5cb. Commit 682e6b4da5cb was also cc'd to upstream stable, but it has not landed in Bionic as of yet. It is also a fix to upstream commit 628daa8d5abf. Commit 34dd25de9fe3 is also needed as a prereq to define OPAL_BUSY_DELAY_MS. == Fixes == 34dd25de9fe3 ("powerpc/powernv: define a standard delay for OPAL_BUSY type retry loops") 682e6b4da5cb ("rtc: opal: Fix OPAL RTC driver OPAL_BUSY loops") == Regression Potential == Low. Limited to powerpc. Fixes a current regression. == Test Case == A test kernel was built with these patches and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. == Comment: #0 - PAVAMAN SUBRAMANIYAM - 2018-05-23 01:15:30 == Install a P9 Open Power Hardware with the latest OP920 Firmware images provided in the following link: http://pfd.austin.ibm.com/releasenotes/openpower9/OP920/OP920_1808A/OP920_1808N_RelNote_Main.html root@witherspoon:~# cat /etc/os-release ID="openbmc-phosphor" NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)" VERSION="ibm-v2.1" VERSION_ID="ibm-v2.1-438-g0030304-r12-0-g5ee4fb0" PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) ibm-v2.1" BUILD_ID="ibm-v2.1-438-g0030304-r12" root@witherspoon:~# cat /var/lib/phosphor-software-manager/pnor/ro/VERSION IBM-witherspoon-ibm-OP9-v2.0-2.14 op-build-v2.0-11-gb248194-dirty buildroot-2018.02.1-6-ga8d1126 skiboot-v6.0.1 hostboot-8ab6717d-pfc036fa occ-77bb5e6 linux-4.16.8-openpower2-pb532d68 petitboot-v1.7.1-p1188545 machine-xml-7cd20a6 hostboot-binaries-276bb70 capp-ucode-p9-dd2-v4 sbe-a596975 hcode-b8173e8 Seeing the following messages in the dmesg logs. [ 16.377405] ipmi_si: Unable to find any System Interface(s) [ 17.384118] nf_conntrack version 0.5.0 (65536 buckets, 262144 max) [ 1372.711730] INFO: rcu_sched self-detected stall on CPU [ 1372.711787] 32-: (5249 ticks this GP) idle=182/141/0 softirq=1093/1093 fqs=2623 [ 1372.711863] (t=5250 jiffies g=22430 c=22429 q=953) [ 1372.711921] Task dump for CPU 32: [ 1372.711922] kworker/32:1R running task0 1123 2 0x0804 [ 1372.711930] Workqueue: events rtc_timer_do_work [ 1372.711931] Call Trace: [ 1372.711934] [c03fd2b97350] [c014a8f8] sched_show_task.part.16+0xd8/0x110 (unreliable) [ 1372.711939] [c03fd2b973c0] [c01aa8bc] rcu_dump_cpu_stacks+0xd4/0x138 [ 1372.711942] [c03fd2b97410] [c01a9988] rcu_check_callbacks+0x8e8/0xb40 [ 1372.711945] [c03fd2b97540] [c01b7c28] update_process_times+0x48/0x90 [ 1372.711948] [c03fd2b97570] [c01cf974] tick_sched_handle.isra.5+0x34/0xd0 [ 1372.711950] [c03fd2b975a0] [c01cfa70] tick_sched_timer+0x60/0xe0 [ 1372.711953] [c03fd2b975e0] [c01b87d4] __hrtimer_run_queues+0x144/0x370 [ 1372.711956] [c03fd2b97660] [c01b972c] hrtimer_interrupt+0xfc/0x350 [ 1372.711959] [c03fd2b97730] [c00249f0] __timer_interrupt+0x90/0x260 [ 1372.711962] [c03fd2b97780] [c0024e08] timer_interrupt+0x98/0xe0 [ 1372.711965] [c03fd2b977b0] [c0009054] decrementer_common+0x114/0x120 [ 1372.711970] --- interrupt: 901 at opal_get_rtc_time+0x98/0x110 LR = opal_return+0x14/0x48 [ 1372.711972] [c03fd2b97aa0] [c0a457b8] opal_get_rtc_time+0x98/0x110 (unreliable) [ 1372.711975] [c03fd2b97ae0] [c0a3f98c] __rtc_read_time+0x7c/0x180 [ 1372.711977] [c03fd2b97b60] [c0a41738] rtc_timer_do_work+0x78/0x250 [ 1372.711980] [c03fd2b97c90] [c0134378] process_one_work+0x298/0x5a0 [ 1372.711982] [c03fd2b97d20] [c0134718] worker_thread+0x98/0x630 [ 1372.711985] [c03fd2b97dc0] [c013d348] kthread+0x1a8/0x1b0 [ 1372.711988] [c03fd2b97e30] [c000b658] ret_from_kernel_thread+0x5c/0x84 == Comment: #1 - PAVAMAN SUBRAMANIYAM - 201
[Kernel-packages] [Bug 1781891] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1781891/+attachment/5164574/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781891 Title: PCI USB card passthrough does not work any more Status in linux package in Ubuntu: Confirmed Bug description: System information: Ubuntu 18.04 LTS (server edition) with kernel 4.15.0-24-generic x86_64 Upgraded from Ubuntu server 17.10 Software: qemu-kvm: Installed: 1:2.11+dfsg-1ubuntu7.4 Candidate: 1:2.11+dfsg-1ubuntu7.4 Version table: *** 1:2.11+dfsg-1ubuntu7.4 500 500 http://za.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:2.11+dfsg-1ubuntu7.3 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1:2.11+dfsg-1ubuntu7 500 500 http://za.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Hardware: Motherboard: X370 Killer SLI CPU: AMD Ryzen 7 1800X PCI device: 27:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (rev 01) IOMMU Group 15 27:00.0 USB controller [0c03]: VIA Technologies, Inc. VL805 USB 3.0 Host Controller [1106:3483] (rev 01) USB controller of PCI card: Bus 003 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Loaded device drivers: Before upgrading to Ubuntu 18.04, this PCI device was added to pci-stub.ids which allowed the device to be passed to a Windows 10 VM. In turn, all USB devices connected to this card worked in the VM and drivers could successfully be installed. Since the upgrade from Ubuntu 17.10 to Ubuntu 18.04, I have tried several approaches to have this device not bound to the xhci driver but all in vain. (In every test I did, I always performed update- initramfs -u as well as update-grub) pci-stub.ids does not stop xhci from grabbing device. So passing PCI card to VM does not work Adding the device ID to /etc/modprobe.d/vfio.conf (options) does seem to load the connect the vfio driver to it, but xhci still binds to it as well, so passing PCI device to VM does not work. Adding ":27:00.0,xhci" to /etc/unbindpci also did not work. By adding the USB controller to the VM, USB devices connected to it does seem to be USB devices on the VM, but some of the drivers does not load correctly in Windows 10. For example, I need to install a device driver for a ROCKEY4 USB dongle and even though the driver installs (which must be done with device disconnected), the driver does not seem to ever bind correctly to the device because the software that uses the dongle does not recognise it. I have successfully bound a PCI graphics adapter to the VM, so in principle PCI passthrough works, bit in the case of the USB PCI card there seems to be no way to pass the device to a VM. Expected result: PCI passthrough should be available to all types of PCI devices and instructions should be available from qemu or kvm documentation even though it involves different parts of the OS (such as making use of /etc/modprobe/vfio.conf, /etc/unbindpci etc) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-24-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=087ca1e6-4fd0-4a4b-a323-8b8ce733b3c7 InstallationDate: Installed on 2018-03-14 (124 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=0286b7bc-6ce2-494c-89aa-6c4402876bad ro ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-generic N/A linux
[Kernel-packages] [Bug 1777716] Re: [SRU Bionic][Cosmic] kernel panic in ipmi_ssif at msg_done_handler
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Critical Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Triaged ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/116 Title: [SRU Bionic][Cosmic] kernel panic in ipmi_ssif at msg_done_handler Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Triaged Bug description: [Impact] When you boot bionic with Boot with i2c and ipmi_ssif enabled on Cavium ThunderX2 systems with a faulty BMC that does not return any data, and the code is trying to print the value if data[2], we get a kernel panic. [ 484.728410] Unable to handle kernel NULL pointer dereference at virtual address 0002 [ 484.736496] pgd = 094a2000 [ 484.739885] [0002] *pgd=0047fcffe003, *pud=0047fcffd003, *pmd= [ 484.748158] Internal error: Oops: 9605 [#1] SMP [...] [ 485.101451] Call trace: [...] [ 485.188473] [] msg_done_handler+0x668/0x700 [ipmi_ssif] [ 485.195249] [] ipmi_ssif_thread+0x110/0x128 [ipmi_ssif] [ 485.202038] [] kthread+0x108/0x138 [ 485.206994] [] ret_from_fork+0x10/0x30 [ 485.212294] Code: aa1903e1 aa1803e0 b900227f 95fef6a5 (39400aa3) [Test] - System with faulty BMC - Boot with i2c and ipmi_ssif enabled. [Fix] Fixed upstream with: commit f002612b9d86613bc6fde0a444e0095225f6053e Author: Kamlakant Patel Date: Tue Mar 13 16:32:27 2018 +0530 ipmi_ssif: Fix kernel panic at msg_done_handler [Regression Potential] ipmi_ssif is only loaded on ARM64 systems, this issue is observed only on Cavium ThunderX2 systems with a faulty BMC. The fix does not impact other architectures or vendor systems. Regression potential is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/116/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781891] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1781891/+attachment/5164573/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781891 Title: PCI USB card passthrough does not work any more Status in linux package in Ubuntu: Confirmed Bug description: System information: Ubuntu 18.04 LTS (server edition) with kernel 4.15.0-24-generic x86_64 Upgraded from Ubuntu server 17.10 Software: qemu-kvm: Installed: 1:2.11+dfsg-1ubuntu7.4 Candidate: 1:2.11+dfsg-1ubuntu7.4 Version table: *** 1:2.11+dfsg-1ubuntu7.4 500 500 http://za.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:2.11+dfsg-1ubuntu7.3 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1:2.11+dfsg-1ubuntu7 500 500 http://za.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Hardware: Motherboard: X370 Killer SLI CPU: AMD Ryzen 7 1800X PCI device: 27:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (rev 01) IOMMU Group 15 27:00.0 USB controller [0c03]: VIA Technologies, Inc. VL805 USB 3.0 Host Controller [1106:3483] (rev 01) USB controller of PCI card: Bus 003 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Loaded device drivers: Before upgrading to Ubuntu 18.04, this PCI device was added to pci-stub.ids which allowed the device to be passed to a Windows 10 VM. In turn, all USB devices connected to this card worked in the VM and drivers could successfully be installed. Since the upgrade from Ubuntu 17.10 to Ubuntu 18.04, I have tried several approaches to have this device not bound to the xhci driver but all in vain. (In every test I did, I always performed update- initramfs -u as well as update-grub) pci-stub.ids does not stop xhci from grabbing device. So passing PCI card to VM does not work Adding the device ID to /etc/modprobe.d/vfio.conf (options) does seem to load the connect the vfio driver to it, but xhci still binds to it as well, so passing PCI device to VM does not work. Adding ":27:00.0,xhci" to /etc/unbindpci also did not work. By adding the USB controller to the VM, USB devices connected to it does seem to be USB devices on the VM, but some of the drivers does not load correctly in Windows 10. For example, I need to install a device driver for a ROCKEY4 USB dongle and even though the driver installs (which must be done with device disconnected), the driver does not seem to ever bind correctly to the device because the software that uses the dongle does not recognise it. I have successfully bound a PCI graphics adapter to the VM, so in principle PCI passthrough works, bit in the case of the USB PCI card there seems to be no way to pass the device to a VM. Expected result: PCI passthrough should be available to all types of PCI devices and instructions should be available from qemu or kvm documentation even though it involves different parts of the OS (such as making use of /etc/modprobe/vfio.conf, /etc/unbindpci etc) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-24-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=087ca1e6-4fd0-4a4b-a323-8b8ce733b3c7 InstallationDate: Installed on 2018-03-14 (124 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=0286b7bc-6ce2-494c-89aa-6c4402876bad ro ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-generic
[Kernel-packages] [Bug 1781891] PciMultimedia.txt
apport information ** Attachment added: "PciMultimedia.txt" https://bugs.launchpad.net/bugs/1781891/+attachment/5164571/+files/PciMultimedia.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781891 Title: PCI USB card passthrough does not work any more Status in linux package in Ubuntu: Confirmed Bug description: System information: Ubuntu 18.04 LTS (server edition) with kernel 4.15.0-24-generic x86_64 Upgraded from Ubuntu server 17.10 Software: qemu-kvm: Installed: 1:2.11+dfsg-1ubuntu7.4 Candidate: 1:2.11+dfsg-1ubuntu7.4 Version table: *** 1:2.11+dfsg-1ubuntu7.4 500 500 http://za.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:2.11+dfsg-1ubuntu7.3 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1:2.11+dfsg-1ubuntu7 500 500 http://za.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Hardware: Motherboard: X370 Killer SLI CPU: AMD Ryzen 7 1800X PCI device: 27:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (rev 01) IOMMU Group 15 27:00.0 USB controller [0c03]: VIA Technologies, Inc. VL805 USB 3.0 Host Controller [1106:3483] (rev 01) USB controller of PCI card: Bus 003 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Loaded device drivers: Before upgrading to Ubuntu 18.04, this PCI device was added to pci-stub.ids which allowed the device to be passed to a Windows 10 VM. In turn, all USB devices connected to this card worked in the VM and drivers could successfully be installed. Since the upgrade from Ubuntu 17.10 to Ubuntu 18.04, I have tried several approaches to have this device not bound to the xhci driver but all in vain. (In every test I did, I always performed update- initramfs -u as well as update-grub) pci-stub.ids does not stop xhci from grabbing device. So passing PCI card to VM does not work Adding the device ID to /etc/modprobe.d/vfio.conf (options) does seem to load the connect the vfio driver to it, but xhci still binds to it as well, so passing PCI device to VM does not work. Adding ":27:00.0,xhci" to /etc/unbindpci also did not work. By adding the USB controller to the VM, USB devices connected to it does seem to be USB devices on the VM, but some of the drivers does not load correctly in Windows 10. For example, I need to install a device driver for a ROCKEY4 USB dongle and even though the driver installs (which must be done with device disconnected), the driver does not seem to ever bind correctly to the device because the software that uses the dongle does not recognise it. I have successfully bound a PCI graphics adapter to the VM, so in principle PCI passthrough works, bit in the case of the USB PCI card there seems to be no way to pass the device to a VM. Expected result: PCI passthrough should be available to all types of PCI devices and instructions should be available from qemu or kvm documentation even though it involves different parts of the OS (such as making use of /etc/modprobe/vfio.conf, /etc/unbindpci etc) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-24-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=087ca1e6-4fd0-4a4b-a323-8b8ce733b3c7 InstallationDate: Installed on 2018-03-14 (124 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=0286b7bc-6ce2-494c-89aa-6c4402876bad ro ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-generic N/A l
[Kernel-packages] [Bug 1781891] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1781891/+attachment/5164576/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781891 Title: PCI USB card passthrough does not work any more Status in linux package in Ubuntu: Confirmed Bug description: System information: Ubuntu 18.04 LTS (server edition) with kernel 4.15.0-24-generic x86_64 Upgraded from Ubuntu server 17.10 Software: qemu-kvm: Installed: 1:2.11+dfsg-1ubuntu7.4 Candidate: 1:2.11+dfsg-1ubuntu7.4 Version table: *** 1:2.11+dfsg-1ubuntu7.4 500 500 http://za.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:2.11+dfsg-1ubuntu7.3 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1:2.11+dfsg-1ubuntu7 500 500 http://za.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Hardware: Motherboard: X370 Killer SLI CPU: AMD Ryzen 7 1800X PCI device: 27:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (rev 01) IOMMU Group 15 27:00.0 USB controller [0c03]: VIA Technologies, Inc. VL805 USB 3.0 Host Controller [1106:3483] (rev 01) USB controller of PCI card: Bus 003 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Loaded device drivers: Before upgrading to Ubuntu 18.04, this PCI device was added to pci-stub.ids which allowed the device to be passed to a Windows 10 VM. In turn, all USB devices connected to this card worked in the VM and drivers could successfully be installed. Since the upgrade from Ubuntu 17.10 to Ubuntu 18.04, I have tried several approaches to have this device not bound to the xhci driver but all in vain. (In every test I did, I always performed update- initramfs -u as well as update-grub) pci-stub.ids does not stop xhci from grabbing device. So passing PCI card to VM does not work Adding the device ID to /etc/modprobe.d/vfio.conf (options) does seem to load the connect the vfio driver to it, but xhci still binds to it as well, so passing PCI device to VM does not work. Adding ":27:00.0,xhci" to /etc/unbindpci also did not work. By adding the USB controller to the VM, USB devices connected to it does seem to be USB devices on the VM, but some of the drivers does not load correctly in Windows 10. For example, I need to install a device driver for a ROCKEY4 USB dongle and even though the driver installs (which must be done with device disconnected), the driver does not seem to ever bind correctly to the device because the software that uses the dongle does not recognise it. I have successfully bound a PCI graphics adapter to the VM, so in principle PCI passthrough works, bit in the case of the USB PCI card there seems to be no way to pass the device to a VM. Expected result: PCI passthrough should be available to all types of PCI devices and instructions should be available from qemu or kvm documentation even though it involves different parts of the OS (such as making use of /etc/modprobe/vfio.conf, /etc/unbindpci etc) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-24-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=087ca1e6-4fd0-4a4b-a323-8b8ce733b3c7 InstallationDate: Installed on 2018-03-14 (124 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=0286b7bc-6ce2-494c-89aa-6c4402876bad ro ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-generic N/A linux
[Kernel-packages] [Bug 1781891] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1781891/+attachment/5164572/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781891 Title: PCI USB card passthrough does not work any more Status in linux package in Ubuntu: Confirmed Bug description: System information: Ubuntu 18.04 LTS (server edition) with kernel 4.15.0-24-generic x86_64 Upgraded from Ubuntu server 17.10 Software: qemu-kvm: Installed: 1:2.11+dfsg-1ubuntu7.4 Candidate: 1:2.11+dfsg-1ubuntu7.4 Version table: *** 1:2.11+dfsg-1ubuntu7.4 500 500 http://za.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:2.11+dfsg-1ubuntu7.3 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1:2.11+dfsg-1ubuntu7 500 500 http://za.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Hardware: Motherboard: X370 Killer SLI CPU: AMD Ryzen 7 1800X PCI device: 27:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (rev 01) IOMMU Group 15 27:00.0 USB controller [0c03]: VIA Technologies, Inc. VL805 USB 3.0 Host Controller [1106:3483] (rev 01) USB controller of PCI card: Bus 003 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Loaded device drivers: Before upgrading to Ubuntu 18.04, this PCI device was added to pci-stub.ids which allowed the device to be passed to a Windows 10 VM. In turn, all USB devices connected to this card worked in the VM and drivers could successfully be installed. Since the upgrade from Ubuntu 17.10 to Ubuntu 18.04, I have tried several approaches to have this device not bound to the xhci driver but all in vain. (In every test I did, I always performed update- initramfs -u as well as update-grub) pci-stub.ids does not stop xhci from grabbing device. So passing PCI card to VM does not work Adding the device ID to /etc/modprobe.d/vfio.conf (options) does seem to load the connect the vfio driver to it, but xhci still binds to it as well, so passing PCI device to VM does not work. Adding ":27:00.0,xhci" to /etc/unbindpci also did not work. By adding the USB controller to the VM, USB devices connected to it does seem to be USB devices on the VM, but some of the drivers does not load correctly in Windows 10. For example, I need to install a device driver for a ROCKEY4 USB dongle and even though the driver installs (which must be done with device disconnected), the driver does not seem to ever bind correctly to the device because the software that uses the dongle does not recognise it. I have successfully bound a PCI graphics adapter to the VM, so in principle PCI passthrough works, bit in the case of the USB PCI card there seems to be no way to pass the device to a VM. Expected result: PCI passthrough should be available to all types of PCI devices and instructions should be available from qemu or kvm documentation even though it involves different parts of the OS (such as making use of /etc/modprobe/vfio.conf, /etc/unbindpci etc) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-24-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=087ca1e6-4fd0-4a4b-a323-8b8ce733b3c7 InstallationDate: Installed on 2018-03-14 (124 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=0286b7bc-6ce2-494c-89aa-6c4402876bad ro ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-generic N/A linux
[Kernel-packages] [Bug 1781891] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1781891/+attachment/5164577/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781891 Title: PCI USB card passthrough does not work any more Status in linux package in Ubuntu: Confirmed Bug description: System information: Ubuntu 18.04 LTS (server edition) with kernel 4.15.0-24-generic x86_64 Upgraded from Ubuntu server 17.10 Software: qemu-kvm: Installed: 1:2.11+dfsg-1ubuntu7.4 Candidate: 1:2.11+dfsg-1ubuntu7.4 Version table: *** 1:2.11+dfsg-1ubuntu7.4 500 500 http://za.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:2.11+dfsg-1ubuntu7.3 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1:2.11+dfsg-1ubuntu7 500 500 http://za.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Hardware: Motherboard: X370 Killer SLI CPU: AMD Ryzen 7 1800X PCI device: 27:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (rev 01) IOMMU Group 15 27:00.0 USB controller [0c03]: VIA Technologies, Inc. VL805 USB 3.0 Host Controller [1106:3483] (rev 01) USB controller of PCI card: Bus 003 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Loaded device drivers: Before upgrading to Ubuntu 18.04, this PCI device was added to pci-stub.ids which allowed the device to be passed to a Windows 10 VM. In turn, all USB devices connected to this card worked in the VM and drivers could successfully be installed. Since the upgrade from Ubuntu 17.10 to Ubuntu 18.04, I have tried several approaches to have this device not bound to the xhci driver but all in vain. (In every test I did, I always performed update- initramfs -u as well as update-grub) pci-stub.ids does not stop xhci from grabbing device. So passing PCI card to VM does not work Adding the device ID to /etc/modprobe.d/vfio.conf (options) does seem to load the connect the vfio driver to it, but xhci still binds to it as well, so passing PCI device to VM does not work. Adding ":27:00.0,xhci" to /etc/unbindpci also did not work. By adding the USB controller to the VM, USB devices connected to it does seem to be USB devices on the VM, but some of the drivers does not load correctly in Windows 10. For example, I need to install a device driver for a ROCKEY4 USB dongle and even though the driver installs (which must be done with device disconnected), the driver does not seem to ever bind correctly to the device because the software that uses the dongle does not recognise it. I have successfully bound a PCI graphics adapter to the VM, so in principle PCI passthrough works, bit in the case of the USB PCI card there seems to be no way to pass the device to a VM. Expected result: PCI passthrough should be available to all types of PCI devices and instructions should be available from qemu or kvm documentation even though it involves different parts of the OS (such as making use of /etc/modprobe/vfio.conf, /etc/unbindpci etc) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-24-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=087ca1e6-4fd0-4a4b-a323-8b8ce733b3c7 InstallationDate: Installed on 2018-03-14 (124 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=0286b7bc-6ce2-494c-89aa-6c4402876bad ro ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-generic N/A linux-firmware
[Kernel-packages] [Bug 1782173] Re: linux: 4.15.0-29.31 -proposed tracker
** Summary changed: - linux: -proposed tracker + linux: 4.15.0-29.31 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader (smb) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader (smb) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader (smb) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782173 Title: linux: 4.15.0-29.31 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1782182 (linux-hwe-edge), bug 1782183 (linux-hwe), bug 1782184 (linux-gcp), bug 1782185 (linux-azure-edge), bug 1782186 (linux-azure) derivatives: bug 1782174 (linux-gcp), bug 1782175 (linux-raspi2), bug 1782176 (linux-aws), bug 1782178 (linux-azure), bug 1782180 (linux-kvm), bug 1782181 (linux-oem) To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1782173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782116] Re: snapcraft.yaml: missing ubuntu-retpoline-extract-one script breaks the build
** Description changed: Impact: - On a generic amd64 environment, check out the Xenia/generic or - Bionic/generic tree, cd into it and execute snapcraft - it should build - the corresponding kernel snap. + The Ubuntu kernel source code depends on the presence of the + retpoline-extract-one file in the script directory during build (see + scripts/Makefile.build::cmd_ubuntu_retpoline) - such a file lives in the debian directory and is copied to scripts during the 'debian/rules clean' phase. - linux $ snapcraft + Snapcraft is oblivious to the debian details, and the clean target is + never invoked, breaking the normal kernel build (make defconfig; make + ...). + + Check out the Xenia/generic or Bionic/generic tree, cd into it and + execute: make defconfig && make. + ... HOSTCC scripts/mod/mk_elfconfig /bin/bash: ./scripts/ubuntu-retpoline-extract-one: No such file or directory scripts/Makefile.build:332: recipe for target 'scripts/mod/empty.o' failed make[2]: *** [scripts/mod/empty.o] Error 127 make[2]: *** Waiting for unfinished jobs HOSTLD arch/x86/tools/relocs HOSTCC scripts/selinux/genheaders/genheaders HOSTCC scripts/selinux/mdp/mdp scripts/Makefile.build:606: recipe for target 'scripts/mod' failed make[1]: *** [scripts/mod] Error 2 make[1]: *** Waiting for unfinished jobs CC arch/x86/purgatory/purgatory.o Makefile:589: recipe for target 'scripts' failed make: *** [scripts] Error 2 make: *** Waiting for unfinished jobs AS arch/x86/purgatory/stack.o /bin/bash: ./scripts/ubuntu-retpoline-extract-one: No such file or directory scripts/Makefile.build:332: recipe for target 'arch/x86/purgatory/purgatory.o' failed make[1]: *** [arch/x86/purgatory/purgatory.o] Error 127 make[1]: *** Waiting for unfinished jobs AS arch/x86/purgatory/setup-x86_64.o /bin/bash: ./scripts/ubuntu-retpoline-extract-one: No such file or directory scripts/Makefile.build:435: recipe for target 'arch/x86/purgatory/stack.o' failed make[1]: *** [arch/x86/purgatory/stack.o] Error 127 /bin/bash: ./scripts/ubuntu-retpoline-extract-one: No such file or directory scripts/Makefile.build:435: recipe for target 'arch/x86/purgatory/setup-x86_64.o' failed make[1]: *** [arch/x86/purgatory/setup-x86_64.o] Error 127 arch/x86/Makefile:260: recipe for target 'archprepare' failed make: *** [archprepare] Error 2 Failed to run 'make -j4 bzImage modules' for 'kernel': Exited with code 2. Verify that the part is using the correct parameters and try again. Fix: - The retpoline-extract-one should be copied to the parts/build/script directory, apply the attached patch to let snapcraft do it before starting the kernel build + + To workaround that, before starting the build, make snapcraft do the + copy and fix the build. Regression risk: - None, since we are only patching the snapcraft.yaml file (and it didn't build in the first place). - --- + The patch only modifies snapcraft.yaml, so none. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782116 Title: snapcraft.yaml: missing ubuntu-retpoline-extract-one script breaks the build Status in linux package in Ubuntu: Incomplete Bug description: Impact: The Ubuntu kernel source code depends on the presence of the retpoline-extract-one file in the script directory during build (see scripts/Makefile.build::cmd_ubuntu_retpoline) - such a file lives in the debian directory and is copied to scripts during the 'debian/rules clean' phase. Snapcraft is oblivious to the debian details, and the clean target is never invoked, breaking the normal kernel build (make defconfig; make ...). Check out the Xenia/generic or Bionic/generic tree, cd into it and execute: make defconfig && make or snapcraft. ... HOSTCC scripts/mod/mk_elfconfig /bin/bash: ./scripts/ubuntu-retpoline-extract-one: No such file or directory scripts/Makefile.build:332: recipe for target 'scripts/mod/empty.o' failed make[2]: *** [scripts/mod/empty.o] Error 127 make[2]: *** Waiting for unfinished jobs HOSTLD arch/x86/tools/relocs HOSTCC scripts/selinux/genheaders/genheaders HOSTCC scripts/selinux/mdp/mdp scripts/Makefile.build:606: recipe for target 'scripts/mod' failed make[1]: *** [scripts/mod] Error 2 make[1]: *** Waiting for unfinished jobs CC arch/x86/purgatory/purgatory.o Makefile:589: recipe for target 'scripts' failed make: *** [scripts] Error 2 make: *** Waiting for unfinished jobs AS arch/x86/purgatory/stack.o /bin/bash: ./scripts/ubuntu-retpoline-extract-one: No such file or directory scripts/Makefile.build:332: recipe for target 'arch/x86/purgatory/purgatory.o' failed make[1]: *** [arch/x86/purgatory/purgatory.o] Error 127 make[1]: *** Waiting for unfinished jobs AS arch/x86/purga
[Kernel-packages] [Bug 1781836] Re: linux: 4.15.0-29.31 -proposed tracker
*** This bug is a duplicate of bug 1782173 *** https://bugs.launchpad.net/bugs/1782173 ** This bug is no longer a duplicate of bug 1781433 linux: 4.15.0-28.30 -proposed tracker ** This bug has been marked a duplicate of bug 1782173 linux: -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781836 Title: linux: 4.15.0-29.31 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1781836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781114] Re: linux: -proposed tracker
*** This bug is a duplicate of bug 1782173 *** https://bugs.launchpad.net/bugs/1782173 ** This bug is no longer a duplicate of bug 1781433 linux: 4.15.0-28.30 -proposed tracker ** This bug has been marked a duplicate of bug 1782173 linux: -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781114 Title: linux: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1781114/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781433] Re: linux: 4.15.0-28.30 -proposed tracker
*** This bug is a duplicate of bug 1782173 *** https://bugs.launchpad.net/bugs/1782173 ** This bug has been marked a duplicate of bug 1782173 linux: -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781433 Title: linux: 4.15.0-28.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1781437 (linux-hwe), bug 1781438 (linux-hwe-edge), bug 1781072 (azure), bug 1781074 (azure-edge), bug 1781115 (gcp) derivatives: bug 1781435 (linux-aws), bug 1781066 (azure), bug 1781067 (gcp), bug 1781068 (kvm), bug 1781063 (raspi2), bug 1781064 (oem) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1781433/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781115] Re: linux-gcp: 4.15.0-1013.13~16.04.1 -proposed tracker
*** This bug is a duplicate of bug 1782184 *** https://bugs.launchpad.net/bugs/1782184 ** This bug has been marked a duplicate of bug 1782184 linux-gcp: -proposed tracker -- 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/1781115 Title: linux-gcp: 4.15.0-1013.13~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1781433 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1781115/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp