Re: [OpenWrt-Devel] tune kernel commandline for headless/embedded systems / oops=panic panic=10 / panic_on_oom=1

2013-01-15 Thread John Szakmeister
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

Re: [OpenWrt-Devel] tune kernel commandline for headless/embedded systems / oops=panic panic=10 / panic_on_oom=1

2013-01-15 Thread Bastian Bittorf
* John Szakmeister j...@szakmeister.net [15.01.2013 12:52]: 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 thanks for this link John, i want to expose a

Re: [OpenWrt-Devel] tune kernel commandline for headless/embedded systems / oops=panic panic=10 / panic_on_oom=1

2013-01-07 Thread Imre Kaloz
On Fri, 04 Jan 2013 16:46:18 +0100, Bastian Bittorf bitt...@bluebottle.com wrote: * Imre Kaloz ka...@openwrt.org [04.01.2013 16:27]: I'm fine with the idea but not the way you did it, because if you're serial attached this gets annoying quite fast. Although we could make this a config

Re: [OpenWrt-Devel] tune kernel commandline for headless/embedded systems / oops=panic panic=10 / panic_on_oom=1

2013-01-07 Thread Bastian Bittorf
* 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,

Re: [OpenWrt-Devel] tune kernel commandline for headless/embedded systems / oops=panic panic=10 / panic_on_oom=1

2013-01-07 Thread Oliver
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,

Re: [OpenWrt-Devel] tune kernel commandline for headless/embedded systems / oops=panic panic=10 / panic_on_oom=1

2013-01-07 Thread Bastian Bittorf
* Oliver oli...@8.c.9.b.0.7.4.0.1.0.0.2.ip6.arpa [07.01.2013 21:46]: 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

Re: [OpenWrt-Devel] tune kernel commandline for headless/embedded systems / oops=panic panic=10 / panic_on_oom=1

2013-01-04 Thread Imre Kaloz
Hi, On Thu, 03 Jan 2013 11:57:56 +0100, Bastian Bittorf bitt...@bluebottle.com wrote: oops=panic panic=10 / panic_on_oom=1 Reply-To: X-Editor: vi http://ex-vi.sourceforge.net/ In our production networks we had issues that some device needed a manual restart, because there where

Re: [OpenWrt-Devel] tune kernel commandline for headless/embedded systems / oops=panic panic=10 / panic_on_oom=1

2013-01-04 Thread Bastian Bittorf
* Imre Kaloz ka...@openwrt.org [04.01.2013 16:27]: I'm fine with the idea but not the way you did it, because if you're serial attached this gets annoying quite fast. Although we could make this a config option and do all kind of magic to set it based on that, I suggest swapping your

[OpenWrt-Devel] tune kernel commandline for headless/embedded systems / oops=panic panic=10 / panic_on_oom=1

2013-01-03 Thread Bastian Bittorf
oops=panic panic=10 / panic_on_oom=1 Reply-To: X-Editor: vi http://ex-vi.sourceforge.net/ In our production networks we had issues that some device needed a manual restart, because there where hanging/panic/oopsing during boot-time. We added to the kernel-commandline the args: 'oops=panic

Re: [OpenWrt-Devel] tune kernel commandline for headless/embedded systems / oops=panic panic=10 / panic_on_oom=1

2013-01-03 Thread Jonathan Bither
Bastian, I currently use these settings on all of my devices as well. Perhaps the simplest way to apply these values without having to modify each target/sub-target is to put a patch under 'target/linux/generic/patches-*' for the kernel that sets these values to defaults within the kernel.