r365488 page faults on AMD Ryzen 9 3950X

classic Classic list List threaded Threaded
24 messages Options
12
Reply | Threaded
Open this post in threaded view
|

r365488 page faults on AMD Ryzen 9 3950X

Rainer Hurling
Since r365488 (and above until recent) my box breaks with the following
error when starting:

Fatal trap 12: page fault while in kernel mode
cpuid = 31; apic id = 1f
fault virtual address   = 0x0
fault code              = supervisor read data, page not present
instruction pointer     = 0x20:0xffffffff808f452b
stack pointer           = 0x28:0xffffffff81711800
frame pointer           = 0x28:0xffffffff81711800
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 0 (swapper)
trap number             = 12
panic: page fault
cpuid = 31
time = 1



Some infos about the system, the page fault occurs:

CPU: AMD Ryzen 9 3950X 16-Core Processor             (3493.50-MHz
K8-class CPU)
  Origin="AuthenticAMD"  Id=0x870f10  Family=0x17  Model=0x71  Stepping=0
Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
Features2=0x7ed8320b<SSE3,PCLMULQDQ,MON,SSSE3,FMA,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND>
  AMD Features=0x2e500800<SYSCALL,NX,MMX+,FFXSR,Page1GB,RDTSCP,LM>
  AMD
Features2=0x75c237ff<LAHF,CMP,SVM,ExtAPIC,CR8,ABM,SSE4A,MAS,Prefetch,OSVW,IBS,SKINIT,WDT,TCE,Topology,PCXC,PNXC,DBE,PL2I,MWAITX,ADMSKX>
  Structured Extended
Features=0x219c91a9<FSGSBASE,BMI1,AVX2,SMEP,BMI2,PQM,PQE,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA>
  Structured Extended Features2=0x400004<UMIP,RDPID>
  XSAVE Features=0xf<XSAVEOPT,XSAVEC,XINUSE,XSAVES>
  AMD Extended Feature Extensions ID
EBX=0x108b657<CLZERO,IRPerf,XSaveErPtr,RDPRU,WBNOINVD,IBPB,STIBP,SSBD>
  SVM: (disabled in BIOS) NP,NRIP,VClean,AFlush,DAssist,NAsids=32768
  TSC: P-state invariant, performance statistics
real memory  = 68717379584 (65534 MB)
avail memory = 66756149248 (63663 MB)
Event timer "LAPIC" quality 600


#cat /etc/sysctl.conf
security.bsd.map_at_zero=1
kern.module_path=/boot/kernel;/boot/modules;/usr/local/modules
kern.evdev.rcpt_mask=6
kern.maxfiles=49312
kern.ipc.shm_allow_removed=1
kern.ipc.maxsockbuf=16777216
vfs.usermount=1
net.inet.tcp.rfc1323=1
net.inet.tcp.sack.enable=1
net.inet.tcp.sendbuf_auto=1
net.inet.tcp.recvbuf_auto=1
net.inet.tcp.sendbuf_max=16777216
net.inet.tcp.recvbuf_max=16777216
net.inet6.ip6.use_tempaddr=1
net.inet6.ip6.prefer_tempaddr=1
net.local.stream.recvspace=65536
net.local.stream.sendspace=65536


Please let me know, if I should provide more info or test something.
Thanks in advance,
Rainer
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: r365488 page faults on AMD Ryzen 9 3950X

monochrome
I am also having this problem. Have you resolved it? Mine is a Ryzen 5 2400G

On 9/12/20 5:22 AM, Rainer Hurling wrote:

> Since r365488 (and above until recent) my box breaks with the following
> error when starting:
>
> Fatal trap 12: page fault while in kernel mode
> cpuid = 31; apic id = 1f
> fault virtual address   = 0x0
> fault code              = supervisor read data, page not present
> instruction pointer     = 0x20:0xffffffff808f452b
> stack pointer           = 0x28:0xffffffff81711800
> frame pointer           = 0x28:0xffffffff81711800
> code segment            = base 0x0, limit 0xfffff, type 0x1b
>                          = DPL 0, pres 1, long 1, def32 0, gran 1
> processor eflags        = interrupt enabled, resume, IOPL = 0
> current process         = 0 (swapper)
> trap number             = 12
> panic: page fault
> cpuid = 31
> time = 1
>
>
>
> Some infos about the system, the page fault occurs:
>
> CPU: AMD Ryzen 9 3950X 16-Core Processor             (3493.50-MHz
> K8-class CPU)
>    Origin="AuthenticAMD"  Id=0x870f10  Family=0x17  Model=0x71  Stepping=0
> Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
> Features2=0x7ed8320b<SSE3,PCLMULQDQ,MON,SSSE3,FMA,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND>
>    AMD Features=0x2e500800<SYSCALL,NX,MMX+,FFXSR,Page1GB,RDTSCP,LM>
>    AMD
> Features2=0x75c237ff<LAHF,CMP,SVM,ExtAPIC,CR8,ABM,SSE4A,MAS,Prefetch,OSVW,IBS,SKINIT,WDT,TCE,Topology,PCXC,PNXC,DBE,PL2I,MWAITX,ADMSKX>
>    Structured Extended
> Features=0x219c91a9<FSGSBASE,BMI1,AVX2,SMEP,BMI2,PQM,PQE,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA>
>    Structured Extended Features2=0x400004<UMIP,RDPID>
>    XSAVE Features=0xf<XSAVEOPT,XSAVEC,XINUSE,XSAVES>
>    AMD Extended Feature Extensions ID
> EBX=0x108b657<CLZERO,IRPerf,XSaveErPtr,RDPRU,WBNOINVD,IBPB,STIBP,SSBD>
>    SVM: (disabled in BIOS) NP,NRIP,VClean,AFlush,DAssist,NAsids=32768
>    TSC: P-state invariant, performance statistics
> real memory  = 68717379584 (65534 MB)
> avail memory = 66756149248 (63663 MB)
> Event timer "LAPIC" quality 600
>
>
> #cat /etc/sysctl.conf
> security.bsd.map_at_zero=1
> kern.module_path=/boot/kernel;/boot/modules;/usr/local/modules
> kern.evdev.rcpt_mask=6
> kern.maxfiles=49312
> kern.ipc.shm_allow_removed=1
> kern.ipc.maxsockbuf=16777216
> vfs.usermount=1
> net.inet.tcp.rfc1323=1
> net.inet.tcp.sack.enable=1
> net.inet.tcp.sendbuf_auto=1
> net.inet.tcp.recvbuf_auto=1
> net.inet.tcp.sendbuf_max=16777216
> net.inet.tcp.recvbuf_max=16777216
> net.inet6.ip6.use_tempaddr=1
> net.inet6.ip6.prefer_tempaddr=1
> net.local.stream.recvspace=65536
> net.local.stream.sendspace=65536
>
>
> Please let me know, if I should provide more info or test something.
> Thanks in advance,
> Rainer
> _______________________________________________
> [hidden email] mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "[hidden email]"
>
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Fwd: Re: r365488 page faults on AMD Ryzen 9 3950X

Rainer Hurling
Hi,
I am AFK until Sunday, so can't investigate ATM.
And no, I haven't solved it until now. Thanks for your report.
Rainer

Am 18. September 2020 00:38:31 MESZ schrieb monochrome <[hidden email]>:

>
>forgot you
>
>-------- Forwarded Message --------
>Subject: Re: r365488 page faults on AMD Ryzen 9 3950X
>Date: Thu, 17 Sep 2020 17:03:49 -0400
>From: monochrome <[hidden email]>
>To: [hidden email]
>
>I am also having this problem. Have you resolved it? Mine is a Ryzen 5 2400G
>
>On 9/12/20 5:22 AM, Rainer Hurling wrote:
>> Since r365488 (and above until recent) my box breaks with the following
>> error when starting:
>>
>> Fatal trap 12: page fault while in kernel mode
>> cpuid = 31; apic id = 1f
>> fault virtual address   = 0x0
>> fault code              = supervisor read data, page not present
>> instruction pointer     = 0x20:0xffffffff808f452b
>> stack pointer           = 0x28:0xffffffff81711800
>> frame pointer           = 0x28:0xffffffff81711800
>> code segment            = base 0x0, limit 0xfffff, type 0x1b
>>                          = DPL 0, pres 1, long 1, def32 0, gran 1
>> processor eflags        = interrupt enabled, resume, IOPL = 0
>> current process         = 0 (swapper)
>> trap number             = 12
>> panic: page fault
>> cpuid = 31
>> time = 1
>>
>>
>>
>> Some infos about the system, the page fault occurs:
>>
>> CPU: AMD Ryzen 9 3950X 16-Core Processor             (3493.50-MHz
>> K8-class CPU)
>>    Origin="AuthenticAMD"  Id=0x870f10  Family=0x17  Model=0x71  Stepping=0
>> Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
>> Features2=0x7ed8320b<SSE3,PCLMULQDQ,MON,SSSE3,FMA,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND>
>>    AMD Features=0x2e500800<SYSCALL,NX,MMX+,FFXSR,Page1GB,RDTSCP,LM>
>>    AMD
>> Features2=0x75c237ff<LAHF,CMP,SVM,ExtAPIC,CR8,ABM,SSE4A,MAS,Prefetch,OSVW,IBS,SKINIT,WDT,TCE,Topology,PCXC,PNXC,DBE,PL2I,MWAITX,ADMSKX>
>>    Structured Extended
>> Features=0x219c91a9<FSGSBASE,BMI1,AVX2,SMEP,BMI2,PQM,PQE,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA>
>>    Structured Extended Features2=0x400004<UMIP,RDPID>
>>    XSAVE Features=0xf<XSAVEOPT,XSAVEC,XINUSE,XSAVES>
>>    AMD Extended Feature Extensions ID
>> EBX=0x108b657<CLZERO,IRPerf,XSaveErPtr,RDPRU,WBNOINVD,IBPB,STIBP,SSBD>
>>    SVM: (disabled in BIOS) NP,NRIP,VClean,AFlush,DAssist,NAsids=32768
>>    TSC: P-state invariant, performance statistics
>> real memory  = 68717379584 (65534 MB)
>> avail memory = 66756149248 (63663 MB)
>> Event timer "LAPIC" quality 600
>>
>>
>> #cat /etc/sysctl.conf
>> security.bsd.map_at_zero=1
>> kern.module_path=/boot/kernel;/boot/modules;/usr/local/modules
>> kern.evdev.rcpt_mask=6
>> kern.maxfiles=49312
>> kern.ipc.shm_allow_removed=1
>> kern.ipc.maxsockbuf=16777216
>> vfs.usermount=1
>> net.inet.tcp.rfc1323=1
>> net.inet.tcp.sack.enable=1
>> net.inet.tcp.sendbuf_auto=1
>> net.inet.tcp.recvbuf_auto=1
>> net.inet.tcp.sendbuf_max=16777216
>> net.inet.tcp.recvbuf_max=16777216
>> net.inet6.ip6.use_tempaddr=1
>> net.inet6.ip6.prefer_tempaddr=1
>> net.local.stream.recvspace=65536
>> net.local.stream.sendspace=65536
>>
>>
>> Please let me know, if I should provide more info or test something.
>> Thanks in advance,
>> Rainer
>> _______________________________________________
>> [hidden email] mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to "[hidden email]"
>>
>_______________________________________________
>[hidden email] mailing list
>https://lists.freebsd.org/mailman/listinfo/freebsd-current
>To unsubscribe, send any mail to "[hidden email]"
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Fwd: Re: r365488 page faults on AMD Ryzen 9 3950X

monochrome
I have confirmed that r365487 is the last kernel that will boot on my
2400G. These are the files changed between r365487 and r365488:

U    sys/vm/phys_pager.c
U    sys/vm/vm_object.c
U    sys/vm/vm_object.h
U    sys/vm/vm_pager.h



On 9/18/20 8:57 AM, Rainer Hurling wrote:

