From owner-freebsd-current@freebsd.org Wed Nov 29 11:56:44 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 261A6E512D9 for ; Wed, 29 Nov 2017 11:56:44 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 84A6F71035 for ; Wed, 29 Nov 2017 11:56:42 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from hermann ([78.52.117.12]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MId0S-1eHp7a3Mme-002GH7 for ; Wed, 29 Nov 2017 12:56:34 +0100 Date: Wed, 29 Nov 2017 12:56:33 +0100 From: "Hartmann, O." To: FreeBSD CURRENT Subject: CURRENT: kernel crash r326347: Cannot access memory at address 0x65657246 Message-ID: <20171129125628.42aa4c99@hermann> Organization: walstatt.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:nxVJbmND4PVqdNSblc5C9sO00iJJpvUj+p0HQOwks9dg3P3ST1X NQAuNkILciNiLBNDZa6iWofXUbF9zRdjiHyjC6cCUhfJkyNpPJc3oYh3HxK7HZdU0fOy9qT FNKr/Z8Xg6QCIAsl5/NsrjefToQln/JavDkLNLr88tt7J66EwDTmMBfY3dG0QPENGO3dzOb tcjSGGrFTboh6rOUZYx9A== X-UI-Out-Filterresults: notjunk:1;V01:K0:vudkYri214M=:5I1TTRIACAL3shNNSqkxTP 4c7+H92M27FoxM6KwctVAvTFD+8vddRRS+iCihSiEHXgkmNAvBsUitRGdSQzqdQwTP5T3miyM bELfq/SepqPI1HqeIuBaZOfAlN17Sfkvlh4D+06rx0V6Pv/0MHojpq0Fh7q7r863KbdKFFwau YUz+UBx+9oFwBrTmp41d/IafdzrDl21gOvqcZS+KakS4ZMBgKPUKooA0FFSos9ds3tPArpMx1 8WqSBMsOlfhW5SEM8Drp6i3V8L/YbDQVLFF9l+EPGMpQrY8whTtbwTUx5VIxkX38WPDOeF4Ig iF4mJY1jiDhhGI44UOvxJmzpQ7ZCTOhfMFmjIZq2PGL2QGtMCfg1ym9QBy92ZD7ILCo9ugFgU qCmDMZkS1N+UXufKbuSC4VKCqHROCro5auDP2htl+/+g7EVKboeCDynwlcGZ5ksK85BiANUyE OeDuyX3JgXYmgFMu5CjNfsgSaDAVeXlOtePbSMi2IjQxwQeD/DUd5ThEeiEIrjyZmaIlApbVW ra9DxizNE4hfu9qc+fANRxbtnbNuncA6xhZUAZKANnI538/MQbKJLZIYAc3V/ej4pZvKDzLmu RiIhxYRnn7jG1MXVQZetFr18G3FHoC0sEkqq8nws4fZZ4IQNFGelqJupV+vKdJWn/HWwiGvQ3 YDXxgT86CK1AxScvF4+Jp65l0nmMr71MlgM1IstUAdIwbiRhD4UCC2eB2Qwb+TVj9LK27dwam RtjFKRXn+pSg6jZnWeMD+Mise86BbpbUqJ8+kCeSt23ztndQNqn74g3ybpB0ixLDy89PlN2i7 i3i6b9hZ4TjXEDa86iqH/k0S1bBpWBPxBJXWQJV3RX90/9j1bkbNaUqHpLOwUHKG//YMyCw X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Nov 2017 11:56:44 -0000 Since yesterday's CURRENT update, I face worse and nasty problems on all of our CURRENT systems! Most recent CURRENT, as with r326363, crashes on booting the kernel, in another case the kernel is stuck and freezing after initialising the USB subsystem (the last thing I see on screen, keyboard fully functional, but no ACPI shutdown any more). Another box is now two days in row after subsequent updates of CURRENT multiple times a day crashing on load on ZFS filesystem. The last known half-ways good kernel is 12.0-CURRENT #157 r326347: Wed Nov 29 01:02:47 CET 2017 amd64. When performing buildworld/buildkernel/relaese/package or poudriere on a ZFS filessystem, I can now bring down the system almost in a reproducable way. Last error seen when core is dumped is: /dev/stdin:1: Error in sourced command file: Cannot access memory at address 0x65657246 /dev/stdin:1: Error in sourced command file: Cannot access memory at address 0x65657246 /dev/stdin:1: Error in sourced command file: Cannot access memory at address 0x65657246 /dev/stdin:1: Error in sourced command file: Cannot access memory at address 0x65657246