I'm not sure this isn't just more noise, but someone points out that I didn't say I checked the tags. Nor did I confirm that I always use explicit tags when building -stable, following the advice in the FAQ. So the following is just to confirm that, and what I say here should be ignored by anyone who doesn't care about what I am sure was the result of trying to carry a non-GENERIC kernel forward.
2015/08/04 20:10 "Stuart Henderson" <s...@spacehopper.org>: > > On 2015-08-04, Joel Rees <joel.r...@gmail.com> wrote: > > Thought login was freezing after the welcome message, beacause there was no > > prompt. So I hit the power button, watched it stop CUPS and something else > > and sync, and moved the old kernel back in for a build with GPT enabled, as > > a first wild guess. Just for the record, I had done a cvs up, with the rOPENBSD_5_7 specified, in .usr/src. I did not build userland before building the kernel. As I said in the original post, I did a csv up three times before building. But I'm sure I specified -rOPENBSD_5_7 each time. > > Same results, but I tried a few commands instead of > > just assuming no prompt meant freeze, and the "only" problem seems to be > > lack of prompt. Sort of. Piping to a pager doesn't page either. > > This kernel and userland are out of sync, there was a change made > at some point (I think it was between 5.7 and now but I could be wrong) > which did exactly this. IIRC this is the behaviour when you have newer > userland and old kernel. It's interesting that the behavior was the same. > Check your CVS trees and make sure they're > at the tags you expect (if that's 5.7, "cd /usr/src && cvs up -Pd -r > OPENBSD_5_7", if -current then -A instead of -r <tag>). I looked at /usr/src/CVS/Tag and it said TOPENBSD_5_7. Checked all the directories going down to /usr/src/sys/arch/amd64, and they were the same. I'm not sure where else I'd look to check, after the fact. (Shell defaults, so I lose my history when I log out.) Well, if it's more important than I think it is, I can practice my skills with find and grep and negative conditions. I'm weak on find expressions. I'm still using this wedged system, since the old kernel has no issues and I never compiled and installed a new userland. I can still look for things if I know what to look for, but I'm willing to assume that it was the non-standard compiler option (GPT), possibly interacting with the changes Stuart mentioned above. And the not being able to go backward. And I'm okay with this. I finally got a block of time to re-install on the outboard drive, and once that's up I'll backup the data on the internal drive and wipe the GPT-enabled system. And try to avoid doing too many things at the same time in the future. Now can I leave this thread behind? -- Joel Rees
