From: Tziporet Koren <tziporet-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org>
To: Bart Van Assche <bart.vanassche-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: OFED mailing list <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: OFED 1.5 complains about freeing invalid memtype
Date: Wed, 28 Oct 2009 09:41:51 +0200 [thread overview]
Message-ID: <4AE7F5BF.3020106@mellanox.co.il> (raw)
In-Reply-To: <e2e108260910271332i50e1f127vc4ea72a0be1239e1-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.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
next prev parent reply other threads:[~2009-10-28 7:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e2e108260910271330n665cbe2eyd2dfce60f4e61cc2@mail.gmail.com>
[not found] ` <e2e108260910271330n665cbe2eyd2dfce60f4e61cc2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-10-27 20:32 ` OFED 1.5 complains about freeing invalid memtype Bart Van Assche
[not found] ` <e2e108260910271332i50e1f127vc4ea72a0be1239e1-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-10-28 7:41 ` Tziporet Koren [this message]
[not found] ` <4AE7F5BF.3020106-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org>
2009-10-28 17:46 ` Bart Van Assche
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AE7F5BF.3020106@mellanox.co.il \
--to=tziporet-vpraknaxozvs1mouv/rt9w@public.gmane.org \
--cc=bart.vanassche-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox