From owner-freebsd-current Thu Apr 18 20:19:29 2002 Delivered-To: freebsd-current@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.19.129.142]) by hub.freebsd.org (Postfix) with ESMTP id 75BC337B405 for ; Thu, 18 Apr 2002 20:19:24 -0700 (PDT) Received: by relay.butya.kz (Postfix, from userid 1000) id 353ED2880B; Fri, 19 Apr 2002 10:19:18 +0700 (ALMST) Received: from localhost (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with ESMTP id 2966328803; Fri, 19 Apr 2002 10:19:18 +0700 (ALMST) Date: Fri, 19 Apr 2002 10:19:18 +0700 (ALMST) From: Boris Popov To: Thomas Wuerfl Cc: Craig Boston , current@freebsd.org Subject: Re: OT: FreeBSD-current works great! In-Reply-To: <200204181454.05171.Thomaswuerfl@gmx.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 18 Apr 2002, Thomas Wuerfl wrote: > Am Donnerstag, 18. April 2002 05:00 schrieb Craig Boston: > > My only trouble so far has been mount_smbfs panicking the machine when > > connecting to certain servers (but not others, weird). I'm compiling a > > debug kernel now and will attempt to get a good backtrace to post. > > I have the same problem, when I mount a smb-share from a Win2000sp2 machine > and try to _move_ files from the win-machine to mine (kernel-panic). When I > try to mount the same share again after reboot -> kernel panic. I first have > to reboot the win-machine to get rid of that. Only by moving files, not copy > or delete. Very strange. Yes, now I'm see this panic too. Something chaged after Apr 7 broke smbfs. Not sure what exactly, though. -- Boris Popov http://rbp.euro.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message