Re: x86_64 account-for-memmap patch in 2.6.18-rc4-mm3 doesn't boot.
- From: Paul Jackson <pj@xxxxxxx>
- Date: Thu, 31 Aug 2006 10:01:56 -0700
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@xxxxxxx> 1.925.600.0401
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- x86_64 account-for-memmap patch in 2.6.18-rc4-mm3 doesn't boot.
- From: Paul Jackson
- Re: x86_64 account-for-memmap patch in 2.6.18-rc4-mm3 doesn't boot.
- From: Mel Gorman
- x86_64 account-for-memmap patch in 2.6.18-rc4-mm3 doesn't boot.
- Prev by Date: Re: - i386-early-fault-handler.patch removed from -mm tree
- Next by Date: Re: Fedora vs. swsusp (was Re: megaraid_sas suspend ok, resume oops)
- Previous by thread: Re: x86_64 account-for-memmap patch in 2.6.18-rc4-mm3 doesn't boot.
- Next by thread: 2.6.18-rc5-git3: compilation failure on numa-q
- Index(es):