This was a one time event, and I don't know of a way to replicate it at this time. Monitors of the box showed it was largely idle at the time the bug exhibited itself. VMware reported repeated high/low CPU consumption from the time of the bug until it was forced off and restarted. The host WAS responding to pings, but was unable to be logged into and monitors of the host stopped at the time of the syslog message of the bug assertion. cacti graphs stopped capturing data at the time of the hang
Prior to the hang, cacti graphs showed a fair bit of Disk IO (for this VM), about 543 sectors/second read, and 1300 sectors/second write, where daily averages are 15 read and 44 write sectors/second respectively. cpu graph from VMware attached ** Attachment added: "VMware CPU graph during hang" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1329769/+attachment/4131125/+files/cpu.PNG -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1329769 Title: kernel BUG at /build/buildd/linux-3.2.0/lib/radix-tree.c:356 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1329769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
