On Monday 07 January 2013 13:17:24 Bastian Bittorf wrote:
> * Imre Kaloz <[email protected]> [07.01.2013 12:55]:
> > >the problem is: most routers are "in production" and not "serial
> > >attached" - so you have really a problem if a node ("rooftop" or "solar
> > >powered") dies during boot. if you are a developer, you can simple build
> > >your own image and disable this option, all other persons (>90%?) like to
> > >have a running/selfrebooting router when the kernel is panic'ing or there
> > >are serious problems.
> > 
> > And those persons likely won't deploy a router with an image that fails to
> > boot, right? So what's wrong with setting these values after boot up?
> this is not the idea:
> face the fact, that a kernel can panic seldom during boot,
> even before preinit, even if the kernel is good.

So if the kernel is good, evidently something else isn't... If you're shipping 
images where things are so messed up that the kernel will panic before it even 
gets to executing init, I'd look to fix the underlying symptoms rather than 
simply trying to work around it with this.

In any case, I'm very opposed to oops=panic - I've had times where the 
wireless or storage would oops, nothing critical enough that the device had 
any visible issues; I definitely would not want to panic on oops, I can 
guarantee you that anything doing that is going to get a reputation for being 
an "unstable POS" pretty fast. If a particular oops is as good as death for 
you, patch it up to a panic.

As for panic on OOM... again, bad idea - let the userspace tasks get killed 
and ensure you've got a watcher daemon that will spin it back up.

But again, the real solution is valgrind and not shipping garbage :)

> 
> the only way to survive is to auto-reboot.

And going into a constant reboot-loop achieves what exactly? If you're 
panicking before you even get to init, dollars to donuts manual intervention 
is required (read: flash a new image).

Regards,
Oliver
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Reply via email to