From: Kyle McMartin <kyle@mcmartin.ca>
To: Guy Martin <gmsoft@tuxicoman.be>
Cc: linux-kernel@vger.kernel.org, linux-parisc@vger.kernel.org
Subject: Re: 64bit kernel not booting with CONFIG_PRINTK_TIME=y
Date: Thu, 17 Jul 2008 14:33:11 -0400 [thread overview]
Message-ID: <20080717183311.GA17111@phobos.i.cabal.ca> (raw)
In-Reply-To: <20080716185627.GC22716@phobos.i.cabal.ca>
On Wed, Jul 16, 2008 at 02:56:27PM -0400, Kyle McMartin wrote:
> On Wed, Jul 16, 2008 at 08:45:52PM +0200, Guy Martin wrote:
> >
> > This is the output of my L2000 when trying to do so :
> >
> > Information: No console specified on kernel command line. This is
> > normal. PALO will choose the console currently used by firmware
> > (serial). Command line for kernel: 'root=/dev/md1 console=ttyS0
> > palo_kernel=2/vmlinux' Selected kernel: /vmlinux from partition 2
> > ELF64 executable
> > Entry 00100000 first 00100000 n 2
> > Segment 0 load 00100000 size 4997120 mediaptr 0x1000
> > Segment 1 load 00634000 size 640576 mediaptr 0x4c5000
> > Branching to kernel entry point 0x00100000. If this is the last
> > message you see, you may need to switch your console. This is
> > a common symptom -- search the FAQ and mailing list at parisc-linux.org
> >
>
How about if you boot with printk_time=0, whilst CONFIG_PRINTK_TIME=y?
r, Kyle
next prev parent reply other threads:[~2008-07-17 18:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 18:45 64bit kernel not booting with CONFIG_PRINTK_TIME=y Guy Martin
2008-07-16 18:56 ` Kyle McMartin
2008-07-17 18:33 ` Kyle McMartin [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-07-17 17:05 Guy Martin
2008-07-19 21:54 ` Kyle McMartin
2008-07-19 23:04 ` Kyle McMartin
2008-07-20 9:23 ` Guy Martin
2008-07-29 4:29 ` Kyle McMartin
2008-07-29 17:42 ` Guy Martin
2008-07-16 17:58 Guy Martin
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=20080717183311.GA17111@phobos.i.cabal.ca \
--to=kyle@mcmartin.ca \
--cc=gmsoft@tuxicoman.be \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.