Ok, now I dunno what is worse that my very stable laptop has gone nuts or that I'm not surprised by it at all.
mentally back tracing events:
using urxvt with zsh
vim running in background during perl file editing session
linux-flock playing my favorite radio station via linux-mplayerplug-in and native mplayer
mv ./myfile.mp3 /tmp/ -> trying to move a file off a sshfs mount to /tmp
system locked up with sound stuck replaying a single note
tried to switch to vtty1
system auto-rebooted, never saw the vtty
On reboot I restarted flock and tried to move the file again, system locked up and rebooted when I tried to switch to vtty0...
Now linux-flock segfaults when I run it and the only other linux app I know that is handy, realplayer also segflauts. I ain't seen any thing informative in /var/ yet either.
Now, my Windows XP machine Blue Screen of Deaths and occasionally Black Screens of Deaths! On me all the time when listing to music while using the server browser in Raven Shield, if I use any thing other then WMP: trying WinAmp == instanto death and often same with MPlayer using the usual DirectX related sound/video opts.
So why do I find it sad that for me it is not so much of a shocker that with a third party kernel module installed from pre-compiled binary (fuse) that was ported from another OS, moving data from a mounted network file system (sshfs) to the local hard drive through SSH and said driver, while running binary programs designed for an entirely different system (linux flock+mplayerplug-in), could possibly cause a system to crash?
At least it's got a better damn reason then Windows XP has got looooool
I've tried fsck'ing the drive but the Linux ABI still seems FUBAR.. All things considered with SSHFS and SMB/CIFS, I am seriously considering putting both NFS and AFS into testing here to see if either will fill the gap.