From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Williams Subject: Re: WARNING in 2.6.25-07422-gb66e1f1 Date: Thu, 08 May 2008 11:46:19 -0700 Message-ID: <1210272379.9697.3.camel@dwillia2-linux.ch.intel.com> References: <200805031151.44287.prakash@punnoor.de> <18462.46639.578272.994939@notabene.brown> <20080505190159.GA329@kernel.dk> <200805082039.01316.rjw@sisk.pl> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200805082039.01316.rjw@sisk.pl> Sender: linux-raid-owner@vger.kernel.org To: "Rafael J. Wysocki" Cc: Jens Axboe , Neil Brown , Jacek Luczak , Prakash Punnoor , Linux Kernel list , linux-raid@vger.kernel.org List-Id: linux-raid.ids On Thu, 2008-05-08 at 11:39 -0700, Rafael J. Wysocki wrote: > I get a similar warning with RAID1 on one of my test boxes: > > WARNING: at /home/rafael/src/linux-2.6/include/linux/blkdev.h:443 blk_remove_plug+0x85/0xa0() > Modules linked in: raid456 async_xor async_memcpy async_tx xor raid0 ehci_hcd ohci_hcd sd_mod edd raid1 ext3 jbd fan sata_uli pata_ali thermal processor > Pid: 2159, comm: md1_raid1 Not tainted 2.6.26-rc1 #158 > > Call Trace: > [] warn_on_slowpath+0x5f/0x80 > [] ? __lock_acquire+0x748/0x10d0 > [] blk_remove_plug+0x85/0xa0 > [] :raid1:flush_pending_writes+0x44/0xb0 > [] :raid1:raid1d+0x59/0xfe0 > [] ? __lock_acquire+0x748/0x10d0 > [] ? trace_hardirqs_on+0xbf/0x150 > [] md_thread+0x3c/0x110 > [] ? autoremove_wake_function+0x0/0x40 > [] ? md_thread+0x0/0x110 > [] kthread+0x4d/0x80 > [] child_rip+0xa/0x12 > [] ? restore_args+0x0/0x30 > [] ? kthread+0x0/0x80 > [] ? child_rip+0x0/0x12 > > ---[ end trace 05d4e0844c61f45d ]--- > > This is the WARN_ON_ONCE(!queue_is_locked(q)) in queue_flag_clear(), > apparently. Yes, it triggers on all RAID levels. The patch in this message: http://marc.info/?l=linux-raid&m=121001065404056&w=2 > ...fixes the raid 0/1/10/5/6 cases, but I am still trying to isolate an issue (potentially unrelated) with linear arrays. -- Dan