From: Paul Jackson <pj@sgi.com>
To: Mel Gorman <mel@csn.ul.ie>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org, haveblue@us.ibm.com,
apw@shadowen.org, ak@muc.de, benh@kernel.crashing.org,
paulus@samba.org, kmannth@gmail.com, tony.luck@intel.com,
kamezawa.hiroyu@jp.fujitsu.com, y-goto@jp.fujitsu.com
Subject: Re: x86_64 account-for-memmap patch in 2.6.18-rc4-mm3 doesn't boot.
Date: Thu, 31 Aug 2006 10:01:56 -0700 [thread overview]
Message-ID: <20060831100156.24fc0521.pj@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0608311650410.13392@skynet.skynet.ie>
Mel wrote:
> Have you any idea why the console garbling is happening?
Yeah - you're right - it's garbled. Looks like its dropping chars.
I don't know why, but I'm not surprised. It's a lab system with a
new (for us) way of rigging the console output. I just got this
particular x86_64's console connection to work at all yesterday.
I've been working indirectly through my good lab tech. I should
drive in to the lab that has this rig (an hour away) and check it
out in person, and see what can be done to get clean console output.
This may take a day or three to yield results, unless I get lucky.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
next prev parent reply other threads:[~2006-08-31 17:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-31 10:46 x86_64 account-for-memmap patch in 2.6.18-rc4-mm3 doesn't boot Paul Jackson
2006-08-31 16:17 ` Mel Gorman
2006-08-31 17:01 ` Paul Jackson [this message]
2006-09-01 8:38 ` Mel Gorman
2006-09-02 3:24 ` Paul Jackson
2006-09-04 9:45 ` Mel Gorman
2006-09-06 22:10 ` Paul Jackson
2006-09-07 14:16 ` Mel Gorman
2006-09-07 14:27 ` [PATCH] Fix memmap accounting by approximating the map size Mel Gorman
2006-09-07 15:33 ` Paul Jackson
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=20060831100156.24fc0521.pj@sgi.com \
--to=pj@sgi.com \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=apw@shadowen.org \
--cc=benh@kernel.crashing.org \
--cc=haveblue@us.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kmannth@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mel@csn.ul.ie \
--cc=paulus@samba.org \
--cc=tony.luck@intel.com \
--cc=y-goto@jp.fujitsu.com \
/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