Sun Netra X1 -- LOM: errors after clearing ram, etc.

[DruiD]

Ditto, I had issues with bad ram in my netra x1 and the messages I had 
resembled the ones you are seeing.

Sort-of keeping with the topic at hand, but has anyone else who has 
FreeBSD installed on a netra x1 had any issues with the time accuracy .

I've installed Freebsd 7.2 on my netra x1 and the time in the LOM seems 
to be off by a few hours and I can't seem to correct it.
Anyone else run into this and/or resolved it?

Thanks
-mb

/* Micah Breedlove
  * druid628 at comcast.net
  */

CONFIDENTIALITY: This email (including any attachments) may contain confidential, proprietary and privileged information, and unauthorized disclosure or use is prohibited. If you received this email in error, please notify the sender and delete this email from your system. Thank you.



On 01/08/2010 04:46 PM, Craig Butler wrote:
> On 07/01/2010 14:21, Zach Wendell wrote:
>> Anyone have any ideas about the LOM output below? Just keeps spitting 
>> out
>> the same thing over and over...
>>
>> Currently there are no drives installed (waiting for a coworker to 
>> bring in
>> an extra HDD and CD-ROM drive so we can install BSD), but there is a 
>> stick
>> of non-ECC PC133, 128MB ram installed.
>>
>> I have 3 sticks of non-ECC PC133, and one stick of non-ECC PC100 ram, 
>> all
>> 128MB. 2 of them immediately throw a "no memory installed, will not 
>> proceed"
>> error -- obviously those are bad (or most likely). The other 2 do what
>> you'll see below... So far, I've only tried one stick at a time, to 
>> rule out
>> bad combos, etc.
>>
>> Thanks in advance!
>> ~zmw
>>
>>
>>
>>
>>
>> lom>
>> LOM event: +0h31m28s host power on
>> `
>> Processor Speed = [Speed Jumper = 7] 400 MHz Baud rate is 9600
>> 8 Data bits, 1 stop bits, no parity (configured from lom)
>>
>> Firmware CORE  Sun Microsystems, Inc.
>> @(#) core 1.0.1 2001/02/19 09:55
>> Hardware Power ON
>> Verifying NVRAM...Done
>> Bootmode is 0
>> MCR0 = 36a0b004
>> MCR1 = c0804000
>> MCR2 = f110006
>> MCR3 = 6
>> Ecache Size = 256 KB
>> NVRAM Test
>> Icache Test
>> Dcache Test
>> MMU Test
>> Ecache Tag Addr Test
>> Ecache RAM Addr Test
>> Clearing E$ Tags Done
>> Clearing I/D TLBs Done
>> Probing memory
>> Done
>> MEMBASE=0x0
>> MEMSIZE=0x8000000
>> Data Line Test
>> Core Memory Test
>>
>> Processor Speed = 400 MHz
>> Baud rate is 9600
>> 8 Data bits, 1 stop bits, no parity (configured from lom)
>>
>> Firmware CORE  Sun Microsystems, Inc.
>> @(#) core 1.0.1 2001/02/19 09:55
>> Software Power ON
>> Verifying NVRAM...Done
>> Bootmode is 0
>> MCR0 = 36a0b004
>> MCR1 = c0804000
>> MCR2 = f110006
>> MCR3 = 6
>> Ecache Size = 256 KB
>> Clearing E$ Tags Done
>> Clearing I/D TLBs Done
>> Probing memory
>> Done
>> MEMBASE=0x0
>> MEMSIZE=0x8000000
>> Clearing memory...Done
>> Turing ON MMUs Done
>> Copy ROM to RAM (148440 bytes) Done
>> Orig PC=0x1fff0007efc  New PC=0xf0f07f54
>> [[ Omitted to shorten reply email -mb ]]
>> lom>
>> LOM event: +0h33m5s host power off
>> lom>
>> _______________________________________________
>> freebsd-sparc64 at freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64
>> To unsubscribe, send any mail to 
>> "freebsd-sparc64-unsubscribe at freebsd.org"
> I've seen the same on mine... turned out to be bad memory... It 
> doesn't like mixed speeds and I think they got to be in matched pairs...
> I could be wrong tho !
>
> Cheers
>
> Craig B
>
>
> _______________________________________________
> freebsd-sparc64 at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64
> To unsubscribe, send any mail to 
> "freebsd-sparc64-unsubscribe at freebsd.org"
>