Comment 34 for bug 1275879

Revision history for this message
Seth Forshee (sforshee) wrote :

It turns out that the check which generates the panic here is likely invalid, and the code will handle the situation just fine, so the check can be removed. I've prepared a kernel with removes that check (and a related one), which I've temporarily replaced with a warning for testing so we can detect that the condition has been encountered. Please test this kernel and wait for a similar message and stack trace to appear in dmesg, and confirm that other than the appearance of the warning everything continues working fine. Thanks!

http://people.canonical.com/~sforshee/lp1278531/linux-3.13.0-14.34+lp1278531v201402280817/