Your message dated Wed, 25 Apr 2018 18:20:21 +0100 with message-id <2278d4df24d66ff3970b0b3d6b06228e4335fb77.camel@decadent.org.uk> and subject line Re: Bug#896881: CPU: 8 PID: 1 Comm: init Not tainted 4.9.0-0.bpo.6-amd64 has caused the Debian Bug report #896881, regarding CPU: 8 PID: 1 Comm: init Not tainted 4.9.0-0.bpo.6-amd64 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 896881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896881 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: CPU: 8 PID: 1 Comm: init Not tainted 4.9.0-0.bpo.6-amd64
- From: Андрей Василишин <a.vasilishin@kpi.ua>
- Date: Wed, 25 Apr 2018 12:35:30 +0300
- Message-id: <[🔎] 7231a4ae-cf74-1505-fcd4-e78e58521955@kpi.ua>
- Reply-to: a.vasilishin@kpi.ua
Package: linux-image-4.9.0-0.bpo.6-amd64 Version: 4.9.82-1+deb9u3~bpo8+1 Hello!After update linux-image from linux-image-3.2.0-4-amd64 3.2.96-2 to linux-image-4.9.0-0.bpo.6-amd64 4.9.82-1+deb9u3~bpo8+1 new kernel does not want boot. After installation linux-image-4.9.0-6-amd64 4.9.82-1+deb9u3 with many deps new kernel booting fine.[ 33.511781] Kernel panic - not syncing:Attempted to kill init! exit code = 0x0000000[ 33.511781][ 33.511887] CPU: 8 PID: 1 Comm: init Not tainted 4.9.0-0.bpo.6-amd64 ttl Debian 4.9.82-l+deb9u3~bpo8+l[ 33.511986] Hardware name: Dell Inc. PowerEdge R730xd/OWCJMT, BIOS 2.4.3 01/17/2017I 33.512082] 00000000000000O0 ffffffffb91305e5 ffff8ee5c7615O00 ffffb69040O0fb88[ 33.512478] ffffffffb8f7fce4 ffff8ee5000O0010 ffffb6904000fe98 ffffb6904000fe30[ 33.512872] 926a88f8c482df27 ffff8efIc49a2068 0O00000000000000 ffff8eflc?0de110 [ 33.513308] Call Trace: [ 33.513420] [<ffffffffb91305e5>] ? dump_stack+0x5c/0x77 [ 33.513536] [<ffffffffb8f7fce4>] ? panic+0xe8/0x248 [ 33.513649] [<ffffffffb8e7df94>] ? do_exit+0xb44/0xb50 [ 33.513761] [<ffffffffb8e7e019>] ? do_group_exit+0x39/0xbO [ 33.513874] E<ffffffffb8e7e0a0>] ? SyS_exit_group+0xlO/0xl0 [ 33.513988] [<ffffffffb8e03bd3>] ? do_sysca1l_64+0x93/0xla0 [ 33.514103] [<ffffffffb94126b8>] ? entry_SYSCALL_64_after_swapgs+0x42/OxbO[ 33.514315] Kernel Offset: Ox37e00000 from 0xffffffff8100000O (relocation range: 0xffffffff8O000000-0xffffffffbfffffff) [ 33.5222341 Rebooting in 1 seconds..
--- End Message ---
--- Begin Message ---
- To: 896881-done@bugs.debian.org
- Subject: Re: Bug#896881: CPU: 8 PID: 1 Comm: init Not tainted 4.9.0-0.bpo.6-amd64
- From: Ben Hutchings <ben@decadent.org.uk>
- Date: Wed, 25 Apr 2018 18:20:21 +0100
- Message-id: <2278d4df24d66ff3970b0b3d6b06228e4335fb77.camel@decadent.org.uk>
- In-reply-to: <[🔎] 2f0a405e-b14e-a4e1-b99e-ec81e28586b1@kpi.ua>
- References: <[🔎] 7231a4ae-cf74-1505-fcd4-e78e58521955@kpi.ua> <[🔎] 8c7a841100ea7d4a540c9152ea3650e0004f0601.camel@decadent.org.uk> <[🔎] 2f0a405e-b14e-a4e1-b99e-ec81e28586b1@kpi.ua>
On Wed, 2018-04-25 at 19:24 +0300, Андрей Василишин wrote: > > > > Which Debian release are you using? Debian 7 "wheezy" or 8 > > "jessie"? > > > > Ben. > > > > cat /etc/debian_version > 7.11 You need to upgrade to jessie before installing packages from jessie- backports. (You can still run a wheezy installation in a chroot or container environment under this kernel version, but that's very different.) Ben. -- Ben Hutchings Design a system any fool can use, and only a fool will want to use it.Attachment: signature.asc
Description: This is a digitally signed message part
--- End Message ---