From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964864AbVKGS2g (ORCPT ); Mon, 7 Nov 2005 13:28:36 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S964893AbVKGS2f (ORCPT ); Mon, 7 Nov 2005 13:28:35 -0500 Received: from mail.kroah.org ([69.55.234.183]:44937 "EHLO perch.kroah.org") by vger.kernel.org with ESMTP id S964864AbVKGS2X (ORCPT ); Mon, 7 Nov 2005 13:28:23 -0500 Date: Mon, 7 Nov 2005 10:22:06 -0800 From: Greg KH To: Frank Overton Cc: linux-kernel@vger.kernel.org Subject: Re: 2.6 series kernels panic on boot at PCI probe with 450nx Message-ID: <20051107182206.GB18861@kroah.com> References: <436BF7BB.9070900@discoverycenters.org> <20051105043056.GA25501@kroah.com> <1131384430.26641.31.camel@coco.overtonshome.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1131384430.26641.31.camel@coco.overtonshome.net> User-Agent: Mutt/1.5.11 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Nov 07, 2005 at 09:27:11AM -0800, Frank Overton wrote: > Greg, > > I don't know any good way to save the oops message. I'd love a pointer > on that. Serial console perhaps? There is documentation on how to do that in the Documentation/ directory. > Here is a hand copy of the oops message I am seeing. > > -- top of screen -- > c316d000 c3126240 00000000 00000000 c01de368 00000000 c31262b8 > c3126240 > > Call Trace: > [] class_device_create_file+0x11/0x16 > [] pci_alloc_child_bus+0x74/0xb8 > [] pci_scan_bridge+0x90/0x1cd > [] pci_scan_child_bus+0x51/0x77 > [] pci_scan_bus_parented+0x11d/0x133 > [] pci_bios_scan_root+0x3d/0x40 > [] acpi_pci_root_add+0x19a/0x1f0 > [] acpi_bus_driver_init+0x2c/0x8c > [] acpi_bus_find_driver+0x110/0x21a > [] acpi_bus_add+0x12c/0x152 > [] acpi_bus_scan+0x104/0x156 > [] acpi_bus_scan_init+0x48/0x5e > [] do_initcalls+0x49/0x8e > [] init+0x0/0x1d8 > [] kernel_thread_helper+0x5/0xb Ugh, I really wish I knew which ddevice acpi was trying to add here. It looks like it is addding 2 pci busses with the same address, which would be very odd. How about creating a bug in bugzilla.kernel.org and assigning it to the ACPI group? They should be able to figure it out :) thanks, greg k-h