Debian Bug report logs - #397997
My own recompilation of 2.6.16 or -17 kernel on my AMD64 fails. Kernel panics, says "tried to kill init!!"

Package: linux-2.6; Maintainer for linux-2.6 is Debian Kernel Team <debian-kernel@lists.debian.org>;

Reported by: Willy Gommel <wg3w@spamcop.net>

Date: Sat, 11 Nov 2006 00:03:01 UTC

Severity: normal

Done: maximilian attems <max@stro.at>

Bug is archived. No further changes may be made.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to debian-bugs-dist@lists.debian.org, unknown-package@qa.debian.org:
Bug#397997; Package linux-source. Full text and rfc822 format available.

Acknowledgement sent to Willy Gommel <wg3w@spamcop.net>:
New Bug report received and forwarded. Copy sent to unknown-package@qa.debian.org. Full text and rfc822 format available.

Message #5 received at submit@bugs.debian.org (full text, mbox):

From: Willy Gommel <wg3w@spamcop.net>
To: submit@bugs.debian.org
Subject: My own recompilation of 2.6.16 or -17 kernel on my AMD64 fails. Kernel panics, says "tried to kill init!!"
Date: Fri, 10 Nov 2006 15:53:11 -0800
Package: linux-source
Version: 2.6.17-9; testing "Etch" version, AMD64

Whenever I try to compile the kernel without any initrd support (the only way 
I know how to do so), and then install the resulting kernel, the system 
becomes unbootable using it.

I use the LILO loader. What happens is this:

When I turn the machine on, or reboot it, LILO loads the kernel, which then 
begins processing. Less than a second later, the kernel panics, saying 
something about "tried to kill init!!" At this point, the screen is locked up 
tight, which means I cannot review more than ~60 lines of preceding 
procedure. Since the kernel, in panicking, fills most of the screen with what 
looks like register hex-dumps, I must say that this is pretty useless to me.

This only happens on my AMD64 machine. I currently have (and am using) an AMD 
1.33-GHz 32-bit machine which, using the same package (but with appropriately 
different headers), handles the booting task just fine. This actually 
suggests to me that the problem is in the 2.6.16&17 header packages, not 
linux-source itself. Mentioning this is all I can do, however.

Both of the amchines are home-built, no-name-brand machines. The AMD64 is 
running at 2.2 GHz, and is described as a "3700+". It has identical twin 
250GB HDDs from Western Digital. The only way I can boot the AMD64 at present 
is to use your precompiled kernels, loaded with heaps of useless junk -- 
including INITRD.

I have yet to try regressing to your unofficial "stable" version for AMD64. If 
necessary for testing purposes, I will be happy to do so.

-- 
  .......................................................... Willy Gommel
http://www.wg3.net



Bug reassigned from package `linux-source' to `linux-2.6'. Request was from Martin Michlmayr <tbm@cyrius.com> to control@bugs.debian.org. Full text and rfc822 format available.

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#397997; Package linux-2.6. Full text and rfc822 format available.

Acknowledgement sent to Willy Gommel <wg3w@spamcop.net>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. Full text and rfc822 format available.

Message #12 received at 397997@bugs.debian.org (full text, mbox):

From: Willy Gommel <wg3w@spamcop.net>
To: 397997@bugs.debian.org
Subject: Further to my problem
Date: Wed, 29 Nov 2006 13:49:45 -0800
It appears that the problem is the omission of essential components. I tried 
two approaches::

(1) starting with an "empty" kernel and filling it with known hardware 
definitions; and

(2) starting with your precompiled kernel, and deleting known absent hardware.

Of the two approaches, only #2 has worked thus far. One known problem I 
encountered: the pseudo-filesystem "TMPFS" is actually essential, at least 
for booting via initrd. However, that was not enough to solve the problems in 
approach #1. Due to the extreme investment of time required for the "hit or 
miss" approach. I have not solved the problems of approach #1.

Thank you *VERY* much!! :)

-- 
  .......................................................... Willy Gommel
http://www.wg3.net



Reply sent to maximilian attems <max@stro.at>:
You have taken responsibility. Full text and rfc822 format available.

Notification sent to Willy Gommel <wg3w@spamcop.net>:
Bug acknowledged by developer. Full text and rfc822 format available.

Message #17 received at 397997-done@bugs.debian.org (full text, mbox):

From: maximilian attems <max@stro.at>
To: 397997-done@bugs.debian.org
Subject: Re: My own recompilation of 2.6.16 or -17 kernel on my AMD64 fails. Kernel panics, says "tried to kill init!!"
Date: Wed, 21 May 2008 17:42:52 +0200
hmm your report has been sitting around as reporting a bug against
linux-2.6 when asking for user support is not the way to go.
please mail to your debian user list of choice for help.

thanks

-- 
maks




Bug archived. Request was from Debbugs Internal Request <owner@bugs.debian.org> to internal_control@bugs.debian.org. (Thu, 19 Jun 2008 07:41:43 GMT) Full text and rfc822 format available.

Send a report that this bug log contains spam.


Debian bug tracking system administrator <owner@bugs.debian.org>. Last modified: Mon Apr 21 00:19:07 2014; Machine Name: beach.debian.org

Debian Bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.