From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tziporet Koren Subject: Re: OFED 1.5 complains about freeing invalid memtype Date: Wed, 28 Oct 2009 09:41:51 +0200 Message-ID: <4AE7F5BF.3020106@mellanox.co.il> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Bart Van Assche Cc: OFED mailing list List-Id: linux-rdma@vger.kernel.org Bart Van Assche wrote: > Hello, > > While /etc/init.d/openibd runs the following kernel messages were generated: > > mstmread:2578 freeing invalid memtype fe600000-fe610000 > mstmread:2578 freeing invalid memtype fe610000-fe700000 > mstmread:2581 freeing invalid memtype fe600000-fe610000 > mstmread:2581 freeing invalid memtype fe610000-fe700000 > mstmread:2584 freeing invalid memtype fe600000-fe610000 > mstmread:2584 freeing invalid memtype fe610000-fe700000 > mstmread:2587 freeing invalid memtype fe600000-fe610000 > mstmread:2587 freeing invalid memtype fe610000-fe700000 > mstmread:2626 freeing invalid memtype fea00000-fea10000 > mstmread:2626 freeing invalid memtype fea10000-feb00000 > mstmread:2629 freeing invalid memtype fea00000-fea10000 > mstmread:2629 freeing invalid memtype fea10000-feb00000 > mstmread:2632 freeing invalid memtype fea00000-fea10000 > mstmread:2632 freeing invalid memtype fea10000-feb00000 > mstmread:2635 freeing invalid memtype fea00000-fea10000 > mstmread:2635 freeing invalid memtype fea10000-feb00000 > > This occurred with a 2.6.30.9 kernel with kernel debugging enabled, > OFED-1.5-20091027-0600 and mlx4 hardware. Is this a known issue ? > > This happened from mstmread utility Are you using it? In any case we will check it in Mellanox Tziporet -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html