On Fri, Sep 14, 2018 at 07:44:45PM +0200, Mark Kettenis wrote: > > Date: Fri, 14 Sep 2018 10:05:34 -0700 > > From: Mike Larkin <[email protected]> > > > > On Thu, Sep 13, 2018 at 11:17:15AM +0200, Hrvoje Popovski wrote: > > > Hi all, > > > > > > i'm having Fujitsu PRIMERGY RX2530 M4 server with Intel Gold 6134 cpu > > > with 8/16 cores. > > > When booting box up to 14 cores everything seems fine, but with 16 cores > > > i'm getting panic. In attachment you can find sendbug. Dmesg in sendbug > > > is with 14 cores. > > > > > > 8 cores (HT disabled) are more than enough for me but maybe this panic > > > is interesting to developers so i report it ... > > > > > > > > > root on sd0a (fa90dc9ea66a7e54.a) swap on sd0b dump on sd0b > > > panipanic: l anel pu > > > gnStopped at db_enter+0x12: popq %r11 > > > TID PID UID PRFLAGS PFLAGS CPU COMMAND > > > 380736 12442 0 0x14000 0x200 5 zerothread > > > 196414 98064 0 0x14000 0x200 7 aiodoned > > > db_enter() at db_enter+0x12 > > > panic() at panic+0x120 > > > acpicpu_idle() at acpicpu_idle+0x2e8 > > > sched_idle(0) at sched_idle+0x245 > > > end trace frame: 0x0, count: 11 > > > https://www.openbsd.org/ddb.html describes the minimum info required in > > > bug reports. Insufficient info makes it difficult to find and fix bugs. > > > > > > > > > ddb{3}> trace > > > db_enter() at db_enter+0x12 > > > panic() at panic+0x120 > > > acpicpu_idle() at acpicpu_idle+0x2e8 > > > > There are only 3 panics in acpicpu_idle. One at the very top: > > panic ("null acpicpu"); > > > > and two much further down: > > panic ("idle with interrupts blocked"); > > > > Based on the fact that it's called at acpicpu_idle+0x2e8, I'm > > inclined to believe it to be the lattter, but the garbled > > panic string seems to more closely match the former. > > > > Can you put a plain printf before each panic and try to repro, > > to see which it is? Just printf the same panic string. > > Mike, look below: > > > > ddb{3}> show panic > > > null acpicpu > > > ddb{3}> > > So it's the first one. > > Hvorje, can you boot this machine with 16 cores but acpicpu(4) > disabled and send us the acpidump output from /var/db/acpi?
Ah, oops. Missed that. Based on later replies, I think you nailed it with _MAT. -ml
