Nope... it is solid so far on my UP x86 box running 2.2.2pre4. This should
be a kernel issue and not a netatalk issue. netatalk shouldn't be able to
lock the kernel.
Brian Macy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/