> Hi,
> I am AFK until Sunday, so can't investigate ATM.
> And no, I haven't solved it until now. Thanks for your report.
> Rainer
>
> Am 18. September 2020 00:38:31 MESZ schrieb monochrome <[hidden email]>:
>>
>> forgot you
>>
>> -------- Forwarded Message --------
>> Subject: Re: r365488 page faults on AMD Ryzen 9 3950X
>> Date: Thu, 17 Sep 2020 17:03:49 -0400
>> From: monochrome <[hidden email]>
>> To: [hidden email]
>>
>> I am also having this problem. Have you resolved it? Mine is a Ryzen 5 2400G
>>
>> On 9/12/20 5:22 AM, Rainer Hurling wrote:
>>> Since r365488 (and above until recent) my box breaks with the following
>>> error when starting:
>>>
>>> Fatal trap 12: page fault while in kernel mode
>>> cpuid = 31; apic id = 1f
>>> fault virtual address   = 0x0
>>> fault code              = supervisor read data, page not present
>>> instruction pointer     = 0x20:0xffffffff808f452b
>>> stack pointer           = 0x28:0xffffffff81711800
>>> frame pointer           = 0x28:0xffffffff81711800
>>> code segment            = base 0x0, limit 0xfffff, type 0x1b
>>>                           = DPL 0, pres 1, long 1, def32 0, gran 1
>>> processor eflags        = interrupt enabled, resume, IOPL = 0
>>> current process         = 0 (swapper)
>>> trap number             = 12
>>> panic: page fault
>>> cpuid = 31
>>> time = 1
>>>
>>>
>>>
>>> Some infos about the system, the page fault occurs:
>>>
>>> CPU: AMD Ryzen 9 3950X 16-Core Processor             (3493.50-MHz
>>> K8-class CPU)
>>>     Origin="AuthenticAMD"  Id=0x870f10  Family=0x17  Model=0x71  Stepping=0
>>> Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
>>> Features2=0x7ed8320b<SSE3,PCLMULQDQ,MON,SSSE3,FMA,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND>
>>>     AMD Features=0x2e500800<SYSCALL,NX,MMX+,FFXSR,Page1GB,RDTSCP,LM>
>>>     AMD
>>> Features2=0x75c237ff<LAHF,CMP,SVM,ExtAPIC,CR8,ABM,SSE4A,MAS,Prefetch,OSVW,IBS,SKINIT,WDT,TCE,Topology,PCXC,PNXC,DBE,PL2I,MWAITX,ADMSKX>
>>>     Structured Extended
>>> Features=0x219c91a9<FSGSBASE,BMI1,AVX2,SMEP,BMI2,PQM,PQE,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA>
>>>     Structured Extended Features2=0x400004<UMIP,RDPID>
>>>     XSAVE Features=0xf<XSAVEOPT,XSAVEC,XINUSE,XSAVES>
>>>     AMD Extended Feature Extensions ID
>>> EBX=0x108b657<CLZERO,IRPerf,XSaveErPtr,RDPRU,WBNOINVD,IBPB,STIBP,SSBD>
>>>     SVM: (disabled in BIOS) NP,NRIP,VClean,AFlush,DAssist,NAsids=32768
>>>     TSC: P-state invariant, performance statistics
>>> real memory  = 68717379584 (65534 MB)
>>> avail memory = 66756149248 (63663 MB)
>>> Event timer "LAPIC" quality 600
>>>
>>>
>>> #cat /etc/sysctl.conf
>>> security.bsd.map_at_zero=1
>>> kern.module_path=/boot/kernel;/boot/modules;/usr/local/modules
>>> kern.evdev.rcpt_mask=6
>>> kern.maxfiles=49312
>>> kern.ipc.shm_allow_removed=1
>>> kern.ipc.maxsockbuf=16777216
>>> vfs.usermount=1
>>> net.inet.tcp.rfc1323=1
>>> net.inet.tcp.sack.enable=1
>>> net.inet.tcp.sendbuf_auto=1
>>> net.inet.tcp.recvbuf_auto=1
>>> net.inet.tcp.sendbuf_max=16777216
>>> net.inet.tcp.recvbuf_max=16777216
>>> net.inet6.ip6.use_tempaddr=1
>>> net.inet6.ip6.prefer_tempaddr=1
>>> net.local.stream.recvspace=65536
>>> net.local.stream.sendspace=65536
>>>
>>>
>>> Please let me know, if I should provide more info or test something.
>>> Thanks in advance,
>>> Rainer
>>> _______________________________________________
>>> [hidden email] mailing list
>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>>> To unsubscribe, send any mail to "[hidden email]"
>>>
>> _______________________________________________
>> [hidden email] mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to "[hidden email]"
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Fwd: Re: r365488 page faults on AMD Ryzen 9 3950X

Jack L.-3
I also have the exact same panic on a Dell motherboard with a Haswell processor.

On Sat, Sep 19, 2020 at 11:05 PM monochrome <[hidden email]> wrote:

>
> I have confirmed that r365487 is the last kernel that will boot on my
> 2400G. These are the files changed between r365487 and r365488:
>
> U    sys/vm/phys_pager.c
> U    sys/vm/vm_object.c
> U    sys/vm/vm_object.h
> U    sys/vm/vm_pager.h
>
>
>
> On 9/18/20 8:57 AM, Rainer Hurling wrote:
> > Hi,
> > I am AFK until Sunday, so can't investigate ATM.
> > And no, I haven't solved it until now. Thanks for your report.
> > Rainer
> >
> > Am 18. September 2020 00:38:31 MESZ schrieb monochrome <[hidden email]>:
> >>
> >> forgot you
> >>
> >> -------- Forwarded Message --------
> >> Subject: Re: r365488 page faults on AMD Ryzen 9 3950X
> >> Date: Thu, 17 Sep 2020 17:03:49 -0400
> >> From: monochrome <[hidden email]>
> >> To: [hidden email]
> >>
> >> I am also having this problem. Have you resolved it? Mine is a Ryzen 5 2400G
> >>
> >> On 9/12/20 5:22 AM, Rainer Hurling wrote:
> >>> Since r365488 (and above until recent) my box breaks with the following
> >>> error when starting:
> >>>
> >>> Fatal trap 12: page fault while in kernel mode
> >>> cpuid = 31; apic id = 1f
> >>> fault virtual address   = 0x0
> >>> fault code              = supervisor read data, page not present
> >>> instruction pointer     = 0x20:0xffffffff808f452b
> >>> stack pointer           = 0x28:0xffffffff81711800
> >>> frame pointer           = 0x28:0xffffffff81711800
> >>> code segment            = base 0x0, limit 0xfffff, type 0x1b
> >>>                           = DPL 0, pres 1, long 1, def32 0, gran 1
> >>> processor eflags        = interrupt enabled, resume, IOPL = 0
> >>> current process         = 0 (swapper)
> >>> trap number             = 12
> >>> panic: page fault
> >>> cpuid = 31
> >>> time = 1
> >>>
> >>>
> >>>
> >>> Some infos about the system, the page fault occurs:
> >>>
> >>> CPU: AMD Ryzen 9 3950X 16-Core Processor             (3493.50-MHz
> >>> K8-class CPU)
> >>>     Origin="AuthenticAMD"  Id=0x870f10  Family=0x17  Model=0x71  Stepping=0
> >>> Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
> >>> Features2=0x7ed8320b<SSE3,PCLMULQDQ,MON,SSSE3,FMA,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND>
> >>>     AMD Features=0x2e500800<SYSCALL,NX,MMX+,FFXSR,Page1GB,RDTSCP,LM>
> >>>     AMD
> >>> Features2=0x75c237ff<LAHF,CMP,SVM,ExtAPIC,CR8,ABM,SSE4A,MAS,Prefetch,OSVW,IBS,SKINIT,WDT,TCE,Topology,PCXC,PNXC,DBE,PL2I,MWAITX,ADMSKX>
> >>>     Structured Extended
> >>> Features=0x219c91a9<FSGSBASE,BMI1,AVX2,SMEP,BMI2,PQM,PQE,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA>
> >>>     Structured Extended Features2=0x400004<UMIP,RDPID>
> >>>     XSAVE Features=0xf<XSAVEOPT,XSAVEC,XINUSE,XSAVES>
> >>>     AMD Extended Feature Extensions ID
> >>> EBX=0x108b657<CLZERO,IRPerf,XSaveErPtr,RDPRU,WBNOINVD,IBPB,STIBP,SSBD>
> >>>     SVM: (disabled in BIOS) NP,NRIP,VClean,AFlush,DAssist,NAsids=32768
> >>>     TSC: P-state invariant, performance statistics
> >>> real memory  = 68717379584 (65534 MB)
> >>> avail memory = 66756149248 (63663 MB)
> >>> Event timer "LAPIC" quality 600
> >>>
> >>>
> >>> #cat /etc/sysctl.conf
> >>> security.bsd.map_at_zero=1
> >>> kern.module_path=/boot/kernel;/boot/modules;/usr/local/modules
> >>> kern.evdev.rcpt_mask=6
> >>> kern.maxfiles=49312
> >>> kern.ipc.shm_allow_removed=1
> >>> kern.ipc.maxsockbuf=16777216
> >>> vfs.usermount=1
> >>> net.inet.tcp.rfc1323=1
> >>> net.inet.tcp.sack.enable=1
> >>> net.inet.tcp.sendbuf_auto=1
> >>> net.inet.tcp.recvbuf_auto=1
> >>> net.inet.tcp.sendbuf_max=16777216
> >>> net.inet.tcp.recvbuf_max=16777216
> >>> net.inet6.ip6.use_tempaddr=1
> >>> net.inet6.ip6.prefer_tempaddr=1
> >>> net.local.stream.recvspace=65536
> >>> net.local.stream.sendspace=65536
> >>>
> >>>
> >>> Please let me know, if I should provide more info or test something.
> >>> Thanks in advance,
> >>> Rainer
> >>> _______________________________________________
> >>> [hidden email] mailing list
> >>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> >>> To unsubscribe, send any mail to "[hidden email]"
> >>>
> >> _______________________________________________
> >> [hidden email] mailing list
> >> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> >> To unsubscribe, send any mail to "[hidden email]"
> _______________________________________________
> [hidden email] mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "[hidden email]"
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Fwd: Re: r365488 page faults on AMD Ryzen 9 3950X

Rainer Hurling
In reply to this post by monochrome
Hi monochrome,

back to keyboard, it tried newest CURRENT (r365920) on my box and even
with newest sources the error occurs.

