Hi, On a vanilla backfire 10.03 I have a case where a set of self compiled modules and a small program causes the box to instantly reboot. Upon reboot, I find no /sys/kernel/debug/crashlog file. Is the crashlog feature expected to work on this hw (I understand the ram needs to not be reinitialized during the reboot. Not sure if this hw doea that).
Long story: I'm trying to setup the box to automatically WoL a server based on specific traffic to it (e.g. a SYN to its port 80). I've compiled a small program to do that and it works perfectly if run on a normal x86 PC. However, on the WRT it reboots and nothing makes it to the remote syslog host (if anything is written at all to syslog). I effectively do: insmod netlink.ko insmod netlink_queue.ko WoLd <queue number> I create an iptables test rule with iptables -I OUTPUT -p icmp -j QUEUE and a single ping to the box kills it An alternaltive iptables -I OUTPUT -p icmp -j LOG rule puts the right lines in syslog without killing the box so the rules should be fine. I've been pondering if there are odd (alignment?) requirements on the mips netlink userspace interface or similar which doesn't trigger on x86, but not found anything. Any help to debug this would be appreciated. -A _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
