More info to cloud up things even more. I tried different versions of kernel and each one of them produced the same error. I went all the way back to 3.5.3 and up to 3.11.1. I might add, I ran that 3.5.3 kernel for months with no problems that I know of, including this one. My longest uptime with that version was 193 days.
Now ain't this interesting? Could this be a hardware issue? O_O Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
