From owner-freebsd-stable@freebsd.org Fri Jun 28 12:36:19 2019 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 983FD15C0037 for ; Fri, 28 Jun 2019 12:36:19 +0000 (UTC) (envelope-from matthias.schuendehuette@siemens.com) Received: from thoth.sbs.de (thoth.sbs.de [192.35.17.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "thoth.sbs.de", Issuer "Siemens Issuing CA Internet Server 2017" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0B26270406 for ; Fri, 28 Jun 2019 12:36:18 +0000 (UTC) (envelope-from matthias.schuendehuette@siemens.com) Received: from mail1.sbs.de (mail1.sbs.de [192.129.41.35]) by thoth.sbs.de (8.15.2/8.15.2) with ESMTPS id x5SCUj2X022369 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 28 Jun 2019 14:30:45 +0200 Received: from DEFTHW99ERLMSX.ww902.siemens.net (defthw99erlmsx.ww902.siemens.net [139.22.70.136]) by mail1.sbs.de (8.15.2/8.15.2) with ESMTPS id x5SCUjs8016776 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 28 Jun 2019 14:30:45 +0200 Received: from DEFTHW99ERPMSX.ww902.siemens.net (139.22.70.202) by DEFTHW99ERLMSX.ww902.siemens.net (139.22.70.136) with Microsoft SMTP Server (TLS) id 14.3.439.0; Fri, 28 Jun 2019 14:30:45 +0200 Received: from DENBGAT9EJ1MSX.ww902.siemens.net ([169.254.8.232]) by DEFTHW99ERPMSX.ww902.siemens.net ([139.22.70.202]) with mapi id 14.03.0439.000; Fri, 28 Jun 2019 14:30:44 +0200 From: "Schuendehuette, Matthias" To: Konstantin Belousov CC: "freebsd-stable@freebsd.org" Subject: AW: GENERIC crash 11.3-PRERELEASE (i386) Thread-Topic: GENERIC crash 11.3-PRERELEASE (i386) Thread-Index: AdUst2TAcuMJGe/CTYqBxBJA9XykUAAUlpEAACifdZA= Date: Fri, 28 Jun 2019 12:30:42 +0000 Message-ID: <1EFE239F82F279488E86A61C92D5E2DE0A082A8F@DENBGAT9EJ1MSX.ww902.siemens.net> References: <1EFE239F82F279488E86A61C92D5E2DE0A082864@DENBGAT9EJ1MSX.ww902.siemens.net> <20190627185956.GP8697@kib.kiev.ua> In-Reply-To: <20190627185956.GP8697@kib.kiev.ua> Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [139.22.70.43] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Rspamd-Queue-Id: 0B26270406 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.98 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[]; NEURAL_HAM_SHORT(-0.98)[-0.979,0] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jun 2019 12:36:19 -0000 Hi Konstantin, thanks for your reply. I'm in doubt if there is a hardware defect. If that would be the case, why should the slightly older kernel work? This (admittedly old) server is running fine with a kernel "r347014" of Jun= e 5th, 2019. The crashing kernel has "r349405", so quite some things have happened in be= tween. Thanks for the hint with "DDB", I'll try that next week. As well as narrowing down the first "crashing-releasenumber". Have a nice weekend :-) with best regards Matthias Sch=FCndeh=FCtte -----Urspr=FCngliche Nachricht----- Von: Konstantin Belousov =20 Gesendet: Donnerstag, 27. Juni 2019 21:00 An: Schuendehuette, Matthias (LDA IT PLM) Cc: 'freebsd-stable@freebsd.org' Betreff: Re: GENERIC crash 11.3-PRERELEASE (i386) On Thu, Jun 27, 2019 at 07:11:40AM +0000, Schuendehuette, Matthias wrote: > Hi, >=20 > the missing attachments can be found here now: >=20 > https://www.dropbox.com/sh/buzxekimo2h2r67/AADpUvLndhm2SHa5t9s9Ckksa?dl= =3D0 >=20 So your AP (Application Processor) seems to get fault, most likely in the trap handler. There were absolutely no changes in the stable/11 in the area of SMP startup for quite long time. To get anywhere, you should perhaps add ddb to your kernel configuration and get the backtrace. The backtrace would be long, I am only interested in the first several frames before faults go into recursion. But, since 1 month earlier kernel worked, and there were no changes, this might indicate either a failing hardware (your machine is quite old, it is Core2 Xeon, am I right ?) or problems with your build environment.