Comment 55 for bug 322867

This is not only a issue of time (which is tight), also that bug is quite annoying in that way that it seems to vanish when trying to get more debugging done. Also a big problem is that the aspire one seems the only machine to hit this. Not that this should count as an excuse. Currently I got a kernel rebooting over and over again (though I also had another one rebooting the whole night just to hit the bug once in the morning). It would be nice if some of you could volunteer to try that test kernel at http://people.ubuntu.com/~smb/bug322867/ and could tell me whether you get it crashing. Thanks.

Note, that kernel is back to not having debug messages but trying to force some sort of sync point at the moment of changing the kernel data to read only as adding debug printks at that point made it quite hard to hit anyways. That operation is quite safe with respect to other machines, so it might be a dumb approach to get around this on the aspire one.