IL Ka,
Thanks for pointing it out. It will take a few days
before I can capture the output through the com
port.
Until then folks,
- Mensaje original -
De: IL Ka
Para: francis dos santos
CC: OpenBSD General Misc
Enviado: Wed, 06 Jun 2018 19:32:32 -0300 (ART)
Asunto: Re: Reboot loop
Oops, spoke to soon. I'll have to break the box open/read
manual to see if there is a com1 option through a header.
- Mensaje original -
De: IL Ka
Para: francis dos santos
CC: OpenBSD General Misc
Enviado: Wed, 06 Jun 2018 18:45:07 -0300 (ART)
Asunto: Re: Reboot loop
Ok, then try
There is no com port on this machine.
Thanks for the assistance.
- Mensaje original -
De: IL Ka
Para: francis dos santos
CC: OpenBSD General Misc
Enviado: Wed, 06 Jun 2018 18:45:07 -0300 (ART)
Asunto: Re: Reboot loop
Ok, then try to follow Stuart Longland's advice: use serial console
. Needless to say, if something gets displayed before
entering the tighter loop, I won't be able to see it.
I do not see a kernel panic.
- Mensaje original -
De: IL Ka
Para: francis dos santos
CC: OpenBSD General Misc
Enviado: Wed, 06 Jun 2018 17:29:55 -0300 (ART)
Asunto: Re: Reboot loop
ddb(4
in a blue moon the system actually boots. The inescapable loop
happens just before it switches to a higher resolution and displays
radeondrm0: ... x ... 32bpp (the actual resolution is irrelevant).
After detection of the ring 2 test failure.
- Mensaje original -
De: IL Ka
Para: francis dos
Theo,
>> uvm_fault(0x81db7f68, 0x58, 0, 1) -> e
> Just that one line? No other lines? I find that hard to believe.
I should've stated that the uvm_fault messageline get's repeated ad
infinitum. What can I do to get more debug info?
Hello,
My apologies if this should've gone to bugs@. There are 3 dmesg.boot
outputs within this text. The last successful boot of version #65 and
two outputs of #82 (xenodm enabled and disabled).
About two days ago I upgraded to the version #65 below, just to see if
the game unknown-horizons
7 matches
Mail list logo
