On 2019-08-25 10:55, Mark Johnston wrote:
>
> Can you please try applying this patch as well?
Thanks, that fixed the panic and allows the system to fully boot again.
--
Rebecca Cran
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.o
On Sun, Aug 25, 2019 at 10:27:48AM -0600, Rebecca Cran wrote:
> On 2019-08-25 08:30, Konstantin Belousov wrote:
> >
> > So what happens, IMO, is that for memory-less domains ds_cnt is zero
> > because ds_mask is zero, which causes the exception on divide. You
> > can try the following combined pat
On 2019-08-25 08:30, Konstantin Belousov wrote:
>
> So what happens, IMO, is that for memory-less domains ds_cnt is zero
> because ds_mask is zero, which causes the exception on divide. You
> can try the following combined patch, but I really dislike the fact
> that I cannot safely use DOMAINSET_F
On Sun, Aug 25, 2019 at 05:30:34PM +0300, Konstantin Belousov wrote:
> On Sun, Aug 25, 2019 at 07:17:20AM -0600, Rebecca Cran wrote:
> > On 2019-08-25 00:24, Konstantin Belousov wrote:
> > > What are the panic messages ?
> >
> > Fatal trap 18: integer divide fault while in kernel mode
> >
> > ins
On Sun, Aug 25, 2019 at 07:17:20AM -0600, Rebecca Cran wrote:
> On 2019-08-25 00:24, Konstantin Belousov wrote:
> > What are the panic messages ?
>
> Fatal trap 18: integer divide fault while in kernel mode
>
> instruction pointer = 0x20:0x80f1027c
>
> stack pointer = 0x28:0x8458
On 2019-08-25 00:24, Konstantin Belousov wrote:
> What are the panic messages ?
Fatal trap 18: integer divide fault while in kernel mode
instruction pointer = 0x20:0x80f1027c
stack pointer = 0x28:0x845809f0
frame pointer = 0x28:0x84580a00
code segment = base 0x0, limit
On Sat, Aug 24, 2019 at 05:29:23PM -0600, Rebecca Cran wrote:
> On 2019-08-24 17:08, Konstantin Belousov wrote:
> >
> > Use gdb instead.
>
> Ah, thanks.
>
> (gdb) info line *0x8117f67c
> Line 405 of "/usr/src/sys/amd64/amd64/mp_machdep.c" starts at address
> 0x8117f674 and ends a
On 2019-08-24 17:08, Konstantin Belousov wrote:
>
> Do you happen to have NUMA node without any local memory ? (Look at the
> SRAT table). If yes, try this patch.
I've just remembered, that's one of the big differences between
ThreadRipper and EPYC: the EPYC has memory links on all four dies, whi
On 2019-08-24 17:08, Konstantin Belousov wrote:
>
> Use gdb instead.
Ah, thanks.
(gdb) info line *0x8117f67c
Line 405 of "/usr/src/sys/amd64/amd64/mp_machdep.c" starts at address
0x8117f674 and ends at
0x8117f69a
> What was the previous bootable version of the kernel ?
On Sat, Aug 24, 2019 at 04:54:26PM -0600, Rebecca Cran wrote:
> On 2019-08-24 14:33, Konstantin Belousov wrote:
> > On Sat, Aug 24, 2019 at 02:22:18PM -0600, Rebecca Cran wrote:
> >> instruction pointer = 0x20: 0x811bc664
> > So what is the source line for this address ?
>
>
> I built a n
On 2019-08-24 14:33, Konstantin Belousov wrote:
> On Sat, Aug 24, 2019 at 02:22:18PM -0600, Rebecca Cran wrote:
>> instruction pointer = 0x20: 0x811bc664
> So what is the source line for this address ?
I built a new kernel and got a new panic instruction pointer address of
0x8117f
On Sat, Aug 24, 2019 at 02:22:18PM -0600, Rebecca Cran wrote:
> I updated my kernel to r351461 today and now get a panic on boot.
>
>
> CPU: AMD Ryzen Threadripper 2990WX 32-Core Processor (2994.45-MHz
> K8-class CPU)
> Origin="AuthenticAMD" Id=0x800f82 Family=0x17 Model=0x8 Stepping=2
>
I updated my kernel to r351461 today and now get a panic on boot.
CPU: AMD Ryzen Threadripper 2990WX 32-Core Processor (2994.45-MHz
K8-class CPU)
Origin="AuthenticAMD" Id=0x800f82 Family=0x17 Model=0x8 Stepping=2
Features=0x178bfbff
Features2=0x7ed8320b
AMD Features=0x2e500800
AMD
F
13 matches
Mail list logo
