linux-kernel - Re: [ANNOUNCE] 3.6.5-rt15

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 15 Nov 2012 18:59:54 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Grant Likely <grant.likely@...retlab.ca>
cc:	LKML <linux-kernel@...r.kernel.org>,
	linux-rt-users <linux-rt-users@...r.kernel.org>
Subject: Re: [ANNOUNCE] 3.6.5-rt15

On Wed, 14 Nov 2012, Grant Likely wrote:
> Hey Thomas,
> 
> I get a kernel bug when going from rt14 to rt15. It appears that
> preempt_lazy on my ARM platform causes (or exposes) the following
> backtrace on boot. I'm basing this on the only relevant change between
> rt14 and rt15 is the typo fix that enables PREEMPT_LAZY. I also see
> the problem on -rt16 and -rt17.
> 
> (full boot log also attached below)
> 
> The actual backtrace changes every time, but it is always related to
> an rt_spin_lock() call.
> 
> This is on a TI AM3894 platform which is equivalent to a TI8160
> without the DSP. The board support isn't mainlined, but there is
> nothing particularly exotic about the changes. It is primarily device
> drivers and device driver data. Cortex-A8 platform.
> 
> Any thoughts on how to debug this?

Probably by staring at the patch to the ASM code in arch/arm. I bet I
messed that up somehow :)

Thanks,

	tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/