As usual, I have been tracking, building, & booting head daily on my laptop for a while. Yesterday, having built head at r217090, I had updated to r217145, built, and booted it OK. (I then booted from my stable/8 slice for the rest of the day, as usual.) This morning, I updated to r217189, but on 3 out of 3 attempts to perform "make -j4 buildworld" while running head at r217145, the machine became unresponsive (while the fans were at top speed and the screen remained lit). I have DDB in the kernel config, but was unable to break to the debugger. After the 3 tries, I booted from the r217090 kernel; the "make -j4 buildworld" was successful. After booting head at r217189, I re-ran the "make -j4 buildworld" just to see if it survived the attempt; it did. So it *appears* that something after r217090 and before r217146 caused a problem, and something after r217145 and before r217190 has fixed or circumvented it. Of course, this isn't an exhaustive test, so take it with an appropriate grain of salt. I've attached dmseg.boot for those iinterested. Peace, david -- David H. Wolfskill david_at_catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key.
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:10 UTC