From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: Problem with current kernel and old sh3 machines
Date: Thu, 30 Jul 2009 05:25:26 +0000 [thread overview]
Message-ID: <20090730052525.GA29064@linux-sh.org> (raw)
In-Reply-To: <aec7e5c30907232030pf8d5e92h1ae9d73d5a5e8e44@mail.gmail.com>
On Wed, Jul 29, 2009 at 10:11:45PM -0300, Rafael Ignacio Zurita wrote:
> Node 0: start_pfn = 0xd000, low = 0xe000
> Zone PFN ranges:
> Normal 0x0000d000 -> 0x0000e000
> Movable zone start PFN for each node
> early_node_map[1] active PFN ranges
> 0: 0x0000d000 -> 0x0000e000
> Built 1 zonelists in Zone order, mobility grouping off. Total pages: 4064
> Kernel command line: mem\x16M init=/bin/sh earlyprintk=serial
> NR_IRQS:256
> PID hash table entries: 64 (order: 6, 256 bytes)
> Console: colour dummy device 80x25
> console handover: boot [sercon0] -> real [tty0]
>
> and I guess that the system hangs.
> Should I try other printks in other places? Suggestions?
>
earlyprintk=serial,keep
next prev parent reply other threads:[~2009-07-30 5:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-24 3:30 Problem with current kernel and old sh3 machines Magnus Damm
2009-07-24 14:49 ` Rafael Ignacio Zurita
2009-07-27 2:40 ` Magnus Damm
2009-07-30 1:11 ` Rafael Ignacio Zurita
2009-07-30 5:25 ` Paul Mundt [this message]
2009-09-11 4:18 ` Rafael Ignacio Zurita
2009-09-12 3:58 ` Rafael Ignacio Zurita
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=20090730052525.GA29064@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox