I had to reboot my machine this morning due to an electrical outage overnight. I selected the previous kernel (linux-image-2.6.35-23-generic) rather than the default latest kernel (linux-image-2.6.35-24-generic), as I still require all four serial ports and I believed that they would all work under 2.6.35-23-generic.
However, the problem reported above has now also occurred under this same, older kernel.
Therefore, I conclude that this bug is not a regression after all, but is in fact caused by some other factor which appears to be unrelated to the kernel version. I am going to reboot into 2.6.35-24-generic to see if the problem goes away, and to see if any pattern can be established.
Any help with debugging this would be most appreciated.
An update on this bug.
I had to reboot my machine this morning due to an electrical outage overnight. I selected the previous kernel (linux- image-2. 6.35-23- generic) rather than the default latest kernel (linux- image-2. 6.35-24- generic) , as I still require all four serial ports and I believed that they would all work under 2.6.35-23-generic.
However, the problem reported above has now also occurred under this same, older kernel.
Therefore, I conclude that this bug is not a regression after all, but is in fact caused by some other factor which appears to be unrelated to the kernel version. I am going to reboot into 2.6.35-24-generic to see if the problem goes away, and to see if any pattern can be established.
Any help with debugging this would be most appreciated.