panic reboot stuck in rtas_os_term

[Olaf Hering]

 On Sun, May 08, Olaf Hering wrote:

>  On Sun, May 08, Olaf Hering wrote:
> 
> > 
> > A panic does not trigger a reboot anymore on JS20, rtas_os_term() is stuck in
> > RTAS. .config is the defconfig.
> > The panic reboot works on a p630, but I miss the 'rebooting in 180 seconds' message.
> > Any ideas how to fix that?
> > 
> > VFS: Cannot open root device "<NULL>" or unknown-block(8,2)
> > Please append a correct "root=" boot option
> > Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,2)
> >  rtas [swapper]:   Entering rtas_call
> > rtas [swapper]:         token    = 0x1a
> > rtas [swapper]:         nargs    = 1
> > rtas [swapper]:         nret     = 1
> > rtas [swapper]:         &outputs = 0x0
> > rtas [swapper]:         narg[0] = 0x72cfa8
> > rtas [swapper]:         entering rtas with 0x72c728
> 
> This appears to be a firmware bug, fails now also with sles9 sp1 kernel.
> ibm,os-term was appearently added with recent firmware updates.

What is the purpose of ibm,os-term anyway?
I just noticed that a POWER4 lpar did not reboot after a panic.
Thats clearly not the way panic=$bignum was designed.
Can we make ppc_md.panic optional please?