I can confirm this bug as well. Like Tech2010, I never see any hints of what's going on in the log files. The error has occurred while running 2.6.34, I have not yet seen it since moving to 2.6.35.
I can confirm this bug as well. Like Tech2010, I never see any hints of what's going on in the log files. The error has occurred while running 2.6.34, I have not yet seen it since moving to 2.6.35.