I just took the offered update from 2.6.12-9 to 2.6.12-10, and this behavior has not improved. Was the patch slated to go into that kernel? If not, how long will it be before it winds up in an available kernel?
Thanks!
I just took the offered update from 2.6.12-9 to 2.6.12-10, and this behavior has
not improved. Was the patch slated to go into that kernel? If not, how long
will it be before it winds up in an available kernel?
Thanks!