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 1N0i3v-0007Sh-04 for garchives@archives.gentoo.org; Wed, 21 Oct 2009 20:45:43 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 90B02E07A8; Wed, 21 Oct 2009 20:45:37 +0000 (UTC) Received: from mail-px0-f198.google.com (mail-px0-f198.google.com [209.85.216.198]) by pigeon.gentoo.org (Postfix) with ESMTP id 5E81BE07A8 for ; Wed, 21 Oct 2009 20:45:37 +0000 (UTC) Received: by pxi36 with SMTP id 36so325936pxi.2 for ; Wed, 21 Oct 2009 13:45:36 -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=DX/Lm1jqbhCY7ssHQ1wNW07MlVbcIPMxE4q8VlgdktI=; b=i9mRmPI6iOGBFvRb6UN1lpiRjXw4o22nujN/Ndvs/me51OSzsDLt9ofr5G9XOf/+ww ANocsDNRVDYshnMQTkVu+2bXP489IVCG3naYowFc7FTU4T9NmQ37MxSNnpB8R7udJjfJ PORFAq/MfywT67EbKhzUXJkNjIA8oMILkKjwc= 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=p7BtKyD6lKV9BbwbVEndliIRfc5pewqmQwWOul05uZlC3xpDm9vQLjjDzwZLpOdVue EAcKIZ1unCsW9BytUK4d+ezTB1CDtN22YhLLbswqcgSGfNjLIwfeDvZYZ/ieyUPi503H LhjWKIExoX2xYIgeutADPJtn2kPxlPO+CYJoI= 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.7.12 with SMTP id 12mr568718wfg.328.1256157936857; Wed, 21 Oct 2009 13:45:36 -0700 (PDT) In-Reply-To: <4ADF5BE6.2070506@gentoo.org> References: <4ADF5BE6.2070506@gentoo.org> Date: Wed, 21 Oct 2009 14:45:36 -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: 2907e713-eed1-466a-85de-2d8cda4be895 X-Archives-Hash: 805b71d710d06e2c41ec3b3205860404 > 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