I am suffering from this at present having upgraded from 2.6.32-25 (works) to 2.6.32-26 (gives above error). Is there anything I can do/provide to either a) provide evidence b) test solution?
Charles
I am suffering from this at present having upgraded from 2.6.32-25 (works) to 2.6.32-26 (gives above error). Is there anything I can do/provide to either
a) provide evidence
b) test solution?
Charles