Re: Current kernel with http://gnats.netbsd.org/39965 and pmap patches

Actually...  This could be the ATARITT kernel serial console issue popping 
up again.  I didn't see any random garbage data on the screen this time so I 
didn't think that was the culprit, but other than that the failure mode is 
similar.  I do have a null modem plugged into the serial port since I'm 
using ghostlink (...although I thought the issue was probably caused by the 
UPS that had been plugged into the other port.  I hadn't had any problems 
booting ATARITT kernels via ghostlink recently with the UPS detached.).

Anyway, I'll try tomorrow with the ATARITT kernel again but downloaded to a 
local drive so I don't have anything plugged into any serial ports.  If that 
doesn't work, I'll try a CD-ROM install using the BOOT kernel below.

David Ross
[email protected]

----- Original Message ----- 
From: "Izumi Tsutsui" <[email protected]>
To: <[email protected]>; <[email protected]>
Cc: <[email protected]>; <[email protected]>; <[email protected]>; 
<[email protected]>; <[email protected]>; <[email protected]>
Sent: Sunday, December 28, 2008 11:02 PM
Subject: Re: Current kernel with http://gnats.netbsd.org/39965 and pmap 
patches


> David Ross wrote:
>
>> Yeah, Tsutsui's kernel below boots and loads sysinst properly.  Does this
>> one have the same same changes to test?  I have not tried using this one 
>> to
>> do an install yet.  It's a little easier for me to use the ATARITT kernel
>> since it has networking support, but I can try the install with this one
>> using a spare CD-ROM if necessary.
>
> Major diffrences between ATARITT (or FALCON) and BOOT
> which might affect pmap changes are:
> - kernel size (due to many MI options)
> - options SERCONSOLE
> - options RELOC_KERNEL
> - options MSGBUFSIZE
>
> I guess the last two items require some special handling
> during pmap initialization. (conversion between PA and VA etc.)
> ---
> Izumi Tsutsui
>
>