From owner-freebsd-bugs  Tue Jan 16 11:10:54 2001
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP id A0A9837B69B
	for <freebsd-bugs@hub.freebsd.org>; Tue, 16 Jan 2001 11:10:04 -0800 (PST)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.11.1/8.11.1) id f0GJA4101122;
	Tue, 16 Jan 2001 11:10:04 -0800 (PST)
	(envelope-from gnats)
Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP id 0BF9437B6A5
	for <freebsd-gnats-submit@FreeBSD.org>; Tue, 16 Jan 2001 11:05:19 -0800 (PST)
Received: (from nobody@localhost)
	by freefall.freebsd.org (8.11.1/8.11.1) id f0GJ5IE98885;
	Tue, 16 Jan 2001 11:05:18 -0800 (PST)
	(envelope-from nobody)
Message-Id: <200101161905.f0GJ5IE98885@freefall.freebsd.org>
Date: Tue, 16 Jan 2001 11:05:18 -0800 (PST)
From: larse@isi.edu
To: freebsd-gnats-submit@FreeBSD.org
X-Send-Pr-Version: www-1.0
Subject: misc/24391: cannot kill amd after interface disappears
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         24391
>Category:       misc
>Synopsis:       cannot kill amd after interface disappears
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Jan 16 11:10:04 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     Lars Eggert
>Release:        4.2-RELEASE
>Organization:
USC Information Sciences Institute
>Environment:
FreeBSD hbo.isi.edu 4.2-RELEASE FreeBSD 4.2-RELEASE #0: Mon Jan 15 17:36:41 PST 2001     larse@hbo.isi.edu:/usr/src/sys/compile/KERNEL-1.9  i386

>Description:
Killing amd after a network interface dissappears (e.g., due to
ejected PC card) fails. Kill -9 works (of course) but leaves the
mount map in such a state that amd cannot be restarted.

We found this when changing pccard_ether to automatically kill and
restart network services based on card insertions/ejections. Since amd
can't be killed once the card is out, this scheme can't be made to work.
>How-To-Repeat:
start amd
eject pccard
kill amd
restart amd
>Fix:
Kill amd before ejecting pccard. Requires user interaction.

>Release-Note:
>Audit-Trail:
>Unformatted:


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message