Handle corrupted dmesg output better - sometimes, we get junk left
around from the last boot, and we have more than one CPU: line. Sometimes (such as at Wisc.), the first instance contains garbage. So, instead of exiting after the first CPU: line, use a different method of handling unknown CPU speeds, modeled after chipset.awk .
Showing with 18 additions and 3 deletions