On Mon, Jan 7, 2013 at 10:51 AM, Oliver
<oli...@8.c.9.b.0.7.4.0.1.0.0.2.ip6.arpa> wrote:
> On Monday 07 January 2013 13:17:24 Bastian Bittorf wrote:
>> * Imre Kaloz <ka...@openwrt.org> [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.
Just to be clear, there are other reasons why things can go wrong and
still have a good kernel. Check out the soft errors page on
Wikipedia:
<http://en.wikipedia.org/wiki/Soft_error>
-John
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
