Re: SATA slow/timeouts, AMD 600 Series AHCI, OpenBSD 7.4 amd64

2024-01-31 Thread blb8
> Divan Santana  [20240131 165546 +0200]:
> 
> b...@po.cwru.edu writes:
> 
> > Onboard SATA seems to require additional initialization on a Gigabyte
> > B650 in OpenBSD 7.4 amd64; basic requests take minutes to complete and
> > each block read takes 30 seconds.  During boot, attached SSDs will block
> > pending these requests; 
> 
> I have the same issue.  I was hoping to install openbsd 7.4 on this new
> AMD MSI board server.
> 
> This issue is quite a show stopper for me.
> 
> If anyone wants some further input from me to debug this, let me know.
> 
> @b...@po.cwru.edu is there any workaround?

The only user-land workaround I know is to suspend with `zzz -z`.  After
resuming, the bus seems to be in a workable state.

I've had great success with the noted kernel driver workaround, which
applies the reset during system startup.  Optical drive performance has
been as expected with that workaround.

Hopefully one of those will work for you, and if any OpenBSD developers
are listening, maybe one of them can see the "right" way to do this.




Re: SATA slow/timeouts, AMD 600 Series AHCI, OpenBSD 7.4 amd64

2024-01-31 Thread Divan Santana
b...@po.cwru.edu writes:

> Onboard SATA seems to require additional initialization on a Gigabyte
> B650 in OpenBSD 7.4 amd64; basic requests take minutes to complete and
> each block read takes 30 seconds.  During boot, attached SSDs will block
> pending these requests; 

I have the same issue.  I was hoping to install openbsd 7.4 on this new
AMD MSI board server.

This issue is quite a show stopper for me.

If anyone wants some further input from me to debug this, let me know.

@b...@po.cwru.edu is there any workaround?



OpenBSD 7.4 (GENERIC.MP) #2: Fri Dec  8 15:39:04 MST 2023

