[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
** Changed in: json-c (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update Status in json-c package in Ubuntu: Fix Released Bug description: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0086 0f10ff6977efbf32 88003d45fe10 8140926b [ 99.996057] 81caddf8 88003d45fea8 88003d45fe98 81195a84 [ 99.996057] 8810 88003d45fea8 88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [] dump_stack+0x6d/0x92 [ 99.996057] [] panic+0xd3/0x227 [ 99.996057] [] do_exit+0xb9d/0xba0 [ 99.996057] [] do_group_exit+0x47/0xb0 [ 99.996057] [] SyS_exit_group+0x14/0x20 [ 99.996057] [] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
Can we close this bug? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update Status in json-c package in Ubuntu: Triaged Bug description: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0086 0f10ff6977efbf32 88003d45fe10 8140926b [ 99.996057] 81caddf8 88003d45fea8 88003d45fe98 81195a84 [ 99.996057] 8810 88003d45fea8 88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [] dump_stack+0x6d/0x92 [ 99.996057] [] panic+0xd3/0x227 [ 99.996057] [] do_exit+0xb9d/0xba0 [ 99.996057] [] do_group_exit+0x47/0xb0 [ 99.996057] [] SyS_exit_group+0x14/0x20 [ 99.996057] [] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
I have one instance that kernel panicked when it updated to 0.11-4ubuntu2.6 using auto updates. However I cannot confirm that I actually rebooted that instance after installing 0.11-4ubuntu2.5 So far none of my other instances panicked. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update Status in json-c package in Ubuntu: Triaged Bug description: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0086 0f10ff6977efbf32 88003d45fe10 8140926b [ 99.996057] 81caddf8 88003d45fea8 88003d45fe98 81195a84 [ 99.996057] 8810 88003d45fea8 88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [] dump_stack+0x6d/0x92 [ 99.996057] [] panic+0xd3/0x227 [ 99.996057] [] do_exit+0xb9d/0xba0 [ 99.996057] [] do_group_exit+0x47/0xb0 [ 99.996057] [] SyS_exit_group+0x14/0x20 [ 99.996057] [] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
@pandeyvinod.india: Can you help us try to understand why your instances are still panicing? - Do you have a copy of the panic string? - How did you update to the 0.11-4ubuntu2.6 package? - Did you reboot the instance after the package was installed? - Have any of the instances that previously paniced had a second panic? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update Status in json-c package in Ubuntu: Triaged Bug description: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0086 0f10ff6977efbf32 88003d45fe10 8140926b [ 99.996057] 81caddf8 88003d45fea8 88003d45fe98 81195a84 [ 99.996057] 8810 88003d45fea8 88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [] dump_stack+0x6d/0x92 [ 99.996057] [] panic+0xd3/0x227 [ 99.996057] [] do_exit+0xb9d/0xba0 [ 99.996057] [] do_group_exit+0x47/0xb0 [ 99.996057] [] SyS_exit_group+0x14/0x20 [ 99.996057] [] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
This package update is still braking few instances hosted on AWS. it is the same issue what we have seen in version "libjson-c2 0.11-4ubuntu2.1" and impacted a lot of users. same issue we are facing in the version libjson-c2/now 0.11-4ubuntu2.6 which caused few aws instances to go in kernel panic mode. do ubuntu have through testing before pushing update and what about revert back. can ubuntu revert back to previous package if unattended upgrade sees any error? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update Status in json-c package in Ubuntu: Triaged Bug description: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0086 0f10ff6977efbf32 88003d45fe10 8140926b [ 99.996057] 81caddf8 88003d45fea8 88003d45fe98 81195a84 [ 99.996057] 8810 88003d45fea8 88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [] dump_stack+0x6d/0x92 [ 99.996057] [] panic+0xd3/0x227 [ 99.996057] [] do_exit+0xb9d/0xba0 [ 99.996057] [] do_group_exit+0x47/0xb0 [ 99.996057] [] SyS_exit_group+0x14/0x20 [ 99.996057] [] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
@jfirebaugh: According to https://usn.ubuntu.com/4360-2/ The CVE fix is in the latest version. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update Status in json-c package in Ubuntu: Triaged Bug description: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0086 0f10ff6977efbf32 88003d45fe10 8140926b [ 99.996057] 81caddf8 88003d45fea8 88003d45fe98 81195a84 [ 99.996057] 8810 88003d45fea8 88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [] dump_stack+0x6d/0x92 [ 99.996057] [] panic+0xd3/0x227 [ 99.996057] [] do_exit+0xb9d/0xba0 [ 99.996057] [] do_group_exit+0x47/0xb0 [ 99.996057] [] SyS_exit_group+0x14/0x20 [ 99.996057] [] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
@cnewcomer, can you clarify whether or not 0.11-4ubuntu2.5 contains the (fixed) security update? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update Status in json-c package in Ubuntu: Triaged Bug description: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0086 0f10ff6977efbf32 88003d45fe10 8140926b [ 99.996057] 81caddf8 88003d45fea8 88003d45fe98 81195a84 [ 99.996057] 8810 88003d45fea8 88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [] dump_stack+0x6d/0x92 [ 99.996057] [] panic+0xd3/0x227 [ 99.996057] [] do_exit+0xb9d/0xba0 [ 99.996057] [] do_group_exit+0x47/0xb0 [ 99.996057] [] SyS_exit_group+0x14/0x20 [ 99.996057] [] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
So if I'm on 20.04, not running Upstart and not experiencing kernel panics, why would I want to install this 'update', re-introducing known security issues? Why is it even pushed to systems running 20.04 without Upstart? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update Status in json-c package in Ubuntu: Triaged Bug description: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0086 0f10ff6977efbf32 88003d45fe10 8140926b [ 99.996057] 81caddf8 88003d45fea8 88003d45fe98 81195a84 [ 99.996057] 8810 88003d45fea8 88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [] dump_stack+0x6d/0x92 [ 99.996057] [] panic+0xd3/0x227 [ 99.996057] [] do_exit+0xb9d/0xba0 [ 99.996057] [] do_group_exit+0x47/0xb0 [ 99.996057] [] SyS_exit_group+0x14/0x20 [ 99.996057] [] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
Official site released the fix about bionic and xenial: https://github.com/json-c/json-c/commit/f2b7d0b5cbd0eccf4fb3c1851ec0864952be1057 But above has a problem in lh_table_insert(): if t->count > INT_MAX * LH_LOAD_FACTOR then error return Thank you. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update Status in json-c package in Ubuntu: Triaged Bug description: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0086 0f10ff6977efbf32 88003d45fe10 8140926b [ 99.996057] 81caddf8 88003d45fea8 88003d45fe98 81195a84 [ 99.996057] 8810 88003d45fea8 88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [] dump_stack+0x6d/0x92 [ 99.996057] [] panic+0xd3/0x227 [ 99.996057] [] do_exit+0xb9d/0xba0 [ 99.996057] [] do_group_exit+0x47/0xb0 [ 99.996057] [] SyS_exit_group+0x14/0x20 [ 99.996057] [] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
I have a Xenial server with upstart. I've made patches for CVE-2020-12762. See: https://gist.github.com/h-yamamo/61161ea78f3bb7761e508ca531c7 Thank you. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-12762 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update Status in json-c package in Ubuntu: Triaged Bug description: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0086 0f10ff6977efbf32 88003d45fe10 8140926b [ 99.996057] 81caddf8 88003d45fea8 88003d45fe98 81195a84 [ 99.996057] 8810 88003d45fea8 88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [] dump_stack+0x6d/0x92 [ 99.996057] [] panic+0xd3/0x227 [ 99.996057] [] do_exit+0xb9d/0xba0 [ 99.996057] [] do_group_exit+0x47/0xb0 [ 99.996057] [] SyS_exit_group+0x14/0x20 [ 99.996057] [] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
FYI, version 0.11-4ubuntu2.5 was recently released. If you are still experiencing this issue, the following steps will correct it: 1. Remove the postinst file from the affected package (version 0.11-4ubuntu2.1): sudo rm /var/lib/dpkg/info/libjson-c2\:amd64.postinst 2. Re-run the package configure step to correct its half-installed status: sudo dpkg --configure -a 3. Update the package list from the repository: sudo apt update 4. Upgrade the affected package to the latest version: sudo apt install libjson-c2 5. Reboot to activate the new package: sudo reboot Any user running a version of the libjson-c2 package not equal to 0.11-4ubuntu2.1 will not have to go through these steps and updating the package to the new version will be done the normal way; either through unattended-updates or manual apt upgrade. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update Status in json-c package in Ubuntu: Triaged Bug description: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0086 0f10ff6977efbf32 88003d45fe10 8140926b [ 99.996057] 81caddf8 88003d45fea8 88003d45fe98 81195a84 [ 99.996057] 8810 88003d45fea8 88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [] dump_stack+0x6d/0x92 [ 99.996057] [] panic+0xd3/0x227 [ 99.996057] [] do_exit+0xb9d/0xba0 [ 99.996057] [] do_group_exit+0x47/0xb0 [ 99.996057] [] SyS_exit_group+0x14/0x20 [ 99.996057] [] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
> Just want to give a heads up that manual unpack followed by apt install -f still crashes as stated in comment 15, you MUST reboot between dpkg --unpack and apt install -f. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update Status in json-c package in Ubuntu: Triaged Bug description: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0086 0f10ff6977efbf32 88003d45fe10 8140926b [ 99.996057] 81caddf8 88003d45fea8 88003d45fe98 81195a84 [ 99.996057] 8810 88003d45fea8 88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [] dump_stack+0x6d/0x92 [ 99.996057] [] panic+0xd3/0x227 [ 99.996057] [] do_exit+0xb9d/0xba0 [ 99.996057] [] do_group_exit+0x47/0xb0 [ 99.996057] [] SyS_exit_group+0x14/0x20 [ 99.996057] [] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
@cekkent: Did you reboot between the "dpkg --unpack..." and "sudo apt install -f" steps? That reboot is incredibly important since it switches out the init process from the faulty one in 2.1 to the one in the 2.2 package. The "apt install -f" is intended to run the pre/post install scripts for the package to get it out if the half-installed state. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update Status in json-c package in Ubuntu: Triaged Bug description: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0086 0f10ff6977efbf32 88003d45fe10 8140926b [ 99.996057] 81caddf8 88003d45fea8 88003d45fe98 81195a84 [ 99.996057] 8810 88003d45fea8 88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [] dump_stack+0x6d/0x92 [ 99.996057] [] panic+0xd3/0x227 [ 99.996057] [] do_exit+0xb9d/0xba0 [ 99.996057] [] do_group_exit+0x47/0xb0 [ 99.996057] [] SyS_exit_group+0x14/0x20 [ 99.996057] [] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
Just want to give a heads up that manual unpack followed by apt install -f still crashes, however the VM automatically rebooted this time (instead of remaining dead) and I was able to proceed with usual apt update afterwards with no further issues. root@web1:~# curl -LO https://launchpad.net/ubuntu/+archive/primary/+files/libjson-c2_0.11-4ubuntu2.2_amd64.deb % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 21858 100 218580 0 10273 0 0:00:02 0:00:02 --:--:-- 164k root@web1:~# dpkg --unpack libjson-c2_0.11-4ubuntu2.2_amd64.deb (Reading database ... 39096 files and directories currently installed.) Preparing to unpack libjson-c2_0.11-4ubuntu2.2_amd64.deb ... Unpacking libjson-c2:amd64 (0.11-4ubuntu2.2) over (0.11-4ubuntu2.2) ... Processing triggers for libc-bin (2.23-0ubuntu11) ... root@web1:~# reboot root@web1:~# logout [root@redacted ~]# vzctl enter 040199a0-e959-4428-87e6-76dd3b26262e entered into CT root@web1:/# apt install -f Reading package lists... Done Building dependency tree... 50% [1]+ Stopped apt install -f Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 15 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up libjson-c2:amd64 (0.11-4ubuntu2.2) ... Processing triggers for libc-bin (2.23-0ubuntu11) ... Got signal 9 [root@redacted ~]# -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update Status in json-c package in Ubuntu: Triaged Bug description: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0086 0f10ff6977efbf32 88003d45fe10 8140926b [ 99.996057] 81caddf8 88003d45fea8 88003d45fe98 81195a84 [ 99.996057] 8810 88003d45fea8 88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [] dump_stack+0x6d/0x92 [ 99.996057] [] panic+0xd3/0x227 [ 99.996057] [] do_exit+0xb9d/0xba0 [ 99.996057] [] do_group_exit+0x47/0xb0 [ 99.996057] [] SyS_exit_group+0x14/0x20 [ 99.996057] [] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
> Attempts to install libjson-c2_0.11-4ubuntu2.2_amd64.deb result in the same lockup which can only be recovered with a hard reboot. The 2.2 version includes only a revert of the patch, so for any system affected by this, the currently-running init still contains the faulty code, and the fixed package's post-install script calls telinit on the currently-running init, which triggers the problem. Work is in progress to produce a new version that also adjusts the package's post-install script to detect the problematic version and avoid calling telinit. For impacted systems, you can follow this process to upgrade to the 0.11-4ubuntu2.2_amd64.deb package version: - Obtain the latest package: ``` $ curl -LO https://launchpad.net/ubuntu/+archive/primary/+files/libjson-c2_0.11-4ubuntu2.2_amd64.deb ``` - Unpack (install without configuring) the package: ``` $ dpkg --unpack libjson-c2_0.11-4ubuntu2.2_amd64.deb ``` - Reboot; this is mandatory in order to proceed: ``` $ sudo reboot ``` - Configure the package: ``` $ sudo apt install -f ``` -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update Status in json-c package in Ubuntu: Triaged Bug description: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0086 0f10ff6977efbf32 88003d45fe10 8140926b [ 99.996057] 81caddf8 88003d45fea8 88003d45fe98 81195a84 [ 99.996057] 8810 88003d45fea8 88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [] dump_stack+0x6d/0x92 [ 99.996057] [] panic+0xd3/0x227 [ 99.996057] [] do_exit+0xb9d/0xba0 [ 99.996057] [] do_group_exit+0x47/0xb0 [ 99.996057] [] SyS_exit_group+0x14/0x20 [ 99.996057] [] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
Also see https://github.com/json-c/json-c/pull/610/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update Status in json-c package in Ubuntu: Triaged Bug description: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0086 0f10ff6977efbf32 88003d45fe10 8140926b [ 99.996057] 81caddf8 88003d45fea8 88003d45fe98 81195a84 [ 99.996057] 8810 88003d45fea8 88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [] dump_stack+0x6d/0x92 [ 99.996057] [] panic+0xd3/0x227 [ 99.996057] [] do_exit+0xb9d/0xba0 [ 99.996057] [] do_group_exit+0x47/0xb0 [ 99.996057] [] SyS_exit_group+0x14/0x20 [ 99.996057] [] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
Sorry, I posted too soon. Post reboot: root@HMPBgZ:~# apt-get update Fetched 51.5 kB in 1s (46.4 kB/s) Reading package lists... Done root@HMPBgZ:~# apt-get upgrade E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. root@HMPBgZ:~# dpkg -s libjson-c2 Package: libjson-c2 Status: install ok half-configured Priority: extra Section: libs Installed-Size: 67 Maintainer: Ubuntu Developers Architecture: amd64 Multi-Arch: same Source: json-c Version: 0.11-4ubuntu2.2 Config-Version: 0.11-4ubuntu2 Depends: libc6 (>= 2.14) Description: JSON manipulation library - shared library This library allows you to easily construct JSON objects in C, output them as JSON formatted strings and parse JSON formatted strings back into the C representation of JSON objects. Homepage: https://github.com/json-c/json-c/wiki Original-Maintainer: fabien boucher -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update Status in json-c package in Ubuntu: Triaged Bug description: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0086 0f10ff6977efbf32 88003d45fe10 8140926b [ 99.996057] 81caddf8 88003d45fea8 88003d45fe98 81195a84 [ 99.996057] 8810 88003d45fea8 88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [] dump_stack+0x6d/0x92 [ 99.996057] [] panic+0xd3/0x227 [ 99.996057] [] do_exit+0xb9d/0xba0 [ 99.996057] [] do_group_exit+0x47/0xb0 [ 99.996057] [] SyS_exit_group+0x14/0x20 [ 99.996057] [] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
This is not fixed with the updated package. Attempts to install libjson-c2_0.11-4ubuntu2.2_amd64.deb result in the same lockup which can only be recovered with a hard reboot. root@HMPBgZ:~# dpkg -i libjson-c2_0.11-4ubuntu2.2_amd64.deb (Reading database ... 154353 files and directories currently installed.) Preparing to unpack libjson-c2_0.11-4ubuntu2.2_amd64.deb ... Unpacking libjson-c2:amd64 (0.11-4ubuntu2.2) over (0.11-4ubuntu2.1) ... Setting up libjson-c2:amd64 (0.11-4ubuntu2.2) ... packet_write_wait: Connection to xx.xx.xx.xx port 22: Broken pipe -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update Status in json-c package in Ubuntu: Triaged Bug description: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0086 0f10ff6977efbf32 88003d45fe10 8140926b [ 99.996057] 81caddf8 88003d45fea8 88003d45fe98 81195a84 [ 99.996057] 8810 88003d45fea8 88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [] dump_stack+0x6d/0x92 [ 99.996057] [] panic+0xd3/0x227 [ 99.996057] [] do_exit+0xb9d/0xba0 [ 99.996057] [] do_group_exit+0x47/0xb0 [ 99.996057] [] SyS_exit_group+0x14/0x20 [ 99.996057] [] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
** Changed in: json-c (Ubuntu) Status: Fix Released => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update Status in json-c package in Ubuntu: Triaged Bug description: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0086 0f10ff6977efbf32 88003d45fe10 8140926b [ 99.996057] 81caddf8 88003d45fea8 88003d45fe98 81195a84 [ 99.996057] 8810 88003d45fea8 88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [] dump_stack+0x6d/0x92 [ 99.996057] [] panic+0xd3/0x227 [ 99.996057] [] do_exit+0xb9d/0xba0 [ 99.996057] [] do_group_exit+0x47/0xb0 [ 99.996057] [] SyS_exit_group+0x14/0x20 [ 99.996057] [] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
This bug was fixed in the package json-c - 0.12.1-1.3ubuntu0.2 --- json-c (0.12.1-1.3ubuntu0.2) bionic-security; urgency=medium * Revert the security fixes and rebuild the old version (LP: #1878723) -- Chris Coulson Fri, 15 May 2020 12:33:56 +0100 ** Changed in: json-c (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update Status in json-c package in Ubuntu: Triaged Bug description: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0086 0f10ff6977efbf32 88003d45fe10 8140926b [ 99.996057] 81caddf8 88003d45fea8 88003d45fe98 81195a84 [ 99.996057] 8810 88003d45fea8 88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [] dump_stack+0x6d/0x92 [ 99.996057] [] panic+0xd3/0x227 [ 99.996057] [] do_exit+0xb9d/0xba0 [ 99.996057] [] do_group_exit+0x47/0xb0 [ 99.996057] [] SyS_exit_group+0x14/0x20 [ 99.996057] [] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
This bug was fixed in the package json-c - 0.13.1+dfsg-4ubuntu0.2 --- json-c (0.13.1+dfsg-4ubuntu0.2) eoan-security; urgency=medium * Revert the security fixes and rebuild the old version (LP: #1878723) -- Chris Coulson Fri, 15 May 2020 12:33:18 +0100 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update Status in json-c package in Ubuntu: Triaged Bug description: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0086 0f10ff6977efbf32 88003d45fe10 8140926b [ 99.996057] 81caddf8 88003d45fea8 88003d45fe98 81195a84 [ 99.996057] 8810 88003d45fea8 88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [] dump_stack+0x6d/0x92 [ 99.996057] [] panic+0xd3/0x227 [ 99.996057] [] do_exit+0xb9d/0xba0 [ 99.996057] [] do_group_exit+0x47/0xb0 [ 99.996057] [] SyS_exit_group+0x14/0x20 [ 99.996057] [] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
This bug was fixed in the package json-c - 0.11-4ubuntu2.2 --- json-c (0.11-4ubuntu2.2) xenial-security; urgency=medium * Revert the security fixes and rebuild the old version (LP: #1878723) -- Chris Coulson Fri, 15 May 2020 12:11:57 +0100 ** Changed in: json-c (Ubuntu) Status: Triaged => Fix Released ** Changed in: json-c (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update Status in json-c package in Ubuntu: Triaged Bug description: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0086 0f10ff6977efbf32 88003d45fe10 8140926b [ 99.996057] 81caddf8 88003d45fea8 88003d45fe98 81195a84 [ 99.996057] 8810 88003d45fea8 88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [] dump_stack+0x6d/0x92 [ 99.996057] [] panic+0xd3/0x227 [ 99.996057] [] do_exit+0xb9d/0xba0 [ 99.996057] [] do_group_exit+0x47/0xb0 [ 99.996057] [] SyS_exit_group+0x14/0x20 [ 99.996057] [] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
** Tags added: id-5ebe6d95d5ae066b83cac917 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update Status in json-c package in Ubuntu: Triaged Bug description: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0086 0f10ff6977efbf32 88003d45fe10 8140926b [ 99.996057] 81caddf8 88003d45fea8 88003d45fe98 81195a84 [ 99.996057] 8810 88003d45fea8 88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [] dump_stack+0x6d/0x92 [ 99.996057] [] panic+0xd3/0x227 [ 99.996057] [] do_exit+0xb9d/0xba0 [ 99.996057] [] do_group_exit+0x47/0xb0 [ 99.996057] [] SyS_exit_group+0x14/0x20 [ 99.996057] [] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
The updated packages just revert the security fixes which resolves this immediate issue. Keeping the bug open though because we still want to resolve the underlying issue so that we can republish an update with the security fixes in it ** Changed in: json-c (Ubuntu) Status: Fix Released => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update Status in json-c package in Ubuntu: Triaged Bug description: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0086 0f10ff6977efbf32 88003d45fe10 8140926b [ 99.996057] 81caddf8 88003d45fea8 88003d45fe98 81195a84 [ 99.996057] 8810 88003d45fea8 88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [] dump_stack+0x6d/0x92 [ 99.996057] [] panic+0xd3/0x227 [ 99.996057] [] do_exit+0xb9d/0xba0 [ 99.996057] [] do_group_exit+0x47/0xb0 [ 99.996057] [] SyS_exit_group+0x14/0x20 [ 99.996057] [] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
This bug was fixed in the package json-c - 0.13.1+dfsg-4ubuntu0.2 --- json-c (0.13.1+dfsg-4ubuntu0.2) eoan-security; urgency=medium * Revert the security fixes and rebuild the old version (LP: #1878723) -- Chris Coulson Fri, 15 May 2020 12:33:18 +0100 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update Status in json-c package in Ubuntu: Triaged Bug description: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0086 0f10ff6977efbf32 88003d45fe10 8140926b [ 99.996057] 81caddf8 88003d45fea8 88003d45fe98 81195a84 [ 99.996057] 8810 88003d45fea8 88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [] dump_stack+0x6d/0x92 [ 99.996057] [] panic+0xd3/0x227 [ 99.996057] [] do_exit+0xb9d/0xba0 [ 99.996057] [] do_group_exit+0x47/0xb0 [ 99.996057] [] SyS_exit_group+0x14/0x20 [ 99.996057] [] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
This bug was fixed in the package json-c - 0.13.1+dfsg-7ubuntu0.2 --- json-c (0.13.1+dfsg-7ubuntu0.2) focal-security; urgency=medium * Revert the security fixes and rebuild the old version (LP: #1878723) -- Chris Coulson Fri, 15 May 2020 12:31:48 +0100 ** Changed in: json-c (Ubuntu) Status: Confirmed => Fix Released ** Changed in: json-c (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update Status in json-c package in Ubuntu: Triaged Bug description: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0086 0f10ff6977efbf32 88003d45fe10 8140926b [ 99.996057] 81caddf8 88003d45fea8 88003d45fe98 81195a84 [ 99.996057] 8810 88003d45fea8 88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [] dump_stack+0x6d/0x92 [ 99.996057] [] panic+0xd3/0x227 [ 99.996057] [] do_exit+0xb9d/0xba0 [ 99.996057] [] do_group_exit+0x47/0xb0 [ 99.996057] [] SyS_exit_group+0x14/0x20 [ 99.996057] [] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
Removed the broken version from the archive, and copied back the previous version. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update Status in json-c package in Ubuntu: Confirmed Bug description: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0086 0f10ff6977efbf32 88003d45fe10 8140926b [ 99.996057] 81caddf8 88003d45fea8 88003d45fe98 81195a84 [ 99.996057] 8810 88003d45fea8 88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [] dump_stack+0x6d/0x92 [ 99.996057] [] panic+0xd3/0x227 [ 99.996057] [] do_exit+0xb9d/0xba0 [ 99.996057] [] do_group_exit+0x47/0xb0 [ 99.996057] [] SyS_exit_group+0x14/0x20 [ 99.996057] [] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
** Changed in: json-c (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update Status in json-c package in Ubuntu: Confirmed Bug description: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0086 0f10ff6977efbf32 88003d45fe10 8140926b [ 99.996057] 81caddf8 88003d45fea8 88003d45fe98 81195a84 [ 99.996057] 8810 88003d45fea8 88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [] dump_stack+0x6d/0x92 [ 99.996057] [] panic+0xd3/0x227 [ 99.996057] [] do_exit+0xb9d/0xba0 [ 99.996057] [] do_group_exit+0x47/0xb0 [ 99.996057] [] SyS_exit_group+0x14/0x20 [ 99.996057] [] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
today's unattended upgrade killed a lot of our hosts running xenial + upstart, please mark as critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update Status in json-c package in Ubuntu: Confirmed Bug description: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0086 0f10ff6977efbf32 88003d45fe10 8140926b [ 99.996057] 81caddf8 88003d45fea8 88003d45fe98 81195a84 [ 99.996057] 8810 88003d45fea8 88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [] dump_stack+0x6d/0x92 [ 99.996057] [] panic+0xd3/0x227 [ 99.996057] [] do_exit+0xb9d/0xba0 [ 99.996057] [] do_group_exit+0x47/0xb0 [ 99.996057] [] SyS_exit_group+0x14/0x20 [ 99.996057] [] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
Also ran into this. It looks like this bug got backported https://github.com/json-c/json-c/issues/599. The upstream fix is this: https://github.com/besser82/json-c/commit/7a4807fe0cdb1d9e20273c79762cbf54833aaae4 ** Bug watch added: github.com/json-c/json-c/issues #599 https://github.com/json-c/json-c/issues/599 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update Status in json-c package in Ubuntu: Confirmed Bug description: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0086 0f10ff6977efbf32 88003d45fe10 8140926b [ 99.996057] 81caddf8 88003d45fea8 88003d45fe98 81195a84 [ 99.996057] 8810 88003d45fea8 88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [] dump_stack+0x6d/0x92 [ 99.996057] [] panic+0xd3/0x227 [ 99.996057] [] do_exit+0xb9d/0xba0 [ 99.996057] [] do_group_exit+0x47/0xb0 [ 99.996057] [] SyS_exit_group+0x14/0x20 [ 99.996057] [] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
I also experienced this bug today. What seems to have happened is that upstart init filled all of the memory on my machine while libjson-c2 was updating, leading to oom-killer killing everything. The kernel panic here would happen if oom-killer tries to act on init. After a reboot my machine managed to upgrade fully before crashing due to running out of memory again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update Status in json-c package in Ubuntu: Confirmed Bug description: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0086 0f10ff6977efbf32 88003d45fe10 8140926b [ 99.996057] 81caddf8 88003d45fea8 88003d45fe98 81195a84 [ 99.996057] 8810 88003d45fea8 88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [] dump_stack+0x6d/0x92 [ 99.996057] [] panic+0xd3/0x227 [ 99.996057] [] do_exit+0xb9d/0xba0 [ 99.996057] [] do_group_exit+0x47/0xb0 [ 99.996057] [] SyS_exit_group+0x14/0x20 [ 99.996057] [] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: json-c (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update Status in json-c package in Ubuntu: Confirmed Bug description: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0086 0f10ff6977efbf32 88003d45fe10 8140926b [ 99.996057] 81caddf8 88003d45fea8 88003d45fe98 81195a84 [ 99.996057] 8810 88003d45fea8 88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [] dump_stack+0x6d/0x92 [ 99.996057] [] panic+0xd3/0x227 [ 99.996057] [] do_exit+0xb9d/0xba0 [ 99.996057] [] do_group_exit+0x47/0xb0 [ 99.996057] [] SyS_exit_group+0x14/0x20 [ 99.996057] [] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
