can you still reproduce this bug with newer linux kernel images, like the linux image 2.6.12? didn't see anymore of these bug reports. assuming it got fixed. thanks for your feedback. -- maks