Re: Reboot loop

Basically yes. It's also possible to use puc(4) in some cases but you'll need to find the memory address yourself in pcidump and set it in the bootloader with "machine comaddr" and I think for some puc devices you might have a hard time setting the port to the baud rate that you want. --

Re: Reboot loop

On 08/06/18 11:36, IL Ka wrote: >> For a system console (with access to DDB etc.) you need a "standard" com > port. > Do you mean I can use "com", but not "ucom(4)", right? Using USB serial would require enumeration of the serial bus then selection of the appropriate protocol (there's at least a

Re: Reboot loop

> OpenBSD doesn't use ACPI to find an isa UART, it only looks in the fixed > locations compiled in to the kernel. Ok, I see that "com.c" does it by reading register, it even has comment "Probe for all known forms of UART" > For a system console (with access to DDB etc.) you need a

Re: Reboot loop

On 2018-06-06, IL Ka wrote: > There is >> com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo > in your dmesg. > > So, I assume your box reports com port somehow (via ACPI probably) OpenBSD doesn't use ACPI to find an isa UART, it only looks in the fixed locations compiled in to the kernel.

Re: Reboot loop

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

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

Re: Reboot loop

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

Re: Reboot loop

. 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

Re: Reboot loop

There is > com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo in your dmesg. So, I assume your box reports com port somehow (via ACPI probably) Some boxes may have comport built into chipset but no external cable for it. I have one, I bought cable separately. Another option is to use UART

Re: Reboot loop

santos CC: OpenBSD General Misc Enviado: Wed, 06 Jun 2018 16:01:24 -0300 (ART) Asunto: Re: Reboot loop https://www.openbsd.org/report.html See "How to create a problem report" step 5

Re: Reboot loop

Ok, then try to follow Stuart Longland's advice: use serial console. Connect your PC using null-modem cable to another pc, and in boot(8) prompt type: boot> set tty com0 On another PC run cu(1) or minicom or screen (or for Windows you may use PuTTY), connect to OpenBSD and you will see all your

Re: Reboot loop

On 06/06/18 22:56, francis.dos.san...@ciudad.com.ar wrote: > About two days ago I upgraded to the version #65 below, just to see if > the game unknown-horizons would run smooth. Starting the computer anew > after evaluating the performance of the game I noticed that the machine > rebooted

Re: Reboot loop

ddb(4): "ddb is invoked upon a kernel panic when the sysctl(8) ddb.panic is set to 1". I belive this value is default. So, kernel should be dropped into ddb on panic. Does it happen? What exactly do you see on screen along with uvm_fault? Do you see whole stacktrace? Check

Re: Reboot loop

https://www.openbsd.org/report.html See "How to create a problem report" step 5

Re: Reboot loop

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?

Re: Reboot loop

francis.dos.san...@ciudad.com.ar wrote: > 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

Re: reboot loop on -current, one machine of several

On 11/13/17 14:24, Gregory Edigarov wrote: ... >> scsibus1 at ahci0: 32 targets >> -sd0 at scsibus1 targ 2 lun 0: SCSI3 0/direct >> fixed naa.50025388400562d4 >> +sd0 at scsibus1 targ 0 lun 0: SCSI3 0/direct >> fixed

Re: reboot loop on -current, one machine of several

On 12.11.17 21:59, Nick Holland wrote: On 11/12/17 14:13, Otto Moerbeek wrote: On Sun, Nov 12, 2017 at 01:28:39PM -0500, Nick Holland wrote: Help. I was upgrading a few very similar machines to -current today. ONE of the three decided to be unpleasant. The thing has a serial console, and

Re: reboot loop on -current, one machine of several

> booting hd0a:/bsd: 8484712+2429968+244048+0+667648 [636809heap full > (0x9d304+65536) Maybe a corrupted or too big /bsd file? I am curious about the cause.

Re: reboot loop on -current, one machine of several

On 11/12/17 14:13, Otto Moerbeek wrote: > On Sun, Nov 12, 2017 at 01:28:39PM -0500, Nick Holland wrote: > >> Help. >> >> I was upgrading a few very similar machines to -current today. >> ONE of the three decided to be unpleasant. The thing has a >> serial console, and but it is about 370km from

Re: reboot loop on -current, one machine of several

On Sun, Nov 12, 2017 at 01:28:39PM -0500, Nick Holland wrote: > Help. > > I was upgrading a few very similar machines to -current today. > ONE of the three decided to be unpleasant. The thing has a > serial console, and but it is about 370km from me. :-/ > > Upgrade from Sep 9 current to