It looks like the drivers are making a few assumptions about headers and
length they shouldn't be. I don't think anyone is maintaining ARCnet any
more, all those who worked on it before have moved on to more real
networking. Its one of those things that may well just vanish in 2.5 if
nobody becomes a maintainer.
Looking at the code it looks like arcnet_header is a bit fragile when handed
non random "normal" network layer frames.
The length check is redundant (and wrong) - which explains the message, but
the oops isn't obvious from inspection. Probably you want to turn on debug
and see where in the build/rebuild of the header it dies
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/