From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261215AbVFDKbR (ORCPT ); Sat, 4 Jun 2005 06:31:17 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261311AbVFDKbR (ORCPT ); Sat, 4 Jun 2005 06:31:17 -0400 Received: from e35.co.us.ibm.com ([32.97.110.133]:62699 "EHLO e35.co.us.ibm.com") by vger.kernel.org with ESMTP id S261215AbVFDKbM (ORCPT ); Sat, 4 Jun 2005 06:31:12 -0400 Message-ID: <1117881061.42a182e535f40@imap.linux.ibm.com> Date: Sat, 4 Jun 2005 06:31:01 -0400 From: Maneesh Soni To: Greg KH Cc: Vivek Goyal , Morton Andrew Morton , Alan Stern , Fastboot mailing list , linux kernel mailing list , "Eric W. Biederman" Subject: Re: [Fastboot] Re: [RFC/PATCH] Kdump: Disabling PCI interrupts in capture kernel MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT User-Agent: Internet Messaging Program (IMP) 3.2.7 X-Originating-IP: 9.182.63.132 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Quoting Greg KH : > On Fri, Jun 03, 2005 at 04:55:24PM +0530, Vivek Goyal wrote: > > Hi, > > > > In kdump, sometimes, general driver initialization issues seems to be > cropping > > in second kernel due to devices not being shutdown during crash and these > > > devices are sending interrupts while second kernel is booting and drivers > are > > not expecting any interrupts yet. > > What are the errors you are seeing? > How would the drivers be able to be getting interrupts delivered to them > if they haven't registered the irq handler yet? Probably the boot log with error messages could have been inlined instead of putting as attachement. This is from attachement in Vievk's post irq 11: nobody cared (try booting with the "irqpoll" option. [] __report_bad_irq+0x2a/0x8d [] handle_IRQ_event+0x39/0x6d [] note_interrupt+0x7f/0xe4 [] __do_IRQ+0x169/0x194 [] do_IRQ+0x1b/0x28 [] common_interrupt+0x1a/0x20 [] __do_softirq+0x2b/0x88 [] do_softirq+0x26/0x2a [] irq_exit+0x33/0x35 [] do_IRQ+0x20/0x28 [] common_interrupt+0x1a/0x20 [] release_console_sem+0x43/0xf6 [] vprintk+0x16c/0x277 [] d_lookup+0x23/0x46 [] d_alloc+0x136/0x1a6 [] printk+0x17/0x1b [] hub_probe+0xa0/0x168 [] sysfs_new_dirent+0x1f/0x64 [] usb_probe_interface+0x59/0x71 [] driver_probe_device+0x2f/0xa7 [] __device_attach+0x0/0x5 [] bus_for_each_drv+0x58/0x78 [] device_attach+0x60/0x64 [] __device_attach+0x0/0x5 [] bus_add_device+0x29/0xa6 [] device_pm_add+0x56/0x9c [] device_add+0xc5/0x14a [] usb_set_configuration+0x346/0x528 [] usb_new_device+0xab/0x1be [] ohci_iso_recv_set_channel_mask+0x3/0xc6 [] register_root_hub+0xaf/0x162 [] usb_add_hcd+0x172/0x396 [] usb_hcd_pci_probe+0x26e/0x375 [] __call_usermodehelper+0x0/0x61 [] pci_device_probe_static+0x40/0x54 [] __pci_device_probe+0x2f/0x42 [] pci_device_probe+0x29/0x47 [] driver_probe_device+0x2f/0xa7 [] __driver_attach+0x0/0x43 [] __driver_attach+0x41/0x43 [] bus_for_each_dev+0x5a/0x7a [] driver_attach+0x26/0x2a [] __driver_attach+0x0/0x43 [] bus_add_driver+0x6b/0xa5 [] pci_register_driver+0x5e/0x7c [] init+0x1d/0x25 [] do_initcalls+0x54/0xb6 [] init+0x0/0x10c [] init+0x0/0x10c [] init+0x2a/0x10c [] kernel_thread_helper+0x0/0xb [] kernel_thread_helper+0x5/0xb handlers: [] (ahd_linux_isr+0x0/0x284) Disabling IRQ #11 Thanks Maneesh -- Maneesh Soni IBM Linux Technology Center IBM India Software Labs, Bangalore, India Ph. 91-80-25044990 email: maneesh@in.ibm.com