linux-kernel - Re: Kernel panic in 2.6.19-rc1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <6844644e0611170644n32aeb454p72e8b1ec9733f30a@mail.gmail.com>
Date:	Fri, 17 Nov 2006 09:44:43 -0500
From:	"Doug Reiland" <dreiland@...il.com>
To:	akpm@...l.org, linux-kernel@...r.kernel.org
Subject: Re: Kernel panic in 2.6.19-rc1

Andrew Morton sorry I missed your reply:

To recap, I said:
     FYI, I had to get CONFIG_SYSCTL_SYSCALL set to solve my
2.6.19-rc1 boot panic.
     Actually, I couldn't get CONFIG_SYSCTL_SYSCALL=y to stick so I
modified kernel/sysctl.c's ifdefs.

You said:
    What boot panic was that?
    It depends on CONFIG_EMBEDDED.

The panic was because init died. I get an error message about unknown
library version (exact message I can't recall) and then the panic.

Again, I am running a new 2.6.x kernel on an old distribution so my
init binary or run-time loader might still be depending on SYSCTL.

I am now playing with a x86_64 kernel and saw this same problem. Your
CONFIG_EMBEDDED hint helped. I set that and CONFIG_SYSCTL_SYSCALL
stays on.

Thanks again and sorry for not attaching this to the original email thread.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/