Kernel Panic - not syncing: Attempted to kill the idle task!

Crogge · 01-30-2012, 12:11 AM

Here is a screenshot of the kernel panic log:
http://i39.tinypic.com/1ruiqr.jpg

LSPCI:

Code:

00:01.0 Host bridge: Advanced Micro Devices [AMD] CS5536 [Geode companion] Host Bridge (rev 31)
00:01.1 VGA compatible controller: Advanced Micro Devices [AMD] Geode LX Video
00:01.2 Entertainment encryption device: Advanced Micro Devices [AMD] Geode LX AES Security Block
00:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10)
00:0f.0 ISA bridge: Advanced Micro Devices [AMD] CS5536 [Geode companion] ISA (rev 03)
00:0f.2 IDE interface: Advanced Micro Devices [AMD] CS5536 [Geode companion] IDE (rev 01)
00:0f.3 Multimedia audio controller: Advanced Micro Devices [AMD] CS5536 [Geode companion] Audio (rev 01)
00:0f.4 USB Controller: Advanced Micro Devices [AMD] CS5536 [Geode companion] OHC (rev 02)
00:0f.5 USB Controller: Advanced Micro Devices [AMD] CS5536 [Geode companion] EHC (rev 02)

(FSC A230 - 512MB RAM + 4GB CF SLC + 1TB USB 2.0 HDD)

I have read that it could be related with "ACPI" settings, but I can't find any option in the BIOS to disable it. What could have caused this kernel panic after days of uptime?

Is there are possibility to enable an automatic restart after a KP?

sundialsvcs · 01-30-2012, 09:02 PM

When the kernel cannot continue executing for some reason, it "panics," and part of the panic-message is a note of whether the panic occurred while the kernel was doing a write to the filesystem. (Nearly always it is not, fortunately, so that part of the message is: "not syncing.")

The last part of the message is the "real" message. In this case, one of the required system processes ... which are not permitted ever to terminate ... ran into a situation where they cannot continue to execute. And so, if they can't keep going, neither can the system itself.

This message is usually "the final paws-up gasp" of the system, and messages preceding it are the true cause of the problem.

WizadNoNext · 04-15-2012, 05:15 AM

It looks to me like something tried to reprogram HRT and this was failed. You should investigate it. Actually HRT is well protected from any access from userspace, but you can change permissions in /dev/ for hrt and if did so, then this could be your problem.