[hch <at> infradead.org: Re: ANNOUNCE: megaraid driver version 2.10.1]
'hch <at> infradead.org' <hch <at> infradead.org>
2004-02-01 15:49:00 GMT
sorry, forgot to Cc the list when replying.
----- Forwarded message from "'hch <at> infradead.org'" <hch <at> infradead.org> -----
Date: Sun, 1 Feb 2004 15:46:11 +0000
From: "'hch <at> infradead.org'" <hch <at> infradead.org>
Subject: Re: ANNOUNCE: megaraid driver version 2.10.1
To: "Mukker, Atul" <Atulm <at> lsil.com>
On Fri, Jan 30, 2004 at 10:03:00AM -0500, Mukker, Atul wrote:
> Hello Christoph,
> I am in process of testing the next version of the megaraid driver. I faced
> an issue while doing the insmod-rmmod sequence. Your patch for PCI hotplug
> does "pci_disable_device" when the driver is unloaded.
> The insmod-rmmod-insmod fails the first time unless you do an explicit
> pci_set_master at driver load time, since pci_enable_device does not seem to
> enable bus mastering, which is disabled by pci_disable_device.
Right, we need the pci_set_master anyway because it's not guaranteed to be
enabled even when loading the first time. (although it usually is on PC
hardware). I'll send a patch to jejb to fix it ASAP, but you should add it
to the 2.4 driver aswell.
> Even with pci_set_master, insmod stalls the CPU after about 2-3 hours of
> insmod-rmmod sequence. So I took out the pci_disable_device altogether to
> find out it takes only longer, about 9 hours, but CPU stalls at the exact