Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S266768AbUJAWfK (ORCPT ); Fri, 1 Oct 2004 18:35:10 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S266663AbUJAWe5 (ORCPT ); Fri, 1 Oct 2004 18:34:57 -0400 Received: from atlrel8.hp.com ([156.153.255.206]:38623 "EHLO atlrel8.hp.com") by vger.kernel.org with ESMTP id S266768AbUJAWd0 (ORCPT ); Fri, 1 Oct 2004 18:33:26 -0400 From: Bjorn Helgaas To: Fernando Pablo Lopez-Lezcano Subject: Re: 2.6.9rc2-mm4 oops Date: Fri, 1 Oct 2004 16:33:10 -0600 User-Agent: KMail/1.7 Cc: Andrew Morton , linux-kernel@vger.kernel.org, mingo@elte.hu, Len Brown , acpi-devel@lists.sourceforge.net, Bernhard Rosenkraenzer References: <1096571653.11298.163.camel@cmn37.stanford.edu> <200410010904.52892.bjorn.helgaas@hp.com> <1096653158.7485.17.camel@cmn37.stanford.edu> In-Reply-To: <1096653158.7485.17.camel@cmn37.stanford.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200410011633.10171.bjorn.helgaas@hp.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1521 Lines: 35 On Friday 01 October 2004 11:52 am, Fernando Pablo Lopez-Lezcano wrote: > On Fri, 2004-10-01 at 08:04, Bjorn Helgaas wrote: > > Also, can you look up the bad address > > (e.g., f8881920) in /proc/kallsyms? > > This is what I find: > f8880f80 ? __mod_vermagic5 [xor] > f8880fcd ? __module_depends [xor] > f8881000 t acpi_button_init [button] > f8881000 t init_module [button] > f8884000 t xor_pII_mmx_2 [xor] > f8884130 t xor_pII_mmx_3 [xor] You are remembering that /proc/kallsyms isn't sorted, right? If you still can't match the address to anything interesting, can you see whether it's related to any of the other modules (i.e., see whether it happens even if you don't load any of the other ACPI drivers, or try leaving out any other drivers you can get along without)? Maybe try loading an ACPI driver other than floppy, at the same point in the module load sequence, to see if the problem is specific to floppy, or if floppy is just an innocent bystander? I looked at all the callers of acpi_bus_register_driver(), and they all look fine (except the hpet one I found yesterday). But maybe there's something I missed, or maybe the acpi_bus_drivers list got corrupted somehow. If you don't load the floppy driver, is the system stable? - 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/