On Tue, Nov 30, 1999 at 04:04:40PM -0700, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Christopher Masto writes:
> : Hey, we're getting somewhere. It works, in that it stops the panic.
> : I get the "ed0: unloaded" message, and the machine doesn't panic, but
> : there are still some problems. It seems that device_delete_child
> : is failing (I forgot to print the return code, but it is not zero),
> : and reinserting the card results in "ed0 already exists, using
> : next available unit number", and then the dreaded "driver allocation
> : failed" (presumably the resources have not been freed).
> :
> : Putting in a different kind of card ends up with two children, so
> : it seems that the only part of the delete actually happens.
>
> Hmmm... That's something... How do you know that the delete_child is
> failing? An if printing that it failed or conjecture based on the
> insertion results?
I added a check of the return value. It seemed to be returning 12
(ENOMEM), but I'm not sure if that's real or garbage, since I'm having
trouble finding a code path that would return that.
And further data on the CDPD card.. removing it while PPP is still
running just paniced in sioioctl. However, the delete_child didn't
fail for sio, unlike with ed. I'm going to reboot and see if I can
successfully remove and reinsert the card if I make sure nothing has
sio open at the time.
--
Christopher Masto Senior Network Monkey NetMonger Communications
[EMAIL PROTECTED] [EMAIL PROTECTED] http://www.netmonger.net
Free yourself, free your machine, free the daemon -- http://www.freebsd.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
