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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sun, 15 Mar 2009 07:48:03 +0100
From:	Uwe Kleine-König 
To:	Thomas Gleixner <>
Cc:	LKML <>,
	rt-users <>,
	Ingo Molnar <>,
	Steven Rostedt <>,
	Peter Zijlstra <>,
	Carsten Emde <>, Clark Williams <>
Subject: Re: some ARM fixes for 2.6.29-rc7-rt1


On Fri, Mar 13, 2009 at 02:04:58AM +0100, Uwe Kleine-König wrote:
> on top of 2.6.29-rc7-rc1 I did some ARM related fixes that you can find
> at
> 	git:// v2.6.29-rc7-rt1-pu
> The top commit currently isn't pretty as it contains several independant
> fixes.  Some of them are netX specific so you probably don't need them,
> but they shouldn't hurt you either.
> I will update this branch as I continue working in a non-fast-forward
> manner.  I use TopGit to manage this branch, you might want to use it,
> too, if you intend to follow my work.
> My status quo is:
> 	Testing tracer sched_switch: PASSED
> 	Testing tracer function: PASSED
> 	Testing tracer irqsoff: .. no entries found ..FAILED!
> 	Testing tracer preemptoff: .. no entries found ..FAILED!
> 	Testing tracer preemptirqsoff: .. no entries found ..
[removed stack dump]
I still have this problem.  I digged into irqsoff without finding the reason.

Looking at trace_selftest_startup_irqsoff I saw that
trace_buffer_lock_reserve is called thrice successfully.

Steven (or someone else of course), do you can give me a hint?

> Other than that my machine boots and reports from time to time
> 	scheduling while atomic
> and
> 	sleeping function called from invalid context at kernel/rtmutex.c:683
> Both errors probably happen because some spin_locks need to be converted
> to raw_spin_locks.  Will look later.
Up to now I didn't try to do much with my system, but just booting
doesn't yield such BUGs or Warnings anymore.
Best regards

Pengutronix e.K.                              | Uwe Kleine-König            |
Industrial Linux Solutions                    |  |
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists