public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Maxim Wexler <maxim.wexler@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: kernel panic -- finding proper config diff
Date: Wed, 21 Oct 2009 19:48:32 -0600	[thread overview]
Message-ID: <a0811460910211848o7788c515k8529a602f69385b9@mail.gmail.com> (raw)
In-Reply-To: <a0811460910211345t4c6afac4s559082afe0d9c9fd@mail.gmail.com>

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 <maxim.wexler@gmail.com> 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
> <help> 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
>



  parent reply	other threads:[~2009-10-22  1:48 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-21 18:25 [gentoo-user] kernel panic -- finding proper config diff Maxim Wexler
2009-10-21 18:56 ` [gentoo-user] " Maxim Wexler
2009-10-21 19:07 ` Jonathan Callen
2009-10-21 19:13   ` Alan McKinnon
2009-10-21 20:22     ` Maxim Wexler
2009-10-21 20:35       ` Albert Hopkins
2009-10-21 20:45   ` Maxim Wexler
2009-10-22  1:19     ` walt
2009-10-22  3:28       ` Maxim Wexler
2009-10-22  3:37         ` William Kenworthy
2009-10-22  3:45           ` Maxim Wexler
2009-10-22 14:18         ` Neil Bothwick
2009-10-22 18:17           ` Maxim Wexler
2009-10-22 18:29             ` Neil Bothwick
2009-10-22 18:36             ` Maxim Wexler
2009-10-22 18:53               ` Alan McKinnon
2009-10-22 20:43                 ` Maxim Wexler
2009-10-22 19:31               ` Neil Bothwick
2009-10-22 18:50             ` Alan McKinnon
2009-10-24 10:41               ` Stroller
2009-10-22  1:48     ` Maxim Wexler [this message]
2009-10-22 23:31 ` walt
2009-10-23  0:31   ` Neil Bothwick
2009-10-23 16:02   ` walt
2009-10-23 21:57     ` Maxim Wexler
2009-10-23 22:54       ` walt
2009-10-24  1:33         ` Richard Marza
2009-10-24  4:05           ` Maxim Wexler
2009-10-24  7:44             ` Neil Bothwick
2009-10-24  7:44       ` Neil Bothwick
2009-10-26  4:52         ` Maxim Wexler
2009-10-26  9:10           ` Neil Bothwick
2009-10-29  4:38             ` waltdnes
2009-10-29  5:45               ` Maxim Wexler
2009-10-29  5:42             ` Maxim Wexler
2009-10-23  0:56 ` Jonathan Callen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a0811460910211848o7788c515k8529a602f69385b9@mail.gmail.com \
    --to=maxim.wexler@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox