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 June 5th, 2019. The crashing kernel has "r349405", so quite some things have happened in between. 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ündehütte -----Ursprüngliche Nachricht----- Von: Konstantin Belousov <kostik...@gmail.com> Gesendet: Donnerstag, 27. Juni 2019 21:00 An: Schuendehuette, Matthias (LDA IT PLM) <matthias.schuendehue...@siemens.com> Cc: 'freebsd-stable@freebsd.org' <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, > > the missing attachments can be found here now: > > https://www.dropbox.com/sh/buzxekimo2h2r67/AADpUvLndhm2SHa5t9s9Ckksa?dl=0 > 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. _______________________________________________ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
