[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070621201624.GD22303@elte.hu>
Date: Thu, 21 Jun 2007 22:16:24 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Chuck Ebbert <cebbert@...hat.com>, Jarek Poplawski <jarkao2@...pl>,
Miklos Szeredi <miklos@...redi.hu>, chris@...ee.ca,
linux-kernel@...r.kernel.org, tglx@...utronix.de,
akpm@...ux-foundation.org
Subject: Re: [BUG] long freezes on thinkpad t60
* Linus Torvalds <torvalds@...ux-foundation.org> wrote:
> It's in fact entirely possible that the long freezes have always been
> there, but the NOHZ option meant that we had much longer stretches of
> time without things like timer interrupts to jumble up the timing! So
> maybe the freezes existed before, but with timer interrupts happening
> hundreds of times a second, they weren't noticeable to humans.
the freezes that Miklos was seeing were hardirq contexts blocking in
task_rq_lock() - that is done with interrupts disabled. (Miklos i think
also tried !NOHZ kernels and older kernels, with a similar result.)
plus on the ptrace side, the wait_task_inactive() code had most of its
overhead in the atomic op, so if any timer IRQ hit _that_ core, it was
likely while we were still holding the runqueue lock!
i think the only thing that eventually got Miklos' laptop out of the
wedge were timer irqs hitting the ptrace CPU in exactly those
instructions where it was not holding the runqueue lock. (or perhaps an
asynchronous SMM event delaying it for a long time)
Ingo
-
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