Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756910Ab3GDSIv (ORCPT ); Thu, 4 Jul 2013 14:08:51 -0400 Received: from terminus.zytor.com ([198.137.202.10]:53102 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756728Ab3GDSIu (ORCPT ); Thu, 4 Jul 2013 14:08:50 -0400 Message-ID: <51D5BA25.9060207@zytor.com> Date: Thu, 04 Jul 2013 11:08:37 -0700 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7 MIME-Version: 1.0 To: Linus Torvalds CC: Dave Jones , Linux Kernel , Ingo Molnar , Thomas Gleixner Subject: Re: scheduling while atomic & hang. References: <20130704015525.GA8486@redhat.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 671 Lines: 17 On 07/03/2013 07:49 PM, Linus Torvalds wrote: >> [] __schedule+0x94f/0x9c0 >> [] schedule_user+0x2e/0x70 >> [] retint_careful+0x12/0x2e This call trace does indeed indicate that we took a hardware interrupt which caused a reschedule. It doesn't necessarily have to be a quantum expiration interrupt, it could just as easily be an I/O completion interrupt. -hpa -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/