Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759257AbXKLNcc (ORCPT ); Mon, 12 Nov 2007 08:32:32 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758632AbXKLNcJ (ORCPT ); Mon, 12 Nov 2007 08:32:09 -0500 Received: from mail-xgw2.externet.hu ([212.40.96.184]:51415 "EHLO mail-xgw2.externet.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758357AbXKLNcH (ORCPT ); Mon, 12 Nov 2007 08:32:07 -0500 To: mikulas@artax.karlin.mff.cuni.cz CC: a.p.zijlstra@chello.nl, akpm@linux-foundation.org, linux-kernel@vger.kernel.org, wfg@mail.ustc.edu.cn In-reply-to: (message from Mikulas Patocka on Sun, 11 Nov 2007 19:29:09 +0100 (CET)) Subject: Re: Temporary lockup on loopback block device References: <20071110145444.a6993df1.akpm@linux-foundation.org> <1194735752.5828.1.camel@lappy> Message-Id: From: Miklos Szeredi Date: Mon, 12 Nov 2007 14:32:03 +0100 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 534 Lines: 15 > On 2.6.23 it could happen even without loopback Let's focus on this point, because we already know how the lockup happens _with_ loopback and any other kind of bdi stacking. Can you describe the setup? Or better still, can you reproduce it and post the sysrq-t output? Thanks, Miklos - 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/