Date: Fri, 15 Feb 2019 09:52:50 -0800 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Andriy Gapon <avg@freebsd.org> Cc: John Baldwin <jhb@freebsd.org>, freebsd-current@freebsd.org Subject: Re: Panic in sys_fstatat() Message-ID: <20190215175250.GA10070@troutmask.apl.washington.edu> In-Reply-To: <03a9628d-9101-c9c4-fb4a-96bc57308c38@FreeBSD.org> References: <20190214024703.GA51003@troutmask.apl.washington.edu> <786f8034-b3ef-54cb-043b-e189e752b18b@FreeBSD.org> <03a9628d-9101-c9c4-fb4a-96bc57308c38@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Feb 15, 2019 at 09:50:55AM +0200, Andriy Gapon wrote: > > So, I suspect something exotic like some sort of a stack alignment issue, or a > CPU bug, or a mismatch between object files, or some local experiment, etc. > You might be right about something exotic. It is an old laptop, so it could be showing signs of hardware failure. I'm also unfortuntely trying to solve an issue with drm-legacy-kmod. In building several different kernels over a few different revisions of -current, I seem to have jump across the introduction of ifunc into the linkers. I'll see if I can come up with a repeatable method for causing the panic. -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190215175250.GA10070>