Bug#305486: Kernel panic: Attempted to kill the iddle task!

[Sergio <sergioicai@gmail.com>]

Package: installation-reports

INSTALL REPORT

Debian-installer-version: RC3
uname -a: ??? 2.6.8-2-386 / 2.4.27-2-386 (from initial msg while boot)
Date: 20 april 2005
Method: Installed from CD.

Machine: PC clone - ASUS A7V400-MX motherboard
Processor: AMD Sempron 3000+
Memory: 512 MB
Root Device: IDE Maxtor - 2 x (6B120P0)
Root Size/partition table: Not yet defined

Output of lspci: Could not arrive
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot worked:         [E]
Configure network HW:   [ ]
Config network:              [ ]
Detect CD:                    [ ]
Load installer modules:   [ ]
Detect hard drives:         [ ]
Partition hard drives:       [ ]
Create file systems:       [ ]
Mount partitions:            [ ]
Install base system:       [ ]
Install boot loader:         [ ]
Reboot:                         [ ]

Comments/Problems:

System won't boot properly, not even arriving to a language selection screen.

I have tried to boot directly from boot prompt, and using _linux26_
parameter, and both of them end up in the same situation: "Kernel
panic: Attempted to kill the iddle task".

However, there is a big difference among both boot options. While
_linux26_ always arrives to the same point, _linux24_ does NOT, which
sounds very strange to me.

I'll finish the explanation after the boot messages:



- These are ONE version of the boot messages for "linux24" boot (each
boot has its own numbers):
----------------------------------------------------------------------------------------------
(...)
Unable to handle kernel paging request at virtual address 000080c08
printing eip:
c029245f
*pde=00000000
Oops: 0002
CPU: 0
EIP: 0010: [<c029245f>]    Not tainted
EFLAGS: 00010283
EIP is at mem_init +0x73/0x1b1    ????Not sure?????
eax: ..........
esi: ........
ds: ..........
Process swapper (pid:1, stackpage:ddfeb000)
Stack: ................
Call Trace: [<c0105058>] [<00106ca4>] [<c0105051>] start_kernel +0x10b/0x192
Code: c7 04 90 00 00 00 00 42 3b 15 c8 b9 29 c0 7c eb 83 fb 04 7e
<0>Kernel panic: Attempted to kill the iddle task!

<STOP>
----------------------------------------------------------------------------------------------



- These are the boot messages for "linux26" boot (each boot ends up in
the same numbers):
----------------------------------------------------------------------------------------------
(...)
Unable to handle kernel paging request at virtual address e033e308
printing eip:
c03127b5
*pde=00000000
Oops: 0000 [#1]
PREEMPT
Modules linked in:
CPU: 0
EIP: 0010: [<c03127b5>]    Not tainted
EFLAGS: 00010293 (2.6.8-2-386)
EIP is at mem_init +0x73/0x1b1
eax: ..........
esi: ........
ds: ..........
Process swapper (pid:0, threadinfo=c0306000 task=c0288a40)
Stack: 00000009 000074c0 0001dff0 00000000 00000000 00000004 0000026a 00000000
           00039100 c033d120 00385007 c03085bf c033e5c0 c010019f
Call Trace: [<c03085bf>] start_kernel +0x10b/0x192
Code: 83 be f4 e2 33 c0 01 75 44 8b 86 e4 e2 33 c0 8b 96 e8 e2 33
<0>Kernel panic: Attempted to kill the iddle task!
In iddle task - not syncing

<STOP>
----------------------------------------------------------------------------------------------




* ADDITIONAL NOTES: 
=================

- System was assembled by myself from different pieces, it's not a "branded" PC.
- There are a couple of lines which are missing in the 2.4 kernel
(PREEMPTIVE, Modules linked in:).
- Kernel's 2.4 behavior is very strange: every boot shows different
parameters, with even different messages, but in the end, they all
finish in "Attempted to kill the iddle task". Some of this mesages
include:

--------------
      <0> Kernel panic: Attempted to kill the iddle task!
      In iddle task - not syncing
--------------
      Segmentation fault
      <0> Kernel panic: Attempted to kill the iddle task!
--------------
      <0> Aiee, killing interrupt handler
      In iddle task - not syncing
--------------

- I also tried to boot the system using a "Knoppix" CD, with different
results depending on the version, parameters, keyboard and monitor.



Hope this helps to debug this problem. Should you need any aditional
info which I could provide, please don't hesitate to ask for it.

Thanks for your work!

    Sergio




Install logs and other status info is available in /var/log/debian-installer/.
Once you have filled out this report, mail it to submit@bugs.debian.org.