From owner-freebsd-current@FreeBSD.ORG  Wed Jun 29 20:34:08 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: current@freebsd.org
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 AF7F016A429
	for <current@freebsd.org>; Wed, 29 Jun 2005 20:34:08 +0000 (GMT)
	(envelope-from silby@silby.com)
Received: from relay.pair.com (relay00.pair.com [209.68.1.20])
	by mx1.FreeBSD.org (Postfix) with SMTP id 4F92F43D55
	for <current@freebsd.org>; Wed, 29 Jun 2005 20:34:08 +0000 (GMT)
	(envelope-from silby@silby.com)
Received: (qmail 18041 invoked from network); 29 Jun 2005 20:34:06 -0000
Received: from unknown (HELO localhost) (unknown)
	by unknown with SMTP; 29 Jun 2005 20:34:06 -0000
X-pair-Authenticated: 209.68.2.70
Date: Wed, 29 Jun 2005 15:33:44 -0500 (CDT)
From: Mike Silbersack <silby@silby.com>
To: Daniel Collins <danccollins@earthlink.net>
In-Reply-To: <42C2E553.7090501@earthlink.net>
Message-ID: <20050629153201.M27720@odysseus.silby.com>
References: <20050629032309.E27720@odysseus.silby.com>
	<42C2E553.7090501@earthlink.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: current@freebsd.org
Subject: Re: mbuf trash-related "memory modified after free" panic fixed.
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jun 2005 20:34:08 -0000


On Wed, 29 Jun 2005, Daniel Collins wrote:

> Mike,
>
> I'm still seeing these printfs.  Much like Pascal, my "value" is fairly 
> consistent.  It does seem to change based on access point...  I've tested 
> this on three different access points-- 2 open, and 1 with WPA-PSK.  When I 
> connect to the open access points, I get "val=102c0de".  When connecting to 
> the WPA-PSK access point, I get "val=2cc0de".  This value is consistent 
> across kernel rebuilds and connect sessions.
>
> My hardware is a Thinkpad 380XD w/ Belkin F5D7010 (ral) pc card nic.
>
> Let me know if I can provide more information.

Actually, that is a real bug. :)

Damien just committed a fix in revision 1.4 of if_ral.c.  Please cvsup and 
see if that stops the warnings.

Thanks,

Mike "Silby" Silbersack