From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Fri, 30 Dec 2005 22:33:38 +0000 Subject: Re: Missing remove event Message-Id: <20051230223338.GA6758@vrfy.org> List-Id: References: <20051229000359.GB15058@hank.org> In-Reply-To: <20051229000359.GB15058@hank.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Fri, Dec 30, 2005 at 02:12:50PM -0800, Bill Moseley wrote: > On Fri, Dec 30, 2005 at 09:52:42PM +0100, Kay Sievers wrote: > > On Fri, Dec 30, 2005 at 12:40:58PM -0800, Bill Moseley wrote: > > > Is there anything else I could provide that might help debug this? > > > > > > Does the udev system get hotplug events differently? That is, would > > > it make any difference if I switch to using udev? > > > > That's very unlikely to change anything. It looks more like a driver > > or bus driver issue. > > By driver do you mean prism54? Yes, that's the first place to ask for already known issues. > I guess not because it looks more like > /sbin/hotplug just isn't being run when the card is pulled out in some > cases. It's the driver, or the bus driver that causes this event. If hotplug doesn't run, it's very likey an issue inside the kernel. > > > > > > > > Then plugging the card back in nothing happens. Manually running > > > > modprobe prism54 goes through much of the same logging, but the > > > > lights never come on on the wireless card: > > > > You may ask the driver maintainer if there is a way to work around this, > > or a known issue. It doesn't look like a hotplug or driver core thing. > > Unfortunately, it's a black box to me. I was assuming that since it > wasn't detecting the card removal that it also wasn't then detecting > the card insertion and that there was something else missing than just > reloading the drivers (such as powering up the slot??). > > Is there something else to watch besides /sbin/hotplug to see if the > kernel is detecting the card removal? Something more low-level I can > check to see what's happening (or not happening) when the card is > ejected? No, not from userspace. As /proc and /sys showed, the device remains in the kernel, even whern it's physically removed. So you very likely need to look _in_ the kernel for the problem. > Sorry for the basic questions. The hardware has worked so well in the > past I haven't had the need to understand how all the parts fit > together. ;) Yeah, no wonder, it's pretty complex and today no single person can understand everything that's going on all over the place on modern operating systems. Kay ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel