not sure if anyone is picking this up, but I have the same on my TP-LINK WR941ND (v3), and if I connect a TTL-serial, I get this in the console:
procd: Console is alive
procd: - watchdog -
[ 3.410000] usbcore: registered new interface driver usbfs
[ 3.420000] usbcore: registered new interface driver hub
[ 3.420000] usbcore: registered new device driver usb
[ 3.680000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 3.680000] ehci-platform: EHCI generic platform driver
[ 3.750000] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
procd: - preinit -
[ 4.280000] eth0: link up (100Mbps/Full duplex)
Press the [f] key and hit [enter] to enter failsafe mode
- failsafe button wps was pressed -
- failsafe -
BusyBox v1.19.4 (2013-08-03 15:36:02 UTC) built-in shell (ash)
Enter 'help' for a list of built-in commands.
ash: can't access tty; job control turned off
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
BARRIER BREAKER (Bleeding Edge, r37660)
As you can see, it thinks I pressed the wps button, I assure you I did not. Seems to me as if the button config is wrong in the latest trunk. Just to trick it (in case of on/off mistake) I keep it pressed during boot, but it still went to failsafe.
Before I was always using an old 10.03.1 trunk to satisfaction, except coova-chilli was getting old. When I upgraded to 10.06 stable, OpenWRT did not communicate if both an LAN *and* WAN cable was attached during boot (worked WAN was disconnected and then connected later. Probably some switch config problem)
So I upgraded to latest trunk, r37660, and now it always goes to failsafe.
I'll probably try to figure out how to downgrade with tftp or something, but if some of the dev's could look at the TP-LINK failsafe button config, that would be great.