r...@syspatch-74-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 67784667136 (64644MB)
avail mem = 65710604288 (62666MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.6 @ 0xb9ad6000 (43 entries)
bios0: vendor American Megatrends International, LLC. version "1.93" date 
01/26/2024
bios0: Micro-Star International Co., Ltd. MS-7E26
efi0 at bios0: UEFI 2.9
efi0: American Megatrends rev 0x50020
acpi0 at bios0: ACPI 6.5
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SSDT SSDT FIDT MCFG HPET WDRT UEFI FPDT VFCT SSDT SSDT 
SSDT SSDT SSDT SSDT WSMT APIC IVRS SSDT SSDT SSDT SSDT SSDT BGRT
acpi0: wakeup devices GPP3(S4) GPP4(S4) GPP5(S4) GPP6(S4) GP17(S4) XHC0(S4) 
XHC1(S4) XHC2(S4) GPP0(S4) GPP1(S4) GPP2(S4) GPP7(S4) UP00(S4) DP48(S4) 
EP00(S4) DP50(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpimcfg0 at acpi0
acpimcfg0: addr 0xe000, bus 0-255
acpihpet0 at acpi0: 14318180 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: AMD Ryzen 9 7900 12-Core Processor, 3700.00 MHz, 19-61-02, patch 0a601206
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,HWPSTATE,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,AVX512F,AVX512DQ,RDSEED,ADX,SMAP,AVX512IFMA,CLFLUSHOPT,CLWB,AVX512CD,SHA,AVX512BW,AVX512VL,AVX512VBMI,UMIP,PKU,L1DF,IBPB,IBRS,STIBP,STIBP_ALL,IBRS_PREF,IBRS_SM,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 1MB 64b/line 
8-way L2 cache, 32MB 64b/line 16-way L3 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 25MHz
cpu0: mwait min=64, max=64, C-substates=1.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: AMD Ryzen 9 7900 12-Core Processor, 3700.00 MHz, 19-61-02, patch 0a601206
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,HWPSTATE,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,AVX512F,AVX512DQ,RDSEED,ADX,SMAP,AVX512IFMA,CLFLUSHOPT,CLWB,AVX512CD,SHA,AVX512BW,AVX512VL,AVX512VBMI,UMIP,PKU,L1DF,IBPB,IBRS,STIBP,STIBP_ALL,IBRS_PREF,IBRS_SM,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
cpu1: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 1MB 64b/line 
8-way L2 cache, 32MB 64b/line 16-way L3 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 4 (application processor)
cpu2: AMD Ryzen 9 7900 12-Core Processor, 3700.00 MHz, 19-61-02, patch 0a601206
cpu2: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,HWPSTATE,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,AVX512F,AVX512DQ,RDSEED,ADX,SMAP,AVX512IFMA,CLFLUSHOPT,CLWB,AVX512CD,SHA,AVX512BW,AVX512VL,AVX512VBMI,UMIP,PKU,L1DF,IBPB,IBRS,STIBP,STIBP_ALL,IBRS_PREF,IBRS_SM,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
cpu2: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 1MB 64b/line 
8-way L2 cache, 32MB 64b/line 16-way L3 cache
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 6 (application processor)
cpu3: AMD Ryzen 9 7900 12-Core Processor, 3700.00 MHz, 19-61-02, patch 0a601206
cpu3: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,HWPSTATE,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,AVX512F,AVX512DQ,RDSEED,ADX,SMAP,AVX512IFMA,CLFLUSHOPT,CLWB,A

Re: DDB Crash Report About if_ether.c and arpinit() Gelen Kutusu

2024-01-31 Thread Samuel Jayden
Hello Valdrin,

Thanks, I'll check it out and write here soon.

On Wed, Jan 31, 2024 at 12:40 PM Valdrin MUJA 
wrote:

> Hello Samuel,
>
> I think you should give a chance to this commit:
>
>
> https://github.com/openbsd/src/commit/73fb5aae645f3bc12746fd705a937dfc9f9abc01
>
> I hope it works for you.
>
> --
> Valdrin
> --
> *From:* owner-m...@openbsd.org  on behalf of
> Samuel Jayden 
> *Sent:* Wednesday, January 31, 2024 10:29
> *To:* misc@openbsd.org 
> *Subject:* Re: DDB Crash Report About if_ether.c and arpinit() Gelen
> Kutusu
>
> Hello again,
>
> My device continues to crash almost every single day.
> Unfortunately, due to the system freeze, I'm unable to generate a crash
> report. These crashes typically result in the following errors:
>
> kernel : protection fault trap, code=0
> Stopped at arptimer+0x45: movq 0x10(%r15),%rdi
> ddb{0}>
>
> Is there a solution to this issue? What steps should I take?
> Thanks.
>
>
> On Sat, Jan 27, 2024 at 10:51 AM Samuel Jayden  >
> wrote:
>
> > Hello Misc,
> >
> > My OpenBSD 7.4 crash with this error messages;
> >
> > panic: kernel diagnostic assertion "ifp != NULL" failed: file
> > "/usr/src/sys/net/inet/if_ether.c", line 758
> >
> > Stopped at db_enter+0x14: popq %rbp
> >TID  PID UID   PRFLAGS   PFLAGS   CPUCOMMAND
> >  399412   7311877   0x112 0   10dhcpleased
> >  360364   39155   115   0x112 0   11slaacd
> >  155433   90182 00x14000  0x2002softnet0
> >  162438   45442 00x14000  0x2004systq
> > * 37835   96688 00x14000 0x42000softclock
> > db_enter() at db_enter+0x14
> > panic(820a8599) at panic+0xc3
> > __assert(821232bc,8209baea,2f6,820712c0) at
> > __assert+0x29
> > arpinit() at arpinit
> > arptimer(825a38e8) at arptimer+0x5f
> > softclock_thread(800021c1fd48) at softclock_thread+0x12b
> > end trace frame: 0x0, count: 9
> > https://www.openbsd.org/ddb.html describes the minimum info required in
> > bug reports. Insufficient info makes it difficult to find and fix bugs.
> > ddb{0}>
> >
> > Dmesg output of my device is in the attachment.
> >
> > Thank you in advance for your interest.
> >
>


Re: DDB Crash Report About if_ether.c and arpinit() Gelen Kutusu

2024-01-31 Thread Valdrin MUJA
Hello Samuel,

I think you should give a chance to this commit:

https://github.com/openbsd/src/commit/73fb5aae645f3bc12746fd705a937dfc9f9abc01

I hope it works for you.

--
Valdrin

From: owner-m...@openbsd.org  on behalf of Samuel 
Jayden 
Sent: Wednesday, January 31, 2024 10:29
To: misc@openbsd.org 
Subject: Re: DDB Crash Report About if_ether.c and arpinit() Gelen Kutusu

Hello again,

My device continues to crash almost every single day.
Unfortunately, due to the system freeze, I'm unable to generate a crash
report. These crashes typically result in the following errors:

kernel : protection fault trap, code=0
Stopped at arptimer+0x45: movq 0x10(%r15),%rdi
ddb{0}>

Is there a solution to this issue? What steps should I take?
Thanks.


On Sat, Jan 27, 2024 at 10:51 AM Samuel Jayden 
wrote:

> Hello Misc,
>
> My OpenBSD 7.4 crash with this error messages;
>
> panic: kernel diagnostic assertion "ifp != NULL" failed: file
> "/usr/src/sys/net/inet/if_ether.c", line 758
>
> Stopped at db_enter+0x14: popq %rbp
>TID  PID UID   PRFLAGS   PFLAGS   CPUCOMMAND
>  399412   7311877   0x112 0   10dhcpleased
>  360364   39155   115   0x112 0   11slaacd
>  155433   90182 00x14000  0x2002softnet0
>  162438   45442 00x14000  0x2004systq
> * 37835   96688 00x14000 0x42000softclock
> db_enter() at db_enter+0x14
> panic(820a8599) at panic+0xc3
> __assert(821232bc,8209baea,2f6,820712c0) at
> __assert+0x29
> arpinit() at arpinit
> arptimer(825a38e8) at arptimer+0x5f
> softclock_thread(800021c1fd48) at softclock_thread+0x12b
> end trace frame: 0x0, count: 9
> https://www.openbsd.org/ddb.html describes the minimum info required in
> bug reports. Insufficient info makes it difficult to find and fix bugs.
> ddb{0}>
>
> Dmesg output of my device is in the attachment.
>
> Thank you in advance for your interest.
>