From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1N0mn4-0004Z4-Mi for garchives@archives.gentoo.org; Thu, 22 Oct 2009 01:48:34 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0AD2EE08D1; Thu, 22 Oct 2009 01:48:33 +0000 (UTC) Received: from mail-px0-f200.google.com (mail-px0-f200.google.com [209.85.216.200]) by pigeon.gentoo.org (Postfix) with ESMTP id D35ABE08D1 for ; Thu, 22 Oct 2009 01:48:32 +0000 (UTC) Received: by pxi38 with SMTP id 38so378116pxi.10 for ; Wed, 21 Oct 2009 18:48:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=Q0ApeErQaA7arKtCg7lDGrCqXDhTzG2ttqm6RsAkLhM=; b=uViIty1h4Bqy3Ezkw+kjDO/vG3vIhJ+bJ8ylVrqBRlKl62KF3l43pg19T2ugWkE1z4 lC6WvNTWUeJErUxMD4CdYGmra/+XalUO4OQbSk15cOYlo5gTGWIYKIv3PxH1DL/q5aDl VYMre2u74Jvf49WjINRWeZ/sQkJOvyVKvKC1I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=KpDp4ZIsps8Z87dvAMViJH2TjzC36Yj3o58H9bVIQG0G7Wb09eb5NAw6Bxva+7CER9 s0ObVEgBIYFnAvBN83aBtmfmMiGoQdKeZn7CcProtI+xzsx3+p/hUEqeNT6VynvupBYL sniAvCiPTlaGJtqgDFKaA3s2R/h8R+KoeYCfU= Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.142.152.26 with SMTP id z26mr604447wfd.201.1256176112270; Wed, 21 Oct 2009 18:48:32 -0700 (PDT) In-Reply-To: References: <4ADF5BE6.2070506@gentoo.org> Date: Wed, 21 Oct 2009 19:48:32 -0600 Message-ID: Subject: Re: [gentoo-user] Re: kernel panic -- finding proper config diff From: Maxim Wexler To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=ISO-8859-1 X-Archives-Salt: be1630aa-8cba-4a2c-ac2c-43c037e29a1a X-Archives-Hash: e03cc64fcfa83bf387d6381c8f5a9e6c Ok, I went back and found what looks like a glaring error. The old config had the CONFIG_PHYSICAL_START=0x1000000 under processor options, the new one was missing a zero. A ha! sez I and "fixed" it. Nope. I get the exact same panic. Setting CONFIG_EXT2_FS_XATTR=y doesn't help either. On a related note, I see that CONFIG_NR_CPUS only allows for 8 in the 30 kernel. Trying any other number leads to an error "Invalid Number" , whereas for the 29 kernel, 64 seems to be the default. On 10/21/09, Maxim Wexler wrote: >> To me, that looks like /dev/sda1 (which is what the kernel is using as >> root=) doesn't contain any of the following: >> /sbin/init >> /etc/init >> /bin/init >> /bin/sh >> >> Noting that the kernel output implied that it was an ext2 filesystem, >> that looks like it mounted your /boot as /, which fails as there isn't >> any init available on it. > > The partitioning scheme and fs hasn't changed. Just the kernel. It > wasn't a problem before. Also, I don't think the fs id is significant > since, if you look at the photo attached to the bug report, ext3 is > involved in that case. In the new config have CONFIG_EXT2_FS_XATTR is > not set, whereas it's set 'y' in the old. Maybe that's it. The > page says choose N if unsure, which is what I did this time. > I'll wait to hear back from the group and give it another try. > > mw >