You are not logged in.

#1 2011-02-16 14:48:34

gejr
Member
Registered: 2007-05-23
Posts: 92

Kernel panic - not syncing: Attempted to kill init!

Second day in a row I get this written on my TTY. Any thoughts on what may be the cause of it?

It looks like a disk is failing, but I'm not sure if this is related to the kernel panic? It could be two different errors showing up here.

EXT3-fs (sda4): error in ext3_orphan_add: Readonly filesystem
EXT3-fs (sda4): error in ext3_ordered_write_end: IO failure
EXT3-fs (sda4): error in ext3_ordered_write_end: IO failure
EXT3-fs (sda4): error: ext3_journal_start_sb: Detected aborted journal
EXT3-fs (sda4): error: remounting filesystem read-only
Kernel panic - not syncing: Attempted to kill init!
Pid: 1, comm: init Tainted: P        2.6.37-ARCH #1
Call Trace:
[<c13124ee>] ? printk+0x18/0x1a
[<c13123d1>] panic+0x61/0x166
...    do_exit ...
...    do_group_exit ...
...    get_signal_to_deliver ...
...    ? force_sig_info_fault
...    ? do_page_fault
...    do_signal
...    wakeup_kswapd
...    do_page_fault+0x0/0x430
...    do_page_fault+0x0/0x430
...    do_page_fault+0x0/0x430
...    copy_to_user
...    do_page_fault+0x0/0x430
...    do_notify_resume
...    work_notifysig

(I had to copy this from my TV-screen so I've left out some of the hex addresses which I guessed arent too interesting. Also all these page faults seem to happen at the same address)

I run stock kernel. Please let me know if there's anything else that could be relevant, if you want to help me troubleshoot this!

# uname -a
Linux raynor 2.6.37-ARCH #1 SMP PREEMPT Sat Jan 29 19:40:04 UTC 2011 i686 Intel(R) Celeron(R) CPU E1500 @ 2.20GHz GenuineIntel GNU/Linux

Thanks! :)

Offline

#2 2011-02-16 15:20:52

metzengerstein
Member
Registered: 2010-06-04
Posts: 60

Re: Kernel panic - not syncing: Attempted to kill init!

You should do a filesytem (fsck) and drive check (smart, badblocks) from a live system environment.

Offline

Board footer

Powered by FluxBB