From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lowell Gilbert Subject: Re: crash on accessing =?iso-8859-1?Q?=2Fproc=2Fxenomai=2Fsched?= =?iso-8859-1?Q?=2F=C2?= References: <44k1infa1k.fsf@be-well.ilk.org> Date: Wed, 30 Jan 2019 14:34:43 -0500 In-Reply-To: (Jan Kiszka's message of "Wed, 30 Jan 2019 10:37:39 +0100") Message-ID: <44va262b3g.fsf@be-well.ilk.org> MIME-Version: 1.0 Content-Type: text/plain List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: xenomai@xenomai.org Jan Kiszka writes: > On 29.01.19 22:06, Lowell Gilbert via Xenomai wrote: >> I was trying to update to 3.0.8, and looking at stat or acct in the >> sched branch of the proc tree gives me an instant kernel crash, usually >> with a null pointer access from a bogus code address, although the >> locations aren't always the same. This is without even having my kernel >> module or application loaded. >> >> The system is a dual-core Cortex-A9. > > Does this patch happen to help? > > https://gitlab.denx.de/Xenomai/xenomai/commit/02500efff060c293a74fa4c914c19b8e1504b9a3 No. I didn't expect it to: I only hook interrupts with rtdm_irq_request() > Otherwise: Is your I-pipe patch from upstream or self-developed. I > suspect the latter as your kernel claims to be LTSI-based. I'm just using the ipipe-core-4.14.71-arm-4.patch, with a couple of very minor changes related to handling ARM errata. I compared the original source tree to the official linux-4.14.71 release, and the differences were minor. I can't seem to reproduce that now, though, so I applied the official patch against the official linux-4.14.71 tree, and still see the same panics. I'm going to try that again to make sure I'm not crazy. Be well.