From: Chuck Ebbert <hidden> Date: 2007-03-26 00:28:08
Also in:lkml
I've now seen several reports of this message from the 3Com
3c59x driver. This seems to be a very old problem that has
somehow come back starting with kernel 2.6.19 AFAICT. What
could cause this?