FWIW, I cannot get my machine to lockup. Tried pushing the CPU by firing off 20+ processes like this:
$ cat /dev/urandom > /dev/null & All I got was this after about 5 hours: $ uptime 21:24:30 up 5:00, 2 users, load average: 25.00, 25.00, 24.83 $ vmstat 1 10 procs -----------memory---------- ---swap-- -----io---- -system-- ----cpu---- r b swpd free buff cache si so bi bo in cs us sy id wa 27 0 38164 380304 10396 48968 0 2 21 295 42 791 37 30 33 0 25 0 38164 380280 10396 48968 0 0 0 0 2 177 11 89 0 0 25 0 38164 380280 10396 48968 0 0 0 0 24 240 11 89 0 0 25 0 38164 380280 10396 48968 0 0 0 0 2 174 10 90 0 0 25 0 38164 380280 10396 48968 0 0 0 0 24 236 12 88 0 0 25 0 38164 380280 10396 48968 0 0 0 0 2 178 8 92 0 0 25 0 38164 380280 10396 48968 0 0 0 0 24 238 13 87 0 0 25 0 38164 380280 10396 48968 0 0 0 0 2 183 11 89 0 0 25 0 38164 380280 10396 48968 0 0 0 0 24 246 10 90 0 0 25 0 38164 380280 10396 48968 0 0 0 0 2 176 11 89 0 0 However, this is a headless machine to which I've ssh'ed to run these processes. Dunno if that matters. Anyone got a suggestion for stress-testing the NIC? Regards, - Robert ** Attachment added: "version.log" http://launchpadlibrarian.net/13953407/version.log -- Linux kernel 2.6.24-12 lockup https://bugs.launchpad.net/bugs/204996 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
