Re: system hangs after "cardctl eject"

David Hinds <[email protected]> Wed, 5 Feb 2003 21:59:09 -0800
Newsgroups gmane.linux.pcmcia.devel
Message-ID <[email protected]>
On Wed, Feb 05, 2003 at 06:03:37PM +0100, Steven Scholz wrote:

> >Is there any chance that some important system service is relying on a
> >running network?
>
> Well, I have one application running that updates the current time on a 
> display via a serial port every second. That hangs.

Ok then; just asking to make sure you don't have an NFS mounted
directory in your path or something lame like that.  No offense
intended, but I get some pretty dumb bug reports.
 
> I have a kernel driver for a status led. That is blinking along until I do 
> "cardctl eject", then it stops and blinks again after pulling out the 
> card...

This sounds like the system is wedged in an interrupt handler.

> >How about if you just do 'ifconfig eth1 down' yourself, rather than
> >doing the 'cardctl eject'?
> Does not help. Still the same.

So you're saying that JUST doing 'ifconfig eth1 down' wedges your
system?

> But I just realized that "shutting down socket 0" is printed twice!?
> Is that some indication?

I don't know what to make of that.  I'll think about it.

-- Dave


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com