After looking around somewhat more, I found some hints about Virtualbox
kernel module having problems with r365488. Unfortunately, I am not able
to find the thread again :(

What seems to help as a workaround is to disable the loading of
VirtualBox in /boot/loader.conf

#vboxdrv_load="YES"

and in /etc/rc.conf

#vboxnet_enable="YES"
#vboxguest_enable="YES"


So probably, this page fault is not restricted to AMD Ryzen?

HTH,
Rainer


Am 20.09.20 um 08:04 schrieb monochrome:

> I have confirmed that r365487 is the last kernel that will boot on my
> 2400G. These are the files changed between r365487 and r365488:
>
> U    sys/vm/phys_pager.c
> U    sys/vm/vm_object.c
> U    sys/vm/vm_object.h
> U    sys/vm/vm_pager.h
>
>
>
> On 9/18/20 8:57 AM, Rainer Hurling wrote:
>> Hi,
>> I am AFK until Sunday, so can't investigate ATM.
>> And no, I haven't solved it until now. Thanks for your report.
>> Rainer
>>
>> Am 18. September 2020 00:38:31 MESZ schrieb monochrome
>> <[hidden email]>:
>>>
>>> forgot you
>>>
>>> -------- Forwarded Message --------
>>> Subject: Re: r365488 page faults on AMD Ryzen 9 3950X
>>> Date: Thu, 17 Sep 2020 17:03:49 -0400
>>> From: monochrome <[hidden email]>
>>> To: [hidden email]
>>>
>>> I am also having this problem. Have you resolved it? Mine is a Ryzen
>>> 5 2400G
>>>
>>> On 9/12/20 5:22 AM, Rainer Hurling wrote:
>>>> Since r365488 (and above until recent) my box breaks with the following
>>>> error when starting:
>>>>
>>>> Fatal trap 12: page fault while in kernel mode
>>>> cpuid = 31; apic id = 1f
>>>> fault virtual address   = 0x0
>>>> fault code              = supervisor read data, page not present
>>>> instruction pointer     = 0x20:0xffffffff808f452b
>>>> stack pointer           = 0x28:0xffffffff81711800
>>>> frame pointer           = 0x28:0xffffffff81711800
>>>> code segment            = base 0x0, limit 0xfffff, type 0x1b
>>>>                           = DPL 0, pres 1, long 1, def32 0, gran 1
>>>> processor eflags        = interrupt enabled, resume, IOPL = 0
>>>> current process         = 0 (swapper)
>>>> trap number             = 12
>>>> panic: page fault
>>>> cpuid = 31
>>>> time = 1
>>>>
>>>>
>>>>
>>>> Some infos about the system, the page fault occurs:
>>>>
>>>> CPU: AMD Ryzen 9 3950X 16-Core Processor             (3493.50-MHz
>>>> K8-class CPU)
>>>>     Origin="AuthenticAMD"  Id=0x870f10  Family=0x17  Model=0x71 
>>>> Stepping=0
>>>> Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
>>>>
>>>> Features2=0x7ed8320b<SSE3,PCLMULQDQ,MON,SSSE3,FMA,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND>
>>>>
>>>>     AMD Features=0x2e500800<SYSCALL,NX,MMX+,FFXSR,Page1GB,RDTSCP,LM>
>>>>     AMD
>>>> Features2=0x75c237ff<LAHF,CMP,SVM,ExtAPIC,CR8,ABM,SSE4A,MAS,Prefetch,OSVW,IBS,SKINIT,WDT,TCE,Topology,PCXC,PNXC,DBE,PL2I,MWAITX,ADMSKX>
>>>>
>>>>     Structured Extended
>>>> Features=0x219c91a9<FSGSBASE,BMI1,AVX2,SMEP,BMI2,PQM,PQE,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA>
>>>>
>>>>     Structured Extended Features2=0x400004<UMIP,RDPID>
>>>>     XSAVE Features=0xf<XSAVEOPT,XSAVEC,XINUSE,XSAVES>
>>>>     AMD Extended Feature Extensions ID
>>>> EBX=0x108b657<CLZERO,IRPerf,XSaveErPtr,RDPRU,WBNOINVD,IBPB,STIBP,SSBD>
>>>>     SVM: (disabled in BIOS) NP,NRIP,VClean,AFlush,DAssist,NAsids=32768
>>>>     TSC: P-state invariant, performance statistics
>>>> real memory  = 68717379584 (65534 MB)
>>>> avail memory = 66756149248 (63663 MB)
>>>> Event timer "LAPIC" quality 600
>>>>
>>>>
>>>> #cat /etc/sysctl.conf
>>>> security.bsd.map_at_zero=1
>>>> kern.module_path=/boot/kernel;/boot/modules;/usr/local/modules
>>>> kern.evdev.rcpt_mask=6
>>>> kern.maxfiles=49312
>>>> kern.ipc.shm_allow_removed=1
>>>> kern.ipc.maxsockbuf=16777216
>>>> vfs.usermount=1
>>>> net.inet.tcp.rfc1323=1
>>>> net.inet.tcp.sack.enable=1
>>>> net.inet.tcp.sendbuf_auto=1
>>>> net.inet.tcp.recvbuf_auto=1
>>>> net.inet.tcp.sendbuf_max=16777216
>>>> net.inet.tcp.recvbuf_max=16777216
>>>> net.inet6.ip6.use_tempaddr=1
>>>> net.inet6.ip6.prefer_tempaddr=1
>>>> net.local.stream.recvspace=65536
>>>> net.local.stream.sendspace=65536
>>>>
>>>>
>>>> Please let me know, if I should provide more info or test something.
>>>> Thanks in advance,
>>>> Rainer
>>>> _______________________________________________
>>>> [hidden email] mailing list
>>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>>>> To unsubscribe, send any mail to
>>>> "[hidden email]"
>>>>
>>> _______________________________________________
>>> [hidden email] mailing list
>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>>> To unsubscribe, send any mail to
>>> "[hidden email]"

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Fwd: Re: r365488 page faults on AMD Ryzen 9 3950X

Hans Petter Selasky-6
On 2020-09-20 10:05, Rainer Hurling wrote:

> Hi monochrome,
>
> back to keyboard, it tried newest CURRENT (r365920) on my box and even
> with newest sources the error occurs.
>
> After looking around somewhat more, I found some hints about Virtualbox
> kernel module having problems with r365488. Unfortunately, I am not able
> to find the thread again :(
>
> What seems to help as a workaround is to disable the loading of
> VirtualBox in /boot/loader.conf
>
> #vboxdrv_load="YES"
>
> and in /etc/rc.conf
>
> #vboxnet_enable="YES"
> #vboxguest_enable="YES"
>
>
> So probably, this page fault is not restricted to AMD Ryzen?
>

Possibly you need to rebuild that kernel module. Maybe the FreeBSD
version was not bumped correctly.

--HPS

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Fwd: Re: r365488 page faults on AMD Ryzen 9 3950X

Rainer Hurling
Am 20.09.20 um 10:20 schrieb Hans Petter Selasky:

> On 2020-09-20 10:05, Rainer Hurling wrote:
>> Hi monochrome,
>>
>> back to keyboard, it tried newest CURRENT (r365920) on my box and even
>> with newest sources the error occurs.
>>
>> After looking around somewhat more, I found some hints about Virtualbox
>> kernel module having problems with r365488. Unfortunately, I am not able
>> to find the thread again :(
>>
>> What seems to help as a workaround is to disable the loading of
>> VirtualBox in /boot/loader.conf
>>
>> #vboxdrv_load="YES"
>>
>> and in /etc/rc.conf
>>
>> #vboxnet_enable="YES"
>> #vboxguest_enable="YES"
>>
>>
>> So probably, this page fault is not restricted to AMD Ryzen?
>>
>
> Possibly you need to rebuild that kernel module. Maybe the FreeBSD
> version was not bumped correctly.
>
> --HPS
>

Thanks for the hint. But I did rebuild all kernel modules before
rebooting, in my case vbox*.ko, nvidia*.ko.

Best wishes,
Rainer
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Fwd: Re: r365488 page faults on AMD Ryzen 9 3950X

Konstantin Belousov
On Sun, Sep 20, 2020 at 10:26:11AM +0200, Rainer Hurling wrote:

> Am 20.09.20 um 10:20 schrieb Hans Petter Selasky:
> > On 2020-09-20 10:05, Rainer Hurling wrote:
> >> Hi monochrome,
> >>
> >> back to keyboard, it tried newest CURRENT (r365920) on my box and even
> >> with newest sources the error occurs.
> >>
> >> After looking around somewhat more, I found some hints about Virtualbox
> >> kernel module having problems with r365488. Unfortunately, I am not able
> >> to find the thread again :(
> >>
> >> What seems to help as a workaround is to disable the loading of
> >> VirtualBox in /boot/loader.conf
> >>
> >> #vboxdrv_load="YES"
> >>
> >> and in /etc/rc.conf
> >>
> >> #vboxnet_enable="YES"
> >> #vboxguest_enable="YES"
> >>
> >>
> >> So probably, this page fault is not restricted to AMD Ryzen?
> >>
> >
> > Possibly you need to rebuild that kernel module. Maybe the FreeBSD
> > version was not bumped correctly.
> >
> > --HPS
> >
>
> Thanks for the hint. But I did rebuild all kernel modules before
> rebooting, in my case vbox*.ko, nvidia*.ko.

Provide backtrace of the panic.
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Fwd: Re: r365488 page faults on AMD Ryzen 9 3950X

Rainer Hurling
Am 20.09.20 um 11:38 schrieb Konstantin Belousov:

> On Sun, Sep 20, 2020 at 10:26:11AM +0200, Rainer Hurling wrote:
>> Am 20.09.20 um 10:20 schrieb Hans Petter Selasky:
>>> On 2020-09-20 10:05, Rainer Hurling wrote:
>>>> Hi monochrome,
>>>>
>>>> back to keyboard, it tried newest CURRENT (r365920) on my box and even
>>>> with newest sources the error occurs.
>>>>
>>>> After looking around somewhat more, I found some hints about Virtualbox
>>>> kernel module having problems with r365488. Unfortunately, I am not able
>>>> to find the thread again :(
>>>>
>>>> What seems to help as a workaround is to disable the loading of
>>>> VirtualBox in /boot/loader.conf
>>>>
>>>> #vboxdrv_load="YES"
>>>>
>>>> and in /etc/rc.conf
>>>>
>>>> #vboxnet_enable="YES"
>>>> #vboxguest_enable="YES"
>>>>
>>>>
>>>> So probably, this page fault is not restricted to AMD Ryzen?
>>>>
>>>
>>> Possibly you need to rebuild that kernel module. Maybe the FreeBSD
>>> version was not bumped correctly.
>>>
>>> --HPS
>>>
>>
>> Thanks for the hint. But I did rebuild all kernel modules before
>> rebooting, in my case vbox*.ko, nvidia*.ko.
>
> Provide backtrace of the panic.
>

Hi Konstantin,

Thanks for your response.

After trying several ways to produce a core dump or a working kdb prompt
without success, all I can offer is the following screen contents. I
built a GENERIC kernel with debugging enabled, enable loading of vboxdrv
via /boot/loader.conf and /etc/rc.conf as described above:


[..snip..]
procfs registered
modulte_register_init: MOD_LOAD (tmpfs, 0xffffffff80caa060,
0xffffffff82520a70) error 17
Timecounters tick every 1.000 msec
lo0: bpf attached
vlan: initialized, using hash tables with chaining


Fatal trap 12: page fault while in kernel mode
cpuid = 31; apic id = 1f
fault virtual address   = 0x0
fault code              = supervisor read data, page not present
instruction pointer     = 0x20:0xffffffff80ea889b
stack pointer           = 0x20:0xffffffff826017e0
frame pointer           = 0x20:0xffffffff826017e0
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 0 (swapper)
trap number             = 12
panic: page fault
cpuid = 31
time = 1
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame
0xffffffff82601490
vpanic() at vpanic+0x182/frame 0xffffffff826014e0
panic() at panic+0x43/frame 0xffffffff82601540
trap_fatal() at trap_fatal+0x387/frame 0xffffffff826015a0
trap_pfault() at trap_pfault+0x97/frame 0xffffffff82601600
calltrap() at calltrap+0x8/frame 0xffffffff82601710
--- trap 0xc, rip = 0xffffffff80ea889b, rsp = 0xffffffff826017e0, rbp =
0xffffffff826017e0 ---
phys_pager_getpages() at phys_pager_getpages+0xb/frame 0xffffffff826017e0
vm_pager_get_pages() at vm_pager_get_pages+0x4f/frame 0xffffffff82601830
vm_fault() at vm_fault+0x5d6/frame 0xffffffff82601940
vm_map_wire_locked() at vm_map_wire_locked+0x3a6/framw 0xffffffff826019f0
vm_map_wire() at vm_map_wire+0x6b/frame 0xffffffff82601a20
rtR0MemObjFreeBSDAllocHelper() at
rtR0MemObjFreeBSDAllocHelper+0xdc/frame 0xffffffff82601a70
rtR0MemObjNativeAllocCont() at rtR0MemObjNativeAllocCont+0x50/frame
0xffffffff82601ac0
supdrvGipCreate() at supdrvGipCreate+0x97/frame 0xffffffff82601b60
supdrvInitDevExt() at supdrvInitDevExt+0x19a/frame 0xffffffff82601bd0
VBoxDrvFreeBSDModuleEvent() at VBoxDrvFreeBSDModuleEvent+0x46/frame
0xffffffff82601bf0
module_register_init() at module_register_init+0xbd/frame 0xffffffff82601c20
mi_startup() at mi_startup+0xec/frame 0xffffffff82601c70
btext() at btext+0x2c
KDB: enter: panic
[ thread pid 0 tid 100000 ]
Stopped at      kdb_enter+0x37: movq    $0,0x10b5796(%rip9
db>


The system freezes at this point, no core dump is generated ;)  This
does not happen without loading VBoxDrv.

At least, the screen dump shows VBoxDrvFreeBSDModuleEvent(). I hope,
this is of some help.

Best regards,
Rainer
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Fwd: Re: r365488 page faults on AMD Ryzen 9 3950X

Konstantin Belousov
On Sun, Sep 20, 2020 at 03:11:26PM +0200, Rainer Hurling wrote:

> Am 20.09.20 um 11:38 schrieb Konstantin Belousov:
> > On Sun, Sep 20, 2020 at 10:26:11AM +0200, Rainer Hurling wrote:
> >> Am 20.09.20 um 10:20 schrieb Hans Petter Selasky:
> >>> On 2020-09-20 10:05, Rainer Hurling wrote:
> >>>> Hi monochrome,
> >>>>
> >>>> back to keyboard, it tried newest CURRENT (r365920) on my box and even
> >>>> with newest sources the error occurs.
> >>>>
> >>>> After looking around somewhat more, I found some hints about Virtualbox
> >>>> kernel module having problems with r365488. Unfortunately, I am not able
> >>>> to find the thread again :(
> >>>>
> >>>> What seems to help as a workaround is to disable the loading of
> >>>> VirtualBox in /boot/loader.conf
> >>>>
> >>>> #vboxdrv_load="YES"
> >>>>
> >>>> and in /etc/rc.conf
> >>>>
> >>>> #vboxnet_enable="YES"
> >>>> #vboxguest_enable="YES"
> >>>>
> >>>>
> >>>> So probably, this page fault is not restricted to AMD Ryzen?
> >>>>
> >>>
> >>> Possibly you need to rebuild that kernel module. Maybe the FreeBSD
> >>> version was not bumped correctly.
> >>>
> >>> --HPS
> >>>
> >>
> >> Thanks for the hint. But I did rebuild all kernel modules before
> >> rebooting, in my case vbox*.ko, nvidia*.ko.
> >
> > Provide backtrace of the panic.
> >
>
> Hi Konstantin,
>
> Thanks for your response.
>
> After trying several ways to produce a core dump or a working kdb prompt
> without success, all I can offer is the following screen contents. I
> built a GENERIC kernel with debugging enabled, enable loading of vboxdrv
> via /boot/loader.conf and /etc/rc.conf as described above:
>
>
> [..snip..]
> procfs registered
> modulte_register_init: MOD_LOAD (tmpfs, 0xffffffff80caa060,
> 0xffffffff82520a70) error 17
> Timecounters tick every 1.000 msec
> lo0: bpf attached
> vlan: initialized, using hash tables with chaining
>
>
> Fatal trap 12: page fault while in kernel mode
> cpuid = 31; apic id = 1f
> fault virtual address   = 0x0
> fault code              = supervisor read data, page not present
> instruction pointer     = 0x20:0xffffffff80ea889b
> stack pointer           = 0x20:0xffffffff826017e0
> frame pointer           = 0x20:0xffffffff826017e0
> code segment            = base 0x0, limit 0xfffff, type 0x1b
>                         = DPL 0, pres 1, long 1, def32 0, gran 1
> processor eflags        = interrupt enabled, resume, IOPL = 0
> current process         = 0 (swapper)
> trap number             = 12
> panic: page fault
> cpuid = 31
> time = 1
> KDB: stack backtrace:
> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame
> 0xffffffff82601490
> vpanic() at vpanic+0x182/frame 0xffffffff826014e0
> panic() at panic+0x43/frame 0xffffffff82601540
> trap_fatal() at trap_fatal+0x387/frame 0xffffffff826015a0
> trap_pfault() at trap_pfault+0x97/frame 0xffffffff82601600
> calltrap() at calltrap+0x8/frame 0xffffffff82601710
> --- trap 0xc, rip = 0xffffffff80ea889b, rsp = 0xffffffff826017e0, rbp =
> 0xffffffff826017e0 ---
> phys_pager_getpages() at phys_pager_getpages+0xb/frame 0xffffffff826017e0
> vm_pager_get_pages() at vm_pager_get_pages+0x4f/frame 0xffffffff82601830
> vm_fault() at vm_fault+0x5d6/frame 0xffffffff82601940
> vm_map_wire_locked() at vm_map_wire_locked+0x3a6/framw 0xffffffff826019f0
> vm_map_wire() at vm_map_wire+0x6b/frame 0xffffffff82601a20
> rtR0MemObjFreeBSDAllocHelper() at
> rtR0MemObjFreeBSDAllocHelper+0xdc/frame 0xffffffff82601a70
> rtR0MemObjNativeAllocCont() at rtR0MemObjNativeAllocCont+0x50/frame
> 0xffffffff82601ac0
> supdrvGipCreate() at supdrvGipCreate+0x97/frame 0xffffffff82601b60
> supdrvInitDevExt() at supdrvInitDevExt+0x19a/frame 0xffffffff82601bd0
> VBoxDrvFreeBSDModuleEvent() at VBoxDrvFreeBSDModuleEvent+0x46/frame
> 0xffffffff82601bf0
> module_register_init() at module_register_init+0xbd/frame 0xffffffff82601c20
> mi_startup() at mi_startup+0xec/frame 0xffffffff82601c70
> btext() at btext+0x2c
> KDB: enter: panic
> [ thread pid 0 tid 100000 ]
> Stopped at      kdb_enter+0x37: movq    $0,0x10b5796(%rip9
> db>
>
>
> The system freezes at this point, no core dump is generated ;)  This
> does not happen without loading VBoxDrv.
>
> At least, the screen dump shows VBoxDrvFreeBSDModuleEvent(). I hope,
> this is of some help.
>
Yes it seems to be enough for me to see where the possible issue is.
Try this patch, I did not even compiled it.  Probably you need to put
it into ports/emulators/virtualbox-ose-kmod/files with the name ending
with .patch.

--- src/VBox/Runtime/r0drv/freebsd/memobj-r0drv-freebsd.c.xxx 2020-09-20 19:40:07.471956776 +0000
+++ src/VBox/Runtime/r0drv/freebsd/memobj-r0drv-freebsd.c 2020-09-20 19:46:03.606966773 +0000
@@ -323,7 +323,8 @@
     size_t      cPages = atop(pMemFreeBSD->Core.cb);
     int         rc;
 
-    pMemFreeBSD->pObject = vm_object_allocate(OBJT_PHYS, cPages);
+    pMemFreeBSD->pObject = vm_pager_allocate(OBJT_PHYS, NULL,
+      pMemFreeBSD->Core.cb, VM_PROT_ALL, 0, curthread->td_ucred);
 
     /* No additional object reference for auto-deallocation upon unmapping. */
 #if __FreeBSD_version >= 1000055
@@ -457,7 +458,8 @@
         return VERR_NO_MEMORY;
     }
 
-    pMemFreeBSD->pObject = vm_object_allocate(OBJT_PHYS, atop(cb));
+    pMemFreeBSD->pObject = vm_pager_allocate(OBJT_PHYS, NULL, cb, VM_PROT_ALL,
+       0, curthread->td_ucred);
 
     if (PhysHighest != NIL_RTHCPHYS)
         VmPhysAddrHigh = PhysHighest;

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Fwd: Re: r365488 page faults on AMD Ryzen 9 3950X

Konstantin Belousov
On Sun, Sep 20, 2020 at 10:55:26PM +0300, Konstantin Belousov wrote:

> On Sun, Sep 20, 2020 at 03:11:26PM +0200, Rainer Hurling wrote:
> > Am 20.09.20 um 11:38 schrieb Konstantin Belousov:
> > > On Sun, Sep 20, 2020 at 10:26:11AM +0200, Rainer Hurling wrote:
> > >> Am 20.09.20 um 10:20 schrieb Hans Petter Selasky:
> > >>> On 2020-09-20 10:05, Rainer Hurling wrote:
> > >>>> Hi monochrome,
> > >>>>
> > >>>> back to keyboard, it tried newest CURRENT (r365920) on my box and even
> > >>>> with newest sources the error occurs.
> > >>>>
> > >>>> After looking around somewhat more, I found some hints about Virtualbox
> > >>>> kernel module having problems with r365488. Unfortunately, I am not able
> > >>>> to find the thread again :(
> > >>>>
> > >>>> What seems to help as a workaround is to disable the loading of
> > >>>> VirtualBox in /boot/loader.conf
> > >>>>
> > >>>> #vboxdrv_load="YES"
> > >>>>
> > >>>> and in /etc/rc.conf
> > >>>>
> > >>>> #vboxnet_enable="YES"
> > >>>> #vboxguest_enable="YES"
> > >>>>
> > >>>>
> > >>>> So probably, this page fault is not restricted to AMD Ryzen?
> > >>>>
> > >>>
> > >>> Possibly you need to rebuild that kernel module. Maybe the FreeBSD
> > >>> version was not bumped correctly.
> > >>>
> > >>> --HPS
> > >>>
> > >>
> > >> Thanks for the hint. But I did rebuild all kernel modules before
> > >> rebooting, in my case vbox*.ko, nvidia*.ko.
> > >
> > > Provide backtrace of the panic.
> > >
> >
> > Hi Konstantin,
> >
> > Thanks for your response.
> >
> > After trying several ways to produce a core dump or a working kdb prompt
> > without success, all I can offer is the following screen contents. I
> > built a GENERIC kernel with debugging enabled, enable loading of vboxdrv
> > via /boot/loader.conf and /etc/rc.conf as described above:
> >
> >
> > [..snip..]
> > procfs registered
> > modulte_register_init: MOD_LOAD (tmpfs, 0xffffffff80caa060,
> > 0xffffffff82520a70) error 17
> > Timecounters tick every 1.000 msec
> > lo0: bpf attached
> > vlan: initialized, using hash tables with chaining
> >
> >
> > Fatal trap 12: page fault while in kernel mode
> > cpuid = 31; apic id = 1f
> > fault virtual address   = 0x0
> > fault code              = supervisor read data, page not present
> > instruction pointer     = 0x20:0xffffffff80ea889b
> > stack pointer           = 0x20:0xffffffff826017e0
> > frame pointer           = 0x20:0xffffffff826017e0
> > code segment            = base 0x0, limit 0xfffff, type 0x1b
> >                         = DPL 0, pres 1, long 1, def32 0, gran 1
> > processor eflags        = interrupt enabled, resume, IOPL = 0
> > current process         = 0 (swapper)
> > trap number             = 12
> > panic: page fault
> > cpuid = 31
> > time = 1
> > KDB: stack backtrace:
> > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame
> > 0xffffffff82601490
> > vpanic() at vpanic+0x182/frame 0xffffffff826014e0
> > panic() at panic+0x43/frame 0xffffffff82601540
> > trap_fatal() at trap_fatal+0x387/frame 0xffffffff826015a0
> > trap_pfault() at trap_pfault+0x97/frame 0xffffffff82601600
> > calltrap() at calltrap+0x8/frame 0xffffffff82601710
> > --- trap 0xc, rip = 0xffffffff80ea889b, rsp = 0xffffffff826017e0, rbp =
> > 0xffffffff826017e0 ---
> > phys_pager_getpages() at phys_pager_getpages+0xb/frame 0xffffffff826017e0
> > vm_pager_get_pages() at vm_pager_get_pages+0x4f/frame 0xffffffff82601830
> > vm_fault() at vm_fault+0x5d6/frame 0xffffffff82601940
> > vm_map_wire_locked() at vm_map_wire_locked+0x3a6/framw 0xffffffff826019f0
> > vm_map_wire() at vm_map_wire+0x6b/frame 0xffffffff82601a20
> > rtR0MemObjFreeBSDAllocHelper() at
> > rtR0MemObjFreeBSDAllocHelper+0xdc/frame 0xffffffff82601a70
> > rtR0MemObjNativeAllocCont() at rtR0MemObjNativeAllocCont+0x50/frame
> > 0xffffffff82601ac0
> > supdrvGipCreate() at supdrvGipCreate+0x97/frame 0xffffffff82601b60
> > supdrvInitDevExt() at supdrvInitDevExt+0x19a/frame 0xffffffff82601bd0
> > VBoxDrvFreeBSDModuleEvent() at VBoxDrvFreeBSDModuleEvent+0x46/frame
> > 0xffffffff82601bf0
> > module_register_init() at module_register_init+0xbd/frame 0xffffffff82601c20
> > mi_startup() at mi_startup+0xec/frame 0xffffffff82601c70
> > btext() at btext+0x2c
> > KDB: enter: panic
> > [ thread pid 0 tid 100000 ]
> > Stopped at      kdb_enter+0x37: movq    $0,0x10b5796(%rip9
> > db>
> >
> >
> > The system freezes at this point, no core dump is generated ;)  This
> > does not happen without loading VBoxDrv.
> >
> > At least, the screen dump shows VBoxDrvFreeBSDModuleEvent(). I hope,
> > this is of some help.
> >
> Yes it seems to be enough for me to see where the possible issue is.
> Try this patch, I did not even compiled it.  Probably you need to put
> it into ports/emulators/virtualbox-ose-kmod/files with the name ending
> with .patch.
This seems to be wrong, name should _start_ with the prefix 'patch-'.

>
> --- src/VBox/Runtime/r0drv/freebsd/memobj-r0drv-freebsd.c.xxx 2020-09-20 19:40:07.471956776 +0000
> +++ src/VBox/Runtime/r0drv/freebsd/memobj-r0drv-freebsd.c 2020-09-20 19:46:03.606966773 +0000
> @@ -323,7 +323,8 @@
>      size_t      cPages = atop(pMemFreeBSD->Core.cb);
>      int         rc;
>  
> -    pMemFreeBSD->pObject = vm_object_allocate(OBJT_PHYS, cPages);
> +    pMemFreeBSD->pObject = vm_pager_allocate(OBJT_PHYS, NULL,
> +      pMemFreeBSD->Core.cb, VM_PROT_ALL, 0, curthread->td_ucred);
>  
>      /* No additional object reference for auto-deallocation upon unmapping. */
>  #if __FreeBSD_version >= 1000055
> @@ -457,7 +458,8 @@
>          return VERR_NO_MEMORY;
>      }
>  
> -    pMemFreeBSD->pObject = vm_object_allocate(OBJT_PHYS, atop(cb));
> +    pMemFreeBSD->pObject = vm_pager_allocate(OBJT_PHYS, NULL, cb, VM_PROT_ALL,
> +       0, curthread->td_ucred);
>  
>      if (PhysHighest != NIL_RTHCPHYS)
>          VmPhysAddrHigh = PhysHighest;
>
> _______________________________________________
> [hidden email] mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "[hidden email]"
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Fwd: Re: r365488 page faults on AMD Ryzen 9 3950X

Rainer Hurling
On 20.09.20 22:07, Konstantin Belousov wrote:

> On Sun, Sep 20, 2020 at 10:55:26PM +0300, Konstantin Belousov wrote:
>> On Sun, Sep 20, 2020 at 03:11:26PM +0200, Rainer Hurling wrote:
>>> Am 20.09.20 um 11:38 schrieb Konstantin Belousov:
>>>> On Sun, Sep 20, 2020 at 10:26:11AM +0200, Rainer Hurling wrote:
>>>>> Am 20.09.20 um 10:20 schrieb Hans Petter Selasky:
>>>>>> On 2020-09-20 10:05, Rainer Hurling wrote:
>>>>>>> Hi monochrome,
>>>>>>>
>>>>>>> back to keyboard, it tried newest CURRENT (r365920) on my box and even
>>>>>>> with newest sources the error occurs.
>>>>>>>
>>>>>>> After looking around somewhat more, I found some hints about Virtualbox
>>>>>>> kernel module having problems with r365488. Unfortunately, I am not able
>>>>>>> to find the thread again :(
>>>>>>>
>>>>>>> What seems to help as a workaround is to disable the loading of
>>>>>>> VirtualBox in /boot/loader.conf
>>>>>>>
>>>>>>> #vboxdrv_load="YES"
>>>>>>>
>>>>>>> and in /etc/rc.conf
>>>>>>>
>>>>>>> #vboxnet_enable="YES"
>>>>>>> #vboxguest_enable="YES"
>>>>>>>
>>>>>>>
>>>>>>> So probably, this page fault is not restricted to AMD Ryzen?
>>>>>>>
>>>>>>
>>>>>> Possibly you need to rebuild that kernel module. Maybe the FreeBSD
>>>>>> version was not bumped correctly.
>>>>>>
>>>>>> --HPS
>>>>>>
>>>>>
>>>>> Thanks for the hint. But I did rebuild all kernel modules before
>>>>> rebooting, in my case vbox*.ko, nvidia*.ko.
>>>>
>>>> Provide backtrace of the panic.
>>>>
>>>
>>> Hi Konstantin,
>>>
>>> Thanks for your response.
>>>
>>> After trying several ways to produce a core dump or a working kdb prompt
>>> without success, all I can offer is the following screen contents. I
>>> built a GENERIC kernel with debugging enabled, enable loading of vboxdrv
>>> via /boot/loader.conf and /etc/rc.conf as described above:
>>>
>>>
>>> [..snip..]
>>> procfs registered
>>> modulte_register_init: MOD_LOAD (tmpfs, 0xffffffff80caa060,
>>> 0xffffffff82520a70) error 17
>>> Timecounters tick every 1.000 msec
>>> lo0: bpf attached
>>> vlan: initialized, using hash tables with chaining
>>>
>>>
>>> Fatal trap 12: page fault while in kernel mode
>>> cpuid = 31; apic id = 1f
>>> fault virtual address   = 0x0
>>> fault code              = supervisor read data, page not present
>>> instruction pointer     = 0x20:0xffffffff80ea889b
>>> stack pointer           = 0x20:0xffffffff826017e0
>>> frame pointer           = 0x20:0xffffffff826017e0
>>> code segment            = base 0x0, limit 0xfffff, type 0x1b
>>>                         = DPL 0, pres 1, long 1, def32 0, gran 1
>>> processor eflags        = interrupt enabled, resume, IOPL = 0
>>> current process         = 0 (swapper)
>>> trap number             = 12
>>> panic: page fault
>>> cpuid = 31
>>> time = 1
>>> KDB: stack backtrace:
>>> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame
>>> 0xffffffff82601490
>>> vpanic() at vpanic+0x182/frame 0xffffffff826014e0
>>> panic() at panic+0x43/frame 0xffffffff82601540
>>> trap_fatal() at trap_fatal+0x387/frame 0xffffffff826015a0
>>> trap_pfault() at trap_pfault+0x97/frame 0xffffffff82601600
>>> calltrap() at calltrap+0x8/frame 0xffffffff82601710
>>> --- trap 0xc, rip = 0xffffffff80ea889b, rsp = 0xffffffff826017e0, rbp =
>>> 0xffffffff826017e0 ---
>>> phys_pager_getpages() at phys_pager_getpages+0xb/frame 0xffffffff826017e0
>>> vm_pager_get_pages() at vm_pager_get_pages+0x4f/frame 0xffffffff82601830
>>> vm_fault() at vm_fault+0x5d6/frame 0xffffffff82601940
>>> vm_map_wire_locked() at vm_map_wire_locked+0x3a6/framw 0xffffffff826019f0
>>> vm_map_wire() at vm_map_wire+0x6b/frame 0xffffffff82601a20
>>> rtR0MemObjFreeBSDAllocHelper() at
>>> rtR0MemObjFreeBSDAllocHelper+0xdc/frame 0xffffffff82601a70
>>> rtR0MemObjNativeAllocCont() at rtR0MemObjNativeAllocCont+0x50/frame
>>> 0xffffffff82601ac0
>>> supdrvGipCreate() at supdrvGipCreate+0x97/frame 0xffffffff82601b60
>>> supdrvInitDevExt() at supdrvInitDevExt+0x19a/frame 0xffffffff82601bd0
>>> VBoxDrvFreeBSDModuleEvent() at VBoxDrvFreeBSDModuleEvent+0x46/frame
>>> 0xffffffff82601bf0
>>> module_register_init() at module_register_init+0xbd/frame 0xffffffff82601c20
>>> mi_startup() at mi_startup+0xec/frame 0xffffffff82601c70
>>> btext() at btext+0x2c
>>> KDB: enter: panic
>>> [ thread pid 0 tid 100000 ]
>>> Stopped at      kdb_enter+0x37: movq    $0,0x10b5796(%rip9
>>> db>
>>>
>>>
>>> The system freezes at this point, no core dump is generated ;)  This
>>> does not happen without loading VBoxDrv.
>>>
>>> At least, the screen dump shows VBoxDrvFreeBSDModuleEvent(). I hope,
>>> this is of some help.
>>>
>> Yes it seems to be enough for me to see where the possible issue is.
>> Try this patch, I did not even compiled it.  Probably you need to put
>> it into ports/emulators/virtualbox-ose-kmod/files with the name ending
>> with .patch.
> This seems to be wrong, name should _start_ with the prefix 'patch-'.

Many thanks for the patch!

Putting it into emulators/virtualbox-ose-kmod/files/ as
patch-src_VBox_Runtime_r0drv_freebsd_memobj-r0drv-freebsd.c does not
patch the sources, probably because emobj-r0drv-freebsd.c was already
patched from the main port (virtualbox-ose).

Patching manually, build and install the kernel module seems to work fine.

Unfortunaly, after rebooting the same page fault occurs :(


>>
>> --- src/VBox/Runtime/r0drv/freebsd/memobj-r0drv-freebsd.c.xxx 2020-09-20 19:40:07.471956776 +0000
>> +++ src/VBox/Runtime/r0drv/freebsd/memobj-r0drv-freebsd.c 2020-09-20 19:46:03.606966773 +0000
>> @@ -323,7 +323,8 @@
>>      size_t      cPages = atop(pMemFreeBSD->Core.cb);
>>      int         rc;
>>  
>> -    pMemFreeBSD->pObject = vm_object_allocate(OBJT_PHYS, cPages);
>> +    pMemFreeBSD->pObject = vm_pager_allocate(OBJT_PHYS, NULL,
>> +      pMemFreeBSD->Core.cb, VM_PROT_ALL, 0, curthread->td_ucred);
>>  
>>      /* No additional object reference for auto-deallocation upon unmapping. */
>>  #if __FreeBSD_version >= 1000055
>> @@ -457,7 +458,8 @@
>>          return VERR_NO_MEMORY;
>>      }
>>  
>> -    pMemFreeBSD->pObject = vm_object_allocate(OBJT_PHYS, atop(cb));
>> +    pMemFreeBSD->pObject = vm_pager_allocate(OBJT_PHYS, NULL, cb, VM_PROT_ALL,
>> +       0, curthread->td_ucred);
>>  
>>      if (PhysHighest != NIL_RTHCPHYS)
>>          VmPhysAddrHigh = PhysHighest;
>>
>> _______________________________________________
>> [hidden email] mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to "[hidden email]"

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Fwd: Re: r365488 page faults on AMD Ryzen 9 3950X

Rainer Hurling
On 20.09.20 22:35, Rainer Hurling wrote:

> On 20.09.20 22:07, Konstantin Belousov wrote:
>> On Sun, Sep 20, 2020 at 10:55:26PM +0300, Konstantin Belousov wrote:
>>> On Sun, Sep 20, 2020 at 03:11:26PM +0200, Rainer Hurling wrote:
>>>> Am 20.09.20 um 11:38 schrieb Konstantin Belousov:
>>>>> On Sun, Sep 20, 2020 at 10:26:11AM +0200, Rainer Hurling wrote:
>>>>>> Am 20.09.20 um 10:20 schrieb Hans Petter Selasky:
>>>>>>> On 2020-09-20 10:05, Rainer Hurling wrote:
>>>>>>>> Hi monochrome,
>>>>>>>>
>>>>>>>> back to keyboard, it tried newest CURRENT (r365920) on my box and even
>>>>>>>> with newest sources the error occurs.
>>>>>>>>
>>>>>>>> After looking around somewhat more, I found some hints about Virtualbox
>>>>>>>> kernel module having problems with r365488. Unfortunately, I am not able
>>>>>>>> to find the thread again :(
>>>>>>>>
>>>>>>>> What seems to help as a workaround is to disable the loading of
>>>>>>>> VirtualBox in /boot/loader.conf
>>>>>>>>
>>>>>>>> #vboxdrv_load="YES"
>>>>>>>>
>>>>>>>> and in /etc/rc.conf
>>>>>>>>
>>>>>>>> #vboxnet_enable="YES"
>>>>>>>> #vboxguest_enable="YES"
>>>>>>>>
>>>>>>>>
>>>>>>>> So probably, this page fault is not restricted to AMD Ryzen?
>>>>>>>>
>>>>>>>
>>>>>>> Possibly you need to rebuild that kernel module. Maybe the FreeBSD
>>>>>>> version was not bumped correctly.
>>>>>>>
>>>>>>> --HPS
>>>>>>>
>>>>>>
>>>>>> Thanks for the hint. But I did rebuild all kernel modules before
>>>>>> rebooting, in my case vbox*.ko, nvidia*.ko.
>>>>>
>>>>> Provide backtrace of the panic.
>>>>>
>>>>
>>>> Hi Konstantin,
>>>>
>>>> Thanks for your response.
>>>>
>>>> After trying several ways to produce a core dump or a working kdb prompt
>>>> without success, all I can offer is the following screen contents. I
>>>> built a GENERIC kernel with debugging enabled, enable loading of vboxdrv
>>>> via /boot/loader.conf and /etc/rc.conf as described above:
>>>>
>>>>
>>>> [..snip..]
>>>> procfs registered
>>>> modulte_register_init: MOD_LOAD (tmpfs, 0xffffffff80caa060,
>>>> 0xffffffff82520a70) error 17
>>>> Timecounters tick every 1.000 msec
>>>> lo0: bpf attached
>>>> vlan: initialized, using hash tables with chaining
>>>>
>>>>
>>>> Fatal trap 12: page fault while in kernel mode
>>>> cpuid = 31; apic id = 1f
>>>> fault virtual address   = 0x0
>>>> fault code              = supervisor read data, page not present
>>>> instruction pointer     = 0x20:0xffffffff80ea889b
>>>> stack pointer           = 0x20:0xffffffff826017e0
>>>> frame pointer           = 0x20:0xffffffff826017e0
>>>> code segment            = base 0x0, limit 0xfffff, type 0x1b
>>>>                         = DPL 0, pres 1, long 1, def32 0, gran 1
>>>> processor eflags        = interrupt enabled, resume, IOPL = 0
>>>> current process         = 0 (swapper)
>>>> trap number             = 12
>>>> panic: page fault
>>>> cpuid = 31
>>>> time = 1
>>>> KDB: stack backtrace:
>>>> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame
>>>> 0xffffffff82601490
>>>> vpanic() at vpanic+0x182/frame 0xffffffff826014e0
>>>> panic() at panic+0x43/frame 0xffffffff82601540
>>>> trap_fatal() at trap_fatal+0x387/frame 0xffffffff826015a0
>>>> trap_pfault() at trap_pfault+0x97/frame 0xffffffff82601600
>>>> calltrap() at calltrap+0x8/frame 0xffffffff82601710
>>>> --- trap 0xc, rip = 0xffffffff80ea889b, rsp = 0xffffffff826017e0, rbp =
>>>> 0xffffffff826017e0 ---
>>>> phys_pager_getpages() at phys_pager_getpages+0xb/frame 0xffffffff826017e0
>>>> vm_pager_get_pages() at vm_pager_get_pages+0x4f/frame 0xffffffff82601830
>>>> vm_fault() at vm_fault+0x5d6/frame 0xffffffff82601940
>>>> vm_map_wire_locked() at vm_map_wire_locked+0x3a6/framw 0xffffffff826019f0
>>>> vm_map_wire() at vm_map_wire+0x6b/frame 0xffffffff82601a20
>>>> rtR0MemObjFreeBSDAllocHelper() at
>>>> rtR0MemObjFreeBSDAllocHelper+0xdc/frame 0xffffffff82601a70
>>>> rtR0MemObjNativeAllocCont() at rtR0MemObjNativeAllocCont+0x50/frame
>>>> 0xffffffff82601ac0
>>>> supdrvGipCreate() at supdrvGipCreate+0x97/frame 0xffffffff82601b60
>>>> supdrvInitDevExt() at supdrvInitDevExt+0x19a/frame 0xffffffff82601bd0
>>>> VBoxDrvFreeBSDModuleEvent() at VBoxDrvFreeBSDModuleEvent+0x46/frame
>>>> 0xffffffff82601bf0
>>>> module_register_init() at module_register_init+0xbd/frame 0xffffffff82601c20
>>>> mi_startup() at mi_startup+0xec/frame 0xffffffff82601c70
>>>> btext() at btext+0x2c
>>>> KDB: enter: panic
>>>> [ thread pid 0 tid 100000 ]
>>>> Stopped at      kdb_enter+0x37: movq    $0,0x10b5796(%rip9
>>>> db>
>>>>
>>>>
>>>> The system freezes at this point, no core dump is generated ;)  This
>>>> does not happen without loading VBoxDrv.
>>>>
>>>> At least, the screen dump shows VBoxDrvFreeBSDModuleEvent(). I hope,
>>>> this is of some help.
>>>>
>>> Yes it seems to be enough for me to see where the possible issue is.
>>> Try this patch, I did not even compiled it.  Probably you need to put
>>> it into ports/emulators/virtualbox-ose-kmod/files with the name ending
>>> with .patch.
>> This seems to be wrong, name should _start_ with the prefix 'patch-'.
>
> Many thanks for the patch!
>
> Putting it into emulators/virtualbox-ose-kmod/files/ as
> patch-src_VBox_Runtime_r0drv_freebsd_memobj-r0drv-freebsd.c does not
> patch the sources, probably because emobj-r0drv-freebsd.c was already
> patched from the main port (virtualbox-ose).
>
> Patching manually, build and install the kernel module seems to work fine.
>
> Unfortunaly, after rebooting the same page fault occurs :(
>
>
>>>
>>> --- src/VBox/Runtime/r0drv/freebsd/memobj-r0drv-freebsd.c.xxx 2020-09-20 19:40:07.471956776 +0000
>>> +++ src/VBox/Runtime/r0drv/freebsd/memobj-r0drv-freebsd.c 2020-09-20 19:46:03.606966773 +0000
>>> @@ -323,7 +323,8 @@
>>>      size_t      cPages = atop(pMemFreeBSD->Core.cb);
>>>      int         rc;
>>>  
>>> -    pMemFreeBSD->pObject = vm_object_allocate(OBJT_PHYS, cPages);
>>> +    pMemFreeBSD->pObject = vm_pager_allocate(OBJT_PHYS, NULL,
>>> +      pMemFreeBSD->Core.cb, VM_PROT_ALL, 0, curthread->td_ucred);
>>>  
>>>      /* No additional object reference for auto-deallocation upon unmapping. */
>>>  #if __FreeBSD_version >= 1000055
>>> @@ -457,7 +458,8 @@
>>>          return VERR_NO_MEMORY;
>>>      }
>>>  
>>> -    pMemFreeBSD->pObject = vm_object_allocate(OBJT_PHYS, atop(cb));
>>> +    pMemFreeBSD->pObject = vm_pager_allocate(OBJT_PHYS, NULL, cb, VM_PROT_ALL,
>>> +       0, curthread->td_ucred);
>>>  
>>>      if (PhysHighest != NIL_RTHCPHYS)
>>>          VmPhysAddrHigh = PhysHighest;
>>>
I tried a second time with the changes of your patch. This time, I
patched
files/patch-src_VBox_Runtime_r0drv_freebsd_memobj-r0drv-freebsd.c in
emulators/virtualbox-ose (the main port).

After rebuilding virtualbox-ose-kmod and virtualbox-ose and rebooting, I
got some more info (lines at the beginning, numbered #6 to #13; lines #1
to #5 are outside of the frozen screen) and afterwards slightly
different messages:


[..snip..]
#6 0xffffffff8255f756 at rtR0MemObjFreeBSDAllocHelper+0x96
#7 0xffffffff8255f8e0 at rtR0MemObjNativeAllocCont+0x50
#8 0xffffffff8253c7b7 at supdrvGipCreate+0x97
#9 0xffffffff8253519a at supdrvInitDevExt+0x19a
#10 0xffffffff825450f6 at VBoxDrvFreeBSDModuleEvent+0x46
#11 0xffffffff80bb41fd at module_register_init+0xbd
#12 0xffffffff80b6985c at mi_startup+0xec
#13 0xffffffff8037002c at btext+0x2c


Fatal trap 12: page fault while in kernel mode
cpuid = 31; apic id = 1f
fault virtual address   = 0x25407efa
fault code              = supervisor read data, page not present
instruction pointer     = 0x20:0xffffffff80ec0b63
stack pointer           = 0x28:0xffffffff826018b0
frame pointer           = 0x28:0xffffffff82601940
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 0 (swapper)
trap number             = 12
panic: page fault
cpuid = 31
time = 1
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame
0xffffffff82601560
vpanic() at vpanic+0x182/frame 0xffffffff826015b0
panic() at panic+0x43/frame 0xffffffff82601610
trap_fatal() at trap_fatal+0x387/frame 0xffffffff82601670
trap_pfault() at trap_pfault+0x97/frame 0xffffffff826016d0
trap() at trap+0x2ab/frame 0xffffffff826017e0
calltrap() at calltrap+0x8/frame 0xffffffff826017e0
--- trap 0xc, rip = 0xffffffff80ec0b63, rsp = 0xffffffff826018b0, rbp =
0xffffffff82601940 ---
vm_map_insert() at vm_map_insert+0x2f3/framw 0xffffffff82601940
vm_map_find() at vm_map_find+0x4a4/frame 0xffffffff82601a00
rtR0MemObjFreeBSDAllocHelper() at
rtR0MemObjFreeBSDAllocHelper+0x96/frame 0xffffffff82601a70
rtR0MemObjNativeAllocCont() at rtR0MemObjNativeAllocCont+0x50/frame
0xffffffff82601ac0
supdrvGipCreate() at supdrvGipCreate+0x97/frame 0xffffffff82601b60
supdrvInitDevExt() at supdrvInitDevExt+0x19a/frame 0xffffffff82601bd0
VBoxDrvFreeBSDModuleEvent() at VBoxDrvFreeBSDModuleEvent+0x46/frame
0xffffffff82601bf0
module_register_init() at module_register_init+0xbd/frame 0xffffffff82601c20
mi_startup() at mi_startup+0xec/frame 0xffffffff82601c70
btext() at btext+0x2c
KDB: enter: panic
[ thread pid 0 tid 100000 ]
Stopped at      kdb_enter+0x37: movq    $0,0x10b5616(%rip)
db>


Perhaps this gives some more insight into the problem? I can't assess,
sorry.
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Fwd: Re: r365488 page faults on AMD Ryzen 9 3950X

Konstantin Belousov
On Mon, Sep 21, 2020 at 08:57:46PM +0200, Rainer Hurling wrote:
> Fatal trap 12: page fault while in kernel mode
> cpuid = 31; apic id = 1f
> fault virtual address   = 0x25407efa
This address is very suspicious.

I cannot claim it as the fact, but most likely cause for such garbage
pointer value is mismatched ABI between kernel and module.  In other
words, the module was built against headers from different kernel.

> fault code              = supervisor read data, page not present
> instruction pointer     = 0x20:0xffffffff80ec0b63
> stack pointer           = 0x28:0xffffffff826018b0
> frame pointer           = 0x28:0xffffffff82601940
> code segment            = base 0x0, limit 0xfffff, type 0x1b
>                         = DPL 0, pres 1, long 1, def32 0, gran 1
> processor eflags        = interrupt enabled, resume, IOPL = 0
> current process         = 0 (swapper)
> trap number             = 12
> panic: page fault
> cpuid = 31
> time = 1
> KDB: stack backtrace:
> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame
> 0xffffffff82601560
> vpanic() at vpanic+0x182/frame 0xffffffff826015b0
> panic() at panic+0x43/frame 0xffffffff82601610
> trap_fatal() at trap_fatal+0x387/frame 0xffffffff82601670
> trap_pfault() at trap_pfault+0x97/frame 0xffffffff826016d0
> trap() at trap+0x2ab/frame 0xffffffff826017e0
> calltrap() at calltrap+0x8/frame 0xffffffff826017e0
> --- trap 0xc, rip = 0xffffffff80ec0b63, rsp = 0xffffffff826018b0, rbp =
> 0xffffffff82601940 ---
> vm_map_insert() at vm_map_insert+0x2f3/framw 0xffffffff82601940
> vm_map_find() at vm_map_find+0x4a4/frame 0xffffffff82601a00
> rtR0MemObjFreeBSDAllocHelper() at
> rtR0MemObjFreeBSDAllocHelper+0x96/frame 0xffffffff82601a70
> rtR0MemObjNativeAllocCont() at rtR0MemObjNativeAllocCont+0x50/frame
> 0xffffffff82601ac0
> supdrvGipCreate() at supdrvGipCreate+0x97/frame 0xffffffff82601b60
> supdrvInitDevExt() at supdrvInitDevExt+0x19a/frame 0xffffffff82601bd0
> VBoxDrvFreeBSDModuleEvent() at VBoxDrvFreeBSDModuleEvent+0x46/frame
> 0xffffffff82601bf0
> module_register_init() at module_register_init+0xbd/frame 0xffffffff82601c20
> mi_startup() at mi_startup+0xec/frame 0xffffffff82601c70
> btext() at btext+0x2c
> KDB: enter: panic
> [ thread pid 0 tid 100000 ]
> Stopped at      kdb_enter+0x37: movq    $0,0x10b5616(%rip)
> db>
>
>
> Perhaps this gives some more insight into the problem? I can't assess,
> sorry.
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Fwd: Re: r365488 page faults on AMD Ryzen 9 3950X

Rainer Hurling
Am 22.09.20 um 00:13 schrieb Konstantin Belousov:
> On Mon, Sep 21, 2020 at 08:57:46PM +0200, Rainer Hurling wrote:
>> Fatal trap 12: page fault while in kernel mode
>> cpuid = 31; apic id = 1f
>> fault virtual address   = 0x25407efa
> This address is very suspicious.
>
> I cannot claim it as the fact, but most likely cause for such garbage
> pointer value is mismatched ABI between kernel and module.  In other
> words, the module was built against headers from different kernel.

Hmm, thanks for the pointer. I will double check this evening and
reporting back.

Normally, this module should have been built and installed with the
kernel build.

>
>> fault code              = supervisor read data, page not present
>> instruction pointer     = 0x20:0xffffffff80ec0b63
>> stack pointer           = 0x28:0xffffffff826018b0
>> frame pointer           = 0x28:0xffffffff82601940
>> code segment            = base 0x0, limit 0xfffff, type 0x1b
>>                          = DPL 0, pres 1, long 1, def32 0, gran 1
>> processor eflags        = interrupt enabled, resume, IOPL = 0
>> current process         = 0 (swapper)
>> trap number             = 12
>> panic: page fault
>> cpuid = 31
>> time = 1
>> KDB: stack backtrace:
>> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame
>> 0xffffffff82601560
>> vpanic() at vpanic+0x182/frame 0xffffffff826015b0
>> panic() at panic+0x43/frame 0xffffffff82601610
>> trap_fatal() at trap_fatal+0x387/frame 0xffffffff82601670
>> trap_pfault() at trap_pfault+0x97/frame 0xffffffff826016d0
>> trap() at trap+0x2ab/frame 0xffffffff826017e0
>> calltrap() at calltrap+0x8/frame 0xffffffff826017e0
>> --- trap 0xc, rip = 0xffffffff80ec0b63, rsp = 0xffffffff826018b0, rbp =
>> 0xffffffff82601940 ---
>> vm_map_insert() at vm_map_insert+0x2f3/framw 0xffffffff82601940
>> vm_map_find() at vm_map_find+0x4a4/frame 0xffffffff82601a00
>> rtR0MemObjFreeBSDAllocHelper() at
>> rtR0MemObjFreeBSDAllocHelper+0x96/frame 0xffffffff82601a70
>> rtR0MemObjNativeAllocCont() at rtR0MemObjNativeAllocCont+0x50/frame
>> 0xffffffff82601ac0
>> supdrvGipCreate() at supdrvGipCreate+0x97/frame 0xffffffff82601b60
>> supdrvInitDevExt() at supdrvInitDevExt+0x19a/frame 0xffffffff82601bd0
>> VBoxDrvFreeBSDModuleEvent() at VBoxDrvFreeBSDModuleEvent+0x46/frame
>> 0xffffffff82601bf0
>> module_register_init() at module_register_init+0xbd/frame 0xffffffff82601c20
>> mi_startup() at mi_startup+0xec/frame 0xffffffff82601c70
>> btext() at btext+0x2c
>> KDB: enter: panic
>> [ thread pid 0 tid 100000 ]
>> Stopped at      kdb_enter+0x37: movq    $0,0x10b5616(%rip)
>> db>
>>
>>
>> Perhaps this gives some more insight into the problem? I can't assess,
>> sorry.

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Fwd: Re: r365488 page faults on AMD Ryzen 9 3950X

monochrome
Rainer, I'm all up and running and clean with the latest again, if it
still doesn't work after your next try, send me your step-by-step to
patch and i'll try it here. I'm using ryzen video so I have to disable
stuff to even see the fault messages.

On 9/22/20 1:06 AM, Rainer Hurling wrote:

> Am 22.09.20 um 00:13 schrieb Konstantin Belousov:
>> On Mon, Sep 21, 2020 at 08:57:46PM +0200, Rainer Hurling wrote:
>>> Fatal trap 12: page fault while in kernel mode
>>> cpuid = 31; apic id = 1f
>>> fault virtual address   = 0x25407efa
>> This address is very suspicious.
>>
>> I cannot claim it as the fact, but most likely cause for such garbage
>> pointer value is mismatched ABI between kernel and module.  In other
>> words, the module was built against headers from different kernel.
>
> Hmm, thanks for the pointer. I will double check this evening and
> reporting back.
>
> Normally, this module should have been built and installed with the
> kernel build.
>
>>
>>> fault code              = supervisor read data, page not present
>>> instruction pointer     = 0x20:0xffffffff80ec0b63
>>> stack pointer           = 0x28:0xffffffff826018b0
>>> frame pointer           = 0x28:0xffffffff82601940
>>> code segment            = base 0x0, limit 0xfffff, type 0x1b
>>>                          = DPL 0, pres 1, long 1, def32 0, gran 1
>>> processor eflags        = interrupt enabled, resume, IOPL = 0
>>> current process         = 0 (swapper)
>>> trap number             = 12
>>> panic: page fault
>>> cpuid = 31
>>> time = 1
>>> KDB: stack backtrace:
>>> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame
>>> 0xffffffff82601560
>>> vpanic() at vpanic+0x182/frame 0xffffffff826015b0
>>> panic() at panic+0x43/frame 0xffffffff82601610
>>> trap_fatal() at trap_fatal+0x387/frame 0xffffffff82601670
>>> trap_pfault() at trap_pfault+0x97/frame 0xffffffff826016d0
>>> trap() at trap+0x2ab/frame 0xffffffff826017e0
>>> calltrap() at calltrap+0x8/frame 0xffffffff826017e0
>>> --- trap 0xc, rip = 0xffffffff80ec0b63, rsp = 0xffffffff826018b0, rbp =
>>> 0xffffffff82601940 ---
>>> vm_map_insert() at vm_map_insert+0x2f3/framw 0xffffffff82601940
>>> vm_map_find() at vm_map_find+0x4a4/frame 0xffffffff82601a00
>>> rtR0MemObjFreeBSDAllocHelper() at
>>> rtR0MemObjFreeBSDAllocHelper+0x96/frame 0xffffffff82601a70
>>> rtR0MemObjNativeAllocCont() at rtR0MemObjNativeAllocCont+0x50/frame
>>> 0xffffffff82601ac0
>>> supdrvGipCreate() at supdrvGipCreate+0x97/frame 0xffffffff82601b60
>>> supdrvInitDevExt() at supdrvInitDevExt+0x19a/frame 0xffffffff82601bd0
>>> VBoxDrvFreeBSDModuleEvent() at VBoxDrvFreeBSDModuleEvent+0x46/frame
>>> 0xffffffff82601bf0
>>> module_register_init() at module_register_init+0xbd/frame
>>> 0xffffffff82601c20
>>> mi_startup() at mi_startup+0xec/frame 0xffffffff82601c70
>>> btext() at btext+0x2c
>>> KDB: enter: panic
>>> [ thread pid 0 tid 100000 ]
>>> Stopped at      kdb_enter+0x37: movq    $0,0x10b5616(%rip)
>>> db>
>>>
>>>
>>> Perhaps this gives some more insight into the problem? I can't assess,
>>> sorry.
>
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Fwd: Re: r365488 page faults on AMD Ryzen 9 3950X

Rainer Hurling
In reply to this post by Rainer Hurling
On 22.09.20 07:06, Rainer Hurling wrote:

> Am 22.09.20 um 00:13 schrieb Konstantin Belousov:
>> On Mon, Sep 21, 2020 at 08:57:46PM +0200, Rainer Hurling wrote:
>>> Fatal trap 12: page fault while in kernel mode
>>> cpuid = 31; apic id = 1f
>>> fault virtual address   = 0x25407efa
>> This address is very suspicious.
>>
>> I cannot claim it as the fact, but most likely cause for such garbage
>> pointer value is mismatched ABI between kernel and module.  In other
>> words, the module was built against headers from different kernel.
>
> Hmm, thanks for the pointer. I will double check this evening and
> reporting back.
>
> Normally, this module should have been built and installed with the
> kernel build.

As I said, the module was rebuild and reinstalled with the kernel build,
and I double checked, the module was the patched version.

So the boot messages about the page fault should be created by the
rebuild, patched module.

>
>>
>>> fault code              = supervisor read data, page not present
>>> instruction pointer     = 0x20:0xffffffff80ec0b63
>>> stack pointer           = 0x28:0xffffffff826018b0
>>> frame pointer           = 0x28:0xffffffff82601940
>>> code segment            = base 0x0, limit 0xfffff, type 0x1b
>>>                          = DPL 0, pres 1, long 1, def32 0, gran 1
>>> processor eflags        = interrupt enabled, resume, IOPL = 0
>>> current process         = 0 (swapper)
>>> trap number             = 12
>>> panic: page fault
>>> cpuid = 31
>>> time = 1
>>> KDB: stack backtrace:
>>> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame
>>> 0xffffffff82601560
>>> vpanic() at vpanic+0x182/frame 0xffffffff826015b0
>>> panic() at panic+0x43/frame 0xffffffff82601610
>>> trap_fatal() at trap_fatal+0x387/frame 0xffffffff82601670
>>> trap_pfault() at trap_pfault+0x97/frame 0xffffffff826016d0
>>> trap() at trap+0x2ab/frame 0xffffffff826017e0
>>> calltrap() at calltrap+0x8/frame 0xffffffff826017e0
>>> --- trap 0xc, rip = 0xffffffff80ec0b63, rsp = 0xffffffff826018b0, rbp =
>>> 0xffffffff82601940 ---
>>> vm_map_insert() at vm_map_insert+0x2f3/framw 0xffffffff82601940
>>> vm_map_find() at vm_map_find+0x4a4/frame 0xffffffff82601a00
>>> rtR0MemObjFreeBSDAllocHelper() at
>>> rtR0MemObjFreeBSDAllocHelper+0x96/frame 0xffffffff82601a70
>>> rtR0MemObjNativeAllocCont() at rtR0MemObjNativeAllocCont+0x50/frame
>>> 0xffffffff82601ac0
>>> supdrvGipCreate() at supdrvGipCreate+0x97/frame 0xffffffff82601b60
>>> supdrvInitDevExt() at supdrvInitDevExt+0x19a/frame 0xffffffff82601bd0
>>> VBoxDrvFreeBSDModuleEvent() at VBoxDrvFreeBSDModuleEvent+0x46/frame
>>> 0xffffffff82601bf0
>>> module_register_init() at module_register_init+0xbd/frame
>>> 0xffffffff82601c20
>>> mi_startup() at mi_startup+0xec/frame 0xffffffff82601c70
>>> btext() at btext+0x2c
>>> KDB: enter: panic
>>> [ thread pid 0 tid 100000 ]
>>> Stopped at      kdb_enter+0x37: movq    $0,0x10b5616(%rip)
>>> db>
>>>
>>>
>>> Perhaps this gives some more insight into the problem? I can't assess,
>>> sorry.

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Fwd: Re: r365488 page faults on AMD Ryzen 9 3950X

Rainer Hurling
In reply to this post by monochrome
On 22.09.20 07:51, monochrome wrote:
> Rainer, I'm all up and running and clean with the latest again, if it
> still doesn't work after your next try, send me your step-by-step to
> patch and i'll try it here. I'm using ryzen video so I have to disable
> stuff to even see the fault messages.

Hi monochrome,

The attached file is the patched version, I put in the files dir of
emulators/virtualbox-ose (the main port, not the kernel modules one).

Then I rebuilt and reinstall the ports mulators/virtualbox-ose-kmod and
mulators/virtualbox-ose and rebooted the box.

In my case, the boot process freezes after the page fault messages.


>
> On 9/22/20 1:06 AM, Rainer Hurling wrote:
>> Am 22.09.20 um 00:13 schrieb Konstantin Belousov:
>>> On Mon, Sep 21, 2020 at 08:57:46PM +0200, Rainer Hurling wrote:
>>>> Fatal trap 12: page fault while in kernel mode
>>>> cpuid = 31; apic id = 1f
>>>> fault virtual address   = 0x25407efa
>>> This address is very suspicious.
>>>
>>> I cannot claim it as the fact, but most likely cause for such garbage
>>> pointer value is mismatched ABI between kernel and module.  In other
>>> words, the module was built against headers from different kernel.
>>
>> Hmm, thanks for the pointer. I will double check this evening and
>> reporting back.
>>
>> Normally, this module should have been built and installed with the
>> kernel build.
>>
>>>
>>>> fault code              = supervisor read data, page not present
>>>> instruction pointer     = 0x20:0xffffffff80ec0b63
>>>> stack pointer           = 0x28:0xffffffff826018b0
>>>> frame pointer           = 0x28:0xffffffff82601940
>>>> code segment            = base 0x0, limit 0xfffff, type 0x1b
>>>>                          = DPL 0, pres 1, long 1, def32 0, gran 1
>>>> processor eflags        = interrupt enabled, resume, IOPL = 0
>>>> current process         = 0 (swapper)
>>>> trap number             = 12
>>>> panic: page fault
>>>> cpuid = 31
>>>> time = 1
>>>> KDB: stack backtrace:
>>>> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame
>>>> 0xffffffff82601560
>>>> vpanic() at vpanic+0x182/frame 0xffffffff826015b0
>>>> panic() at panic+0x43/frame 0xffffffff82601610
>>>> trap_fatal() at trap_fatal+0x387/frame 0xffffffff82601670
>>>> trap_pfault() at trap_pfault+0x97/frame 0xffffffff826016d0
>>>> trap() at trap+0x2ab/frame 0xffffffff826017e0
>>>> calltrap() at calltrap+0x8/frame 0xffffffff826017e0
>>>> --- trap 0xc, rip = 0xffffffff80ec0b63, rsp = 0xffffffff826018b0, rbp =
>>>> 0xffffffff82601940 ---
>>>> vm_map_insert() at vm_map_insert+0x2f3/framw 0xffffffff82601940
>>>> vm_map_find() at vm_map_find+0x4a4/frame 0xffffffff82601a00
>>>> rtR0MemObjFreeBSDAllocHelper() at
>>>> rtR0MemObjFreeBSDAllocHelper+0x96/frame 0xffffffff82601a70
>>>> rtR0MemObjNativeAllocCont() at rtR0MemObjNativeAllocCont+0x50/frame
>>>> 0xffffffff82601ac0
>>>> supdrvGipCreate() at supdrvGipCreate+0x97/frame 0xffffffff82601b60
>>>> supdrvInitDevExt() at supdrvInitDevExt+0x19a/frame 0xffffffff82601bd0
>>>> VBoxDrvFreeBSDModuleEvent() at VBoxDrvFreeBSDModuleEvent+0x46/frame
>>>> 0xffffffff82601bf0
>>>> module_register_init() at module_register_init+0xbd/frame
>>>> 0xffffffff82601c20
>>>> mi_startup() at mi_startup+0xec/frame 0xffffffff82601c70
>>>> btext() at btext+0x2c
>>>> KDB: enter: panic
>>>> [ thread pid 0 tid 100000 ]
>>>> Stopped at      kdb_enter+0x37: movq    $0,0x10b5616(%rip)
>>>> db>
>>>>
>>>>
>>>> Perhaps this gives some more insight into the problem? I can't assess,
>>>> sorry.
>>

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Fwd: Re: r365488 page faults on AMD Ryzen 9 3950X

Oleg V. Nauman-3
In reply to this post by Rainer Hurling
On 2020 M09 22, Tue 19:45:25 EEST Rainer Hurling wrote:

> On 22.09.20 07:06, Rainer Hurling wrote:
> > Am 22.09.20 um 00:13 schrieb Konstantin Belousov:
> >> On Mon, Sep 21, 2020 at 08:57:46PM +0200, Rainer Hurling wrote:
> >>> Fatal trap 12: page fault while in kernel mode
> >>> cpuid = 31; apic id = 1f
> >>> fault virtual address   = 0x25407efa
> >>
> >> This address is very suspicious.
> >>
> >> I cannot claim it as the fact, but most likely cause for such garbage
> >> pointer value is mismatched ABI between kernel and module.  In other
> >> words, the module was built against headers from different kernel.
> >
> > Hmm, thanks for the pointer. I will double check this evening and
> > reporting back.
> >
> > Normally, this module should have been built and installed with the
> > kernel build.
>
> As I said, the module was rebuild and reinstalled with the kernel build,
> and I double checked, the module was the patched version.
>
> So the boot messages about the page fault should be created by the
> rebuild, patched module.
>
> >>> fault code              = supervisor read data, page not present
> >>> instruction pointer     = 0x20:0xffffffff80ec0b63
> >>> stack pointer           = 0x28:0xffffffff826018b0
> >>> frame pointer           = 0x28:0xffffffff82601940
> >>> code segment            = base 0x0, limit 0xfffff, type 0x1b
> >>>                          = DPL 0, pres 1, long 1, def32 0, gran 1
> >>> processor eflags        = interrupt enabled, resume, IOPL = 0
> >>> current process         = 0 (swapper)
> >>> trap number             = 12
> >>> panic: page fault
> >>> cpuid = 31
> >>> time = 1
> >>> KDB: stack backtrace:
> >>> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame
> >>> 0xffffffff82601560
> >>> vpanic() at vpanic+0x182/frame 0xffffffff826015b0
> >>> panic() at panic+0x43/frame 0xffffffff82601610
> >>> trap_fatal() at trap_fatal+0x387/frame 0xffffffff82601670
> >>> trap_pfault() at trap_pfault+0x97/frame 0xffffffff826016d0
> >>> trap() at trap+0x2ab/frame 0xffffffff826017e0
> >>> calltrap() at calltrap+0x8/frame 0xffffffff826017e0
> >>> --- trap 0xc, rip = 0xffffffff80ec0b63, rsp = 0xffffffff826018b0, rbp =
> >>> 0xffffffff82601940 ---
> >>> vm_map_insert() at vm_map_insert+0x2f3/framw 0xffffffff82601940
> >>> vm_map_find() at vm_map_find+0x4a4/frame 0xffffffff82601a00
> >>> rtR0MemObjFreeBSDAllocHelper() at
> >>> rtR0MemObjFreeBSDAllocHelper+0x96/frame 0xffffffff82601a70
> >>> rtR0MemObjNativeAllocCont() at rtR0MemObjNativeAllocCont+0x50/frame
> >>> 0xffffffff82601ac0
> >>> supdrvGipCreate() at supdrvGipCreate+0x97/frame 0xffffffff82601b60
> >>> supdrvInitDevExt() at supdrvInitDevExt+0x19a/frame 0xffffffff82601bd0
> >>> VBoxDrvFreeBSDModuleEvent() at VBoxDrvFreeBSDModuleEvent+0x46/frame
> >>> 0xffffffff82601bf0
> >>> module_register_init() at module_register_init+0xbd/frame
> >>> 0xffffffff82601c20
> >>> mi_startup() at mi_startup+0xec/frame 0xffffffff82601c70
> >>> btext() at btext+0x2c
> >>> KDB: enter: panic
> >>> [ thread pid 0 tid 100000 ]
> >>> Stopped at      kdb_enter+0x37: movq    $0,0x10b5616(%rip)
> >>> db>
> >>>
> >>>
> >>> Perhaps this gives some more insight into the problem? I can't assess,
> >>> sorry.


 I am experiencing the same issue with panic caused by 'kldload vboxdrv'
Below is the stack strace , with both virtualbox-ose and virtualbox-ose-kmod
patched:

Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0x1e419ada
fault code              = supervisor read data, page not present
instruction pointer     = 0x20:0xffffffff80731b0d
stack pointer           = 0x28:0xfffffe008223b4d0
frame pointer           = 0x28:0xfffffe008223b550
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 2194 (kldload)
trap number             = 12
panic: page fault
cpuid = 0
time = 1600808943
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe008223b1b0
vpanic() at vpanic+0x182/frame 0xfffffe008223b200
panic() at panic+0x43/frame 0xfffffe008223b260
trap_fatal() at trap_fatal+0x387/frame 0xfffffe008223b2c0
trap_pfault() at trap_pfault+0x49/frame 0xfffffe008223b2f0
trap() at trap+0x259/frame 0xfffffe008223b400
calltrap() at calltrap+0x8/frame 0xfffffe008223b400
--- trap 0xc, rip = 0xffffffff80731b0d, rsp = 0xfffffe008223b4d0, rbp =
0xfffffe008223b550 ---
vm_map_insert() at vm_map_insert+0x24d/frame 0xfffffe008223b550
vm_map_find() at vm_map_find+0x539/frame 0xfffffe008223b630
rtR0MemObjFreeBSDAllocHelper() at rtR0MemObjFreeBSDAllocHelper+0x96/frame
0xfffffe008223b6a0
rtR0MemObjNativeAllocCont() at rtR0MemObjNativeAllocCont+0x50/frame
0xfffffe008223b6f0
supdrvGipCreate() at supdrvGipCreate+0x97/frame 0xfffffe008223b790
supdrvInitDevExt() at supdrvInitDevExt+0x19a/frame 0xfffffe008223b800
VBoxDrvFreeBSDModuleEvent() at VBoxDrvFreeBSDModuleEvent+0x46/frame
0xfffffe008223b820
module_register_init() at module_register_init+0x94/frame 0xfffffe008223b850
linker_load_module() at linker_load_module+0xb78/frame 0xfffffe008223bb60
kern_kldload() at kern_kldload+0xa3/frame 0xfffffe008223bba0
sys_kldload() at sys_kldload+0x5b/frame 0xfffffe008223bbd0
amd64_syscall() at amd64_syscall+0xff/frame 0xfffffe008223bcf0
fast_syscall_common() at fast_syscall_common+0xf8/frame 0xfffffe008223bcf0
--- syscall (304, FreeBSD ELF64, sys_kldload), rip = 0x80037a11a, rsp =
0x7fffffffe598, rbp = 0x7fffffffeb10 ---
KDB: enter: panic

__curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:55
55              __asm("movq %%gs:%P1,%0" : "=r" (td) : "n" (offsetof(struct
pcpu,
(kgdb) #0  __curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:55
#1  doadump (textdump=0) at /usr/src/sys/kern/kern_shutdown.c:394
#2  0xffffffff8035104a in db_dump (dummy=<optimized out>,
    dummy2=<optimized out>, dummy3=<unavailable>, dummy4=<unavailable>)
    at /usr/src/sys/ddb/db_command.c:575
#3  0xffffffff80350e10 in db_command (last_cmdp=<optimized out>,
    cmd_table=<optimized out>, dopager=1) at /usr/src/sys/ddb/db_command.c:482
#4  0xffffffff80350b7d in db_command_loop ()
    at /usr/src/sys/ddb/db_command.c:535
#5  0xffffffff80353df6 in db_trap (type=<optimized out>, code=<optimized out>)
    at /usr/src/sys/ddb/db_main.c:270
#6  0xffffffff805983c3 in kdb_trap (type=3, code=0, tf=<optimized out>)
    at /usr/src/sys/kern/subr_kdb.c:699
#7  0xffffffff807ac26a in trap (frame=0xfffffe008223b0e0)
    at /usr/src/sys/amd64/amd64/trap.c:576
#8  <signal handler called>
#9  kdb_enter (why=0xffffffff80831558 "panic", msg=<optimized out>)
    at /usr/src/sys/kern/subr_kdb.c:486
#10 0xffffffff80552f0e in vpanic (fmt=<optimized out>, ap=<optimized out>)
    at /usr/src/sys/kern/kern_shutdown.c:902
#11 0xffffffff80552d63 in panic (
    fmt=0xffffffff80a8e688 <vt_conswindow+16>
"\275\317\203\200\377\377\377\377") at /usr/src/sys/kern/kern_shutdown.c:839
#12 0xffffffff807ac6a7 in trap_fatal (frame=0xfffffe008223b410, eva=507615962)
    at /usr/src/sys/amd64/amd64/trap.c:915
#13 0xffffffff807ac6f9 in trap_pfault (frame=0xfffffe008223b410,
    usermode=<optimized out>, signo=<optimized out>, ucode=<optimized out>)
    at /usr/src/sys/amd64/amd64/trap.c:732
#14 0xffffffff807abdd9 in trap (frame=0xfffffe008223b410)
    at /usr/src/sys/amd64/amd64/trap.c:398
#15 <signal handler called>
#16 vm_map_insert (map=<optimized out>, object=<optimized out>,
    offset=<optimized out>, start=18446741876713496576,
    end=18446741876713500672, prot=<optimized out>, max=7 '\a', cow=0)
    at /usr/src/sys/vm/vm_map.c:1660
#17 0xffffffff807341e9 in vm_map_find (map=<optimized out>,
    object=<optimized out>, offset=0, addr=<optimized out>, length=4096,
    max_addr=0, find_space=1, prot=3 '\003', max=7 '\a', cow=0)
    at /usr/src/sys/vm/vm_map.c:2156
#18 0xffffffff811c9326 in rtR0MemObjFreeBSDAllocHelper ()
   from /boot/modules/vboxdrv.ko
#19 0xffffffff811c94b0 in rtR0MemObjNativeAllocCont ()
   from /boot/modules/vboxdrv.ko
#20 0xffffffff811a6787 in supdrvGipCreate () from /boot/modules/vboxdrv.ko
#21 0xffffffff8119f19a in supdrvInitDevExt () from /boot/modules/vboxdrv.ko
#22 0xffffffff811aeff6 in VBoxDrvFreeBSDModuleEvent ()
   from /boot/modules/vboxdrv.ko
#23 0xffffffff8053a204 in module_register_init (arg=0x0)
    at /usr/src/sys/kern/kern_module.c:123
#24 0xffffffff8052df88 in linker_file_sysinit (lf=<optimized out>)
    at /usr/src/sys/kern/kern_linker.c:235
#25 linker_load_file (filename=<optimized out>, result=<optimized out>)
    at /usr/src/sys/kern/kern_linker.c:460
#26 linker_load_module (kldname=<optimized out>,
    modname=0xfffff80003525000 "vboxdrv", parent=0x0,
    verinfo=<optimized out>, lfpp=<optimized out>)
    at /usr/src/sys/kern/kern_linker.c:2129
#27 0xffffffff8052f5c3 in kern_kldload (td=<optimized out>,
    file=<optimized out>, fileid=0xfffffe008223bbb4)
    at /usr/src/sys/kern/kern_linker.c:1089
#28 0xffffffff8052f69b in sys_kldload (td=0xfffffe0081dd5c00,
    uap=<optimized out>) at /usr/src/sys/kern/kern_linker.c:1115
#29 0xffffffff807ace1f in syscallenter (td=0xfffffe0081dd5c00)
    at /usr/src/sys/amd64/amd64/../../kern/subr_syscall.c:162
#30 amd64_syscall (td=0xfffffe0081dd5c00, traced=0)
    at /usr/src/sys/amd64/amd64/trap.c:1156
#31 <signal handler called>
#32 0x000000080037a11a in ?? ()
Backtrace stopped: Cannot access memory at address 0x7fffffffe598
(kgdb)

Thank you

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
12