From: Bryan Donlan <bdonlan@gmail.com>
To: Anders Eriksson <aeriksson@fastmail.fm>
Cc: Yinghai Lu <yinghai@kernel.org>,
mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: Memory probing fails after 2.6.30 (bisected)
Date: Tue, 5 Jan 2010 16:59:27 -0500 [thread overview]
Message-ID: <3e8340491001051359m799df6bai86ec42dfff96f0f0@mail.gmail.com> (raw)
In-Reply-To: <20100105211522.57A3E33C5F5@tippex.mynet.homeunix.org>
On Tue, Jan 5, 2010 at 4:15 PM, Anders Eriksson <aeriksson@fastmail.fm> wrote:
>
> yinghai@kernel.org said:
>> whole boot log with debug with boot command line?
>>
>> > I can produce a pic of the dmesg for the fingered commit of needed.
>> boot that with earlyprintk=vga please.
>
> I managed to pull this one from the failing boot.
> Does it help?
>
> Linux version 2.6.30-rc2-00450-g8ecee46 (root@korven) (gcc version 4.3.2 (Gentoo 4.3.2-r3 p1.6, pie-10.1.5) ) #21 SMP Tue Jan 5 10:45:52 CET 2010
[...]
> EXT3-fs: mounted filesystem with writeback data mode.
> VFS: Mounted root (ext3 filesystem) readonly on device 8:5.
> Freeing unused kernel memory: 324k freed
> EXT3 FS on sda5, internal journal
Looks like the boot succeeded, at least long enough to mount the root
fs. Assuming you're not using bootsplash or something, you should have
seen something. Are you sure this is the log from the failed boot? If
it didn't make it to userspace, it won't leave anything in kern.log.
next prev parent reply other threads:[~2010-01-05 21:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 11:02 Anders Eriksson
2010-01-05 19:02 ` Yinghai Lu
2010-01-05 21:15 ` Anders Eriksson
2010-01-05 21:59 ` Bryan Donlan [this message]
2010-01-06 8:38 ` Anders Eriksson
2010-01-05 22:19 ` Yinghai Lu
2010-01-08 14:04 ` Anders Eriksson
2010-01-09 23:03 ` Yinghai Lu
2010-01-10 22:06 ` Anders Eriksson
2010-01-06 0:55 ` Robert Hancock
2010-01-06 8:32 ` Anders Eriksson
2010-01-06 23:53 ` Robert Hancock
2010-01-07 4:04 ` Bryan Donlan
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=3e8340491001051359m799df6bai86ec42dfff96f0f0@mail.gmail.com \
--to=bdonlan@gmail.com \
--cc=aeriksson@fastmail.fm \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=yinghai@kernel.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
all inboxes | Powered by JetHome®