From owner-freebsd-current@FreeBSD.ORG Fri Oct 22 15:13:17 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BDBF616A4CE; Fri, 22 Oct 2004 15:13:17 +0000 (GMT) Received: from mail.vtec.ipme.de (Ad3de.a.pppool.de [213.6.211.222]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3090543D49; Fri, 22 Oct 2004 15:13:15 +0000 (GMT) (envelope-from volker@vwsoft.com) Received: from [192.168.16.24] (unknown [192.168.16.24]) by bellona.sz.vwsoft.com (Postfix) with ESMTP id 2B5E45CCF; Fri, 22 Oct 2004 16:40:30 +0200 (CEST) Message-ID: <41791BDD.8030702@vwsoft.com> Date: Fri, 22 Oct 2004 16:40:29 +0200 From: Volker User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040822 Thunderbird/0.7+ Mnenhy/0.6.0.101 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Scott Long X-Enigmail-Version: 0.85.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: current@FreeBSD.org Subject: Re: 5.3-RELEASE TODO X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Oct 2004 15:13:18 -0000 Scott, > |--------------------+---------------+--------------+--------------------| > | | | | There have been | > | | | | reports of system | > | | | | hangs while using | > | | | | ISDN with the i4b | > | | | | ISDN framework on | > | | | | SMP systems. These | > | | | | likely result from | > | | | | insufficient | > | | | | synchronization in | > | | | | the i4b | > | | | | implementation | > | | | | when runnning | > | | | | without the Giant | > | | | | lock over the | > | Reports of hangs | | Robert | network stack. The | > | using i4b | Needs testing | Watson | workaround until | > | (isdn4bsd) | | | this is fixed is | > | | | | to re-assert the | > | | | | Giant lock over | > | | | | the stack when i4b | > | | | | is compiled into | > | | | | the kernel; this | > | | | | has been committed | > | | | | to 6.x and and | > | | | | 5.x. The Release | > | | | | Engineering team | > | | | | awaits word that | > | | | | this corrects the | > | | | | problems | > | | | | experienced by the | > | | | | submitter. | > |--------------------+---------------+--------------+--------------------| I've been the initial reporter for this problem. As I've posted here a few days ago, from my point you my change the state of this issue to 'done' as i4b now works fine again for me. (One exception: I've had some line disconnects over the last few days, but I don't think it's an i4b or mpsafe/Giant problem.) I've not seen any other guy here on the list having trouble with i4b under 5.3 so I guess nobody will shout for the state change to 'done'. Thanks, Volker -- GPG/PGP fingerprint: FF93 13A1 2477 B631 E953 06DF 4C49 ADD9 E4BF 79B1