If you can see a stack trace on the screen the first few lines of
at func_one+0x...
at func_two+0x...

or a photo would help.

I'm suprised the stack trace shows on the screen with db_panic 0
when you mentioned it previously booted to a black screen.




The output on the screen seems to be different each time, but repeatedly providing pieces of similar information and seemingly randomly some text is distorted with those white areas which are not always in perfect shape, but I include this URL below which has a bit more consistent piece of text that fits your described pattern. So previous 3 examples were done on yesterdays snapshot,
this one after getting another snapshot upgrade an hour or so ago.


I'm trying to grasp for how could I provide more information consulting someone on IRC in offtopic channel as I'm also reading man pages for crash and related. And as crash(8) provides an example of looking for information with pattern "function+04711" or similar, something like that is always visible
on the screen with your suggested boot options.


Disabling swap.encrypt does not seem to aid in genrating anything at /car/crash. But to follow with the example I see that I need to get sources and do stuff that's beyond me especially while any building on that machine takes centuries. SO I'll continue reading these man pages and try to understand how
exactly to get more information on this out of the system.


I could reinstall back to 6.8 unsure whether that or these snapshots use would be more useful in solving this. I'll just keep it on snapshots for now. Also I forgot to clarify that connecting external monitor when screen is blacked out results in just same black screen on that external monitor, with not responsive keyboard, ctrl_alt_esc does not do anything and I was also trying to adjust ddb.console to 1

that still did not let ctrl_alt_esc to happen from the point which can be seen in the picture.


P.S. I havent really used mailing lists before and previously I've attempted to send this with an image attachment, but havent noticed it being delivered for a while now and someone on #openbsd told me it might be better to use an upload service, so I'm resending this with an URL instead of attachment.

https://0x0.st/-XcC.jpg

Reply via email to