There is a potential fix for this issue in the 2.6.26-20 kernel in proposed-updates. Can someone who has seen this issue please verify the fix? -- dann frazier