From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756908AbYEDNH2 (ORCPT ); Sun, 4 May 2008 09:07:28 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751441AbYEDNHU (ORCPT ); Sun, 4 May 2008 09:07:20 -0400 Received: from fg-out-1718.google.com ([72.14.220.152]:49416 "EHLO fg-out-1718.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751087AbYEDNHS (ORCPT ); Sun, 4 May 2008 09:07:18 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=nAIAHXieVCuEzE5vbgvuBoyCQ+0CgyAjm3nAFNq6L9phWF/u1Chyq86sX2YYRlLDNOJiUJEhBnDa+sck5WQhA3w3J2bRryAwAvF3S20IG2x/qoJVzZ6MKBCS1rV3CsqnAlgGW6VCrVkJGtz363XyMGPmfmiCyOw0OkMOwBqAwNQ= Message-ID: <481DB3F3.5080102@gmail.com> Date: Sun, 04 May 2008 15:02:43 +0200 From: Jacek Luczak User-Agent: Thunderbird 2.0.0.9 (X11/20071031) MIME-Version: 1.0 To: Prakash Punnoor CC: Linux Kernel list , Jens Axboe , neilb@suse.de Subject: Re: WARNING in 2.6.25-07422-gb66e1f1 References: <200805031151.44287.prakash@punnoor.de> In-Reply-To: <200805031151.44287.prakash@punnoor.de> Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, I've CC:-ed few guys which may help. Prakash Punnoor pisze: > Hi, I got this on boot: > > usb 2-1.3: new full speed USB device using ehci_hcd and address 3 > usb 2-1.3: configuration #1 chosen from 1 choice > Clocksource tsc unstable (delta = -117343945 ns) > ------------[ cut here ]------------ > WARNING: at include/linux/blkdev.h:443 blk_remove_plug+0x7d/0x90() > Modules linked in: kvm_amd kvm powernow_k8 ehci_hcd ohci_hcd usbcore forcedeth > Pid: 1681, comm: fsck.ext3 Not tainted 2.6.25-07422-gb66e1f1-dirty #74 > > Call Trace: > [] warn_on_slowpath+0x64/0xa0 > [] generic_make_request+0x194/0x250 > [] submit_bio+0x97/0x140 > [] blk_remove_plug+0x7d/0x90 > [] raid5_unplug_device+0x44/0x110 > [] sync_page+0x2e/0x50 > [] __wait_on_bit+0x65/0x90 > [] wait_on_page_bit+0x78/0x80 > [] wake_bit_function+0x0/0x40 > [] pagevec_lookup_tag+0x1a/0x30 > [] wait_on_page_writeback_range+0xbd/0x130 > [] do_writepages+0x20/0x40 > [] __filemap_fdatawrite_range+0x52/0x60 > [] filemap_write_and_wait+0x44/0x50 > [] __blkdev_put+0x148/0x1b0 > [] __fput+0xb1/0x1c0 > [] filp_close+0x48/0x80 > [] sys_close+0x9f/0x110 > [] system_call_after_swapgs+0x7b/0x80 > > ---[ end trace 94c0787a2e4d19eb ]--- > EXT3 FS on md1, internal journal > kjournald starting. Commit interval 5 seconds > EXT3 FS on md2, internal journal > EXT3-fs: mounted filesystem with writeback data mode. > kjournald starting. Commit interval 5 seconds > EXT3 FS on md3, internal journal > EXT3-fs: mounted filesystem with writeback data mode. > eth0: no link during initialization. > r8169: eth1: link up > r8169: eth1: link up > NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory > NFSD: starting 90-second grace period Is this problem reproducible? Trace is printed by last change from Jens on Apr-29 (commit: 7663c1e2792a9662b23dec6e19bfcd3d55360b8f, Improve queue_is_locked()), but it looks like raid5_unplug_device() is called during EXT3 check on md0 [why?]. -Jacek