From: ebiederm@xmission.com (Eric W. Biederman)
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Gene Heskett <gene.heskett@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.35-rc4, no boot
Date: Mon, 19 Jul 2010 08:40:34 -0700 [thread overview]
Message-ID: <m1mxtn7a4t.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <20100719083340.195d4496.rdunlap@xenotime.net> (Randy Dunlap's message of "Mon\, 19 Jul 2010 08\:33\:40 -0700")
Randy Dunlap <rdunlap@xenotime.net> writes:
> On Sun, 18 Jul 2010 23:42:09 -0700 Eric W. Biederman wrote:
>
>> Gene Heskett <gene.heskett@gmail.com> writes:
>>
>> > Phenom 9550, 4G ram, asus m2n-sli deluxe mobo, all sata drives (4 + optical
>> > burner)
>> >
>> > I have now built 35-rc4 4 times, the last 2 with
>> >
>> > 2.6.31-12-mdv.config & make oldconfig (lots of accepts), & build
>> >
>> > And a working .config from 2.6.35-rc3 + make oldconfig (no changes reported)
>> > & build.
>> >
>> > Both fail at the attached image point booting from a grub2 menu on a
>> > different drive that has been working with rc3 for quite a few boots but its
>> > all bitchy this morning so is booted to the mdv 2.6.31-12 kernel above ATM.
>> >
>> > Last .config also attached.
>> >
>> > What do I need to do here?
>>
>> That does sound bizarre. You have some weird initrd dependency on the
>> kernel doing something, but it isn't clear to me what that might be.
>> Shrug.
>>
>> Not being able to mount /dev and /sys feels like they simply weren't
>> compiled in. But your config suggests otherwise.
>
> I would change the second line below to be enabled:
>
> CONFIG_DEVTMPFS=y
> # CONFIG_DEVTMPFS_MOUNT is not set
>
> and give that a shot.
That is such a truly evil option. *shiver*
Eric
prev parent reply other threads:[~2010-07-19 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-05 16:50 2.6.35-rc4, no boot Gene Heskett
2010-07-19 6:42 ` Eric W. Biederman
2010-07-19 15:33 ` Randy Dunlap
2010-07-19 15:40 ` Eric W. Biederman [this message]
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=m1mxtn7a4t.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=gene.heskett@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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