Hi tyler, I've seen a similar bug report to this http://bugzilla.kernel.org/show_bug.cgi?id=7929 which may be indicating a hardware specific problem more than a kernel problem. However, seeing that you are upgrading to the latest kernel is a good starting point for me to debug this further. The difficulty is in reproducing this problem. It may be worth exercising the filesystem by using the following command:
find / -type f -print I've looked at the (assembler) object and source code that is causing the Oops and there is no clear reason why the oops is occurring as the data should be correct - but clearly the Oops means it is isn't OK :-( Secondly, it may be worth doing a memtest86 soak test for several iterations (from the Ubuntu LiveCD or grub boot menu) just to be 100% sure the memory is not causing the dcache entries to get corrupted and hence trigger this Oops. Let me know of the results Colin -- [hardy] kernel crash https://bugs.launchpad.net/bugs/204064 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
