From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Thu, 16 Jun 2016 19:16:05 +0200 From: Gilles Chanteperdrix Message-ID: <20160616171605.GD32532@hermes.click-hack.org> References: <20160608193911.GA31360@hermes.click-hack.org> <20160609174118.GD1785@hermes.click-hack.org> <575AF2E1.3060401@siemens.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Xenomai] Xenomai/Cobalt on i7-3770S CPU List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Heinick, J Michael" Cc: "xenomai@xenomai.org" On Thu, Jun 16, 2016 at 03:51:17PM +0000, Heinick, J Michael wrote: > problem, the stripped down driver would hang the core2 computer > just like the i7 computer. Are you running a graphic system? If yes, have you tried to plug a serial console or netconsole to try and retrieve the kernel console when the hang happens? Because if the hang is in fact a kernel oops, the oops message may indicate what the problem is. > Eventually, I noticed that only nrt > handlers were specified in the ops structure. After moving our > ioctl functions to .ioctl_rt, both the stripped down driver and > the full driver run on both the core2 and i7 computers. You can not call "sleeping" services from an _nrt handler. If that is what you were doing. > Why the core2 computers appeared to work with only the ioctl_nrt > handler specified in the full driver and hang the i7 computer is > still a mystery to us. Did the two machines run with the same kernel? Or were there differences in the kernel configuration? Like I-pipe checks disabled/enabled? -- Gilles. https://click-hack.org