[Kernel-packages] [Bug 1802021] Re: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()
Hey guys, I am not sure how to do this but can you also make a patch for Xenial, 4.15.0-generic, for linux-hwe package? We have the same problem and we can't upgrade the boxes to a newer release so this would really help us. ** Package changed: linux (Ubuntu) => linux-hwe (Ubuntu) ** Changed in: linux-hwe (Ubuntu) Status: Incomplete => Confirmed -- 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/1802021 Title: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start() Status in linux-azure package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in linux-azure source package in Bionic: In Progress Status in linux-hwe source package in Bionic: Confirmed Status in linux-azure source package in Cosmic: In Progress Status in linux-hwe source package in Cosmic: Confirmed Bug description: We had a customer seeing traces like the following: tack trace from kern.log: 2018-10-10T04:43:08.542464+00:00 hbp2ann-2 kernel: INFO: task kworker/u16:0:16678 blocked for more than 120 seconds. 2018-10-10T04:43:08.542503+00:00 hbp2ann-2 kernel: Not tainted 4.15.0-1023-azure #24~16.04.1-Ubuntu 2018-10-10T04:43:08.542513+00:00 hbp2ann-2 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. 2018-10-10T04:43:08.547366+00:00 hbp2ann-2 kernel: kworker/u16:0 D 0 16678 2 0x8000 2018-10-10T04:43:08.547386+00:00 hbp2ann-2 kernel: Workqueue: events_unbound fsnotify_mark_destroy_workfn 2018-10-10T04:43:08.547395+00:00 hbp2ann-2 kernel: Call Trace: 2018-10-10T04:43:08.547413+00:00 hbp2ann-2 kernel: __schedule+0x3d6/0x8b0 2018-10-10T04:43:08.547422+00:00 hbp2ann-2 kernel: ? check_preempt_wakeup+0xfb/0x240 2018-10-10T04:43:08.547431+00:00 hbp2ann-2 kernel: ? sched_clock_local+0x17/0x90 2018-10-10T04:43:08.547440+00:00 hbp2ann-2 kernel: schedule+0x36/0x80 2018-10-10T04:43:08.547448+00:00 hbp2ann-2 kernel: schedule_timeout+0x1db/0x370 2018-10-10T04:43:08.547458+00:00 hbp2ann-2 kernel: ? __enqueue_entity+0x5c/0x60 2018-10-10T04:43:08.547467+00:00 hbp2ann-2 kernel: ? enqueue_entity+0x112/0x670 2018-10-10T04:43:08.547477+00:00 hbp2ann-2 kernel: wait_for_completion+0xb4/0x140 2018-10-10T04:43:08.547486+00:00 hbp2ann-2 kernel: ? wake_up_q+0x70/0x70 2018-10-10T04:43:08.547510+00:00 hbp2ann-2 kernel: __synchronize_srcu.part.13+0x85/0xb0 2018-10-10T04:43:08.547535+00:00 hbp2ann-2 kernel: ? trace_raw_output_rcu_utilization+0x50/0x50 2018-10-10T04:43:08.547560+00:00 hbp2ann-2 kernel: synchronize_srcu+0xd3/0xe0 2018-10-10T04:43:08.547594+00:00 hbp2ann-2 kernel: ? synchronize_srcu+0xd3/0xe0 2018-10-10T04:43:08.547604+00:00 hbp2ann-2 kernel: fsnotify_mark_destroy_workfn+0x7c/0xe0 2018-10-10T04:43:08.547612+00:00 hbp2ann-2 kernel: process_one_work+0x14d/0x410 2018-10-10T04:43:08.547620+00:00 hbp2ann-2 kernel: worker_thread+0x4b/0x460 2018-10-10T04:43:08.547628+00:00 hbp2ann-2 kernel: kthread+0x105/0x140 2018-10-10T04:43:08.547637+00:00 hbp2ann-2 kernel: ? process_one_work+0x410/0x410 2018-10-10T04:43:08.547645+00:00 hbp2ann-2 kernel: ? kthread_destroy_worker+0x50/0x50 2018-10-10T04:43:08.547654+00:00 hbp2ann-2 kernel: ? do_syscall_64+0x73/0x130 2018-10-10T04:43:08.547677+00:00 hbp2ann-2 kernel: ? SyS_exit_group+0x14/0x20 2018-10-10T04:43:08.547685+00:00 hbp2ann-2 kernel: ret_from_fork+0x35/0x40 Error Code: INFO: task kworker/u16:0:16678 blocked for more than 120 seconds. We are seeing more issue with fsnotify related callbacks. These are not a soft/hard lockup but seem to significantly degrade the responsiveness of systemd (and from there everything else). The following upstream commit may fix this issue, but it is in Paul's RCU tree and not in linux-next or upstream yet: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux- rcu.git/commit/?h=dev=1a05c0cd2fee234a10362cc8f66057557cbb291f srcu: Lock srcu_data structure in srcu_gp_start() The srcu_gp_start() function is called with the srcu_struct structure's ->lock held, but not with the srcu_data structure's ->lock. This is problematic because this function accesses and updates the srcu_data structure's ->srcu_cblist, which is protected by that lock. Failing to hold this lock can result in corruption of the SRCU callback lists, which in turn can result in arbitrarily bad results. This commit therefore makes srcu_gp_start() acquire the srcu_data structure's ->lock across the calls to rcu_segcblist_advance() and rcu_segcblist_accelerate(), thus preventing this corruption. Please investigate this issue and evaluate the proposed fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1802021/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1802021] Re: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()
Can't run the logs collection tool since the system is stuck in D state and times out. (Also the tool is not installed on the systems). We just need this fix back-ported on 4.15.0-generic for Xenial on linux-hwe package (we don't use linux-azure) ** Changed in: linux-hwe (Ubuntu Cosmic) Status: Incomplete => Confirmed -- 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/1802021 Title: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start() Status in linux-azure package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in linux-azure source package in Bionic: In Progress Status in linux-hwe source package in Bionic: Confirmed Status in linux-azure source package in Cosmic: In Progress Status in linux-hwe source package in Cosmic: Confirmed Bug description: We had a customer seeing traces like the following: tack trace from kern.log: 2018-10-10T04:43:08.542464+00:00 hbp2ann-2 kernel: INFO: task kworker/u16:0:16678 blocked for more than 120 seconds. 2018-10-10T04:43:08.542503+00:00 hbp2ann-2 kernel: Not tainted 4.15.0-1023-azure #24~16.04.1-Ubuntu 2018-10-10T04:43:08.542513+00:00 hbp2ann-2 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. 2018-10-10T04:43:08.547366+00:00 hbp2ann-2 kernel: kworker/u16:0 D 0 16678 2 0x8000 2018-10-10T04:43:08.547386+00:00 hbp2ann-2 kernel: Workqueue: events_unbound fsnotify_mark_destroy_workfn 2018-10-10T04:43:08.547395+00:00 hbp2ann-2 kernel: Call Trace: 2018-10-10T04:43:08.547413+00:00 hbp2ann-2 kernel: __schedule+0x3d6/0x8b0 2018-10-10T04:43:08.547422+00:00 hbp2ann-2 kernel: ? check_preempt_wakeup+0xfb/0x240 2018-10-10T04:43:08.547431+00:00 hbp2ann-2 kernel: ? sched_clock_local+0x17/0x90 2018-10-10T04:43:08.547440+00:00 hbp2ann-2 kernel: schedule+0x36/0x80 2018-10-10T04:43:08.547448+00:00 hbp2ann-2 kernel: schedule_timeout+0x1db/0x370 2018-10-10T04:43:08.547458+00:00 hbp2ann-2 kernel: ? __enqueue_entity+0x5c/0x60 2018-10-10T04:43:08.547467+00:00 hbp2ann-2 kernel: ? enqueue_entity+0x112/0x670 2018-10-10T04:43:08.547477+00:00 hbp2ann-2 kernel: wait_for_completion+0xb4/0x140 2018-10-10T04:43:08.547486+00:00 hbp2ann-2 kernel: ? wake_up_q+0x70/0x70 2018-10-10T04:43:08.547510+00:00 hbp2ann-2 kernel: __synchronize_srcu.part.13+0x85/0xb0 2018-10-10T04:43:08.547535+00:00 hbp2ann-2 kernel: ? trace_raw_output_rcu_utilization+0x50/0x50 2018-10-10T04:43:08.547560+00:00 hbp2ann-2 kernel: synchronize_srcu+0xd3/0xe0 2018-10-10T04:43:08.547594+00:00 hbp2ann-2 kernel: ? synchronize_srcu+0xd3/0xe0 2018-10-10T04:43:08.547604+00:00 hbp2ann-2 kernel: fsnotify_mark_destroy_workfn+0x7c/0xe0 2018-10-10T04:43:08.547612+00:00 hbp2ann-2 kernel: process_one_work+0x14d/0x410 2018-10-10T04:43:08.547620+00:00 hbp2ann-2 kernel: worker_thread+0x4b/0x460 2018-10-10T04:43:08.547628+00:00 hbp2ann-2 kernel: kthread+0x105/0x140 2018-10-10T04:43:08.547637+00:00 hbp2ann-2 kernel: ? process_one_work+0x410/0x410 2018-10-10T04:43:08.547645+00:00 hbp2ann-2 kernel: ? kthread_destroy_worker+0x50/0x50 2018-10-10T04:43:08.547654+00:00 hbp2ann-2 kernel: ? do_syscall_64+0x73/0x130 2018-10-10T04:43:08.547677+00:00 hbp2ann-2 kernel: ? SyS_exit_group+0x14/0x20 2018-10-10T04:43:08.547685+00:00 hbp2ann-2 kernel: ret_from_fork+0x35/0x40 Error Code: INFO: task kworker/u16:0:16678 blocked for more than 120 seconds. We are seeing more issue with fsnotify related callbacks. These are not a soft/hard lockup but seem to significantly degrade the responsiveness of systemd (and from there everything else). The following upstream commit may fix this issue, but it is in Paul's RCU tree and not in linux-next or upstream yet: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux- rcu.git/commit/?h=dev=1a05c0cd2fee234a10362cc8f66057557cbb291f srcu: Lock srcu_data structure in srcu_gp_start() The srcu_gp_start() function is called with the srcu_struct structure's ->lock held, but not with the srcu_data structure's ->lock. This is problematic because this function accesses and updates the srcu_data structure's ->srcu_cblist, which is protected by that lock. Failing to hold this lock can result in corruption of the SRCU callback lists, which in turn can result in arbitrarily bad results. This commit therefore makes srcu_gp_start() acquire the srcu_data structure's ->lock across the calls to rcu_segcblist_advance() and rcu_segcblist_accelerate(), thus preventing this corruption. Please investigate this issue and evaluate the proposed fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1802021/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1802021] Re: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()
Can't run the logs collection tool since the system is stuck in D state and times out. (Also the tool is not installed on the systems). We just need this fix back-ported on 4.15.0-generic for Xenial on linux-hwe package (we don't use linux-azure) ** Changed in: linux-hwe (Ubuntu Bionic) Status: Incomplete => Confirmed -- 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/1802021 Title: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start() Status in linux-azure package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in linux-azure source package in Bionic: In Progress Status in linux-hwe source package in Bionic: Confirmed Status in linux-azure source package in Cosmic: In Progress Status in linux-hwe source package in Cosmic: Confirmed Bug description: We had a customer seeing traces like the following: tack trace from kern.log: 2018-10-10T04:43:08.542464+00:00 hbp2ann-2 kernel: INFO: task kworker/u16:0:16678 blocked for more than 120 seconds. 2018-10-10T04:43:08.542503+00:00 hbp2ann-2 kernel: Not tainted 4.15.0-1023-azure #24~16.04.1-Ubuntu 2018-10-10T04:43:08.542513+00:00 hbp2ann-2 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. 2018-10-10T04:43:08.547366+00:00 hbp2ann-2 kernel: kworker/u16:0 D 0 16678 2 0x8000 2018-10-10T04:43:08.547386+00:00 hbp2ann-2 kernel: Workqueue: events_unbound fsnotify_mark_destroy_workfn 2018-10-10T04:43:08.547395+00:00 hbp2ann-2 kernel: Call Trace: 2018-10-10T04:43:08.547413+00:00 hbp2ann-2 kernel: __schedule+0x3d6/0x8b0 2018-10-10T04:43:08.547422+00:00 hbp2ann-2 kernel: ? check_preempt_wakeup+0xfb/0x240 2018-10-10T04:43:08.547431+00:00 hbp2ann-2 kernel: ? sched_clock_local+0x17/0x90 2018-10-10T04:43:08.547440+00:00 hbp2ann-2 kernel: schedule+0x36/0x80 2018-10-10T04:43:08.547448+00:00 hbp2ann-2 kernel: schedule_timeout+0x1db/0x370 2018-10-10T04:43:08.547458+00:00 hbp2ann-2 kernel: ? __enqueue_entity+0x5c/0x60 2018-10-10T04:43:08.547467+00:00 hbp2ann-2 kernel: ? enqueue_entity+0x112/0x670 2018-10-10T04:43:08.547477+00:00 hbp2ann-2 kernel: wait_for_completion+0xb4/0x140 2018-10-10T04:43:08.547486+00:00 hbp2ann-2 kernel: ? wake_up_q+0x70/0x70 2018-10-10T04:43:08.547510+00:00 hbp2ann-2 kernel: __synchronize_srcu.part.13+0x85/0xb0 2018-10-10T04:43:08.547535+00:00 hbp2ann-2 kernel: ? trace_raw_output_rcu_utilization+0x50/0x50 2018-10-10T04:43:08.547560+00:00 hbp2ann-2 kernel: synchronize_srcu+0xd3/0xe0 2018-10-10T04:43:08.547594+00:00 hbp2ann-2 kernel: ? synchronize_srcu+0xd3/0xe0 2018-10-10T04:43:08.547604+00:00 hbp2ann-2 kernel: fsnotify_mark_destroy_workfn+0x7c/0xe0 2018-10-10T04:43:08.547612+00:00 hbp2ann-2 kernel: process_one_work+0x14d/0x410 2018-10-10T04:43:08.547620+00:00 hbp2ann-2 kernel: worker_thread+0x4b/0x460 2018-10-10T04:43:08.547628+00:00 hbp2ann-2 kernel: kthread+0x105/0x140 2018-10-10T04:43:08.547637+00:00 hbp2ann-2 kernel: ? process_one_work+0x410/0x410 2018-10-10T04:43:08.547645+00:00 hbp2ann-2 kernel: ? kthread_destroy_worker+0x50/0x50 2018-10-10T04:43:08.547654+00:00 hbp2ann-2 kernel: ? do_syscall_64+0x73/0x130 2018-10-10T04:43:08.547677+00:00 hbp2ann-2 kernel: ? SyS_exit_group+0x14/0x20 2018-10-10T04:43:08.547685+00:00 hbp2ann-2 kernel: ret_from_fork+0x35/0x40 Error Code: INFO: task kworker/u16:0:16678 blocked for more than 120 seconds. We are seeing more issue with fsnotify related callbacks. These are not a soft/hard lockup but seem to significantly degrade the responsiveness of systemd (and from there everything else). The following upstream commit may fix this issue, but it is in Paul's RCU tree and not in linux-next or upstream yet: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux- rcu.git/commit/?h=dev=1a05c0cd2fee234a10362cc8f66057557cbb291f srcu: Lock srcu_data structure in srcu_gp_start() The srcu_gp_start() function is called with the srcu_struct structure's ->lock held, but not with the srcu_data structure's ->lock. This is problematic because this function accesses and updates the srcu_data structure's ->srcu_cblist, which is protected by that lock. Failing to hold this lock can result in corruption of the SRCU callback lists, which in turn can result in arbitrarily bad results. This commit therefore makes srcu_gp_start() acquire the srcu_data structure's ->lock across the calls to rcu_segcblist_advance() and rcu_segcblist_accelerate(), thus preventing this corruption. Please investigate this issue and evaluate the proposed fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1802021/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1804841] Re: iwlwifi Microcode SW error detected. Restarting 0x2000000.
At least for me the error stopped showing up since 11th January up to now. So whatever I did when experimenting/reporting that bug has resolved it. Unfortunately I can't clearly tell anyone else affected what exactly that would be :-/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1804841 Title: iwlwifi Microcode SW error detected. Restarting 0x200. Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Incomplete Bug description: This seems to be a return of an existing bug, in newer hardware and microcode versions. Wireless card: Intel Corporation Wireless 8265 / 8275 [8086:24fd] (rev 78) Firmware version: 34.0.1 Description:Ubuntu 18.04.1 LTS Frequent errors as soon as I connect to wifi: Microcode SW error detected. Restarting 0x200. Expected to happen: Great and stable wifi like a couple of weeks ago What happens: very slow, intermittent internet access, lots of ping loss Found a suggestion of a workaround: adding these lines to /etc/NetworkManager/NetworkManager.conf [device] wifi.scan-rand-mac-address=no These lines were already there, not added by me. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.2 [modified: lib/firmware/iwlwifi-8265-36.ucode] ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Fri Nov 23 15:23:54 2018 Dependencies: InstallationDate: Installed on 2018-09-03 (81 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804841/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799388] Comment bridged from LTC Bugzilla
--- Comment From mranw...@us.ibm.com 2019-02-04 01:35 EDT--- I ran the 4.18.0-14 kernel and on my dd2.2 hardware (two boxes) and ran some tests - I didn't see any regressions from this, looks good. -- 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/1799388 Title: TM (Hardware Transactional Memory) instructions halt application on baremetal POWER9 DD2.1 Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Cosmic: Incomplete Bug description: == Comment: #0 - Michael Ranweiler - 2018-10-15 08:55:55 == +++ This bug was initially created as a clone of Bug #167756 +++ ---Problem Description--- TM (Hardware Transactional Memory) instructions halt application on baremetal POWER9 DD2.1 Contact Information = grom...@br.ibm.com ---Additional Hardware Info--- POWER9 DD2.1 (pvr 004e 1201) baremetal. Witherspoon. Machine Type = POWER9 DD2.1 (pvr 004e 1201) baremetal ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Currently TM (Hardware Transactional Memory) on baremetal POWER9 DD2.1 (pvr 004e 1201) with the latest firmware [1] (Firmware level [2] was also tested with the same result) and running Linux from Linus' upstream tree [3] or powerpc/next branch [4] is not working as expected. Once a TM instruction is executed in a process (any instruction), the process halts completely and has to be killed. A simple test case is to execute a 'tend.' which accordingly to POWER8 behaviour and the ISA v3.00 if executed "in Non-transactional state is treated as a no-op." [5]. It means that the instruction in the test case below should be treated simply as a 'nop' instruction and the process would terminate normally but instead it halts and the process never terminates: root@io83:~/gromero# cat t.c int main() { asm ("tend.;"); } root@io83:~/gromero# make t make: 't' is up to date. root@io83:~/gromero# ./t ^C Ubuntu stock kernel 4.15.0-20-generic was also tested with the same result. I confirmed with Erich Hauptli (FW team) that FW stack levels [1] contain all the TM fixes we have at the moment. Thus, that issue affects any application that uses TM on a baremetal POWER9 DD2.1 (pvr 004e 1201). [1] IBM-witherspoon-ibm-OP9_v1.19_1.160 op-build-v1.21.2-255-g6ad1636-dirty buildroot-2017.11-5-g65679be skiboot-v5.10.5-op910-1 hostboot-ed53939 linux-4.14.24-openpower1-paed97e8 petitboot-v1.6.6-p41a158a machine-xml-4af occ-ef5d466 hostboot-binaries-6a92b6d capp-ucode-p9-dd2-v3 sbe-7e02c23 [2] open-power-witherspoon-v1.22-82-gebe1295-dirty buildroot-2018.02.1-6-ga8d11267c2 skiboot-v6.0-rc1 hostboot-d9bf361-p6755b85 occ-f741c41 linux-4.16.7-openpower1-p945838d petitboot-v1.7.1-pd695626 machine-xml-7cd20a6 hostboot-binaries-53aece6 capp-ucode-p9-dd2-v4 sbe-8e0105e hcode-hw050318a.op920 [3] https://github.com/torvalds/linux.git (master) [4] https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git (next) [5] Power ISA - Book II, p. 894 Stack trace output: no Oops output: no Userspace tool common name: any tool using TM instruction set Userspace rpm: not relevant The userspace tool has the following bit modes: 64-bit System Dump Info: The system is not configured to capture a system dump. Userspace tool obtained from project website: na *Additional Instructions for grom...@br.ibm.com: -Attach sysctl -a output output to the bug. -Attach ltrace and strace of userspace application. The following patch fixes this issue: http://patchwork.ozlabs.org/patch/968375/ Author: Michael Neuling Date: Tue Sep 11 13:07:56 2018 +1000 powerpc/tm: Fix HFSCR bit for no suspend case Currently on P9N DD2.1 we end up taking infinite TM facility unavailable exceptions on the first TM usage by userspace. In the special case of TM no suspend (P9N DD2.1), Linux is told TM is off via CPU dt-ftrs but told to (partially) use it via OPAL_REINIT_CPUS_TM_SUSPEND_DISABLED. So HFSCR[TM] will be off from dt-ftrs but we need to turn it on for the no suspend case. This patch fixes this by enabling HFSCR TM in this case. Cc: sta...@vger.kernel.org # 4.15+ Signed-off-by: Michael Neuling == Comment: #2 - Michael Ranweiler - 2018-10-15 13:52:13 == This is in the powerpc -next branch: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=dd9a8c5a87395b6f05552c3b44e42fdc95760552 To manage notifications about this bug go
[Kernel-packages] [Bug 1813934] Re: Vsock connect fails with ENODEV for large CID
** Changed in: ubuntu-z-systems Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813934 Title: Vsock connect fails with ENODEV for large CID Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: - Problem Descripion: Kernel 4.19 introduced a bug in the Vsock protocol when using a large Context ID. E.g. CID 0xfff000 works correctly but CID 0xfff001 fails with ENODEV when trying to connect to the listener. The issue now also shows up in Ubuntu 18.04 with -> kernel 4.15.0-44-generic #47-Ubuntu on x86_64 and s390x. It is already fixed upstream kernel by: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7fbe078c37aba3088359c9256c1a1d0c3e39ee81 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1813934/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812198] Re: user_copy in user from ubuntu_kernel_selftests failed on KVM kernel
** Changed in: linux-kvm (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-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1812198 Title: user_copy in user from ubuntu_kernel_selftests failed on KVM kernel Status in ubuntu-kernel-tests: In Progress Status in linux-kvm package in Ubuntu: In Progress Status in linux-kvm source package in Xenial: Fix Released Status in linux-kvm source package in Bionic: Fix Committed Status in linux-kvm source package in Cosmic: Fix Released Bug description: == Justification == This user_copy test has failed while attempting to insert the test_user_copy module, but this module does not exist in the Bionic KVM kernel as the CONFIG_TEST_USER_COPY was not enabled. # modprobe test_user_copy modprobe: FATAL: Module test_user_copy not found in directory /lib/modules/4.15.0-1028-kvm == Fix == d7d5311 (selftests: user: return Kselftest Skip code for skipped tests) 3c07aae (selftests: kselftest: change KSFT_SKIP=4 instead of KSFT_PASS) c31d02d (selftests: kselftest: Remove outdated comment) This fix will make the test return a skipped retun code if the test_user_copy module does not exist. This patch set can be cherry-picked into Bionic, and we already have it in Cosmic / Disco. For Xenial, it already got d7d5311 and does not need the other two. == Test == With this patch, the test will return "skipped" as expected: $ sudo ./test_user_copy.sh user: module test_user_copy is not found [SKIP] $ echo $? 4 Note that the test framework will need another fix to treat the SKIP return code properly. (bug 1812352) == Regression potential == None, this patch just change the code for the testing tool. -- This test_user_copy module will need the CONFIG_TEST_USER_COPY to be enabled https://cateee.net/lkddb/web-lkddb/TEST_USER_COPY.html ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28 ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18 Uname: Linux 4.15.0-1028-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Thu Jan 17 10:57:57 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812198/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806472] Re: RTL8822BE WiFi Disabled in Kernel 4.18.0-12
** Changed in: linux (Ubuntu Bionic) Status: Triaged => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: Triaged => 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/1806472 Title: RTL8822BE WiFi Disabled in Kernel 4.18.0-12 Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: ===SRU Justification=== [Impact] Realtek 8822be doesn't work under kernel lockdown. [Fix] Add r8822be.ko to signature-inclusion, so it can be signed and be loaded when lockdown is enabled. [Test] Since I can't signed the kernel so it's not tested. [Regression Potential] Low. The driver is maintained by a Realtek guy, so bugs are actually getting fixed. ===Original Bug Report=== Received kernel patch 4.18.0-12 today on my machine. On reboot my WiFi appears to be unavailable. lspci still recognises the installed RTL8822BE card and a reboot back to the previous kernel version (4.18.0-11) seems to resolve the problem. We tried some debugging in the IRC channel and didn't get very far. The r8822be module alias is intact, trying to modprobe it or insert results in a "operation not permitted" error. Modprobing mac80211 and cfg80211 which r8822be depends on did not seem to help. KMod Lists for -12 and -11 kernels: https://paste.ubuntu.com/p/pwx5mKszVt/ `ls -latr /lib/modules/4.18.0-12-*/ ; grep -i B822 /lib/modules/4.18.0-12-*/modules.alias` : https://paste.ubuntu.com/p/5zcCbXyM5g/ ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: callum 2989 F pulseaudio /dev/snd/controlC0: callum 2989 F pulseaudio CurrentDesktop: KDE Date: Mon Dec 3 19:27:16 2018 InstallationDate: Installed on 2018-11-10 (22 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: LENOVO 90H90015UK ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=d5f81e09-382c-4759-8a6d-2503fe6959b4 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175.1 SourcePackage: linux StagingDrivers: r8822be UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2018 dmi.bios.vendor: LENOVO dmi.bios.version: O3FKT26A dmi.board.name: 36E1 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN 3259620440547 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrO3FKT26A:bd06/15/2018:svnLENOVO:pn90H90015UK:pvrLegionY720T-34ASU:rvnLENOVO:rn36E1:rvrSDK0J40709WIN3259620440547:cvnLENOVO:ct3:cvrNone: dmi.product.family: Legion Y720T-34ASU dmi.product.name: 90H90015UK dmi.product.sku: LENOVO_MT_90H9_BU_LENOVO_FM_Legion Y720T-34ASU dmi.product.version: Legion Y720T-34ASU dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806472/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812086] Re: kernel BUG at /build/linux-vxxS7y/linux-4.15.0/mm/slub.c:296!
** Changed in: linux (Ubuntu Bionic) Status: New => 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/1812086 Title: kernel BUG at /build/linux-vxxS7y/linux-4.15.0/mm/slub.c:296! Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: == SRU Justification == Rebooting an iSCSI target while the initiator is writing to a LUN leads to the following trace: [ 59.879202] [ cut here ] [ 59.879202] kernel BUG at /build/linux-vxxS7y/linux-4.15.0/mm/slub.c:296! [ 59.880636] invalid opcode: [#1] SMP PTI [ 59.881569] Modules linked in: iscsi_target_mod target_core_pscsi target_core_file target_core_iblock target_core_user uio target_core_mod nls_iso8859_1 kvm_intel isofs kvm irqbypass joydev input_leds serio_raw sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear psmouse virtio_blk virtio_net floppy [ 59.891096] CPU: 0 PID: 1027 Comm: iscsi_np Not tainted 4.15.0-43-generic #46-Ubuntu [ 59.892726] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.11.1-1ubuntu1 04/01/2014 [ 59.894606] RIP: 0010:kfree+0x16a/0x180 [ 59.895429] RSP: 0018:ac0d8050fe58 EFLAGS: 00010246 [ 59.896531] RAX: 9cf099475800 RBX: 9cf099475800 RCX: 9cf099475800 [ 59.898083] RDX: 00011bbb RSI: 9cf09fc27140 RDI: 9cf09f002000 [ 59.899627] RBP: ac0d8050fe70 R08: R09: c07a329b [ 59.901186] R10: e95780651d40 R11: a511dc90 R12: 9cf099625600 [ 59.902769] R13: c07a329b R14: 9cf09ee07600 R15: 9cf099475800 [ 59.904321] FS: () GS:9cf09fc0() knlGS: [ 59.906120] CS: 0010 DS: ES: CR0: 80050033 [ 59.907806] CR2: 7f7153b88470 CR3: 1babe000 CR4: 06f0 [ 59.909376] DR0: DR1: DR2: [ 59.910950] DR3: DR6: fffe0ff0 DR7: 0400 [ 59.913098] Call Trace: [ 59.913783] iscsi_target_login_sess_out+0x1fb/0x250 [iscsi_target_mod] [ 59.915292] iscsi_target_login_thread+0x44d/0x1060 [iscsi_target_mod] [ 59.916775] kthread+0x121/0x140 [ 59.917622] ? iscsi_target_login_sess_out+0x250/0x250 [iscsi_target_mod] [ 59.919244] ? kthread_create_worker_on_cpu+0x70/0x70 [ 59.920483] ? do_syscall_64+0x73/0x130 [ 59.921460] ? SyS_exit_group+0x14/0x20 [ 59.922583] ret_from_fork+0x35/0x40 [ 59.923523] Code: c4 80 74 04 41 8b 72 6c 4c 89 d7 e8 61 1c f9 ff eb 86 41 b8 01 00 00 00 48 89 d9 48 89 da 4c 89 d6 e8 8b f6 ff ff e9 6d ff ff ff <0f> 0b 48 8b 3d 6d c4 1c 01 e9 c9 fe ff ff 0f 1f 84 00 00 00 00 [ 59.927778] RIP: kfree+0x16a/0x180 RSP: ac0d8050fe58 [ 59.929063] ---[ end trace 082da4d341633d3e ]--- == Fix == Backport the following 3 commits: * scsi: iscsi: target: Fix conn_ops double free * scsi: iscsi: target: Set conn->sess to NULL when iscsi_login_set_conn_values fails * iscsi target: fix session creation failure handling == Regression Potential == Low. Clean cherry-picks that modify a very isolated area. == Test == Setup an iSCSI target using the scsi_target_user module and tcmu_runner. Setup an initiator to connect to the target and do IOs. Reboot the target. When the target comes back, the kernel falls over when the initiator tries to re-connect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812086/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793901] Re: kernel oops in bcache module
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793901 Title: kernel oops in bcache module Status in linux package in Ubuntu: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: SRU Justification = [Impact] Some users see panics like the following when performing fstrim on a bcached volume: [ 529.803060] BUG: unable to handle kernel NULL pointer dereference at 0008 [ 530.183928] #PF error: [normal kernel read fault] [ 530.412392] PGD 801f42163067 P4D 801f42163067 PUD 1f42168067 PMD 0 [ 530.750887] Oops: [#1] SMP PTI [ 530.920869] CPU: 10 PID: 4167 Comm: fstrim Kdump: loaded Not tainted 5.0.0-rc1+ #3 [ 531.290204] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 12/27/2015 [ 531.693137] RIP: 0010:blk_queue_split+0x148/0x620 [ 531.922205] Code: 60 38 89 55 a0 45 31 db 45 31 f6 45 31 c9 31 ff 89 4d 98 85 db 0f 84 7f 04 00 00 44 8b 6d 98 4c 89 ee 48 c1 e6 04 49 03 70 78 <8b> 46 08 44 8b 56 0c 48 8b 16 44 29 e0 39 d8 48 89 55 a8 0f 47 c3 [ 532.838634] RSP: 0018:b9b708df39b0 EFLAGS: 00010246 [ 533.093571] RAX: RBX: 00046000 RCX: [ 533.441865] RDX: 0200 RSI: RDI: [ 533.789922] RBP: b9b708df3a48 R08: 940d3b3fdd20 R09: [ 534.137512] R10: b9b708df3958 R11: R12: [ 534.485329] R13: R14: R15: 940d39212020 [ 534.833319] FS: 7efec26e3840() GS:940d1f48() knlGS: [ 535.224098] CS: 0010 DS: ES: CR0: 80050033 [ 535.504318] CR2: 0008 CR3: 001f4e256004 CR4: 001606e0 [ 535.851759] Call Trace: [ 535.970308] ? mempool_alloc_slab+0x15/0x20 [ 536.174152] ? bch_data_insert+0x42/0xd0 [bcache] [ 536.403399] blk_mq_make_request+0x97/0x4f0 [ 536.607036] generic_make_request+0x1e2/0x410 [ 536.819164] submit_bio+0x73/0x150 [ 536.980168] ? submit_bio+0x73/0x150 [ 537.149731] ? bio_associate_blkg_from_css+0x3b/0x60 [ 537.391595] ? _cond_resched+0x1a/0x50 [ 537.573774] submit_bio_wait+0x59/0x90 [ 537.756105] blkdev_issue_discard+0x80/0xd0 [ 537.959590] ext4_trim_fs+0x4a9/0x9e0 [ 538.137636] ? ext4_trim_fs+0x4a9/0x9e0 [ 538.324087] ext4_ioctl+0xea4/0x1530 [ 538.497712] ? _copy_to_user+0x2a/0x40 [ 538.679632] do_vfs_ioctl+0xa6/0x600 [ 538.853127] ? __do_sys_newfstat+0x44/0x70 [ 539.051951] ksys_ioctl+0x6d/0x80 [ 539.212785] __x64_sys_ioctl+0x1a/0x20 [ 539.394918] do_syscall_64+0x5a/0x110 [ 539.568674] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [Fix] Under certain conditions, the test for whether an operation should be written back to the underlying device was incorrect. Specifically, in should_writeback(), we were hitting a case where an optimisation for partial stripe conditions was returning true and so should_writeback() was returning true early. This caused the code to go down an incorrect path and create bios that contained NULL pointers. To fix this issue, make sure that should_writeback() on a discard op never returns true. [Test Case] We have observed it on some systems where both: 1) LVM/devmapper is involved (bcache backing device is LVM volume) and 2) writeback cache is involved (bcache cache_mode is writeback) Not every machine exhibits the bug. On one machine that does exhibit the bug, we can reliably reproduce it with: # echo writeback > /sys/block/bcache0/bcache/cache_mode # mount /dev/bcache0 /test # for i in {0..10}; do file="$(mktemp /test/zero.XXX)"; dd if=/dev/zero of="$file" bs=1M count=256; sync; rm $file; done; fstrim -v /test [Regression Potential] This could affect any device where bcache is used. In mitigation, however: the patch is simple, is limited to considering discard operations. The patch has been accepted upstream [1] and the maintainer will be including it in SuSE kernels [2]. A Gentoo user validated the upstream patch independently [3]. [1] https://www.spinics.net/lists/linux-bcache/msg06997.html [2] https://www.spinics.net/lists/linux-bcache/msg06998.html [3] https://bugzilla.kernel.org/show_bug.cgi?id=196103#c3 [Original Description] This was on an 18.04.1 install running the 4.15-34 generic kernel image, running from a normal ext4 root device. I had
[Kernel-packages] [Bug 1808886] Re: Microcode SW error detected. Restarting 0x0.
Still actual for me. Please, can someone answer on 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/1808886 Title: Microcode SW error detected. Restarting 0x0. Status in linux package in Ubuntu: Confirmed Bug description: intel-microcode: Installed: 3.20180807a.0ubuntu0.18.04.1 Candidate: 3.20180807a.0ubuntu0.18.04.1 Version table: *** 3.20180807a.0ubuntu0.18.04.1 500 500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.20180312.0~ubuntu18.04.1 500 500 http://ru.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Version: Ubuntu 4.15.0-42.45-generic 4.15.18 Error: [ 3136.084499] rtsx_pci :06:00.0: VPD access failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update [ 3136.085614] r8169 :06:00.1: invalid short VPD tag 00 at offset 1 [ 3136.085624] dpc :00:1d.0:pcie010: DPC containment event, status:0x1f00 source:0x [ 3136.085662] pcieport :00:1d.0: AER: Multiple Corrected error received: id=00e8 [ 3136.085683] pcieport :00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e8(Transmitter ID) [ 3136.085694] pcieport :00:1d.0: device [8086:a335] error status/mask=1101/2000 [ 3136.085701] pcieport :00:1d.0:[ 0] Receiver Error (First) [ 3136.085722] pcieport :00:1d.0:[ 8] RELAY_NUM Rollover [ 3136.085741] pcieport :00:1d.0:[12] Replay Timer Timeout [ 3166.625429] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [ 3166.625797] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 3166.625805] iwlwifi :00:14.3: Status: 0x0100, count: 6 [ 3166.625810] iwlwifi :00:14.3: Loaded firmware version: 34.0.0 [ 3166.625817] iwlwifi :00:14.3: 0x1007 | ADVANCED_SYSASSERT [ 3166.625823] iwlwifi :00:14.3: 0x0080A614 | trm_hw_status0 [ 3166.625828] iwlwifi :00:14.3: 0x | trm_hw_status1 [ 3166.625834] iwlwifi :00:14.3: 0x00456D06 | branchlink2 [ 3166.625839] iwlwifi :00:14.3: 0x0046064A | interruptlink1 [ 3166.625844] iwlwifi :00:14.3: 0x | interruptlink2 [ 3166.625850] iwlwifi :00:14.3: 0x00030400 | data1 [ 3166.625855] iwlwifi :00:14.3: 0x040B | data2 [ 3166.625860] iwlwifi :00:14.3: 0x | data3 [ 3166.625866] iwlwifi :00:14.3: 0xAD418817 | beacon time [ 3166.625871] iwlwifi :00:14.3: 0x6A2317EF | tsf low [ 3166.625876] iwlwifi :00:14.3: 0x0184 | tsf hi [ 3166.625881] iwlwifi :00:14.3: 0x | time gp1 [ 3166.625887] iwlwifi :00:14.3: 0x0ADF380D | time gp2 [ 3166.625892] iwlwifi :00:14.3: 0x0001 | uCode revision type [ 3166.625897] iwlwifi :00:14.3: 0x0022 | uCode version major [ 3166.625903] iwlwifi :00:14.3: 0x | uCode version minor [ 3166.625908] iwlwifi :00:14.3: 0x0312 | hw version [ 3166.625913] iwlwifi :00:14.3: 0x00C89008 | board version [ 3166.625918] iwlwifi :00:14.3: 0x0A9E001C | hcmd [ 3166.625924] iwlwifi :00:14.3: 0xA4022002 | isr0 [ 3166.625929] iwlwifi :00:14.3: 0x0100 | isr1 [ 3166.625934] iwlwifi :00:14.3: 0x08001802 | isr2 [ 3166.625939] iwlwifi :00:14.3: 0x0041B8C5 | isr3 [ 3166.625944] iwlwifi :00:14.3: 0x | isr4 [ 3166.625950] iwlwifi :00:14.3: 0x00EC019C | last cmd Id [ 3166.625955] iwlwifi :00:14.3: 0x | wait_event [ 3166.625960] iwlwifi :00:14.3: 0x0080 | l2p_control [ 3166.625965] iwlwifi :00:14.3: 0x00012034 | l2p_duration [ 3166.625971] iwlwifi :00:14.3: 0x003F | l2p_mhvalid [ 3166.625976] iwlwifi :00:14.3: 0x00CE | l2p_addr_match [ 3166.625981] iwlwifi :00:14.3: 0x000F | lmpm_pmg_sel [ 3166.625987] iwlwifi :00:14.3: 0x12111721 | timestamp [ 3166.625992] iwlwifi :00:14.3: 0x9090 | flow_handler [ 3166.626141] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 3166.626147] iwlwifi :00:14.3: Status: 0x0100, count: 7 [ 3166.626152] iwlwifi :00:14.3: 0x0070 | ADVANCED_SYSASSERT [ 3166.626158] iwlwifi :00:14.3: 0x | umac branchlink1 [ 3166.626163] iwlwifi :00:14.3: 0xC0087D08 | umac branchlink2 [ 3166.626168] iwlwifi :00:14.3: 0xC0083A08 | umac interruptlink1 [ 3166.626173] iwlwifi :00:14.3: 0xC0083A08 | umac interruptlink2 [ 3166.626178] iwlwifi :00:14.3: 0x0800 | umac data1 [ 3166.626184] iwlwifi :00:14.3: 0xC0083A08 | umac data2 [ 3166.626189] iwlwifi :00:14.3: 0xDEADBEEF | umac data3 [ 3166.626194] iwlwifi :00:14.3: 0x0022 | umac major [ 3166.626199] iwlwifi :00:14.3: 0x | umac minor
[Kernel-packages] [Bug 1813532] Re: x86/mm: Found insecure W+X mapping at address (ptrval)/0xc00a0000
** Changed in: linux (Ubuntu Cosmic) Status: New => 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/1813532 Title: x86/mm: Found insecure W+X mapping at address (ptrval)/0xc00a Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: == SRU Justification == Booting an i386 Bionic kernel in a VM with a 64-bit CPU leads to: [1.074702] Freeing unused kernel memory: 1092K [1.084027] Write protecting the kernel text: 8836k [1.085115] Write protecting the kernel read-only data: 3480k [1.086361] NX-protecting the kernel data: 7548k [1.087457] [ cut here ] [1.088400] x86/mm: Found insecure W+X mapping at address (ptrval)/0xc00a [1.089738] WARNING: CPU: 0 PID: 1 at /build/linux-bnzN1b/linux-4.15.0/arch/x86/mm/dump_pagetables.c:266 note_page+0x670/0x860 [1.091893] Modules linked in: [1.092522] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.15.0-43-generic #46-Ubuntu [1.094362] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.11.1-1ubuntu1 04/01/2014 [1.096279] EIP: note_page+0x670/0x860 [1.097012] EFLAGS: 00010282 CPU: 0 [1.097807] EAX: 0041 EBX: df4fbf44 ECX: 01ba EDX: [1.099083] ESI: 8000 EDI: EBP: df4fbf10 ESP: df4fbee4 [1.100328] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [1.101418] CR0: 80050033 CR2: b7d99092 CR3: 0ce16000 CR4: 06f0 [1.102693] DR0: DR1: DR2: DR3: [1.103928] DR6: fffe0ff0 DR7: 0400 [1.104733] Call Trace: [1.105316] ptdump_walk_pgd_level_core+0x2ac/0x2e0 [1.106266] ptdump_walk_pgd_level_checkwx+0x18/0x20 [1.107207] mark_rodata_ro+0xf5/0x117 [1.107947] ? rest_init+0xa0/0xa0 [1.108627] kernel_init+0x33/0xf0 [1.109300] ret_from_fork+0x2e/0x38 [1.110016] Code: cc e9 0c fb ff ff f7 c6 00 10 00 00 74 8c 68 fe ae ae cc e9 16 fe ff ff 52 52 68 ac af ae cc c6 05 a8 a8 cb cc 01 e8 40 74 00 00 <0f> 0b 8b 53 0c 83 c4 0c e9 38 fa ff ff 50 6a 08 52 6a 08 68 ae [1.113395] ---[ end trace 0dce1996d96c40bb ]--- [1.114324] x86/mm: Checked W+X mappings: FAILED, 96 W+X pages found. == Fix == Backport commit c200dac78fec ("x86/mm: Do not warn about PCI BIOS W+X mappings"). == Regression Potential == Low. The patch only modifies debugging output. == Test Case == To reproduce, boot an i386 kernel in QEMU with '-cpu qemu64' and check the kernel logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813532/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813733] Re: Ignore "incomplete report" from Elan touchpanels
** Changed in: linux (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: New => Fix Committed ** Changed in: linux (Ubuntu Disco) Status: Incomplete => 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/1813733 Title: Ignore "incomplete report" from Elan touchpanels Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: [Impact] When using Elan touchpanels, this message keeps getting spurted out: [ 136.138487] i2c_hid i2c-DELL08D6:00: i2c_hid_get_input: incomplete report (14/65535) This is an error message, so systemd-journald flushes to disk as soon as the message shows. This prevents the storage enters power saving state, hurting battery time. Other than the annoying message, the touchpad itself works fine. [Fix] Just warn once to avoid the annoying message. [Test] The annoying message stops once the fix applied. [Regression Potential] None. The user still gets the warning from dmesg without all the flooding. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1813733/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813934] Re: Vsock connect fails with ENODEV for large CID
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813934 Title: Vsock connect fails with ENODEV for large CID Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: - Problem Descripion: Kernel 4.19 introduced a bug in the Vsock protocol when using a large Context ID. E.g. CID 0xfff000 works correctly but CID 0xfff001 fails with ENODEV when trying to connect to the listener. The issue now also shows up in Ubuntu 18.04 with -> kernel 4.15.0-44-generic #47-Ubuntu on x86_64 and s390x. It is already fixed upstream kernel by: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7fbe078c37aba3088359c9256c1a1d0c3e39ee81 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1813934/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782212] Re: KVM CLX ACPI HMAT table support
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782212 Title: KVM CLX ACPI HMAT table support Status in linux package in Ubuntu: Expired Bug description: ACPI HMAT table support : HMAT is a new ACPI table that records the performance parameter of memory, so MCDRAM (or next gen HBM2) can be described well by this table. We need to support this table in kernel and qemu so that guest can get and parse this table then to find where the high-performance memory is. Heterogeneous Memory Attribute Table (HMAT) describes the memory attributes, such as memory side cache attributes and bandwidth and latency details, related to the System Physical Address (SPA) Memory Ranges. The software is expected to use this information as hint for optimization. HMAT is defined in ACPI 6.2: 5.2.27 Heterogeneous Memory Attribute Table (HMAT). http://www.uefi.org/sites/default/files/resources/ACPI_6_2.pdf patches: http://lists.nongnu.org/archive/html/qemu-devel/2018-06/msg05368.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782212/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806817] Re: With nvidia-340 driver installed it won't boot to SDDM
[Expired for nvidia-graphics-drivers-340 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806817 Title: With nvidia-340 driver installed it won't boot to SDDM Status in linux package in Ubuntu: Expired Status in nvidia-graphics-drivers-340 package in Ubuntu: Expired Status in nvidia-prime package in Ubuntu: Expired Status in sddm package in Ubuntu: Expired Bug description: It's hard to report this bug on a laptop with this driver installed, so I'm reporting this with on my laptop with a much newer NVIDIA driver (but not recommended). My laptop, Lenovo Z40, has NVIDIA GeForce GT820M. With nvidia-340 driver installed it won't boot to SDDM (also tried with LightDM). Opening up another TTY is useless because the same message "PKCS#7 signature not signed with a trusted key" keeps getting spammed. I had to go to recovery to switch to Intel graphics. [CODE] $ lspci 03:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] (rev a1) [/CODE] --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yamiyukisenpai 2601 F pulseaudio /dev/snd/controlC1: yamiyukisenpai 2601 F pulseaudio CurrentDesktop: KDE Dependencies: DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-08-05 (121 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20366 NonfreeKernelModules: wl Package: nvidia-prime 0.8.10 PackageArchitecture: all ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic root=UUID=3ac3d3b6-dc27-4365-a548-82d3be4e5ac9 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 RelatedPackageVersions: linux-restricted-modules-4.18.0-12-generic N/A linux-backports-modules-4.18.0-12-generic N/A linux-firmware 1.175.1 Tags: cosmic Uname: Linux 4.18.0-12-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-10 (55 days ago) UserGroups: adm cdrom dip kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN91WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 4A5 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z40-70 dmi.modalias: dmi:bvnLENOVO:bvr9BCN91WW:bd07/21/2015:svnLENOVO:pn20366:pvrLenovoZ40-70:rvnLENOVO:rnLancer4A5:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoZ40-70: dmi.product.family: IDEAPAD dmi.product.name: 20366 dmi.product.sku: LENOVO_MT_20366_BU_idea_FM_Lenovo Z40-70 dmi.product.version: Lenovo Z40-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806817/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806817] Re: With nvidia-340 driver installed it won't boot to SDDM
[Expired for sddm (Ubuntu) because there has been no activity for 60 days.] ** Changed in: sddm (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806817 Title: With nvidia-340 driver installed it won't boot to SDDM Status in linux package in Ubuntu: Expired Status in nvidia-graphics-drivers-340 package in Ubuntu: Expired Status in nvidia-prime package in Ubuntu: Expired Status in sddm package in Ubuntu: Expired Bug description: It's hard to report this bug on a laptop with this driver installed, so I'm reporting this with on my laptop with a much newer NVIDIA driver (but not recommended). My laptop, Lenovo Z40, has NVIDIA GeForce GT820M. With nvidia-340 driver installed it won't boot to SDDM (also tried with LightDM). Opening up another TTY is useless because the same message "PKCS#7 signature not signed with a trusted key" keeps getting spammed. I had to go to recovery to switch to Intel graphics. [CODE] $ lspci 03:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] (rev a1) [/CODE] --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yamiyukisenpai 2601 F pulseaudio /dev/snd/controlC1: yamiyukisenpai 2601 F pulseaudio CurrentDesktop: KDE Dependencies: DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-08-05 (121 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20366 NonfreeKernelModules: wl Package: nvidia-prime 0.8.10 PackageArchitecture: all ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic root=UUID=3ac3d3b6-dc27-4365-a548-82d3be4e5ac9 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 RelatedPackageVersions: linux-restricted-modules-4.18.0-12-generic N/A linux-backports-modules-4.18.0-12-generic N/A linux-firmware 1.175.1 Tags: cosmic Uname: Linux 4.18.0-12-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-10 (55 days ago) UserGroups: adm cdrom dip kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN91WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 4A5 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z40-70 dmi.modalias: dmi:bvnLENOVO:bvr9BCN91WW:bd07/21/2015:svnLENOVO:pn20366:pvrLenovoZ40-70:rvnLENOVO:rnLancer4A5:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoZ40-70: dmi.product.family: IDEAPAD dmi.product.name: 20366 dmi.product.sku: LENOVO_MT_20366_BU_idea_FM_Lenovo Z40-70 dmi.product.version: Lenovo Z40-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806817/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806817] Re: With nvidia-340 driver installed it won't boot to SDDM
[Expired for nvidia-prime (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nvidia-prime (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806817 Title: With nvidia-340 driver installed it won't boot to SDDM Status in linux package in Ubuntu: Expired Status in nvidia-graphics-drivers-340 package in Ubuntu: Expired Status in nvidia-prime package in Ubuntu: Expired Status in sddm package in Ubuntu: Expired Bug description: It's hard to report this bug on a laptop with this driver installed, so I'm reporting this with on my laptop with a much newer NVIDIA driver (but not recommended). My laptop, Lenovo Z40, has NVIDIA GeForce GT820M. With nvidia-340 driver installed it won't boot to SDDM (also tried with LightDM). Opening up another TTY is useless because the same message "PKCS#7 signature not signed with a trusted key" keeps getting spammed. I had to go to recovery to switch to Intel graphics. [CODE] $ lspci 03:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] (rev a1) [/CODE] --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yamiyukisenpai 2601 F pulseaudio /dev/snd/controlC1: yamiyukisenpai 2601 F pulseaudio CurrentDesktop: KDE Dependencies: DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-08-05 (121 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20366 NonfreeKernelModules: wl Package: nvidia-prime 0.8.10 PackageArchitecture: all ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic root=UUID=3ac3d3b6-dc27-4365-a548-82d3be4e5ac9 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 RelatedPackageVersions: linux-restricted-modules-4.18.0-12-generic N/A linux-backports-modules-4.18.0-12-generic N/A linux-firmware 1.175.1 Tags: cosmic Uname: Linux 4.18.0-12-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-10 (55 days ago) UserGroups: adm cdrom dip kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN91WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 4A5 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z40-70 dmi.modalias: dmi:bvnLENOVO:bvr9BCN91WW:bd07/21/2015:svnLENOVO:pn20366:pvrLenovoZ40-70:rvnLENOVO:rnLancer4A5:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoZ40-70: dmi.product.family: IDEAPAD dmi.product.name: 20366 dmi.product.sku: LENOVO_MT_20366_BU_idea_FM_Lenovo Z40-70 dmi.product.version: Lenovo Z40-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806817/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806817] Re: With nvidia-340 driver installed it won't boot to SDDM
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806817 Title: With nvidia-340 driver installed it won't boot to SDDM Status in linux package in Ubuntu: Expired Status in nvidia-graphics-drivers-340 package in Ubuntu: Expired Status in nvidia-prime package in Ubuntu: Expired Status in sddm package in Ubuntu: Expired Bug description: It's hard to report this bug on a laptop with this driver installed, so I'm reporting this with on my laptop with a much newer NVIDIA driver (but not recommended). My laptop, Lenovo Z40, has NVIDIA GeForce GT820M. With nvidia-340 driver installed it won't boot to SDDM (also tried with LightDM). Opening up another TTY is useless because the same message "PKCS#7 signature not signed with a trusted key" keeps getting spammed. I had to go to recovery to switch to Intel graphics. [CODE] $ lspci 03:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] (rev a1) [/CODE] --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yamiyukisenpai 2601 F pulseaudio /dev/snd/controlC1: yamiyukisenpai 2601 F pulseaudio CurrentDesktop: KDE Dependencies: DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-08-05 (121 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20366 NonfreeKernelModules: wl Package: nvidia-prime 0.8.10 PackageArchitecture: all ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic root=UUID=3ac3d3b6-dc27-4365-a548-82d3be4e5ac9 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 RelatedPackageVersions: linux-restricted-modules-4.18.0-12-generic N/A linux-backports-modules-4.18.0-12-generic N/A linux-firmware 1.175.1 Tags: cosmic Uname: Linux 4.18.0-12-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-10 (55 days ago) UserGroups: adm cdrom dip kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN91WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 4A5 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z40-70 dmi.modalias: dmi:bvnLENOVO:bvr9BCN91WW:bd07/21/2015:svnLENOVO:pn20366:pvrLenovoZ40-70:rvnLENOVO:rnLancer4A5:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoZ40-70: dmi.product.family: IDEAPAD dmi.product.name: 20366 dmi.product.sku: LENOVO_MT_20366_BU_idea_FM_Lenovo Z40-70 dmi.product.version: Lenovo Z40-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806817/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814489] Re: package linux-image-4.4.0-31-generic 4.4.0-31.50 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814489 Title: package linux-image-4.4.0-31-generic 4.4.0-31.50 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127 Status in linux package in Ubuntu: Invalid Bug description: please i needto upgrade my system ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cng1494 F pulseaudio Date: Sun Feb 3 22:25:17 2019 DpkgHistoryLog: Start-Date: 2019-02-03 22:25:06 Commandline: /usr/bin/unattended-upgrade Remove: linux-image-extra-4.4.0-34-generic:amd64 (4.4.0-34.53), linux-image-4.4.0-38-generic:amd64 (4.4.0-38.57), linux-image-4.4.0-36-generic:amd64 (4.4.0-36.55), linux-image-extra-4.4.0-36-generic:amd64 (4.4.0-36.55), linux-image-extra-4.4.0-38-generic:amd64 (4.4.0-38.57), linux-image-4.4.0-43-generic:amd64 (4.4.0-43.63), linux-image-extra-4.4.0-43-generic:amd64 (4.4.0-43.63), linux-image-4.4.0-42-generic:amd64 (4.4.0-42.62), linux-image-extra-4.4.0-42-generic:amd64 (4.4.0-42.62), linux-image-4.4.0-45-generic:amd64 (4.4.0-45.66), linux-image-extra-4.4.0-45-generic:amd64 (4.4.0-45.66), linux-image-4.4.0-47-generic:amd64 (4.4.0-47.68), linux-image-extra-4.4.0-47-generic:amd64 (4.4.0-47.68), linux-image-4.4.0-31-generic:amd64 (4.4.0-31.50), linux-image-extra-4.4.0-31-generic:amd64 (4.4.0-31.50), linux-image-4.4.0-34-generic:amd64 (4.4.0-34.53) ErrorMessage: subprocess installed post-removal script returned error exit status 1 HibernationDevice: RESUME=UUID=76dc88f1-b6fd-43ba-a659-d2f2fff57043 InstallationDate: Installed on 2016-03-31 (1040 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 03f0:231d Hewlett-Packard Broadcom 2070 Bluetooth Combo Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP G42 Notebook PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-35-generic root=UUID=d016df5d-2081-4e81-9578-1df4f9bb40b8 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.14 SourcePackage: linux Title: package linux-image-4.4.0-31-generic 4.4.0-31.50 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127 UpgradeStatus: Upgraded to xenial on 2019-02-04 (0 days ago) dmi.bios.date: 04/07/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.37 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1425 dmi.board.vendor: Hewlett-Packard dmi.board.version: 54.57 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.37:bd04/07/2011:svnHewlett-Packard:pnHPG42NotebookPC:pvr049C112027102:rvnHewlett-Packard:rn1425:rvr54.57:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP G42 Notebook PC dmi.product.version: 049C112027102 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814489/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814489] 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/1814489 Title: package linux-image-4.4.0-31-generic 4.4.0-31.50 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127 Status in linux package in Ubuntu: Confirmed Bug description: please i needto upgrade my system ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cng1494 F pulseaudio Date: Sun Feb 3 22:25:17 2019 DpkgHistoryLog: Start-Date: 2019-02-03 22:25:06 Commandline: /usr/bin/unattended-upgrade Remove: linux-image-extra-4.4.0-34-generic:amd64 (4.4.0-34.53), linux-image-4.4.0-38-generic:amd64 (4.4.0-38.57), linux-image-4.4.0-36-generic:amd64 (4.4.0-36.55), linux-image-extra-4.4.0-36-generic:amd64 (4.4.0-36.55), linux-image-extra-4.4.0-38-generic:amd64 (4.4.0-38.57), linux-image-4.4.0-43-generic:amd64 (4.4.0-43.63), linux-image-extra-4.4.0-43-generic:amd64 (4.4.0-43.63), linux-image-4.4.0-42-generic:amd64 (4.4.0-42.62), linux-image-extra-4.4.0-42-generic:amd64 (4.4.0-42.62), linux-image-4.4.0-45-generic:amd64 (4.4.0-45.66), linux-image-extra-4.4.0-45-generic:amd64 (4.4.0-45.66), linux-image-4.4.0-47-generic:amd64 (4.4.0-47.68), linux-image-extra-4.4.0-47-generic:amd64 (4.4.0-47.68), linux-image-4.4.0-31-generic:amd64 (4.4.0-31.50), linux-image-extra-4.4.0-31-generic:amd64 (4.4.0-31.50), linux-image-4.4.0-34-generic:amd64 (4.4.0-34.53) ErrorMessage: subprocess installed post-removal script returned error exit status 1 HibernationDevice: RESUME=UUID=76dc88f1-b6fd-43ba-a659-d2f2fff57043 InstallationDate: Installed on 2016-03-31 (1040 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 03f0:231d Hewlett-Packard Broadcom 2070 Bluetooth Combo Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP G42 Notebook PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-35-generic root=UUID=d016df5d-2081-4e81-9578-1df4f9bb40b8 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.14 SourcePackage: linux Title: package linux-image-4.4.0-31-generic 4.4.0-31.50 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127 UpgradeStatus: Upgraded to xenial on 2019-02-04 (0 days ago) dmi.bios.date: 04/07/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.37 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1425 dmi.board.vendor: Hewlett-Packard dmi.board.version: 54.57 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.37:bd04/07/2011:svnHewlett-Packard:pnHPG42NotebookPC:pvr049C112027102:rvnHewlett-Packard:rn1425:rvr54.57:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP G42 Notebook PC dmi.product.version: 049C112027102 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814489/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814489] Re: package linux-image-4.4.0-31-generic 4.4.0-31.50 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814489 Title: package linux-image-4.4.0-31-generic 4.4.0-31.50 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127 Status in linux package in Ubuntu: New Bug description: please i needto upgrade my system ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cng1494 F pulseaudio Date: Sun Feb 3 22:25:17 2019 DpkgHistoryLog: Start-Date: 2019-02-03 22:25:06 Commandline: /usr/bin/unattended-upgrade Remove: linux-image-extra-4.4.0-34-generic:amd64 (4.4.0-34.53), linux-image-4.4.0-38-generic:amd64 (4.4.0-38.57), linux-image-4.4.0-36-generic:amd64 (4.4.0-36.55), linux-image-extra-4.4.0-36-generic:amd64 (4.4.0-36.55), linux-image-extra-4.4.0-38-generic:amd64 (4.4.0-38.57), linux-image-4.4.0-43-generic:amd64 (4.4.0-43.63), linux-image-extra-4.4.0-43-generic:amd64 (4.4.0-43.63), linux-image-4.4.0-42-generic:amd64 (4.4.0-42.62), linux-image-extra-4.4.0-42-generic:amd64 (4.4.0-42.62), linux-image-4.4.0-45-generic:amd64 (4.4.0-45.66), linux-image-extra-4.4.0-45-generic:amd64 (4.4.0-45.66), linux-image-4.4.0-47-generic:amd64 (4.4.0-47.68), linux-image-extra-4.4.0-47-generic:amd64 (4.4.0-47.68), linux-image-4.4.0-31-generic:amd64 (4.4.0-31.50), linux-image-extra-4.4.0-31-generic:amd64 (4.4.0-31.50), linux-image-4.4.0-34-generic:amd64 (4.4.0-34.53) ErrorMessage: subprocess installed post-removal script returned error exit status 1 HibernationDevice: RESUME=UUID=76dc88f1-b6fd-43ba-a659-d2f2fff57043 InstallationDate: Installed on 2016-03-31 (1040 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 03f0:231d Hewlett-Packard Broadcom 2070 Bluetooth Combo Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP G42 Notebook PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-35-generic root=UUID=d016df5d-2081-4e81-9578-1df4f9bb40b8 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.14 SourcePackage: linux Title: package linux-image-4.4.0-31-generic 4.4.0-31.50 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127 UpgradeStatus: Upgraded to xenial on 2019-02-04 (0 days ago) dmi.bios.date: 04/07/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.37 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1425 dmi.board.vendor: Hewlett-Packard dmi.board.version: 54.57 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.37:bd04/07/2011:svnHewlett-Packard:pnHPG42NotebookPC:pvr049C112027102:rvnHewlett-Packard:rn1425:rvr54.57:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP G42 Notebook PC dmi.product.version: 049C112027102 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814489/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814489] [NEW] package linux-image-4.4.0-31-generic 4.4.0-31.50 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127
Public bug reported: please i needto upgrade my system ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cng1494 F pulseaudio Date: Sun Feb 3 22:25:17 2019 DpkgHistoryLog: Start-Date: 2019-02-03 22:25:06 Commandline: /usr/bin/unattended-upgrade Remove: linux-image-extra-4.4.0-34-generic:amd64 (4.4.0-34.53), linux-image-4.4.0-38-generic:amd64 (4.4.0-38.57), linux-image-4.4.0-36-generic:amd64 (4.4.0-36.55), linux-image-extra-4.4.0-36-generic:amd64 (4.4.0-36.55), linux-image-extra-4.4.0-38-generic:amd64 (4.4.0-38.57), linux-image-4.4.0-43-generic:amd64 (4.4.0-43.63), linux-image-extra-4.4.0-43-generic:amd64 (4.4.0-43.63), linux-image-4.4.0-42-generic:amd64 (4.4.0-42.62), linux-image-extra-4.4.0-42-generic:amd64 (4.4.0-42.62), linux-image-4.4.0-45-generic:amd64 (4.4.0-45.66), linux-image-extra-4.4.0-45-generic:amd64 (4.4.0-45.66), linux-image-4.4.0-47-generic:amd64 (4.4.0-47.68), linux-image-extra-4.4.0-47-generic:amd64 (4.4.0-47.68), linux-image-4.4.0-31-generic:amd64 (4.4.0-31.50), linux-image-extra-4.4.0-31-generic:amd64 (4.4.0-31.50), linux-image-4.4.0-34-generic:amd64 (4.4.0-34.53) ErrorMessage: subprocess installed post-removal script returned error exit status 1 HibernationDevice: RESUME=UUID=76dc88f1-b6fd-43ba-a659-d2f2fff57043 InstallationDate: Installed on 2016-03-31 (1040 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 03f0:231d Hewlett-Packard Broadcom 2070 Bluetooth Combo Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP G42 Notebook PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-35-generic root=UUID=d016df5d-2081-4e81-9578-1df4f9bb40b8 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.14 SourcePackage: linux Title: package linux-image-4.4.0-31-generic 4.4.0-31.50 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127 UpgradeStatus: Upgraded to xenial on 2019-02-04 (0 days ago) dmi.bios.date: 04/07/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.37 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1425 dmi.board.vendor: Hewlett-Packard dmi.board.version: 54.57 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.37:bd04/07/2011:svnHewlett-Packard:pnHPG42NotebookPC:pvr049C112027102:rvnHewlett-Packard:rn1425:rvr54.57:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP G42 Notebook PC dmi.product.version: 049C112027102 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814489 Title: package linux-image-4.4.0-31-generic 4.4.0-31.50 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127 Status in linux package in Ubuntu: New Bug description: please i needto upgrade my system ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cng1494 F pulseaudio Date: Sun Feb 3 22:25:17 2019 DpkgHistoryLog: Start-Date: 2019-02-03 22:25:06 Commandline: /usr/bin/unattended-upgrade Remove: linux-image-extra-4.4.0-34-generic:amd64 (4.4.0-34.53), linux-image-4.4.0-38-generic:amd64 (4.4.0-38.57), linux-image-4.4.0-36-generic:amd64 (4.4.0-36.55), linux-image-extra-4.4.0-36-generic:amd64 (4.4.0-36.55), linux-image-extra-4.4.0-38-generic:amd64 (4.4.0-38.57), linux-image-4.4.0-43-generic:amd64 (4.4.0-43.63), linux-image-extra-4.4.0-43-generic:amd64 (4.4.0-43.63), linux-image-4.4.0-42-generic:amd64 (4.4.0-42.62), linux-image-extra-4.4.0-42-generic:amd64 (4.4.0-42.62), linux-image-4.4.0-45-generic:amd64 (4.4.0-45.66), linux-image-extra-4.4.0-45-generic:amd64 (4.4.0-45.66),
[Kernel-packages] [Bug 1811857] Re: linux-lts-trusty: 3.13.0-165.215~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-precise ** Tags removed: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811856 - phase: Holding before Release - phase-changed: Friday, 01. February 2019 12:38 UTC + phase: Release + phase-changed: Monday, 04. February 2019 00:45 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-security: Holding -- master bug not ready for release - promote-to-updates: Holding -- master bug not ready for release + promote-to-security: Pending -- ready to copy + promote-to-updates: Pending -- ready to copy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1811857 Title: linux-lts-trusty: 3.13.0-165.215~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811856 phase: Release phase-changed: Monday, 04. February 2019 00:45 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy promote-to-updates: Pending -- ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811851] Re: linux-aws: 4.4.0-1075.85 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-xenial ** Tags removed: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811846 - phase: Holding before Release - phase-changed: Friday, 01. February 2019 14:39 UTC + phase: Release + phase-changed: Monday, 04. February 2019 00:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-security: Holding -- master bug not ready for release - promote-to-updates: Holding -- master bug not ready for release + promote-to-security: Pending -- ready to copy + promote-to-updates: Pending -- ready to copy -- 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/1811851 Title: linux-aws: 4.4.0-1075.85 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed 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: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811846 phase: Release phase-changed: Monday, 04. February 2019 00:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy promote-to-updates: Pending -- ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811851/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811854] Re: linux-raspi2: 4.4.0-1103.111 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-xenial ** Tags removed: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811846 - phase: Holding before Release - phase-changed: Friday, 01. February 2019 14:36 UTC + phase: Release + phase-changed: Monday, 04. February 2019 00:39 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-security: Holding -- master bug not ready for release - promote-to-updates: Holding -- master bug not ready for release + promote-to-security: Pending -- ready to copy + promote-to-updates: Pending -- ready to copy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1811854 Title: linux-raspi2: 4.4.0-1103.111 -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 promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 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: 1811846 phase: Release phase-changed: Monday, 04. February 2019 00:39 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy promote-to-updates: Pending -- ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811854/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811847] Re: linux-aws: 4.4.0-1038.41 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-trusty ** Tags removed: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811846 - phase: Holding before Release - phase-changed: Friday, 01. February 2019 14:42 UTC + phase: Release + phase-changed: Monday, 04. February 2019 00:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-security: Holding -- master bug not ready for release - promote-to-updates: Holding -- master bug not ready for release + promote-to-security: Pending -- ready to copy + promote-to-updates: Pending -- ready to copy -- 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/1811847 Title: linux-aws: 4.4.0-1038.41 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811846 phase: Release phase-changed: Monday, 04. February 2019 00:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy promote-to-updates: Pending -- ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811847/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811853] Re: linux-kvm: 4.4.0-1040.46 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-xenial ** Tags removed: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811846 - phase: Holding before Release - phase-changed: Friday, 01. February 2019 14:39 UTC + phase: Release + phase-changed: Monday, 04. February 2019 00:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-security: Holding -- master bug not ready for release - promote-to-updates: Holding -- master bug not ready for release + promote-to-security: Pending -- ready to copy + promote-to-updates: Pending -- ready to copy -- 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/1811853 Title: linux-kvm: 4.4.0-1040.46 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811846 phase: Release phase-changed: Monday, 04. February 2019 00:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy promote-to-updates: Pending -- ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811853/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811432] Re: linux-gcp: 4.15.0-1027.28~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-xenial ** Tags removed: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1813779 - phase: Holding before Release - phase-changed: Friday, 01. February 2019 11:01 UTC + phase: Release + phase-changed: Monday, 04. February 2019 00:19 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-security: Holding -- cycle not ready to release - promote-to-updates: Holding -- cycle not ready to release + promote-to-security: Pending -- ready to copy + promote-to-updates: Pending -- ready to copy -- 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/1811432 Title: linux-gcp: 4.15.0-1027.28~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed 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: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released 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: 1813779 phase: Release phase-changed: Monday, 04. February 2019 00:19 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy promote-to-updates: Pending -- ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811432/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811846] Re: linux: 4.4.0-142.168 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-xenial ** Tags removed: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1811847 (linux-aws), bug 1811848 (linux-lts-xenial) derivatives: bug 1811851 (linux-aws), bug 1811852 (linux-euclid), bug 1811853 (linux-kvm), bug 1811854 (linux-raspi2), bug 1811855 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true - phase: Holding before Release - phase-changed: Friday, 01. February 2019 14:40 UTC + phase: Release + phase-changed: Monday, 04. February 2019 00:17 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-security: Holding -- cycle not ready to release - promote-to-updates: Holding -- cycle not ready to release + promote-to-security: Pending -- ready to copy + promote-to-updates: Pending -- ready to copy -- 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/1811846 Title: linux: 4.4.0-142.168 -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: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed 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-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released 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 1811847 (linux-aws), bug 1811848 (linux-lts-xenial) derivatives: bug 1811851 (linux-aws), bug 1811852 (linux-euclid), bug 1811853 (linux-kvm), bug 1811854 (linux-raspi2), bug 1811855 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Release phase-changed: Monday, 04. February 2019 00:17 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy promote-to-updates: Pending -- ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811846/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811412] Re: linux-raspi2: 4.18.0-1009.11 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-cosmic ** Tags removed: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811406 - phase: Holding before Release - phase-changed: Friday, 01. February 2019 10:56 UTC + phase: Release + phase-changed: Monday, 04. February 2019 00:15 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-security: Holding -- cycle not ready to release - promote-to-updates: Holding -- cycle not ready to release + promote-to-security: Pending -- ready to copy + promote-to-updates: Pending -- ready to copy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1811412 Title: linux-raspi2: 4.18.0-1009.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811406 phase: Release phase-changed: Monday, 04. February 2019 00:15 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy promote-to-updates: Pending -- ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811412/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811417] Re: linux-kvm: 4.18.0-1007.7 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-cosmic ** Tags removed: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811406 - phase: Holding before Release - phase-changed: Friday, 01. February 2019 11:03 UTC + phase: Release + phase-changed: Monday, 04. February 2019 00:14 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-security: Holding -- cycle not ready to release - promote-to-updates: Holding -- cycle not ready to release + promote-to-security: Pending -- ready to copy + promote-to-updates: Pending -- ready to copy -- 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/1811417 Title: linux-kvm: 4.18.0-1007.7 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811406 phase: Release phase-changed: Monday, 04. February 2019 00:14 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy promote-to-updates: Pending -- ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811417/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811414] Re: linux-aws: 4.18.0-1008.10 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-cosmic ** Tags removed: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811406 - phase: Holding before Release - phase-changed: Friday, 01. February 2019 11:02 UTC + phase: Release + phase-changed: Monday, 04. February 2019 00:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-security: Holding -- cycle not ready to release - promote-to-updates: Holding -- cycle not ready to release + promote-to-security: Pending -- ready to copy + promote-to-updates: Pending -- ready to copy -- 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/1811414 Title: linux-aws: 4.18.0-1008.10 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811406 phase: Release phase-changed: Monday, 04. February 2019 00:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy promote-to-updates: Pending -- ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811414/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811847] Re: linux-aws: 4.4.0-1038.41 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811846 phase: Holding before Release phase-changed: Friday, 01. February 2019 14:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-security: Holding -- cycle not ready to release - promote-to-updates: Holding -- cycle not ready to release + promote-to-security: Holding -- master bug not ready for release + promote-to-updates: Holding -- master bug not ready for release -- 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/1811847 Title: linux-aws: 4.4.0-1038.41 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811846 phase: Holding before Release phase-changed: Friday, 01. February 2019 14:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- master bug not ready for release promote-to-updates: Holding -- master bug not ready for release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811847/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811856] Re: linux: 3.13.0-165.215 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-trusty ** Tags removed: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1811857 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: true - phase: Holding before Release - phase-changed: Friday, 01. February 2019 12:40 UTC + phase: Release + phase-changed: Monday, 04. February 2019 00:18 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-security: Holding -- cycle not ready to release - promote-to-updates: Holding -- cycle not ready to release + promote-to-security: Pending -- ready to copy + promote-to-updates: Pending -- ready to copy -- 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/1811856 Title: linux: 3.13.0-165.215 -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: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1811857 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Release phase-changed: Monday, 04. February 2019 00:18 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy promote-to-updates: Pending -- ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811856/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811857] Re: linux-lts-trusty: 3.13.0-165.215~precise1 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811856 phase: Holding before Release phase-changed: Friday, 01. February 2019 12:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-security: Holding -- cycle not ready to release - promote-to-updates: Holding -- cycle not ready to release + promote-to-security: Holding -- master bug not ready for release + promote-to-updates: Holding -- master bug not ready for release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1811857 Title: linux-lts-trusty: 3.13.0-165.215~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811856 phase: Holding before Release phase-changed: Friday, 01. February 2019 12:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- master bug not ready for release promote-to-updates: Holding -- master bug not ready for release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811854] Re: linux-raspi2: 4.4.0-1103.111 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811846 phase: Holding before Release phase-changed: Friday, 01. February 2019 14:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-security: Holding -- cycle not ready to release - promote-to-updates: Holding -- cycle not ready to release + promote-to-security: Holding -- master bug not ready for release + promote-to-updates: Holding -- master bug not ready for release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1811854 Title: linux-raspi2: 4.4.0-1103.111 -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 promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 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: 1811846 phase: Holding before Release phase-changed: Friday, 01. February 2019 14:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- master bug not ready for release promote-to-updates: Holding -- master bug not ready for release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811854/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811853] Re: linux-kvm: 4.4.0-1040.46 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811846 phase: Holding before Release phase-changed: Friday, 01. February 2019 14:39 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-security: Holding -- cycle not ready to release - promote-to-updates: Holding -- cycle not ready to release + promote-to-security: Holding -- master bug not ready for release + promote-to-updates: Holding -- master bug not ready for release -- 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/1811853 Title: linux-kvm: 4.4.0-1040.46 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811846 phase: Holding before Release phase-changed: Friday, 01. February 2019 14:39 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- master bug not ready for release promote-to-updates: Holding -- master bug not ready for release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811853/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811406] Re: linux: 4.18.0-14.15 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-cosmic ** Tags removed: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1811407 (linux-hwe), bug 1811408 (linux-hwe-edge), bug 1811409 (linux-aws-edge), bug 1811410 (linux-azure-edge), bug 1811411 (linux-gcp-edge), bug 1811418 (linux-azure-edge) derivatives: bug 1811412 (linux-raspi2), bug 1811414 (linux-aws), bug 1811415 (linux-azure), bug 1811416 (linux-gcp), bug 1811417 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true - phase: Holding before Release - phase-changed: Friday, 01. February 2019 10:54 UTC + phase: Release + phase-changed: Monday, 04. February 2019 00:09 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-security: Holding -- cycle not ready to release - promote-to-updates: Holding -- cycle not ready to release + promote-to-security: Pending -- ready to copy + promote-to-updates: Pending -- ready to copy -- 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/1811406 Title: linux: 4.18.0-14.15 -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: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1811407 (linux-hwe), bug 1811408 (linux-hwe-edge), bug 1811409 (linux-aws-edge), bug 1811410 (linux-azure-edge), bug 1811411 (linux-gcp-edge), bug 1811418 (linux-azure-edge) derivatives: bug 1811412 (linux-raspi2), bug 1811414 (linux-aws), bug 1811415 (linux-azure), bug 1811416 (linux-gcp), bug 1811417 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Release phase-changed: Monday, 04. February 2019 00:09 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy promote-to-updates: Pending -- ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811406/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811851] Re: linux-aws: 4.4.0-1075.85 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811846 phase: Holding before Release phase-changed: Friday, 01. February 2019 14:39 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-security: Holding -- cycle not ready to release - promote-to-updates: Holding -- cycle not ready to release + promote-to-security: Holding -- master bug not ready for release + promote-to-updates: Holding -- master bug not ready for release -- 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/1811851 Title: linux-aws: 4.4.0-1075.85 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811846 phase: Holding before Release phase-changed: Friday, 01. February 2019 14:39 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- master bug not ready for release promote-to-updates: Holding -- master bug not ready for release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811851/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811422] Re: linux-aws: 4.15.0-1032.34 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-bionic ** Tags removed: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1813779 - phase: Holding before Release - phase-changed: Friday, 01. February 2019 10:58 UTC + phase: Release + phase-changed: Monday, 04. February 2019 00:02 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-security: Holding -- cycle not ready to release - promote-to-updates: Holding -- cycle not ready to release + promote-to-security: Pending -- ready to copy + promote-to-updates: Pending -- ready to copy -- 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/1811422 Title: linux-aws: 4.15.0-1032.34 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed 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: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1813779 phase: Release phase-changed: Monday, 04. February 2019 00:02 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy promote-to-updates: Pending -- ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811422/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811424] Re: linux-gcp: 4.15.0-1027.28 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-bionic ** Tags removed: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1813779 - phase: Holding before Release - phase-changed: Friday, 01. February 2019 10:53 UTC + phase: Release + phase-changed: Monday, 04. February 2019 00:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-security: Holding -- cycle not ready to release - promote-to-updates: Holding -- cycle not ready to release + promote-to-security: Pending -- ready to copy + promote-to-updates: Pending -- ready to copy -- 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/1811424 Title: linux-gcp: 4.15.0-1027.28 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed 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: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1813779 phase: Release phase-changed: Monday, 04. February 2019 00:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy promote-to-updates: Pending -- ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811424/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811416] Re: linux-gcp: 4.18.0-1006.7 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-cosmic ** Tags removed: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811406 - phase: Holding before Release - phase-changed: Friday, 01. February 2019 10:59 UTC + phase: Release + phase-changed: Monday, 04. February 2019 00:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-security: Holding -- cycle not ready to release - promote-to-updates: Holding -- cycle not ready to release + promote-to-security: Pending -- ready to copy + promote-to-updates: Pending -- ready to copy -- 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/1811416 Title: linux-gcp: 4.18.0-1006.7 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811406 phase: Release phase-changed: Monday, 04. February 2019 00:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy promote-to-updates: Pending -- ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811416/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811420] Re: linux-raspi2: 4.15.0-1031.33 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-bionic ** Tags removed: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1813779 - phase: Holding before Release - phase-changed: Friday, 01. February 2019 11:00 UTC + phase: Release + phase-changed: Monday, 04. February 2019 00:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-security: Holding -- cycle not ready to release - promote-to-updates: Holding -- cycle not ready to release + promote-to-security: Pending -- ready to copy + promote-to-updates: Pending -- ready to copy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1811420 Title: linux-raspi2: 4.15.0-1031.33 -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 promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1813779 phase: Release phase-changed: Monday, 04. February 2019 00:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy promote-to-updates: Pending -- ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811425] Re: linux-kvm: 4.15.0-1029.29 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-bionic ** Tags removed: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1813779 - phase: Holding before Release - phase-changed: Friday, 01. February 2019 10:56 UTC + phase: Release + phase-changed: Monday, 04. February 2019 00:04 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-security: Holding -- cycle not ready to release - promote-to-updates: Holding -- cycle not ready to release + promote-to-security: Pending -- ready to copy + promote-to-updates: Pending -- ready to copy -- 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/1811425 Title: linux-kvm: 4.15.0-1029.29 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1813779 phase: Release phase-changed: Monday, 04. February 2019 00:04 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy promote-to-updates: Pending -- ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811425/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806695] Re: Touchpad not detected
*** This bug is a duplicate of bug 1802712 *** https://bugs.launchpad.net/bugs/1802712 ** Changed in: linux (Ubuntu) Status: Fix Released => Fix Committed ** Tags added: kernel-fixed-upstream ** Changed in: linux (Ubuntu) Status: Fix Committed => Confirmed ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Dan Schwarz (rednblk) -- 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/1806695 Title: Touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Laptop Model: Lenovo ideapad 330-15ARR Model Name: 81D2 Ubuntu Version: 18.04 LTS cat /proc/version_signature Ubuntu 4.15.0-42.45-generic 4.15.18 The touchpad didn't worked from the beginning and seems to be not detected. /proc/bus/input/devices doesn't show it. Dmesg output: ~$ dmesg | grep -i i2c [1.268675] i2c /dev entries driver [1.454039] i2c_hid i2c-ELAN061E:00: i2c-ELAN061E:00 supply vdd not found, using dummy regulator ~$ dmesg | grep -i i8042 [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=014f4a02-c22c-4497-beef-d038781a3158 ro quiet splash i8042.reset i8042.nomux=1 i8042.nopnp i8042.noloop vt.handoff=1 [0.00] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=014f4a02-c22c-4497-beef-d038781a3158 ro quiet splash i8042.reset i8042.nomux=1 i8042.nopnp i8042.noloop vt.handoff=1 [1.252982] i8042: PNP detection disabled [1.267585] serio: i8042 KBD port at 0x60,0x64 irq 1 [1.267589] serio: i8042 AUX port at 0x60,0x64 irq 12 [1.278595] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3 and lspci -vnvn attached --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rednblk1643 F pulseaudio /dev/snd/controlC0: rednblk1643 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-12-03 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 81D2 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=014f4a02-c22c-4497-beef-d038781a3158 ro quiet splash i8042.nopnp vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 Tags: bionic Uname: Linux 4.15.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/16/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7VCN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15ARR dmi.modalias: dmi:bvnLENOVO:bvr7VCN44WW:bd08/16/2018:svnLENOVO:pn81D2:pvrLenovoideapad330-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0E50510NODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15ARR: dmi.product.family: ideapad 330-15ARR dmi.product.name: 81D2 dmi.product.version: Lenovo ideapad 330-15ARR dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806695/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787857] Re: USB mouse cursor lags after random time of correct behaviour
Also subscribing rtirq since this may be related. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: rtirq (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/1787857 Title: USB mouse cursor lags after random time of correct behaviour Status in Ubuntu Studio: Incomplete Status in linux package in Ubuntu: Confirmed Status in rtirq package in Ubuntu: Confirmed Bug description: I installed Ubuntu Studio 18.04.1 LTS. After the first apt-get update I noticed the following behaviour: after havig logged in, my USB mouse works normally for about ten seconds, then the cursor starts lagging a lot which makes the mouse pretty much unusable. The last dmesg always contain lines these: (more in attached file) [<9e659b0c>] irq_default_primary_handler threaded [] usb_hcd_irq [<9e659b0c>] irq_default_primary_handler threaded [ ] _rtl_pci_interrupt [rtl_pci] Disabling IRQ #18 Out of frustration & curiosity I disabled most autostart apps (Settings > Session ... > Autostart) and re-enabled them after rebooting. Since then I rarely encounter the lagging cursor. If I open Settings > Mouse & Touchpad and toggle any option on/off the cursor starts lagging. How can make the cursor work reliably? Some comment in dmesg mentions "irqpoll" boot option Ubuntu Studio 18.04.1 4.15.0-20-lowlatency #21-Ubuntu SMP PREEMPT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntustudio/+bug/1787857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787857] Re: USB mouse cursor lags after random time of correct behaviour
Still need to know hardware specifics. I, for one, have AMD Graphics which exhibits this behavior without some AMD-specific kernel parameters in the command line in grub. Either way, subscribing the kernel package to this as well. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: rtirq (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/1787857 Title: USB mouse cursor lags after random time of correct behaviour Status in Ubuntu Studio: Incomplete Status in linux package in Ubuntu: Confirmed Status in rtirq package in Ubuntu: Confirmed Bug description: I installed Ubuntu Studio 18.04.1 LTS. After the first apt-get update I noticed the following behaviour: after havig logged in, my USB mouse works normally for about ten seconds, then the cursor starts lagging a lot which makes the mouse pretty much unusable. The last dmesg always contain lines these: (more in attached file) [<9e659b0c>] irq_default_primary_handler threaded [] usb_hcd_irq [<9e659b0c>] irq_default_primary_handler threaded [ ] _rtl_pci_interrupt [rtl_pci] Disabling IRQ #18 Out of frustration & curiosity I disabled most autostart apps (Settings > Session ... > Autostart) and re-enabled them after rebooting. Since then I rarely encounter the lagging cursor. If I open Settings > Mouse & Touchpad and toggle any option on/off the cursor starts lagging. How can make the cursor work reliably? Some comment in dmesg mentions "irqpoll" boot option Ubuntu Studio 18.04.1 4.15.0-20-lowlatency #21-Ubuntu SMP PREEMPT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntustudio/+bug/1787857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1721909] Re: Goodix GF3208 (fingerprint reader) not being recognised by kernel/system
Likewise: Dell Inspiron 17 7000 2-in-1 # lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671b Microdia Bus 001 Device 002: ID 27c6:538c Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Happy to help with testing (don't know much about coding). Thanks in advance to anyone able to advance this. -- 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/1721909 Title: Goodix GF3208 (fingerprint reader) not being recognised by kernel/system Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: The Goodix GF3208 is not being recognised by the system (Dell Inspiron 15 7577). What's worse is that it isn't even showing the manufacturer vendor id information when doing: $ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 27c6:5301 Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 005: ID 0bda:5652 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Note that the vendor id 27c6 should at least say "Shenzhen Huiding Technology Co., Ltd." as per https://github.com/torvalds/linux/blob/e19b205be43d11bff638cad4487008c48d21c103/Documentation/devicetree/bindings /vendor-prefixes.txt Will/has support been made for the Goodix GF3208 Fingerprint reader/scanner? Thanks in advance, Haz ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-35-generic 4.10.0-35.39~16.04.1 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 7 04:03:25 2017 InstallationDate: Installed on 2017-10-01 (5 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1721909/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752251] Re: Missing mcelog userspace package in bionic - or maybe linux kernel config should disable mcelog_legacy
As long as there is no working alternative I would like to have mcelog back. Some tool to get hardware error messages is rather important, I think. Actually I already built mce from sources (and it works fine), but on general principles it'd be nicer to have it packaged properly. -- 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/1752251 Title: Missing mcelog userspace package in bionic - or maybe linux kernel config should disable mcelog_legacy Status in linux package in Ubuntu: Confirmed Status in mcelog package in Ubuntu: Confirmed Bug description: There is no mcelog package in bionic. $ sudo apt install mcelog Reading package lists... Done Building dependency tree Reading state information... Done Package mcelog is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'mcelog' has no installation candidate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752251/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800839] Re: Dualshock3 hid_sony accelerometer not registering as joystick
'kernel-bug-exists-upstream' ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1800839 Title: Dualshock3 hid_sony accelerometer not registering as joystick Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: [12649.015762] input: Sony PLAYSTATION(R)3 Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/bluetooth/hci0/hci0:512/0005:054C:0268.0004/input/input25 [12649.015925] input: Sony PLAYSTATION(R)3 Controller as /devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/bluetooth/hci0/hci0:512/0005:054C:0268.0004/input/input24 [12649.016117] sony 0005:054C:0268.0004: input,hidraw3: BLUETOOTH HID v80.00 Joystick [Sony PLAYSTATION(R)3 Controller] on 60:f6:77:dd:db:90 4.15.0-38-generic #41-Ubuntu SMP Wed Oct 10 10:59:38 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux perhaps this is only a config issue as when the new split gyro & analog sticks/buttons/triggers both appeared as joysticks while you can now see only Sony PLAYSTATION(R)3 Controller(input24) registers as a joystick while Sony PLAYSTATION(R)3 Controller Motion Sensors (input25) does not. Any questions I am happy to respond, I have every reason to believe this is actually not a bluez issue but google gives me no returns other than general compatibility issues over the new hid_sony driver splitting the gyro from the pad. I use this to stay current on instrument flying while working out of town using FlightGear flight simulator, the PS3 gyro is an excellent yoke simulator that fis in my laptop bag. thanks dave ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: MATE Date: Wed Oct 31 15:06:00 2018 InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUSTeK COMPUTER INC. GL503VD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=ec87be72-8832-43e4-a6d1-08c4d60d73b1 ro quiet splash modprobe.blacklist=nouveau vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-08-01 (90 days ago) dmi.bios.date: 03/13/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL503VD.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL503VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL503VD.307:bd03/13/2018:svnASUSTeKCOMPUTERINC.:pnGL503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: GL503VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0:Type: Primary Bus: USB BD Address: 60:F6:77:DD:DB:90 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:624605 acl:10743 sco:0 events:125 errors:0 TX bytes:5814 acl:12 sco:0 commands:106 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1800839/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
Hey All. I run into troubles with sound also on my Asus UX331UAL (EG022T) laptop with ALC294 sound card. I run Kubuntu 18.04. I confirmed that after updating kernel to v4.19.19 Sound works well. Updated only kernel without any patches. Updated using Ukuu app. And it is not depending form method of shutdown windows OS (shutdown or restart). Thanks this topic) PS: I also run into other troubles. When laptop in sleep mode when running Kubuntu battery is not charging (battery led not lighting). When I trying to charge laptop when Kubuntu work normally, the battery starts charging (battery led lighting), but it never finishes charging and led always lighting with orange. When I shutting down my laptop battery charging in normal mode. Also, all works perfectly in Windows. Did the anyone run into such troubles? And I will appreciate if anyone can forward me to the solution for this issue. -- 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811415] Re: linux-azure: 4.18.0-1008.8 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811406 phase: Holding before Release phase-changed: Friday, 01. February 2019 10:53 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-security: Holding -- cycle not ready to release - promote-to-updates: Holding -- cycle not ready to release + promote-to-security: Holding -- package in development blackout + promote-to-updates: Holding -- package in development blackout -- 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/1811415 Title: linux-azure: 4.18.0-1008.8 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811406 phase: Holding before Release phase-changed: Friday, 01. February 2019 10:53 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- package in development blackout promote-to-updates: Holding -- package in development blackout To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811415/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811423] Re: linux-azure: 4.15.0-1037.39 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1813779 phase: Holding before Release phase-changed: Friday, 01. February 2019 11:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-security: Holding -- cycle not ready to release - promote-to-updates: Holding -- cycle not ready to release + promote-to-security: Holding -- package in development blackout + promote-to-updates: Holding -- package in development blackout -- 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/1811423 Title: linux-azure: 4.15.0-1037.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1813779 phase: Holding before Release phase-changed: Friday, 01. February 2019 11:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- package in development blackout promote-to-updates: Holding -- package in development blackout To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811423/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811431] Re: linux-azure: 4.15.0-1037.39~16.04.1 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1813779 phase: Holding before Release phase-changed: Friday, 01. February 2019 10:57 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-security: Holding -- cycle not ready to release - promote-to-updates: Holding -- cycle not ready to release + promote-to-security: Holding -- package in development blackout + promote-to-updates: Holding -- package in development blackout -- 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/1811431 Title: linux-azure: 4.15.0-1037.39~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1813779 phase: Holding before Release phase-changed: Friday, 01. February 2019 10:57 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- package in development blackout promote-to-updates: Holding -- package in development blackout To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811431/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811429] Re: linux-azure: 4.15.0-1037.39~14.04.2 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1813779 phase: Holding before Release phase-changed: Friday, 01. February 2019 11:00 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-security: Holding -- cycle not ready to release - promote-to-updates: Holding -- cycle not ready to release + promote-to-security: Holding -- package in development blackout + promote-to-updates: Holding -- package in development blackout -- 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/1811429 Title: linux-azure: 4.15.0-1037.39~14.04.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1813779 phase: Holding before Release phase-changed: Friday, 01. February 2019 11:00 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- package in development blackout promote-to-updates: Holding -- package in development blackout To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811429/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814439] Re: No login on the text console (tty) more possible (4.15.0-45)
*** This bug is a duplicate of bug 1812095 *** https://bugs.launchpad.net/bugs/1812095 Hi, My system is a KDE Neon system and here the package "apport" is not installed. Can I attach the required log files manually here to the bug report. Which files are that? Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814439 Title: No login on the text console (tty) more possible (4.15.0-45) Status in linux package in Ubuntu: Incomplete Bug description: Dear Maintainer, When updating the kernel from 4.15.0-43 to 4.15.0-45, a fatal error occurs when logging in to the text console (multi-user target, Runlevel 3). After entering the login name (eg root) plus enter key, the cursor immediately moves on from the input prompt for the password, i. it sent an empty password for login. This is wrong and not correct. The cursor moves to enter the password, but jumps immediately. The error message "Login incorrect" appears four times. Then the erroneous login messages are cleared on the screen and it starts all over again. The bug also occurs with kernel 4.18.0-14, which I have installed as a trial, affecting at least two kernel versions of it 4.15.0-45 and 4.18.0-14. The error does not occur if you want to log in as root after starting the KDE desktop with the console. So the last working kernel is 4.15.0-42. The error does not occur if you want to log in as root after starting the KDE desktop with the console. Is the error already known neon or is there a bug report about it? What can you do that the login with the above mentioned kernel versions in the text console works again? Distribution: KDE neon User Edition 5.14 Kernel : 4.15.0-45-generic # cat /proc/version_signature Ubuntu 4.15.0-45.48-generic 4.15.18 regards Michael To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1803658] Re: XPS 9560 won't boot with this kernel version
Thanks. So maybe this still affects Bionic (4.15) but fixed in newer versions. ** Changed in: linux (Ubuntu) Status: Expired => 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/1803658 Title: XPS 9560 won't boot with this kernel version Status in linux package in Ubuntu: Fix Released Bug description: When booting with 4.15.0-39, only a black screen with a blinking cursor is shown. Tapping power button shuts down correctly. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adriaan1904 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19 InstallationDate: Installed on 2018-07-06 (132 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626 MachineType: Dell Inc. XPS 15 9560 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=121551ab-5f59-40b1-b0af-df73ec65f3c7 ro quiet splash acpi_rev_override=5 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 Tags: tara Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip games lpadmin plugdev sambashare sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/05/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.1 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.1:bd07/05/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803658/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813745] Re: ubuntu 18-04 hangs on graphical start with kernel 4-15-0-44
4.15.0-45 does not fix my problem. The boot continues to hang when gnome tries to start. I cannot "Ctrl-Alt-F1 (or any F?)", but I can ssh from another computer to this affected computer. Log files don't show anything remarkable to me, but I wouldn't know what was remarkable in all of the verbiage. The boot process was working fine in the week of Jan 28 2019 through, oh say Jan 31. The only way I can boot is tell grub to boot to 4.15.0-45-generic (recovery mode). The system comes up, but my display is affected. I have: Acer Aspire R15 Processor: Intel Core I5-7200 CPU @ 2.50Gz x 4 Graphics: Intel HD Graphics (620 (KabyLake GT2) x86/MMX/SSE2 OS type: 32-bit but when booted in recovery mode, it shows: Graphics: llvmpipe (llvm 6.0, 256 bits) uname -a shows: Linux AcerAspireR15 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:27:25 UTC 2019 i686 i686 i686 GNU/Linux This is a newly installed system so I cannot revert back to a 4.15.0-43 monitor (I reinstalled when I encountered this problem). Wanted to let yall know that the 4.15.0-45 update did not fix the problem for every computer. And, I don't know how to install one of the kernels at "https://people.canonical.com/~khfeng/lp1813663/;, and wouldn't know which one to install anyway. -- 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/1813745 Title: ubuntu 18-04 hangs on graphical start with kernel 4-15-0-44 Status in linux package in Ubuntu: Confirmed Bug description: I updated my machine's kernel to 4.15.0-44. After a restart the whole machine was messed up. The machine starts regularly up to the point, where the graphical interface would appear (rough guess). The monitor gets black (normal) to change the screen resolution. Unfortunately, the monitor never comes back to life. Nothing useful is displayed anymore and my input devices are non-functional. I cannot change to any tty not change the state of the Num-Lock-LED on the keyboard. 4.15.0-43 kernel boots fine from grub-menu. From there, demsg shows a crash in Intel video driver: [ 47.320244] [ cut here ] [ 47.320245] Unknown pixelformat 0x [ 47.320267] WARNING: CPU: 2 PID: 3603 at /build/linux-vxxS7y/linux-4.15.0/drivers/media/v4l2-core/v4l2-ioctl.c:1291 v4l_fill_fmtdesc+0xf41/0x1250 [videodev] [ 47.320267] Modules linked in: rfcomm hid_generic uhid algif_hash algif_skcipher af_alg thunderbolt xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 cdc_ether usbnet iptable_nat nf_nat_ipv4 nf_nat ipheth r8152 mii snd_usb_audio snd_usbmidi_lib msr nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp cmac bridge stp llc bnep uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core videodev media arc4 btusb btrtl btbcm btintel bluetooth ecdh_generic ebtable_filter ebtables devlink ip6table_filter ip6_tables pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) iptable_filter vboxdrv(O) snd_hda_codec_hdmi hid_multitouch snd_hda_codec_realtek dell_laptop snd_hda_codec_generic snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp [ 47.320292] snd_soc_sst_ipc snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine intel_rapl x86_pkg_temp_thermal intel_powerclamp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf binfmt_misc kvm_intel kvm irqbypass joydev input_leds nls_iso8859_1 serio_raw snd_hda_intel dell_wmi snd_hda_codec dell_smbios dcdbas snd_hda_core dell_wmi_descriptor snd_hwdep wmi_bmof intel_wmi_thunderbolt snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd soundcore ath10k_pci ath10k_core ath mac80211 idma64 virt_dma cfg80211 rtsx_pci_ms memstick mei_me intel_lpss_pci processor_thermal_device shpchp mei intel_lpss intel_soc_dts_iosf intel_pch_thermal int3403_thermal int340x_thermal_zone [ 47.320325] intel_hid int3400_thermal mac_hid acpi_thermal_rel acpi_pad sparse_keymap sch_fq_codel coretemp parport_pc ppdev lp parport sunrpc ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq uas usb_storage hid_logitech_hidpp hid_logitech_dj usbhid rtsx_pci_sdmmc i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect psmouse sysimgblt nvme fb_sys_fops i2c_i801 nvme_core drm rtsx_pci i2c_hid wmi hid video pinctrl_sunrisepoint [ 47.320346] CPU: 2 PID: 3603 Comm: AudioThread Tainted: G O 4.15.0-43-generic #46-Ubuntu [ 47.320347] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.6.3 11/04/2018 [ 47.320350] RIP: 0010:v4l_fill_fmtdesc+0xf41/0x1250 [videodev] [ 47.320350] RSP: 0018:a8cc4530bc30 EFLAGS: 00010282 [ 47.320351] RAX: RBX: a8cc4530bd68 RCX: 0006 [ 47.320352] RDX: 0007
[Kernel-packages] [Bug 1813745] Re: ubuntu 18-04 hangs on graphical start with kernel 4-15-0-44
Is it possible to boot under -45, reboot to -43, then attach output of `journalctl -b -1 -k`? ** This bug is no longer a duplicate of bug 1813663 External monitors does not work anymore 4.15.0-44 -- 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/1813745 Title: ubuntu 18-04 hangs on graphical start with kernel 4-15-0-44 Status in linux package in Ubuntu: Confirmed Bug description: I updated my machine's kernel to 4.15.0-44. After a restart the whole machine was messed up. The machine starts regularly up to the point, where the graphical interface would appear (rough guess). The monitor gets black (normal) to change the screen resolution. Unfortunately, the monitor never comes back to life. Nothing useful is displayed anymore and my input devices are non-functional. I cannot change to any tty not change the state of the Num-Lock-LED on the keyboard. 4.15.0-43 kernel boots fine from grub-menu. From there, demsg shows a crash in Intel video driver: [ 47.320244] [ cut here ] [ 47.320245] Unknown pixelformat 0x [ 47.320267] WARNING: CPU: 2 PID: 3603 at /build/linux-vxxS7y/linux-4.15.0/drivers/media/v4l2-core/v4l2-ioctl.c:1291 v4l_fill_fmtdesc+0xf41/0x1250 [videodev] [ 47.320267] Modules linked in: rfcomm hid_generic uhid algif_hash algif_skcipher af_alg thunderbolt xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 cdc_ether usbnet iptable_nat nf_nat_ipv4 nf_nat ipheth r8152 mii snd_usb_audio snd_usbmidi_lib msr nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp cmac bridge stp llc bnep uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core videodev media arc4 btusb btrtl btbcm btintel bluetooth ecdh_generic ebtable_filter ebtables devlink ip6table_filter ip6_tables pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) iptable_filter vboxdrv(O) snd_hda_codec_hdmi hid_multitouch snd_hda_codec_realtek dell_laptop snd_hda_codec_generic snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp [ 47.320292] snd_soc_sst_ipc snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine intel_rapl x86_pkg_temp_thermal intel_powerclamp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf binfmt_misc kvm_intel kvm irqbypass joydev input_leds nls_iso8859_1 serio_raw snd_hda_intel dell_wmi snd_hda_codec dell_smbios dcdbas snd_hda_core dell_wmi_descriptor snd_hwdep wmi_bmof intel_wmi_thunderbolt snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd soundcore ath10k_pci ath10k_core ath mac80211 idma64 virt_dma cfg80211 rtsx_pci_ms memstick mei_me intel_lpss_pci processor_thermal_device shpchp mei intel_lpss intel_soc_dts_iosf intel_pch_thermal int3403_thermal int340x_thermal_zone [ 47.320325] intel_hid int3400_thermal mac_hid acpi_thermal_rel acpi_pad sparse_keymap sch_fq_codel coretemp parport_pc ppdev lp parport sunrpc ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq uas usb_storage hid_logitech_hidpp hid_logitech_dj usbhid rtsx_pci_sdmmc i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect psmouse sysimgblt nvme fb_sys_fops i2c_i801 nvme_core drm rtsx_pci i2c_hid wmi hid video pinctrl_sunrisepoint [ 47.320346] CPU: 2 PID: 3603 Comm: AudioThread Tainted: G O 4.15.0-43-generic #46-Ubuntu [ 47.320347] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.6.3 11/04/2018 [ 47.320350] RIP: 0010:v4l_fill_fmtdesc+0xf41/0x1250 [videodev] [ 47.320350] RSP: 0018:a8cc4530bc30 EFLAGS: 00010282 [ 47.320351] RAX: RBX: a8cc4530bd68 RCX: 0006 [ 47.320352] RDX: 0007 RSI: 0086 RDI: 8c8d6e496490 [ 47.320352] RBP: a8cc4530bc40 R08: 0001 R09: 04c7 [ 47.320353] R10: 8c8d5abe2d00 R11: R12: 8c8cda86c500 [ 47.320353] R13: c11bc900 R14: 8c8d5abe2d80 R15: 8c8cda86c500 [ 47.320354] FS: 7f9ad4ff9700() GS:8c8d6e48() knlGS: [ 47.320355] CS: 0010 DS: ES: CR0: 80050033 [ 47.320355] CR2: 7ff9f0083905 CR3: 00043fd80006 CR4: 003606e0 [ 47.320356] Call Trace: [ 47.320360] v4l_enum_fmt+0x74/0x110 [videodev] [ 47.320362] __video_do_ioctl+0x370/0x380 [videodev] [ 47.320364] ? terminate_walk+0x8e/0xf0 [ 47.320366] ? aa_path_perm+0xe2/0x130 [ 47.320367] ? aa_path_perm+0xf6/0x130 [ 47.320370] video_usercopy+0x24d/0x640 [videodev] [ 47.320372] ? video_ioctl2+0x20/0x20 [videodev] [ 47.320374] video_ioctl2+0x15/0x20 [videodev] [ 47.320376] v4l2_ioctl+0xc8/0xf0 [videodev] [ 47.320378]
[Kernel-packages] [Bug 1814439] Re: No login on the text console (tty) more possible (4.15.0-45)
*** This bug is a duplicate of bug 1812095 *** https://bugs.launchpad.net/bugs/1812095 ** This bug has been marked a duplicate of bug 1814293 4.15.0-44-generic kernel tty doesn't wait for password ** This bug is no longer a duplicate of bug 1814293 4.15.0-44-generic kernel tty doesn't wait for password ** This bug has been marked a duplicate of bug 1812095 console login loop after entering username followed by RETURN -- 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/1814439 Title: No login on the text console (tty) more possible (4.15.0-45) Status in linux package in Ubuntu: Incomplete Bug description: Dear Maintainer, When updating the kernel from 4.15.0-43 to 4.15.0-45, a fatal error occurs when logging in to the text console (multi-user target, Runlevel 3). After entering the login name (eg root) plus enter key, the cursor immediately moves on from the input prompt for the password, i. it sent an empty password for login. This is wrong and not correct. The cursor moves to enter the password, but jumps immediately. The error message "Login incorrect" appears four times. Then the erroneous login messages are cleared on the screen and it starts all over again. The bug also occurs with kernel 4.18.0-14, which I have installed as a trial, affecting at least two kernel versions of it 4.15.0-45 and 4.18.0-14. The error does not occur if you want to log in as root after starting the KDE desktop with the console. So the last working kernel is 4.15.0-42. The error does not occur if you want to log in as root after starting the KDE desktop with the console. Is the error already known neon or is there a bug report about it? What can you do that the login with the above mentioned kernel versions in the text console works again? Distribution: KDE neon User Edition 5.14 Kernel : 4.15.0-45-generic # cat /proc/version_signature Ubuntu 4.15.0-45.48-generic 4.15.18 regards Michael To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1813745] Re: ubuntu 18-04 hangs on graphical start with kernel 4-15-0-44
*** This bug is a duplicate of bug 1813663 *** https://bugs.launchpad.net/bugs/1813663 Hi Kai, I (the original bug reporter) have the same issue on my Dell 9370: - 4.15.0-43 boots fine - 4.15.0-44 hangs at or before login GUI - your 4.0.15-45 test kernel boots fine - the official 4.0.15-45 signed kernel made available on software update the day after your test kernel hangs at or before GUI So I have reverted to 4.15.0-43; the bug is in fact not fixed in the official 4.0.15-45. What is probably misleading is that my bug was made a duplicate of another bug related to boot problems with second screen or dock stations; which in fact turns out to be a different problem, appearently fixed by the official -45 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/1813745 Title: ubuntu 18-04 hangs on graphical start with kernel 4-15-0-44 Status in linux package in Ubuntu: Confirmed Bug description: I updated my machine's kernel to 4.15.0-44. After a restart the whole machine was messed up. The machine starts regularly up to the point, where the graphical interface would appear (rough guess). The monitor gets black (normal) to change the screen resolution. Unfortunately, the monitor never comes back to life. Nothing useful is displayed anymore and my input devices are non-functional. I cannot change to any tty not change the state of the Num-Lock-LED on the keyboard. 4.15.0-43 kernel boots fine from grub-menu. From there, demsg shows a crash in Intel video driver: [ 47.320244] [ cut here ] [ 47.320245] Unknown pixelformat 0x [ 47.320267] WARNING: CPU: 2 PID: 3603 at /build/linux-vxxS7y/linux-4.15.0/drivers/media/v4l2-core/v4l2-ioctl.c:1291 v4l_fill_fmtdesc+0xf41/0x1250 [videodev] [ 47.320267] Modules linked in: rfcomm hid_generic uhid algif_hash algif_skcipher af_alg thunderbolt xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 cdc_ether usbnet iptable_nat nf_nat_ipv4 nf_nat ipheth r8152 mii snd_usb_audio snd_usbmidi_lib msr nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp cmac bridge stp llc bnep uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core videodev media arc4 btusb btrtl btbcm btintel bluetooth ecdh_generic ebtable_filter ebtables devlink ip6table_filter ip6_tables pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) iptable_filter vboxdrv(O) snd_hda_codec_hdmi hid_multitouch snd_hda_codec_realtek dell_laptop snd_hda_codec_generic snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp [ 47.320292] snd_soc_sst_ipc snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine intel_rapl x86_pkg_temp_thermal intel_powerclamp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf binfmt_misc kvm_intel kvm irqbypass joydev input_leds nls_iso8859_1 serio_raw snd_hda_intel dell_wmi snd_hda_codec dell_smbios dcdbas snd_hda_core dell_wmi_descriptor snd_hwdep wmi_bmof intel_wmi_thunderbolt snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd soundcore ath10k_pci ath10k_core ath mac80211 idma64 virt_dma cfg80211 rtsx_pci_ms memstick mei_me intel_lpss_pci processor_thermal_device shpchp mei intel_lpss intel_soc_dts_iosf intel_pch_thermal int3403_thermal int340x_thermal_zone [ 47.320325] intel_hid int3400_thermal mac_hid acpi_thermal_rel acpi_pad sparse_keymap sch_fq_codel coretemp parport_pc ppdev lp parport sunrpc ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq uas usb_storage hid_logitech_hidpp hid_logitech_dj usbhid rtsx_pci_sdmmc i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect psmouse sysimgblt nvme fb_sys_fops i2c_i801 nvme_core drm rtsx_pci i2c_hid wmi hid video pinctrl_sunrisepoint [ 47.320346] CPU: 2 PID: 3603 Comm: AudioThread Tainted: G O 4.15.0-43-generic #46-Ubuntu [ 47.320347] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.6.3 11/04/2018 [ 47.320350] RIP: 0010:v4l_fill_fmtdesc+0xf41/0x1250 [videodev] [ 47.320350] RSP: 0018:a8cc4530bc30 EFLAGS: 00010282 [ 47.320351] RAX: RBX: a8cc4530bd68 RCX: 0006 [ 47.320352] RDX: 0007 RSI: 0086 RDI: 8c8d6e496490 [ 47.320352] RBP: a8cc4530bc40 R08: 0001 R09: 04c7 [ 47.320353] R10: 8c8d5abe2d00 R11: R12: 8c8cda86c500 [ 47.320353] R13: c11bc900 R14: 8c8d5abe2d80 R15: 8c8cda86c500 [ 47.320354] FS: 7f9ad4ff9700() GS:8c8d6e48() knlGS: [ 47.320355] CS: 0010 DS: ES: CR0: 80050033 [ 47.320355] CR2: 7ff9f0083905 CR3: 00043fd80006 CR4:
[Kernel-packages] [Bug 1814439] 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 1814439 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/1814439 Title: No login on the text console (tty) more possible (4.15.0-45) Status in linux package in Ubuntu: Incomplete Bug description: Dear Maintainer, When updating the kernel from 4.15.0-43 to 4.15.0-45, a fatal error occurs when logging in to the text console (multi-user target, Runlevel 3). After entering the login name (eg root) plus enter key, the cursor immediately moves on from the input prompt for the password, i. it sent an empty password for login. This is wrong and not correct. The cursor moves to enter the password, but jumps immediately. The error message "Login incorrect" appears four times. Then the erroneous login messages are cleared on the screen and it starts all over again. The bug also occurs with kernel 4.18.0-14, which I have installed as a trial, affecting at least two kernel versions of it 4.15.0-45 and 4.18.0-14. The error does not occur if you want to log in as root after starting the KDE desktop with the console. So the last working kernel is 4.15.0-42. The error does not occur if you want to log in as root after starting the KDE desktop with the console. Is the error already known neon or is there a bug report about it? What can you do that the login with the above mentioned kernel versions in the text console works again? Distribution: KDE neon User Edition 5.14 Kernel : 4.15.0-45-generic # cat /proc/version_signature Ubuntu 4.15.0-45.48-generic 4.15.18 regards Michael To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814440] [NEW] Bluetooth switches off automatically
Public bug reported: Buetooth will switch automatically when i try to connect to my speaker. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 3 14:13:24 2019 InstallationDate: Installed on 2019-01-09 (24 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80J2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=215a5782-5ca0-46f3-9fcf-f3a8c1e344db ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/02/2016 dmi.bios.vendor: LENOVO dmi.bios.version: A8CN54WW(V3.07) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo E50-80 dmi.board.vendor: LENOVO dmi.board.version: 31900056 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo E50-80 dmi.modalias: dmi:bvnLENOVO:bvrA8CN54WW(V3.07):bd09/02/2016:svnLENOVO:pn80J2:pvrLenovoE50-80:rvnLENOVO:rnLenovoE50-80:rvr31900056WIN:cvnLENOVO:ct10:cvrLenovoE50-80: dmi.product.family: IDEAPAD dmi.product.name: 80J2 dmi.product.version: Lenovo E50-80 dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: B8:86:87:44:55:70 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:748 acl:0 sco:0 events:59 errors:0 TX bytes:4892 acl:0 sco:0 commands:59 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1814440 Title: Bluetooth switches off automatically Status in bluez package in Ubuntu: New Bug description: Buetooth will switch automatically when i try to connect to my speaker. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 3 14:13:24 2019 InstallationDate: Installed on 2019-01-09 (24 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80J2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=215a5782-5ca0-46f3-9fcf-f3a8c1e344db ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/02/2016 dmi.bios.vendor: LENOVO dmi.bios.version: A8CN54WW(V3.07) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo E50-80 dmi.board.vendor: LENOVO dmi.board.version: 31900056 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo E50-80 dmi.modalias: dmi:bvnLENOVO:bvrA8CN54WW(V3.07):bd09/02/2016:svnLENOVO:pn80J2:pvrLenovoE50-80:rvnLENOVO:rnLenovoE50-80:rvr31900056WIN:cvnLENOVO:ct10:cvrLenovoE50-80: dmi.product.family: IDEAPAD dmi.product.name: 80J2 dmi.product.version: Lenovo E50-80 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: B8:86:87:44:55:70 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:748 acl:0 sco:0 events:59 errors:0 TX bytes:4892 acl:0 sco:0 commands:59 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1814440/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814439] [NEW] No login on the text console (tty) more possible (4.15.0-45)
Public bug reported: Dear Maintainer, When updating the kernel from 4.15.0-43 to 4.15.0-45, a fatal error occurs when logging in to the text console (multi-user target, Runlevel 3). After entering the login name (eg root) plus enter key, the cursor immediately moves on from the input prompt for the password, i. it sent an empty password for login. This is wrong and not correct. The cursor moves to enter the password, but jumps immediately. The error message "Login incorrect" appears four times. Then the erroneous login messages are cleared on the screen and it starts all over again. The bug also occurs with kernel 4.18.0-14, which I have installed as a trial, affecting at least two kernel versions of it 4.15.0-45 and 4.18.0-14. The error does not occur if you want to log in as root after starting the KDE desktop with the console. So the last working kernel is 4.15.0-42. The error does not occur if you want to log in as root after starting the KDE desktop with the console. Is the error already known neon or is there a bug report about it? What can you do that the login with the above mentioned kernel versions in the text console works again? Distribution: KDE neon User Edition 5.14 Kernel : 4.15.0-45-generic # cat /proc/version_signature Ubuntu 4.15.0-45.48-generic 4.15.18 regards Michael ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "summary_lspci_and_dmesg.log" https://bugs.launchpad.net/bugs/1814439/+attachment/5235535/+files/summary_lspci_and_dmesg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814439 Title: No login on the text console (tty) more possible (4.15.0-45) Status in linux package in Ubuntu: New Bug description: Dear Maintainer, When updating the kernel from 4.15.0-43 to 4.15.0-45, a fatal error occurs when logging in to the text console (multi-user target, Runlevel 3). After entering the login name (eg root) plus enter key, the cursor immediately moves on from the input prompt for the password, i. it sent an empty password for login. This is wrong and not correct. The cursor moves to enter the password, but jumps immediately. The error message "Login incorrect" appears four times. Then the erroneous login messages are cleared on the screen and it starts all over again. The bug also occurs with kernel 4.18.0-14, which I have installed as a trial, affecting at least two kernel versions of it 4.15.0-45 and 4.18.0-14. The error does not occur if you want to log in as root after starting the KDE desktop with the console. So the last working kernel is 4.15.0-42. The error does not occur if you want to log in as root after starting the KDE desktop with the console. Is the error already known neon or is there a bug report about it? What can you do that the login with the above mentioned kernel versions in the text console works again? Distribution: KDE neon User Edition 5.14 Kernel : 4.15.0-45-generic # cat /proc/version_signature Ubuntu 4.15.0-45.48-generic 4.15.18 regards Michael To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic
This problem still exists for me on debian testing with 4.19.0-1-amd64 #1 SMP Debian 4.19.12-1 Only if I put my laptop directly next to a device emitting a wifi network I am able to connect. Few meters away it already becomes unusable. ant_sel=1 makes it worse. ant_sel=2 not better. Detailed information here: http://forums.debian.net/viewtopic.php?f=5=140368=691244#p691244 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1234 F pulseaudio /dev/snd/controlC0: al 1234 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Notebook Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8137 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.02 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1803658] Re: XPS 9560 won't boot with this kernel version
Hi, the problem is no longer there. My system works fine in the latest kernel (4.18.0-13) -- 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/1803658 Title: XPS 9560 won't boot with this kernel version Status in linux package in Ubuntu: Expired Bug description: When booting with 4.15.0-39, only a black screen with a blinking cursor is shown. Tapping power button shuts down correctly. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adriaan1904 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19 InstallationDate: Installed on 2018-07-06 (132 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626 MachineType: Dell Inc. XPS 15 9560 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=121551ab-5f59-40b1-b0af-df73ec65f3c7 ro quiet splash acpi_rev_override=5 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 Tags: tara Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip games lpadmin plugdev sambashare sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/05/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.1 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.1:bd07/05/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803658/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813683] Re: linux-image-4.15.0-44-generic tty login not work
*** This bug is a duplicate of bug 1812095 *** https://bugs.launchpad.net/bugs/1812095 Backport of LP: #1813873 should solve this. -- 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/1813683 Title: linux-image-4.15.0-44-generic tty login not work Status in linux package in Ubuntu: Incomplete Bug description: I just updated my ubuntu 18.04 and received the linux- image-4.15.0-44-generic. After update and reboot the machine, my computer starts normally. Seems boot normally but when gets to the login screen (I'm not use any kind of graphical login manager, boot pure on console/text) I just need to press enter (doesn't matter if type my login or not), then starts a loop, like if my 'enter' key has some kind of mechanical defect. Keeps pressing 'enter' until I do a CTRL-C. If I press enter key again, starts all over again. Periodically pressing 'enter' key in lapse of seconds. To prevent, I just had to boot using linux-image-4.15.0-43-generic and could login normally. What can I provide to you look this? I think it's my first time here or one of firsts Thanks in advanced. Regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813683/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814431] 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 1814431 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/1814431 Title: Touchpad not working on Ubuntu. Status in linux package in Ubuntu: Incomplete Bug description: Touchpad is not working on Ubuntu. I tried to reinstall and now it is giving an error. Model - Acer Predator PH315-51 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.6 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 3 15:38:48 2019 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=en_IN PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814431/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784152] Re: i2c_hid_get_input floods system logs
Once the SRU [1] has completed, the issue should be solved. [1] https://lists.ubuntu.com/archives/kernel- team/2019-January/098134.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/1784152 Title: i2c_hid_get_input floods system logs Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.15.0-29.31-generic 4.15.18 After upgrading to kernel version 4.15.0-29 from 4.15.0-23, the system logs are flooded whenever I move the cursor with my touchpad. It looks like this: i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) etc... This problem did not occur on the previous kernel version so there must have been a change to the "drivers/hid/i2c-hid/i2c-hid.c" file. This seems to be fixed in a recent commit here: https://github.com/torvalds/linux/commit/ef6eaf27274c0351f7059163918f3795da13199c I am currently running the older kernel version but would still like to be up to date without this flooding happening. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784152/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814431] Re: Touchpad not working on Ubuntu.
** Package changed: ubiquity (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/1814431 Title: Touchpad not working on Ubuntu. Status in linux package in Ubuntu: New Bug description: Touchpad is not working on Ubuntu. I tried to reinstall and now it is giving an error. Model - Acer Predator PH315-51 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.6 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 3 15:38:48 2019 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=en_IN PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814431/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1803658] Re: XPS 9560 won't boot with this kernel version
Sorry for the late reply. Can you enable -proposed, upgrade all packages and see if the problem still exists? The log in -42 doesn't show anything meaningful. So the error happens after the graphical session starts. -- 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/1803658 Title: XPS 9560 won't boot with this kernel version Status in linux package in Ubuntu: Expired Bug description: When booting with 4.15.0-39, only a black screen with a blinking cursor is shown. Tapping power button shuts down correctly. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adriaan1904 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19 InstallationDate: Installed on 2018-07-06 (132 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626 MachineType: Dell Inc. XPS 15 9560 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=121551ab-5f59-40b1-b0af-df73ec65f3c7 ro quiet splash acpi_rev_override=5 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 Tags: tara Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip games lpadmin plugdev sambashare sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/05/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.1 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.1:bd07/05/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803658/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814431] [NEW] Touchpad not working on Ubuntu.
You have been subscribed to a public bug: Touchpad is not working on Ubuntu. I tried to reinstall and now it is giving an error. Model - Acer Predator PH315-51 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.6 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 3 15:38:48 2019 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=en_IN PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.6 ubuntu -- Touchpad not working on Ubuntu. https://bugs.launchpad.net/bugs/1814431 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 1813745] Re: ubuntu 18-04 hangs on graphical start with kernel 4-15-0-44
*** This bug is a duplicate of bug 1813663 *** https://bugs.launchpad.net/bugs/1813663 Can you attach `dpkg -l | grep linux`? Maybe some packages are not correctly installed. -- 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/1813745 Title: ubuntu 18-04 hangs on graphical start with kernel 4-15-0-44 Status in linux package in Ubuntu: Confirmed Bug description: I updated my machine's kernel to 4.15.0-44. After a restart the whole machine was messed up. The machine starts regularly up to the point, where the graphical interface would appear (rough guess). The monitor gets black (normal) to change the screen resolution. Unfortunately, the monitor never comes back to life. Nothing useful is displayed anymore and my input devices are non-functional. I cannot change to any tty not change the state of the Num-Lock-LED on the keyboard. 4.15.0-43 kernel boots fine from grub-menu. From there, demsg shows a crash in Intel video driver: [ 47.320244] [ cut here ] [ 47.320245] Unknown pixelformat 0x [ 47.320267] WARNING: CPU: 2 PID: 3603 at /build/linux-vxxS7y/linux-4.15.0/drivers/media/v4l2-core/v4l2-ioctl.c:1291 v4l_fill_fmtdesc+0xf41/0x1250 [videodev] [ 47.320267] Modules linked in: rfcomm hid_generic uhid algif_hash algif_skcipher af_alg thunderbolt xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 cdc_ether usbnet iptable_nat nf_nat_ipv4 nf_nat ipheth r8152 mii snd_usb_audio snd_usbmidi_lib msr nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp cmac bridge stp llc bnep uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core videodev media arc4 btusb btrtl btbcm btintel bluetooth ecdh_generic ebtable_filter ebtables devlink ip6table_filter ip6_tables pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) iptable_filter vboxdrv(O) snd_hda_codec_hdmi hid_multitouch snd_hda_codec_realtek dell_laptop snd_hda_codec_generic snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp [ 47.320292] snd_soc_sst_ipc snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine intel_rapl x86_pkg_temp_thermal intel_powerclamp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf binfmt_misc kvm_intel kvm irqbypass joydev input_leds nls_iso8859_1 serio_raw snd_hda_intel dell_wmi snd_hda_codec dell_smbios dcdbas snd_hda_core dell_wmi_descriptor snd_hwdep wmi_bmof intel_wmi_thunderbolt snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd soundcore ath10k_pci ath10k_core ath mac80211 idma64 virt_dma cfg80211 rtsx_pci_ms memstick mei_me intel_lpss_pci processor_thermal_device shpchp mei intel_lpss intel_soc_dts_iosf intel_pch_thermal int3403_thermal int340x_thermal_zone [ 47.320325] intel_hid int3400_thermal mac_hid acpi_thermal_rel acpi_pad sparse_keymap sch_fq_codel coretemp parport_pc ppdev lp parport sunrpc ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq uas usb_storage hid_logitech_hidpp hid_logitech_dj usbhid rtsx_pci_sdmmc i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect psmouse sysimgblt nvme fb_sys_fops i2c_i801 nvme_core drm rtsx_pci i2c_hid wmi hid video pinctrl_sunrisepoint [ 47.320346] CPU: 2 PID: 3603 Comm: AudioThread Tainted: G O 4.15.0-43-generic #46-Ubuntu [ 47.320347] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.6.3 11/04/2018 [ 47.320350] RIP: 0010:v4l_fill_fmtdesc+0xf41/0x1250 [videodev] [ 47.320350] RSP: 0018:a8cc4530bc30 EFLAGS: 00010282 [ 47.320351] RAX: RBX: a8cc4530bd68 RCX: 0006 [ 47.320352] RDX: 0007 RSI: 0086 RDI: 8c8d6e496490 [ 47.320352] RBP: a8cc4530bc40 R08: 0001 R09: 04c7 [ 47.320353] R10: 8c8d5abe2d00 R11: R12: 8c8cda86c500 [ 47.320353] R13: c11bc900 R14: 8c8d5abe2d80 R15: 8c8cda86c500 [ 47.320354] FS: 7f9ad4ff9700() GS:8c8d6e48() knlGS: [ 47.320355] CS: 0010 DS: ES: CR0: 80050033 [ 47.320355] CR2: 7ff9f0083905 CR3: 00043fd80006 CR4: 003606e0 [ 47.320356] Call Trace: [ 47.320360] v4l_enum_fmt+0x74/0x110 [videodev] [ 47.320362] __video_do_ioctl+0x370/0x380 [videodev] [ 47.320364] ? terminate_walk+0x8e/0xf0 [ 47.320366] ? aa_path_perm+0xe2/0x130 [ 47.320367] ? aa_path_perm+0xf6/0x130 [ 47.320370] video_usercopy+0x24d/0x640 [videodev] [ 47.320372] ? video_ioctl2+0x20/0x20 [videodev] [ 47.320374] video_ioctl2+0x15/0x20 [videodev] [ 47.320376] v4l2_ioctl+0xc8/0xf0 [videodev] [ 47.320378] do_vfs_ioctl+0xa8/0x630 [