From owner-freebsd-stable  Wed Jul 25  7:34:25 2001
Delivered-To: freebsd-stable@freebsd.org
Received: from nova.fnal.gov (nova.fnal.gov [131.225.121.207])
	by hub.freebsd.org (Postfix) with ESMTP id D513B37B638
	for <stable@FreeBSD.ORG>; Wed, 25 Jul 2001 07:28:44 -0700 (PDT)
	(envelope-from zingelman@fnal.gov)
Received: from localhost (tez@localhost)
	by nova.fnal.gov (8.9.3+Sun/8.9.3) with ESMTP id JAA07402;
	Wed, 25 Jul 2001 09:09:57 -0500 (CDT)
X-Authentication-Warning: nova.fnal.gov: tez owned process doing -bs
Date: Wed, 25 Jul 2001 09:09:57 -0500 (CDT)
From: Tim Zingelman <zingelman@fnal.gov>
X-Sender:  <tez@nova.fnal.gov>
To: Dimitry Andric <dim@xs4all.nl>
Cc: James Satterfield <jsatterfield@intertrust.com>,
	<stable@FreeBSD.ORG>, Boris Popov <bp@butya.kz>
Subject: SMBFS panic: malloc: wrong bucket (was: 4.3-20010721-STABLE)
In-Reply-To: <6012739628.20010724230821@xs4all.nl>
Message-ID: <Pine.GSO.4.30.0107250904080.6429-100000@nova.fnal.gov>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-stable.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-stable>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-stable>
X-Loop: FreeBSD.ORG

This is a known bug, but not fixed.  I worked with the maintainer, Boris
Popov on it a little, but in my case it took some time between the mount
and the panic, and I was not able to give him login access to the
machines involved.  As a result it remains unfixed.  If you have a case
that panics immediately and can work with him, I think he would be
interested in getting this fixed.  (I know I would :)

 - Tim

On Tue, 24 Jul 2001, Dimitry Andric wrote:

> On 2001-07-24 at 19:49:52 James Satterfield wrote:
>
> JS> panic: malloc: wrong bucket
>
> JS> syncing disks...
>
> JS> Could someone give me some insight into what may have caused this?
> JS> The only changes I'd made from the base install was to recompile the kernel
> JS> with LIBMCHAIN and LIBICONV.
> JS> I also had an SMB share mounted via smbfs.
>
> This seems to be caused by smbfs. I haven't been able to use it
> normally for quite some time now. As soon as I smbmount any share, it
> immediately panics, with the error you mentioned above.
>
> I'd recommend contacting the smbfs maintainer. It seems the kernel
> module for smbfs is now integrated into the main sources, but you
> still need to install a port. So I'm guessing it's now in some sort of
> transitional status (and thus quite unstable).
>
> Cheers,
> --
> Dimitry Andric <dim@xs4all.nl>
> PGP Key: http://www.xs4all.nl/~dim/dim.asc
> Fingerprint: 7AB462D2CE35FC6D42394FCDB05EA30A2E2096A3
> Signature by unknown keyid: 0x2E2096A3
>



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