Post B6coyEqrLG3gMB4WB6 by kaidenshi@exquisite.social
(DIR) More posts by kaidenshi@exquisite.social
(DIR) Post #B6cmwRxbQuQIWdFHPs by justine@snac.smithies.me.uk
0 likes, 0 repeats
OK then. I have just dowmloaded the #OpenBSD 7.9 img and done a fresh install on my desktop machine wiping everything from the past out. It boot perfectly fine on release so I proceeded to switch to my usual -current as per the docs and it ran through the upgrade without issue.Can you guess what happened when it tried to boot the /bsd kernel on this intel i5 machine ?That's right it failed with the same error 255 that the bugs mailinglist told me was an issue I had probably caused so go reinstall. I knew it wasn't me as it was extremely strange how I could rollback to the 14th May or earlier with out any issues it always booted the /bsd ( MP ) kernel but after the 14th May it would not but would boot the copy I had of the last working /bsd renamed /bsd.xyzI'm too tired to go back to the misc or bugs mailinglists to be told it's me. I know I wouldn't have got that response from the #FreeBSD devs so maybe it is a sign from above ? :runbsd:
(DIR) Post #B6co24xZxcoMsmTy0u by kaidenshi@exquisite.social
0 likes, 0 repeats
@justine I feel like this has to be a hardware issue, something in the -current kernel is not working with something (likely CPU but who knows?) with your particular hardware. Obviously this is difficult if not impossible to diagnose on your own, and I am pissed on your behalf that the devs are being dismissive about a bug report on the mailing lists especially as that is the project's preferred place to discuss bugs in -current. I'm sorry, I really wish I could help.
(DIR) Post #B6co25S48HCKPKkJX6 by justine@snac.smithies.me.uk
0 likes, 0 repeats
Don't apologise it really isn't your fault at all. I just find it strange that for near a year I have been running -current on that same machine and randomly the kernel stops booting after the 14th May snapshot. I can easily rollback to any date before that and it boots perfectly fine.
(DIR) Post #B6coyEqrLG3gMB4WB6 by kaidenshi@exquisite.social
0 likes, 0 repeats
@justine I wonder if it will be found and fixed in the next snapshot? But that will likely require a kernel developer with your CPU and close enough hardware to replicate it first. I'd love to try and replicate this myself just so you have another voice to add to the report. I don't have a 10th gen Intel system here at home but at work I have either a 10th or 11th gen (I honestly don't remember) I can try it on when I have downtime. I'll see if I can find the time this week to attempt it.
(DIR) Post #B6coyF5OTDgV5Fs7pg by justine@snac.smithies.me.uk
0 likes, 0 repeats
Thank you so much. I just find it strange that I seem to be the only person with this issue so far.
(DIR) Post #B6cpyxG8KqSO2SnbMW by jeanmimi@mamot.fr
0 likes, 0 repeats
@justine I had a problem of this sort. I had to update the firmwares to correct the problem.
(DIR) Post #B6cpyxQlhIxoZRm5wG by justine@snac.smithies.me.uk
0 likes, 0 repeats
Already tried that but thank you anyway.