From owner-freebsd-current@freebsd.org Fri Jul 10 15:23:16 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5309236C15F for ; Fri, 10 Jul 2020 15:23:16 +0000 (UTC) (envelope-from tsoome@me.com) Received: from st43p00im-ztbu10073601.me.com (st43p00im-ztbu10073601.me.com [17.58.63.184]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4B3GyW2gmNz4kNf for ; Fri, 10 Jul 2020 15:23:14 +0000 (UTC) (envelope-from tsoome@me.com) Received: from nazgul.lan (148-52-235-80.sta.estpak.ee [80.235.52.148]) by st43p00im-ztbu10073601.me.com (Postfix) with ESMTPSA id 60EA5820177; Fri, 10 Jul 2020 15:23:13 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) Subject: Re: Geli encryption issue on r362779 From: Toomas Soome In-Reply-To: <0100017339421ff8-fbe5f6ae-efe6-4308-8639-8a194ce24599-000000@email.amazonses.com> Date: Fri, 10 Jul 2020 18:23:11 +0300 Cc: freebsd-current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <01000173051a6c1b-ceec77e5-6fee-4969-ada0-70ad8789e1dd-000000@email.amazonses.com> <0100017305bed46f-20efa601-2169-491f-bc95-a4fd8cffafa3-000000@email.amazonses.com> <9ACB03CF-2168-4CCE-B1DC-6D76E33DE9C8@me.com> <01000173063d9d8d-f46774e6-d490-43cc-925d-e729c82904fa-000000@email.amazonses.com> <72383E6F-668A-47B5-AD2C-9F8E436BD995@me.com> <010001732a1273f6-b5d1c86c-a1de-4589-bee5-08d13ae603a6-000000@email.amazonses.com> <0100017338902ab8-976b4288-f267-420b-8663-be56cceb84b7-000000@email.amazonses.com> <0100017339421ff8-fbe5f6ae-efe6-4308-8639-8a194ce24599-000000@email.amazonses.com> To: lausts@acm.org X-Mailer: Apple Mail (2.3608.80.23.2.2) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.235, 18.0.687 definitions=2020-07-10_10:2020-07-10, 2020-07-10 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-2004280000 definitions=main-2007100105 X-Rspamd-Queue-Id: 4B3GyW2gmNz4kNf X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.22 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; FREEMAIL_FROM(0.00)[me.com]; MV_CASE(0.50)[]; TO_DN_NONE(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:17.58.0.0/16]; DKIM_TRACE(0.00)[me.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[me.com,quarantine]; NEURAL_HAM_SHORT(-0.57)[-0.574]; RECEIVED_SPAMHAUS_PBL(0.00)[80.235.52.148:received]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[me.com]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:714, ipnet:17.58.63.0/24, country:US]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.01)[-1.010]; R_DKIM_ALLOW(-0.20)[me.com:s=1a1hai]; RCVD_IN_DNSWL_LOW(-0.10)[17.58.63.184:from]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.03)[-1.033]; MIME_GOOD(-0.10)[text/plain]; DWL_DNSWL_LOW(-1.00)[me.com:dkim]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[17.58.63.184:from]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.33 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: Fri, 10 Jul 2020 15:23:16 -0000 > On 10. Jul 2020, at 18:05, Thomas Laus wrote: >=20 >> On 2020-07-10 03:56, Toomas Soome wrote: >>>=20 >>> ok, then next one is r363042. By nature it is an safeguard against = read >>> past disk end. >>>=20 >>> If that does not do, we really need to insert checkpoints in code = and >>> see where exactly this reset will happen. Also note I >>> have https://reviews.freebsd.org/D25605 waiting in the queue. >>>=20 >> I updated to r363042 and should complete building in a few hours. = I'll >> post the results when complete. >>=20 > I updated my source to r363042 and the results on my laptop were a > little worse. I tried to boot 5 times and none were successful. All = of > them killed the kernel and 4 left a stack trace. I took a photograph = of > the stack trace, if it is any help. If you need the stack trace, let = me > know where to post. I don't think that this mailing list allows > attachments. >=20 > This is the same laptop that you helped me with a 'Geli Taste' issue a > few months ago. That problem never went completely away but was > tolerable. It only happens about once every 2 weeks instead of daily > and always boots on the second attempt. >=20 > Tom >=20 You can mail it directly, thats no problem. But if you get kernel killed = and stack trace=E2=80=A6 stack trace from kernel? So it does mean you do = get loader running and kernel loaded? could you get to loader prompt and = get output of command: smap ? thanks, toomas=