Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932512AbWLSAmZ (ORCPT ); Mon, 18 Dec 2006 19:42:25 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932513AbWLSAmZ (ORCPT ); Mon, 18 Dec 2006 19:42:25 -0500 Received: from smtp.osdl.org ([65.172.181.25]:36164 "EHLO smtp.osdl.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932512AbWLSAmY (ORCPT ); Mon, 18 Dec 2006 19:42:24 -0500 Date: Mon, 18 Dec 2006 16:42:20 -0800 From: Andrew Morton To: Randy Dunlap Cc: linux-kernel@vger.kernel.org Subject: Re: 2.6.20-rc1-mm1 Message-Id: <20061218164220.5b174bfd.akpm@osdl.org> In-Reply-To: <20061218162902.9820426d.randy.dunlap@oracle.com> References: <20061214225913.3338f677.akpm@osdl.org> <20061218162902.9820426d.randy.dunlap@oracle.com> X-Mailer: Sylpheed version 2.2.7 (GTK+ 2.8.6; 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: 1858 Lines: 44 On Mon, 18 Dec 2006 16:29:02 -0800 Randy Dunlap wrote: > On Thu, 14 Dec 2006 22:59:13 -0800 Andrew Morton wrote: > > Got this on booting up on x86_64 test box. > Didn't happen on next boot. > > > BUG: scheduling while atomic: hald-addon-stor/0x20000000/3300 > > Call Trace: > [] show_trace+0x34/0x47 > [] dump_stack+0x12/0x17 > [] __sched_text_start+0x5d/0x7ba > [] __cond_resched+0x1c/0x44 > [] cond_resched+0x29/0x30 > [] __reacquire_kernel_lock+0x26/0x44 > [] thread_return+0xac/0xea > [] __cond_resched+0x1c/0x44 > [] cond_resched+0x29/0x30 > [] wait_for_completion+0x17/0xd2 > [] blk_execute_rq+0x98/0xb8 > [] scsi_execute+0xd4/0xf1 > [] scsi_execute_req+0xb9/0xde > [] scsi_test_unit_ready+0x39/0x75 > [] sd_media_changed+0x40/0x87 > [] check_disk_change+0x1f/0x76 > [] sd_open+0x80/0x113 > [] do_open+0x9f/0x2a7 > [] blkdev_open+0x2e/0x5d > [] __dentry_open+0xd9/0x1a7 > [] do_filp_open+0x2a/0x38 > [] do_sys_open+0x44/0xc8 > [] system_call+0x7e/0x83 Bit 29 of current->preempt_count got set. I don't think there's any way in which that can happen normally. So probably some hardware or software error reached out and flipped that bit. - 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/