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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 6 Oct 2009 11:00:45 +0200
From:	"Mehlan, Markus" <Markus.Mehlan@...ter.info>
To:	"Thomas Gleixner" <tglx@...utronix.de>
CC:	<linux-kernel@...r.kernel.org>
Subject: AW: clock_nanosleep: cyclic POSIX thread freezes during time setting

Hello Thomas,

> -----Ursprüngliche Nachricht-----
> Von: Thomas Gleixner [mailto:tglx@...utronix.de] 
> Gesendet: Montag, 5. Oktober 2009 20:58
> An: Mehlan, Markus
> Cc: linux-kernel@...r.kernel.org
> Betreff: Re: clock_nanosleep: cyclic POSIX thread freezes 
> during time setting
> 
> Markus,
> 
> On Mon, 5 Oct 2009, Mehlan, Markus wrote:
> > I have the following problem on a MPC5200b customer board, 
> tested with 
> > linux-2.6.24.7-rt11 and 2.6.26.8-rt16.
> > 
> > I start the test application. Every 200ms I can see a new 
> line on the 
> > console ("ping"). Then I set the time with "date 
> 100509152009" a few 
> > times on a second console. The effect is that the output on 
> the first 
> > console freezes and if I check the time with "date", the 
> time doesn't 
> > progress during the "freeze time". After the "freeze time" the time 
> > makes a jump of several seconds.
> > 
> > In the real application the "ping" should reset the watchdog-timer. 
> > The freezing causes an elapsing of the watchdog-timer and finally a 
> > reboot.
> > 
> > Has someone an idea?
> 
> Just tested on a MPC5200 board with cyclictest and setting 
> date on a second console. Unfortunately I cannot reproduce 
> that problem. Can you try to activate the function tracer and 
> capture what the system is doing. That might us give some 
> clue about the problem.
> 
> Thanks,
> 
> 	tglx
> 
do you mean kernel function trace (KFT patch) with function trace
or user space "strace"?

Thank you,
Markus

Sitz der Gesellschaft: Oberhausen
Handelsregister Amtsgericht Duisburg HRB-Nr. 17168 UST ID-Nr. DE 814009849
Geschaftsfuehrer: Manfred A. Wagner und Dr. Uwe Baader

--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