You are not logged in.
after last pacman upgrade I rebooted and got Kernel Panic : not syncing exiting init
tried rebooting and screenlocking, but the boot process is too short.
tried with the recovery disk mounted /dev/sdb3 to /mnt/arch
mounted /dev/sdb1 to /mnt/arch/boot
tried journalctl -b no output
so i cd /mnt/arch/etc and ran mkinitcpio -p linux it rebuilt the initramfs image success rebooted same kernel panic
tried arch-chroot /mnt/arch /usr/bin/mkinitcpio -p linux it rebuilt the initramfs image success reboot same kernel panic
tried to downgrade linux4.0.7-2-i686.tar.xz worked rebuilt the initramfs image rebooted same thing
when I check certain files and directories they come up so the hdd works. I don't know where to go from here since I can't get anything from the journal or the startup page.
Offline
At a guess, it sounds like your init process died. Since the init process is systemd, it probably died before journaling could be started in order to write out the buffered log messages.
Try and run some memory/hardware diagnostics first to rule out any hardware problems.
If the hardware checks out, use https://wiki.archlinux.org/index.php/Sy … t_problems and the debugging information from the freedesktop site to try and get hold of the kernel log (dmesg).
Offline
I have the same problem. On a separate hard disk I reinstalled and got the same result.
A partial list of the problems:
failed to find cpu0 device node
BUG: unable to handle kernel NULL pointer dereference at 000000ac
IPCc1350d737 free-cache attributes +0x8310.d0
pda = 000000000
Oops:0002 (#1) PREEMPT SMP
Modules linked:
CPU 0 PD; 1 Comm:swrapper/0 not tainted 4.1.2-2 Arch#1
kernel panic - not syncing: Attempt to kill init exit code 0x000000009
Online
I think we will have to wait for the new kernel linux-4.1.3-1 to appear. It's now in testing.
Offline
I have the same issue after -Syyu today. Kernel panic something something killing init.
I added the LTS kernel to keep running for now.
Offline
Same here.
"An it harm none, do what thou wilt"
Offline
Took the suggestion to install the linux-lts kernel. Still a kernel panic. This may not be a kernel problem.
Offline
Same thing with Antergos, kernel panic.
http://i61.tinypic.com/16hojlx.jpg
Yes I know Antergos isn't supported, it's just a comparison to show
that it happens there as well.
-- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code [jwr] --
"An it harm none, do what thou wilt"
Offline
@Pednick: please stop posting unless you have something useful to add
https://wiki.archlinux.org/index.php/Fo … mpty_posts
Offline
I guess it's all relative, let's just hope they resolve it soon.
"An it harm none, do what thou wilt"
Offline
read https://wiki.archlinux.org/index.php/Sy … t_problems and the debugging information from the freedesktop site. Tried to reboot and waited 0ver 5 minutes to see if it would continue on but it stayed froze. Got no shell. From there I tried the ctrl+alt+del for a reboot ...nothing. So I tried to get a virtual by ctrl+alt+F1 thru F12 nothing stayed froze. Could not get a shell or Virtual machine.
Booted with these parameters on the kernel command line: systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M got the same results Kernel Panic : not syncing exiting init
with no debug info. Where would the debug info go for me to find? Don't know where to try and get any info to continue trying any ideas??
Offline
After upgrading from 4.0.7-2 -> 4.1.3-1, I rebooted. The Syslinux boot screen came up, then went to start linux, but came up with the following page of text:-
[1.53584] Failed to find cpu0 device node
[1.53637] BUG: unable to handle kernel NULL pointer dereference at 000000ac
( - will leave out [numbers] as I'm typing from a photo... - )
IP: [<c13516d3>] free_cache_attributes *0x83/0xd0
*pde =00000000
Oops: 0002 [01] PREEMPT SMP
Modules linked in:
CPU: 2 PID: 1 Conn: swapper/0 Not tainted 4.1.3-1-ARCH *1
It goes on to list the hardware name... gives a stack trace... then a call trace:-
detect_cache_attributes*0x165/0x290
? container_dev_init*0x28/0x28
cacheinfo_sysfs_init*0x30/0x73
do_one_initcall*0xaa/0x200
? container_dev_init*0x28/0x28
? repair_env_string*0x12/0x54
kernel_init_freeable*0x134/0x1d0
kernel_init*0x10/0xe0
ret_from_kernel_thread*0x21/0x30
? rest_init*0x80/0x80
( - then there's a couple of lines of (Hex) Code: and the trace ends - )
Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009
Kernel Offset: disabled
end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009
_
It was a complete freeze up - keyboard was dead - the only way to escape was to switch off.
I used my old install disc to mount my partitions - then arch-chrooted in to reinstall 4.0.7-2
suspected Syslinux, so installed grub. Updated again with same result.
I've been using linux since 1980, and Arch for a good 10 years. This is the 1st time I've been REALLY stuck.
Any ideas?
Last edited by harry2703 (2015-07-30 17:36:13)
Offline
For information, same problem here.
This issue occurs with linux-4.1.2-2 and linux-4.1.3-1
Run fine with linux-4.0.7-2 (and linux-lts)
Note also that linux-4.1.3-1 runs fine on other machines...
Failed to find cpu0 device node
BUG: unable to handle kernel NULL pointer dereference at 000000ac
IP: [<c13516d3>] free_cache_attributes +0x83/0xd0
*pde =00000000
Oops: 0002 [01] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.1.3-1-ARCH #1
Hardware name : Gigabyte Technology Co.,Ltd. GA-870-UD3/GA-870-UD3, BIOS F5 08/01/2011
task: f4ce8000 ti: f4cae000 task.ti: f4cae000
EIP: 0060:[<c13516d3>] EFLAGS: 00010206 CPU: 1
EIP is at free_cache_attributes+0x83/0xd0
EAX: 00000001 EBX: f4d91eec ECX: 00000090 EDX: 33b4f000
ESI: 00000000 EDI: c1716a80 EBP: f4cafec0 ESP: f4cafea0
DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
CR0: 8005003b CR2: 000000ac CR3: 01723000 CR4: 000006d0
Stack:
c1716a80 f5253a80 00000003 c1716a80 00000090 c1716a80 fffffffe 00000000
f4cafef4 c1351a15 c15bf9ac 00000000 00000000 f4d9c5a0 c1588673 f5253a80
c16116e0 f5253a80 00000000 c16116e0 c16ba2ae f4caff04 c16ba2de f4d9c5a0
Call Trace:
detect_cache_attributes+0x165/0x290
? container_dev_init+0x28/0x28
cacheinfo_sysfs_init+0x30/0x73
do_one_initcall+0xaa/0x200
? container_dev_init+0x28/0x28
? repair_env_string+0x12/0x54
kernel_init_freeable+0x134/0x1d0
kernel_init+0x10/0xe0
ret_from_kernel_thread+0x21/0x30
? rest_init+0x80/0x80
Code:
8d 48 01 ba 08 00 00 00 89 d8 e8 19 89 f1 ff 3b 05 6c e9 67
c1 73 21 39 c6 74 e5 8b 14 85 40 de 67 c1 8b 7d ec 8b 4d f0
03 0c 3a <f0> 0f b3 71 1c f0 0f b3 03 eb ca 66 90 8b 7d f0
8b 04 b5 40 de
EIP: [<c13516d3>] free_cache_attributes+0x83/0xd0 SS:ESP 0068:f4cafea0
CR2: 00000000000000ac
---[end trace a79419a63734b6f1]---
Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009
Kernel Offset: disabled
end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009
_
Last edited by eburon (2015-07-30 15:48:35)
Offline
Similar issue: https://bbs.archlinux.org/viewtopic.php … 4#p1546544
Are you using LVM or encrypted volume?
If I code something, it's probably at https://github.com/kellcodes
Do **NOT** expect a response from me.
Offline
just upgraded the kernel to linux-4.1.3-1 and linux-headers=4.1.3-1 and systemd.
kernel panic persists.
Has anyone solved?
Offline
Neither encryption nor LVM... I am running i686 installation on a 64 bit quad amd, but everything runs fine with 4.0.7 -2.
Having no problems on an EFI booting laptop running x86_64 on another 64 bit quad amd, even after update to latest kernel.
Last edited by harry2703 (2015-07-30 17:40:48)
Offline
What sort of system is this?
Maybe this is relevant: https://bugzilla.kernel.org/show_bug.cgi?id=101971
If not, as you have a kernel oops/panic listing, log a bug against the kernel so they can investigate.
Offline
Is this an AMD system? Maybe this is relevant: https://bugzilla.kernel.org/show_bug.cgi?id=101971
Offline
It's an old advent AMD quad core... Arch installed years ago, and kept going with regular updates. At time of install x86_64 didn't have lots of applications available, so did an i686 install.
Your link interesting, but, other than re-installing with x86_64, I'm still puzzled. Why does 4.0.7-2 not have this bug, if it's down to the number of cpus?
Offline
I've been using linux since 1980
you were about 11 years early
Are you both running i686 system on machines that fail to boot with the 4.1 kernel? (just as OP on the thread kev717 linked) The issue could be something that's only present on i686 kernels. You should open a bug report and stick to older kernels until the issue is fixed.
Also, use code tags when pasting code: https://wiki.archlinux.org/index.php/Fo … s_and_code
Offline
It's an old advent AMD quad core... Arch installed years ago, and kept going with regular updates. At time of install x86_64 didn't have lots of applications available, so did an i686 install.
Your link interesting, but, other than re-installing with x86_64, I'm still puzzled. Why does 4.0.7-2 not have this bug, if it's down to the number of cpus?
I don't know the ins and outs (I just searched the kernel bugzilla) but the title and text does say "regression" - I.e introduced bug to the 4.1 line of kernels.
Offline
Sorry ooo, I'm an old man, so, maybe, memory's not too good. I seem to recall my first system was SUSE 1.6. Thanks for the pointer re: " code " - corrected.
Also, ukhippo, I take your point re: regression.
Last edited by harry2703 (2015-07-30 17:39:06)
Offline
Thank you ukhippo. My problem exactly.
My next problem is that I do not code. I'm 84 and use Archlinux because it does precisely what I want. As a result, your information is correct and describes my problem, but I have absolutely no idea how to fix it.
What must I do?
Offline
What sort of system is this?
Maybe this is relevant: https://bugzilla.kernel.org/show_bug.cgi?id=101971If not, as you have a kernel oops/panic listing, log a bug against the kernel so they can investigate.
This seems relevant.
I'am running with an AMD Phenom II dual core, i686 architecture.
This issue is not seen on Intel i3 architecture or an old AMD Athlon64 (i686, 1 core)
Last edited by eburon (2015-07-30 15:40:52)
Offline
Until a fixed kernel is available, you can either downgrade to a 4.0.X kernel (see https://wiki.archlinux.org/index.php/Do … _packages) or switch to the LTS kernel, which may be easier depending on what you have installed. Note if you install the LTS kernel, you'll have to add an entry to your bootloader for it.
Offline
@eburon
From my post https://bbs.archlinux.org/viewtopic.php … 6#p1549046
Until a fixed kernel is available, you can either downgrade to a 4.0.X kernel (see https://wiki.archlinux.org/index.php/Do … _packages) or switch to the LTS kernel, which may be easier depending on what you have installed. Note if you install the LTS kernel, you'll have to add an entry to your bootloader for it.
Offline