Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261410AbTH2QXp (ORCPT ); Fri, 29 Aug 2003 12:23:45 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261415AbTH2QXp (ORCPT ); Fri, 29 Aug 2003 12:23:45 -0400 Received: from fw.osdl.org ([65.172.181.6]:12173 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S261410AbTH2QXg (ORCPT ); Fri, 29 Aug 2003 12:23:36 -0400 Date: Fri, 29 Aug 2003 09:07:27 -0700 From: Andrew Morton To: Jens Axboe Cc: linux-kernel@vger.kernel.org, rl@hellgate.ch, Bartlomiej Zolnierkiewicz Subject: Re: [2.6] kernel BUG at arch/i386/mm/highmem.c:14! Message-Id: <20030829090727.10ea0099.akpm@osdl.org> In-Reply-To: <20030829083556.GB28216@suse.de> References: <20030826173337.GA3993@k3.hellgate.ch> <20030826180146.GF862@suse.de> <20030826190252.GA3642@k3.hellgate.ch> <20030829083556.GB28216@suse.de> X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1579 Lines: 41 Jens Axboe wrote: > > > ---------------------------------------------------------------------------- > > hda: DMA disabled > > bad: scheduling while atomic! > > Call Trace: > > [] schedule+0x510/0x520 > > [] blk_run_queues+0x120/0x300 > > [] find_get_page+0x70/0x140 > > [] io_schedule+0xe/0x20 > > [] __wait_on_buffer+0xcf/0xe0 > > [] autoremove_wake_function+0x0/0x50 > > [] autoremove_wake_function+0x0/0x50 > > [] flush_commit_list+0x31a/0x440 > > [] do_journal_end+0x5fb/0xc00 > > [] flush_old_commits+0x139/0x1d0 > > [] reiserfs_write_super+0x30/0x40 > > [] sync_supers+0x1ef/0x280 > > [] wb_kupdate+0x63/0x160 > > [] schedule+0x1f2/0x520 > > [] __pdflush+0x21c/0x5f0 > > [] pdflush+0x0/0x20 > > [] pdflush+0x11/0x20 > > [] wb_kupdate+0x0/0x160 > > [] kernel_thread_helper+0x5/0xc > > These traces look suspicious. Are you using a standard kernel? What > options? This trace has been reported several times, and it always correlates with an IDE error message of some form. I'm suspecting that something in the IDE error handling path either forgets to undo a spinlock or leaves interrupts disabled. - 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/