Bug#305486: marked as done (Kernel panic: Attempted to kill the iddle task!)
Your message dated Sat, 30 Apr 2005 01:28:01 +0200
with message-id <200504300128.02306.aragorn@tiscali.nl>
and subject line Bug#305486: Kernel panic: Attempted to kill the iddle task!
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 20 Apr 2005 09:52:50 +0000
>From sergioicai@gmail.com Wed Apr 20 02:52:50 2005
Return-path: <sergioicai@gmail.com>
Received: from zproxy.gmail.com [64.233.162.196]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DOBt4-0007mt-00; Wed, 20 Apr 2005 02:52:50 -0700
Received: by zproxy.gmail.com with SMTP id 8so88777nzo
for <submit@bugs.debian.org>; Wed, 20 Apr 2005 02:52:18 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=beta; d=gmail.com;
h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
b=nkhxs+BFp54bcHpmcon9GF1svsd7v5gqLY7CTi9k2aLwB4t3vdY9kM26yU2GH77VHMOJ6KJZ4G0np04oQvAH0RPP0QkuW5rJpd7+iLJzsUk9BlXVEMZE52h9WMZee33lG81g/yyesOWK/blVRATOK+LBB1rOID5WH1ewAk/FV3g=
Received: by 10.36.8.17 with SMTP id 17mr65303nzh;
Wed, 20 Apr 2005 02:52:18 -0700 (PDT)
Received: by 10.36.58.14 with HTTP; Wed, 20 Apr 2005 02:52:18 -0700 (PDT)
Message-ID: <[🔎] 4028d2e0050420025263ac20fa@mail.gmail.com>
Date: Wed, 20 Apr 2005 11:52:18 +0200
From: Sergio <sergioicai@gmail.com>
Reply-To: Sergio <sergioicai@gmail.com>
To: submit@bugs.debian.org
Subject: Kernel panic: Attempted to kill the iddle task!
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
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] =3D OK, [E] =3D Error (please elaborate below), [ ] =3D 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 scree=
n.
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=3D00000000
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/0x19=
2
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=3D00000000
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=3Dc0306000 task=3Dc0288a40)
Stack: 00000009 000074c0 0001dff0 00000000 00000000 00000004 0000026a 00000=
000
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:=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
- 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-installe=
r/.
Once you have filled out this report, mail it to submit@bugs.debian.org.
---------------------------------------
Received: (at 305486-done) by bugs.debian.org; 29 Apr 2005 23:27:57 +0000
>From aragorn@tiscali.nl Fri Apr 29 16:27:57 2005
Return-path: <aragorn@tiscali.nl>
Received: from smtp-out0.tiscali.nl [195.241.79.175]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DRetp-0005v6-00; Fri, 29 Apr 2005 16:27:57 -0700
Received: from strider.fjphome.nl (195-240-184-66-mx.xdsl.tiscali.nl [195.240.184.66])
by smtp-out0.tiscali.nl (Postfix) with ESMTP id 3793E80112CD
for <305486-done@bugs.debian.org>; Sat, 30 Apr 2005 01:27:56 +0200 (CEST)
From: Frans Pop <aragorn@tiscali.nl>
To: 305486-done@bugs.debian.org
Subject: Re: Bug#305486: Kernel panic: Attempted to kill the iddle task!
Date: Sat, 30 Apr 2005 01:28:01 +0200
User-Agent: KMail/1.7.2
References: <[🔎] 4028d2e0050420025263ac20fa@mail.gmail.com> <[🔎] 200504231313.20757.aragorn@tiscali.nl> <[🔎] 4028d2e005042916052427a2c2@mail.gmail.com>
In-Reply-To: <[🔎] 4028d2e005042916052427a2c2@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200504300128.02306.aragorn@tiscali.nl>
Delivered-To: 305486-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
On Saturday 30 April 2005 01:05, Sergio wrote:
> I'm sorry to say that the bug I submitted was due to an incorrect
> RAM module configuration. Thus, this bug should be closed.
>
> Thanks anyway for your help!
Thanks for letting us know.
Reply to: