Re: Strange NVRAM corruption on Sun Blade 2500

[Sujit K M <sjt.kar%gmail.com@localhost>]

> ERROR: Last Trap: Fast Data Access MMU Miss

http://unix.ittoolbox.com/groups/technical-functional/solaris-l/fast-data-access-mmu-miss-4136629

>
> debug:
>
> The "debug:" prompt is just a restricted version of the "ok" prompt, but
> booting is disabled. A "set defaults" does not fix it, but after some playing
> around with NVRAM values, setting things back and forth (details of which I
> unfortunately did not log) the machine worked again - and then I restored
> all settings to normal.

could you try and boot from the CD Rom just to check whether it is an NVRAM
issue.

>
> This machine does not have the typical combined clock/nvram chip, but
> uses an extra Atmel 24C64B serial EEPPROM (mounted in a "holder" to
> allow easy replacement and hidden below a Sun host ID label, but stock
> PL27 package inside).
>
> First time through I actually thought this chip would be dead and got an
> (empty) replacement, which imediately fixed the issue.

Seems to be the only solution as per me.

>
> So my theory is that somehow the kernel call into OF to do the poweroff
> messes up some parts of the eeprom content, which "set defaults" does not
> cover. Or something. Maybe I should try to get access to that chip from
> some other device and dump full content, with working and non-working
> versions and cmpare.
>
> However, since we call OF to do the power-off, why does it work from the
> ok prompt, but not from within the NetBSD kernel? I don't feel happy trying
> this a lot ;-)
>
> Does anyone see something similar?
>
> Any ideas?
>
>
> Martin



-- 
-- Sujit K M

blog(http://kmsujit.blogspot.com/)