Hi,

CONFIG_CMDLINE is used.
Maybe do the change to config-3.3 and do a 

make target/linux/clean
make

Now your kernel should be called with the CMDLINE.

/Regards
Peter
On Wednesday 15 August 2012 14:30:56 Bastian Bittorf wrote:
> we have sometimes the problem that a board will not
> come up after a remote reboot. we already switched on
> during early boot in /etc/init.d/00... these sysctl flags:
> 
> vm.panic_on_oom=1
> kernel.panic_on_oops=1
> kernel.panic=10
> 
> but this is sometimes not enough. i'am unsure what happens,
> but if a board hangs during boot a simple poweroff/on
> helps to "fix" that. we believe that adding panic=X to
> kernel-commandline would recover such situations.
> 
> how to do that in a clean way?
> we already tried to change e.g.
> 
> target/linux/ar71xx/config-3.3
> -> CONFIG_CMDLINE
> 
> but this has no effect. any tips?
> 
> bye, bastian.
> 
> _______________________________________________
> openwrt-devel mailing list
> [email protected]
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Reply via email to