On Tue, Sep 19, 2017 at 6:02 PM, Shuah Khan <[email protected]> wrote: > Hi Greg, > > On 08/20/2017 03:56 AM, tip-bot for Greg Hackmann wrote: >> Commit-ID: a524b1184b8e86141d689fa78ad150fbf2db9b4c >> Gitweb: >> http://git.kernel.org/tip/a524b1184b8e86141d689fa78ad150fbf2db9b4c >> Author: Greg Hackmann <[email protected]> >> AuthorDate: Tue, 25 Jul 2017 14:36:25 -0700 >> Committer: John Stultz <[email protected]> >> CommitDate: Thu, 17 Aug 2017 12:14:54 -0700 >> >> kselftests: timers: set-timer-lat: Tweak reporting when timer fires early >> >> Rather than printing an error inside the alarm signal handler, set a >> flag that we check later. This keeps the test from spamming the console >> every time the alarm fires early. It also fixes the test exiting with >> error code 0 if this was the only test failure. >> >> Cc: Thomas Gleixner <[email protected]> >> Cc: Ingo Molnar <[email protected]> >> Cc: Miroslav Lichvar <[email protected]> >> Cc: Richard Cochran <[email protected]> >> Cc: Prarit Bhargava <[email protected]> >> Cc: Stephen Boyd <[email protected]> >> Cc: Shuah Khan <[email protected]> >> Cc: [email protected] >> Signed-off-by: Greg Hackmann <[email protected]> >> Signed-off-by: John Stultz <[email protected]> > > This commit is making the set-timer-lat hang. I reverted this commit > and there is no hang. Could you please take a look and see if this > commit should be reverted. > > make kselftest as well as make -C tools/testing/selftests/timers run_tests > hang.
Do you have any specific details as to how the test hangs? (ie: Log data, as in where it might be when it hangs? Any details about the machine?) I'm not seeing it so far in my testing. thanks -john
