From owner-freebsd-current Fri Dec 3 15: 5:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 3764C14FFC; Fri, 3 Dec 1999 15:05:26 -0800 (PST) (envelope-from hibma@skylink.it) Received: from skylink.it (va-154.skylink.it [194.185.55.154]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id AAA12653; Sat, 4 Dec 1999 00:04:43 +0100 Received: from localhost (localhost [127.0.0.1]) by skylink.it (8.9.3/8.9.3) with ESMTP id XAA54087; Fri, 3 Dec 1999 23:10:34 +0100 (CET) (envelope-from hibma@skylink.it) Date: Fri, 3 Dec 1999 23:10:33 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@henny.jrc.it Reply-To: Nick Hibma To: Mike Smith Cc: Warner Losh , FreeBSD CURRENT Mailing List Subject: Re: your mail In-Reply-To: <199912010952.BAA00549@mass.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Actually, I don't think so. I'm not 100% sure, but I think that you end > up in the interrupt handler for the card that's going away, but with tty > interrupts masked so you can't get back into DDB. If it's a modem card, > then you'll have them masked as well. > > I'm _fairly_ sure that you'll find you're spinning in the card's > interrupt handler. Stick a printf or two in there and see for yourself. I guess you must have been right. The card suspend and resumes fine now (apart from resource allocation, but that is a different issue). It seems that the proper deleting of the driver solved the problem of freezing my machine. Cheers, Nick -- hibma@skylink.it n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message