From owner-freebsd-isdn Sun Apr 5 03:36:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA29803 for freebsd-isdn-outgoing; Sun, 5 Apr 1998 03:36:42 -0700 (PDT) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from server.amis.net (server.amis.net [195.10.52.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA29749 for ; Sun, 5 Apr 1998 03:36:36 -0700 (PDT) (envelope-from blaz@gold.amis.net) Received: (from uucp@localhost) by server.amis.net (8.8.8/8.8.8) with UUCP id MAA29016; Sun, 5 Apr 1998 12:36:21 +0200 (CEST) Received: from localhost (blaz@localhost) by gold.amis.net (8.8.8/8.8.8) with SMTP id MAA00622; Sun, 5 Apr 1998 12:36:03 +0200 (CEST) Date: Sun, 5 Apr 1998 12:36:02 +0200 (CEST) From: Blaz Zupan To: Wolfgang Helbig cc: freebsd-isdn@FreeBSD.ORG Subject: Re: i4b-L1-F_ill:What is this? (fwd) In-Reply-To: <199804041035.MAA00661@rvc1.informatik.ba-stuttgart.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Does this trick work w/o I4B_SMP_WORKAROUND? > Please apply this patch: I was running a kernel with the patch and I4B_SMP_WORKAROUND yesterday without any trouble (except for the error messages that I already posted). Today I am running a kernel without I4B_SMP_WORKAROUND and it seems to work just the same, i.e. the workaround has absolutely no effect on the operation of i4b on my machine. So it seems like the patch fixed the problem. Now my questions is, is this patch only a "test" or can it be applied to the i4b source tree in the future, i.e. does it only work on my (and possibly some other machines) but breaks something on other machines? Is anybody else running the same patch without problems? Blaz Zupan, blaz@medinet.si, http://home.amis.net/blaz Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message