• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: kernel panics and nvram issues
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: kernel panics and nvram issues


  • Subject: Re: kernel panics and nvram issues
  • From: Godfrey van der Linden <email@hidden>
  • Date: Fri, 11 Feb 2005 22:11:58 -0800

Finally I might add that I have recently discovered the sysctl for allowing dynamic modification of boot arguments. This stuff is fairly easy to do, You may want to use bug-reporter to file an enhancement request.

Are you guys building your own kernel? If so we may be able to work out a sysctl to allow the setting of the 'boot-args' in the kernels current state.

Cheers

Godfrey

On Feb 9, , at 11:05, Garth Cummings wrote:

Hi David,

On Feb 9, 2005, at 10:21 AM, David Osguthorpe wrote:

On Tue, Feb 08, 2005 at 03:12:11PM -0800, Shantonu Sen wrote:

You are most likely running the nvram(8) commandline tool and not
rebooting. The core dumping settings will not be honored (they are only
parsed at startup) and the settings will not be preserved.



Is there no way to force the nvram update without rebooting?

The issue is not that NVRAM requires a reboot to be changed. It doesn't. The NVRAM has indeed been updated once you've run the nvram command.


The issue is that the kernel only reads the changed variables out of NVRAM at boot time.

Anybody know if the kernel hooks in the IOKit for the NVRAM allow
for the creation of such a program?

Is the NVRAM memory mapped into the kernel such that the bsd kvm_read/kvm_write
calls can be used to update the NVRAM?

Neither of these will affect when the kernel will next read NVRAM.


It makes for difficult cluster management if you have to reboot the nodes just to udpate the nvram variables

A valid point. But if you've panicked, you have to reboot anyway. You can save one reboot by updating NVRAM using the Open Firmware UI, but that requires you to be physically present at the server. There are a few Technical Q&As showing how to update the config variables using the OFUI.



David

--gc __________________________________________________________________ Garth Cummings Apple Developer Technical Support email@hidden

http://developer.apple.com/technicalsupport
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden

_______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >kernel panics and nvram issues (From: David Osguthorpe <email@hidden>)
 >Re: kernel panics and nvram issues (From: Shantonu Sen <email@hidden>)
 >Re: kernel panics and nvram issues (From: David Osguthorpe <email@hidden>)
 >Re: kernel panics and nvram issues (From: Garth Cummings <email@hidden>)

  • Prev by Date: Re: Serial port arbitration (UUCP device locking protocol?)
  • Next by Date: Re: Serial port arbitration (UUCP device locking protocol?)
  • Previous by thread: Re: kernel panics and nvram issues
  • Next by thread: bsd static lib question
  • Index(es):
    • Date
    • Thread