[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: port-amd64/54489: panic: assertion "rcr4() & CR4_SMAP" failed on HP DL380 Gen10
The following reply was made to PR port-amd64/54489; it has been noted by GNATS.
From: Takahiro Kambe <taca%back-street.net@localhost>
Subject: Re: port-amd64/54489: panic: assertion "rcr4() & CR4_SMAP" failed
on HP DL380 Gen10
Date: Thu, 13 Aug 2020 00:03:14 +0900 (JST)
In message <20190826151500.50B6F7A1DC%mollari.NetBSD.org@localhost>
on Mon, 26 Aug 2019 15:15:00 +0000 (UTC),
>>Synopsis: panic: assertion "rcr4() & CR4_SMAP" failed on HP DL380 Gen10
>>Arrival-Date: Mon Aug 26 15:15:00 +0000 2019
>>Originator: Tobias Nygren
I met the same problem with a machine at my office.
HPE Proliant MicroServer Gen10 Plus
Release 9.99.70 and I have several photo of screen.
> Tried to boot a -current GENERIC kernel on a dual socket HP DL380 Gen10.
> It failed with assertion "rcr4() & CR4_SMAP" at arch/x86/x86/patch.c line 299 during multiprocessor hatch.
The same failure.
> The machine has:
> Slot 0: 16 core "Intel(R) Xeon(R) Gold 6130 CPU 2 2.10GHz"
> Slot 1: 16 core "Intel(R) Xeon(R) Gold 6130 CPU 2 2.10GHz"
> Memory: 384 GB RAM.
Intel(R) Xeon (R) E-23224 CPU @ 3.40GHz
> I tried to #if 0 the SMAP code but then the kernel asserted later with "ci->ci_tlbstate != TLBSTATE_VALID" in x86/pmap.c line 2792.
I've confirmed the same situation.
> State-Changed-From-To: open->feedback
> State-Changed-By: maxv%NetBSD.org@localhost
> State-Changed-When: Tue, 29 Oct 2019 10:20:06 +0000
> On which CPU does the SMAP KASSERT fire?
"cpu0" in my case.
Takahiro Kambe <taca%back-street.net@localhost>
Main Index |
Thread Index |