Just to say, this is one of those issues where bailing out of a situation early without restoring the state gets us in one big hole. The script offlines a CPU, then bails out. When detecting any error condition, code should try to restore back to the proper pre-test state where possible, e.g. on-lining the CPU. So, this needs fixing IMHO
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/926136 Title: CPU1 on Dell PowerEdge M610, R715 and IBM X3500 M3 goes offline after exercising frequency governors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/926136/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
