Subject: Re: SCSI aic7xxx driver: Initialization Failure over a kdump reboot
From: Vivek Goyal <vgoyal@in.ibm.com>
To: linux-os@analogic.com
Cc: Lukasz Kosewski <lkosewsk@nit.ca>, Andrew Morton <akpm@osdl.org>,
       Arjan van de Ven <arjan@infradead.org>,
       Linux kernel <linux-kernel@vger.kernel.org>,
       linux scsi <linux-scsi@vger.kernel.org>,
       dipankar sarma <dipankar@in.ibm.com>
In-Reply-To: <Pine.LNX.4.61.0501070945540.12958@chaos.analogic.com>
References: <1105014959.2688.296.camel@2fwv946.in.ibm.com>
	 <1105013524.4468.3.camel@laptopd505.fenrus.org>
	 <20050106195043.4b77c63e.akpm@osdl.org> <41DE15C7.6030102@nit.ca>
	 <41DEA2E8.8030701@nit.ca>
	 <Pine.LNX.4.61.0501070945540.12958@chaos.analogic.com>
Content-Type: text/plain
Organization: 
Message-Id: <1105112690.2688.390.camel@2fwv946.in.ibm.com>
Mime-Version: 1.0
Date: 07 Jan 2005 21:14:50 +0530
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 2450
Lines: 64

On Fri, 2005-01-07 at 20:20, linux-os wrote:
> On Fri, 7 Jan 2005, Lukasz Kosewski wrote:
> 
> > Lukasz Kosewski wrote:
> >> Andrew Morton wrote:
> >> 
> >>>> looks like the following is happening:
> >>>> the controller wants to send an irq (probably from previous life)
> >>>> then suddenly the driver gets loaded
> >>>> * which registers an irq handler
> >>>> * which does pci_enable_device()
> >>>> and .. the irq goes through. the irq handler just is not yet expecting 
> >>>> this irq, so
> >>>> returns "uh dunno not mine"
> >>>> the kernel then decides to disable the irq on the apic level
> >>>> and then the driver DOES need an irq during init
> >>>> ... which never happens.
> >>>> 
> >>> 
> >>> 
> >>> yes, that's exactly what e100 was doing on my laptop last month.  Fixed
> >>> that by arranging for the NIC to be reset before the call to
> >>> pci_set_master().
> >
> > After reading this again when I /wasn't/ semi-comatose, I retract my 
> > statement insofar as it wouldn't help you (but I think it's still rather 
> > necessary) :)
> >
> > The system did exactly what I'm talking about (which it didn't do for me, 
> > possibly because the board/processor didn't support APIC).  I guess my 
> > question to you is:  do you have other devices sharing this interrupt?  In 
> > other words, are you /sure/ that it's the adaptec controller which is setting 
> > the interrupt line high?
> >
> > Luke Kosewski
> > Human Cannonball
> > Net Integration Technologies
> 
> 
> Note that Linux-2.6.10 PCI code will report the __wrong__ IRQ
> unless pci_enable_device() is executed first! Hopefully, there
> may be an additional callable procedure in the future that
> sets up the IRQ routing independent of actually enabling the
> device. In the meantime, enable the device before you believe
> dev->irq.

pci_enable_device() has already executed by the time i check for what
irq line aic7xxx adapter is requesting for. So i hope that irq 9
information is right.

> 
> 
> Cheers,
> Dick Johnson
> Penguin : Linux version 2.6.10 on an i686 machine (5537.79 BogoMips).
>   Notice : All mail here is now cached for review by Dictator Bush.
>                   98.36% of all statistics are fiction.
> 

-
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/