Re: Random system freeze.
On Mon, May 27, 2019 at 03:16:26PM +0200, Paco Esteban wrote: [...] > Later Karel Gardas suggested my RAM could be failing. I did a full test > with memtest86 which returned no errors. If somebody knows a better method > to test that (or if this tool is good enough to rule bad ram out), > please tell me. [...] I would too sucpect: it's a faulty RAM module. Give "stress" a try: https://people.seas.harvard.edu/~apw/stress/ Is this an IBM server? Test it with the DSA tools (Dynamis System Analysis). Marco.
Re: Good options for SAS HBA or SATA expansion cards?
On Mon, Apr 15, 2019 at 06:44:57AM +, John Long wrote: [...] > I found a lot of problems with various chipsets which > is why I asked on the list here to see what is supported well by > OpenBSD. [...] John, go get a LSI SAS 9260-8i HBA (it is based on the LSI SAS2008 chip) -Fast -Reliable -Professional server grade hardware -Supported by OpenBSD -Recommended by enthusiasts -Can be crossflashed (No Linux, Windows or whaterver box needed. Just an USB key and FreeDOS). -Rebranded by several hardware suppliers (LSI, IBM, broadcom...) -Cheap on eb*y -Please read https://www.servethehome.com/ibm-serveraid-m1015-part-4/ Please read the following lines: On Fri, Apr 12, 2019 at 10:22:14AM +0200, Marco Nuessgen wrote: > On Thu, Apr 11, 2019 at 07:50:36AM +, John Long wrote: > [...] > > Can anybody recommend some good 2 or 4 port SATA (internal) > > expansion > > cards or a SAS HBA that works well with OpenBSD? > > Have a look at the IBM ServeRaid M1015 SAS 6.0gbps SATA III. HBA. It > is > based on the LSI SAS2008 chip and can be crossflashed to: > LSI9211-IT Straight pass through no RAID > LSI9211-IR Pass through, RAID 0, 1, 1e, 10 > > https://www.servethehome.com/ibm-serveraid-m1015-part-4/ On Fri, Apr 12, 2019 at 02:13:35PM -0400, Johan Huldtgren wrote: [...] > mfi0 at pci1 dev 0 function 0 "Symbios Logic MegaRAID SAS2108 GEN2" > rev 0x05: apic 2 int 2 > mfi0: "LSI MegaRAID SAS 9260-8i", firmware 12.15.0-0239, 512MB cache [...] On Sun, Apr 14, 2019 at 02:53:34PM -0400, gwes wrote: [...] > I'll second the LSI Logic/Avago/Broadcom? SAS/SATA controllers. > They run as many disks as I want at full speed. As previously > mentioned they can be quite inexpensive if you buy one relabelled > as (for instance) an IBM card. [...] Marco
Re: Good options for SAS HBA or SATA expansion cards?
On Thu, Apr 11, 2019 at 07:50:36AM +, John Long wrote: [...] > Can anybody recommend some good 2 or 4 port SATA (internal) expansion > cards or a SAS HBA that works well with OpenBSD? Have a look at the IBM ServeRaid M1015 SAS 6.0gbps SATA III. HBA. It is based on the LSI SAS2008 chip and can be crossflashed to: LSI9211-IT Straight pass through no RAID LSI9211-IR Pass through, RAID 0, 1, 1e, 10 https://www.servethehome.com/ibm-serveraid-m1015-part-4/ Marco.
Re: IBM x3650 M3 fatal page fault in supervisor mode
Today I successfully reproduced the installation process. OpenBSD 6.4 Machine type/ model: 7945B2G Host firmware (UEFI) 1.22, build date 2018-06-04 System settings - Processors Power C-States Report C2 to OS Virtualization VT-d Cache Data Prefetch Data Reuse Execute Disable Hyperthreading System settings - Memory Memory Speed Max Performance LV-DIMM Power Memory Channel Mode Socket Interleave Patrol Scrub Demand Scrub Static Driver Impedance Memory Refresh <1x> Thermal Mode System settings - Devices and I/ O Ports Configure IDE mode Interrupt Round Robin System settings - Operating Modes Choose Operating mode System settings - Legacy Support Rehook INT 19h Legacy Thunk Support Boot Manager Change Boot Order The install medium must be the first in the boot order list. You have to boot without using the Boot-Manager (F12).
Re: IBM x3650 M3 fatal page fault in supervisor mode
Success, system boots! In the BIOS options everything is set to porformance and powersave to C3. In the boot order the USB or DVD device must be the first and then you have to boot without using the Boot-Manager (F12). With the Boot-Manager the start is not possible and fails. It seams that there are some things not initialized at this point.
Re: IBM x3650 M3 fatal page fault in supervisor mode
Hrvoje, thanks for your help. On Tue, Mar 12, 2019 at 11:47:36PM +0100, Hrvoje Popovski wrote: > On 12.3.2019. 22:26, Marco Nuessgen wrote: > > I am trying to install OpenBSD 6.4 amd64 on an IBM x-series server. The > > boot process halts after the kernel gets a "fatal page fault in > > supervisor mode". > > > > The machine is a x3650 M3 server, 2x six-core XEON E5645 2.4GHz, 88GB > > RAM, 3 x 146GB HDD, Serveraid M1015 7945 RAID adapter, 4 x Broadcom > > NetXtreme II. NICs. [...] > if you change your bios settings like: > - disable hyper-threading > - operating mode to maximum performance > - disable TPM device [...] I gave it a try - no effect. I also disabled virtualization and set powersave to C3. > if not, can you update firmware ? i can help you with that. I updated the firmware, system still hangs.
Re: IBM x3650 M3 fatal page fault in supervisor mode
Tom, thanks for your help! On Tue, Mar 12, 2019 at 09:55:56PM +, Tom Smyth wrote: [...] > but check out any advanced I/O PCI-E settings on your server board Bios [...] System still halts the boot process..
IBM x3650 M3 fatal page fault in supervisor mode
I am trying to install OpenBSD 6.4 amd64 on an IBM x-series server. The
boot process halts after the kernel gets a "fatal page fault in
supervisor mode".
The machine is a x3650 M3 server, 2x six-core XEON E5645 2.4GHz, 88GB
RAM, 3 x 146GB HDD, Serveraid M1015 7945 RAID adapter, 4 x Broadcom
NetXtreme II. NICs.
I have to install Nextcloud on it. The system is going to serve a small
non-profit organization I am in, so budget is low. Any help is greatly
appreciated!
What I tried so far:
-Boot amd install64 from CDROM:
entry point at 0x1000158
Copyright [...]
OpenBSD 6.4 (RAMDISK_CD) #348: Thu Oct 11 13:36:16 MDT 2018
[...]
real mem = 94427459584 (90053MB)
avail mem = 91561881600m(87320MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.5 @ 0x7f6bd000 (90 entries)
bios0: vendor IBM Corp. Version „-[D6E149AUS-1.09]-“ date 09/21/2018
bios0: IBM 90Y4784
acpi0 at bios0: rev 2uvm_fault(0x818a5ea0, ax80b467133ae7,
0, 1) -> e
fatal page fault in supervisor mode
trap type 6 code 0 rip 810f35fc cs 8 rflags 10282 cr2
80b467133ae7
cpl e rsp 81a069d0
gsbase 0x81872ff0 kgsbase 0x0
panic: trap type 6, code=0, pc=810f35fc
The operating system halted.
Please press any key to reboot.
-Tried to boot with the Serveraid card pulled out.
-Tried to boot with all adapters disabled in BIOS
-Tried "machine memory =128M" at the boot prompt.
-I made a 6.4 amd64 USB install medium and copied a 6.5 bsd.mp kernel
onto it. The boot process stopped at the kernel debugger prompt:
booting hd0a:bsd.mp: 10913719+2565136+34+0+671744
[681039+128+854832+595905]=0xfdcbc8
entry point at 0x1001000
[ using 2132936 bytes of bsd ELF symbol table ]
Copyright [...]
OpenBSD 6.5-beta (GENERIC.MP) #774: Tue Mar 5 18:29:25 MST 2019
[...]
real mem = 94427459584 (90053MB)
avail mem = 91555721216 (87314MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.5 @ 0x7f6bd000 (90 entries)
bios0: vendor IBM Corp. Version „-[D6E149AUS-1.09]- date 09/21/2018
acpi0 at bios0: rev 2Data modified on freelist: word 580502 of object
0x8000
00055ae0 size 0x18 previous type ??? (invalid addr 0x8012e1d35a14}
uvm_fault(0x81d61390, 0x8012e1d35a1c, 0, 1) -> e
kernel: page fault trap, code=0
Stopped at malloc+0x4a8: movq0x8(%r14),%rbx
ddb{0}>
I entered some commands at the debugger prompt:
ddb{0}> trace
malloc(19,21,9,19,6cf7d31ce462d81a,11) at malloc+0x4a8
_aml_setvalue(80073e88,3,11,80055aa8,42804d280b8fe628,
80073288) at _aml_setvalue+0xbb
aml_copyvalue(80073088,80073288,9a9510b4d6198009,
8000900073f08,80027049,0) at aml_copyvalue+0x155
aml_parse(80073e08,54,0,80073e08,480307f8c08a1716,
80073e08) at aml_parse+0x2805
acpi_parse_aml(80021400,8002703c,5378,80021400,
f2116dcad63d77c1,0) at acpi_parse_aml+0xc0
acpi_attach_common(80021400,fdf0,5311d428102ac7c1,
80023180,81fe3bc8,81d22870) at
acpi_attach_common+0x30d
config_attach(80023180,81cf8b50,81fe3bc8,
81251ae0,c08e080b991d0f22,32) at config_attach+0x1ee
bios_attach(80023100,80023180,81fe3d30,
80023100,4d8a47db40c7e6a4,80023100) at bios_attach+0x733
config_attach(80023100,81cf37c0,81fe3d30,
81595d20,c08e080b99615c62,81fe3d30) at
config_attach+0x1ee
mainbus_attach(0,80023100,0,0,7855bdcc20aee,0) at
mainbus_attach+0x93
cofig_attach(0,81cf3788,0,0,c08e080b992067c2,0) at
config_attach+0x1ee
config_rootfound(81ac29ae,0,b967e08c91ca8ab2,e060,
6e000,1f)
at config_rootfound+0xe3
cpu_configure(86e15cbe252c165a,e060,6e000,80024000,
81906e93,81fe3f00) at cpu_configure+0x33
main(0,0,e060,6e000,7da936cc,3f71f7f418380651) at
main+0x4b5
end trace frame: 0x0, count: -14
ddb{0}> show bcstats
Current Buffer Cache status:
numbufs 0 busymapped 0, delwri 0
kvaslots 6357 avail kva slots 6357
bufpages 0, dmapages 0, dirtypages 0
pendingreads 0, pendinwrites 0
highflips 0, highflops 0, damflips 0
ddb{0}> show panic
kernel page fault
uvm_fault(0x81d61390, 0x8012e1d35a1c, 0, 1) -> e
malloc(19,21,9,19,6cf7d31ce462d81a,11) at malloc+0x4a8
end trace frame: 0x81fe38d0, count: 0
ddb{0}> show socket
socket 0x81407558
so_type: 18641
so_options: 0xd189
so_linger: -30904
so_state: 0x87481475
so_pcb: 0xd98748d93948d987
so_proto: 0x481f8948085e8b49
so_sigio: 0xdfe90012cd94
so_head: 0xf4981dac858e514
so_onq: 0xfbd1c5c7490456bf
so_q0: @0x81407588 first: 0x91fa813881ac
so_q: @0x81407598 first: 0xbe1274c08581cf96
so_eq: next: 0xaa840fd9394800
so_q0len: 18687
so_qlen: -9935
so_qlimit: -30392
so_timeo:
