As mentioned in upstream bugzilla, this was fixed (perhaps in 2.6.20), and I am no longer getting an oops since I installed linux-image-2.6.21-1-k7 -- Jonas Häggqvist rasher(at)rasher(dot)dk