The night before yesterday, I have run stress-ng for one night, looks it isn't crashed on mcdivitt.
Yesterday, I found my system is upgraded from trysty to vivid directly and the 'systemd' package isn't installed, then 'systemd-timesyn' can't be found, so I install the package and make sure systemd-timesyncd is installed because the process was reported two times in Colin's reports. Then last night, I enable the the server by 'sudo timedatectl set-ntp true' before running the test, but still not crash, see the logs attached. ** Attachment added: "mcdivitt-log-not-duplicatd.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1469218/+attachment/4423691/+files/mcdivitt-log-not-duplicatd.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1469218 Title: HP ProLiant m400 Server sda timeout causes file system hang Status in linux package in Ubuntu: Triaged Bug description: While running stress-ng on a ProLiant m400 Server I managed to cause the disk controller to timeout which causes a file system hang. I am wondering if the timeout was causes because I completely overloaded the system causing it to be slow on ata handling times. I ran: stress-ng --all 64 -t 600 -v and the machine slowly clogged up with stress processes, and finally hit the hang. Had to reboot the system. Attached is a kernel log. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1469218/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
