Am 14. Januar 2019 16:40:48 MEZ schrieb Theo de Raadt <dera...@openbsd.org>:
>It sure looks like you have a pile of your own changes which are highly
>unconventional,
>and you are very far away from a stock OpenBSD configuration.
Well, that's right so far, because I have decided to use the tool resflash to
create images (https://stable.rcesoftware.com/resflash/).
That's the "only" changes, that made the system away from a stock OpenBSD
configuration.
But sure, to get this also out of the way of possible causes, I could install
current to the server on the hard disc. I just thought resflash just did some
changes to the boot process and I assume the issue more at the bridge-part.
>Having made those decisions, you are responsible for your own issues.
>
>Sorry.
That seems fair enough to me.
Let me have a look at the ddb stuff, Stuart mentioned and the splassert stuff
Hrvoje mentioned, before I'm going to reinstall the server with a stock current
OpenBSD.
Cheers,
Marco
>> Hi Stuart,
>>
>> thanks for having a look at this.
>>
>>
>> > Is it the same or different hardware type and BIOS version for the
>> > working and hanging machines? (maybe diff the two dmesgs)
>> >
>> > Same or different filesystem mount options? (Are you using
>softdep?)
>>
>> it's (nearly) the same hardware.
>>
>> But thanks to your hint of diffing the dmesg outputs I found a small
>> difference :
>>
>>
>> * server1:
>>
>> bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xec200 (78 entries)
>> bios0: vendor American Megatrends Inc. version "4.6.5" date
>03/02/2015
>> bios0: INTEL Corporation DENLOW_WS
>>
>> * server2:
>>
>> bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xec200 (77
>entries)
>> bios0: vendor American Megatrends Inc. version "4.6.5" date
>03/02/2015
>> bios0: INTEL Corporation
>DENLOW_WS
>>
>>
>> * server2 has an additional entry, I do not see on server1
>>
>> acpipci0 at acpi0 PCI0: 0x00000010 0x00000011 0x00000000
>>
>>
>> * server2 also seems to have a slightly different memory setup :
>>
>> spdmem0 at iic0 addr 0x50: 8GB DDR3 SDRAM PC3-12800
>>
>> * whereas server1 has :
>>
>> spdmem0 at iic0 addr 0x50: 4GB DDR3 SDRAM PC3-12800
>> spdmem1 at iic0 addr 0x52: 4GB DDR3 SDRAM PC3-12800
>>
>>
>>
>> On the filesystem I can't see any differences :
>>
>> * server1:
>> $
>>
>mount
>
>>
>> /dev/sd0d on / type ffs (local, noatime, nodev,
>> read-only)
>> mfs:14405 on /tmp type mfs (asynchronous, local, noatime, nodev,
>nosuid,
>> size=65536 512-blocks)
>> mfs:35803 on /dev type mfs (asynchronous, local, noatime, noexec,
>> size=12288 512-blocks)
>> mfs:30894 on /etc type mfs (asynchronous, local, noatime, nodev,
>nosuid,
>> size=65536 512-blocks)
>> mfs:75826 on /var type mfs (asynchronous, local, noatime, nodev,
>noexec,
>> size=131072 512-blocks)
>> mfs:23894 on /usr/lib type mfs (asynchronous, local, noatime, nodev,
>> nosuid, size=262144 512-blocks)
>> mfs:21714 on /usr/libexec type mfs (asynchronous, local, noatime,
>nodev,
>> size=262144 512-blocks)
>> $ cat
>>
>/etc/fstab
>
>>
>> dd6727251088320b.a /mbr ffs rw,noatime,nodev,noexec,noauto 1
>> 2
>> dd6727251088320b.d / ffs ro,noatime,nodev 1
>> 1
>> dd6727251088320b.f /cfg ffs rw,noatime,nodev,noexec,noauto 1
>> 2
>> dd6727251088320b.i /efi msdos rw,noatime,nodev,noexec,noauto 0
>> 0
>> swap /tmp mfs rw,async,noatime,nodev,nosuid,-s32M 0
>> 0
>>
>$
>
>>
>>
>>
>> * server2:
>>
>> $ mount
>> /dev/sd0e on / type ffs (local, noatime, nodev, read-only)
>> mfs:19530 on /tmp type mfs (asynchronous, local, noatime, nodev,
>nosuid,
>> size=65536 512-blocks)
>> mfs:65784 on /dev type mfs (asynchronous, local, noatime, noexec,
>> size=12288 512-blocks)
>> mfs:41465 on /etc type mfs (asynchronous, local, noatime, nodev,
>nosuid,
>> size=65536 512-blocks)
>> mfs:86708 on /var type mfs (asynchronous, local, noatime, nodev,
>noexec,
>> size=262144 512-blocks)
>> mfs:90223 on /usr/lib type mfs (asynchronous, local, noatime, nodev,
>> nosuid, size=262144 512-blocks)
>> mfs:22430 on /usr/libexec type mfs (asynchronous, local, noatime,
>nodev,
>> size=262144 512-blocks)
>> $ cat
>>
>/etc/fstab
>
>>
>> 9f97b8d42ceedbf4.a /mbr ffs rw,noatime,nodev,noexec,noauto 1
>> 2
>> 9f97b8d42ceedbf4.e / ffs ro,noatime,nodev 1 1
>> 9f97b8d42ceedbf4.f /cfg ffs rw,noatime,nodev,noexec,noauto 1
>> 2
>> 9f97b8d42ceedbf4.i /efi msdos rw,noatime,nodev,noexec,noauto 0
>> 0
>> swap /tmp mfs rw,async,noatime,nodev,nosuid,-s32M 0 0
>> $
>>
>>
>>
>> For the other suggestions, let me run the system with "
>>
>> sysctl ddb.console=1" and wait until the problem will occur to answer
>your questions as soon I have the additional information.
>>
>>
>> Cheers,
>> Marco
>>
>>
