549884e502
received frame under certain conditions. wpaul said the length 0xfff0 is special meaning that indicates hardware is in the process of copying a packet into host memory. But it seems there are other cases that hardware is busy or stuck in bad situation even if the received frame length is not 0xfff0. To work-around this condition, add a check that verifys that recevied frame length is in valid range. If received length is out of range reinitialize hardware to recover from stuck condition. Reported by: Mike Tancsa ( mike AT sentex DOT net ) Tested by: Mike Tancsa Obtained from: OpenBSD MFC after: 1 week |
||
|---|---|---|
| .. | ||
| alpm.c | ||
| amdpm.c | ||
| amdsmb.c | ||
| if_mn.c | ||
| if_pcn.c | ||
| if_pcnreg.h | ||
| if_rl.c | ||
| if_rlreg.h | ||
| if_sis.c | ||
| if_sisreg.h | ||
| if_ste.c | ||
| if_stereg.h | ||
| if_tl.c | ||
| if_tlreg.h | ||
| if_wb.c | ||
| if_wbreg.h | ||
| if_xl.c | ||
| if_xlreg.h | ||
| intpm.c | ||
| intpmreg.h | ||
| locate.pl | ||
| ncr.c | ||
| ncrreg.h | ||
| nfsmb.c | ||
| viapm.c | ||