From: "Alan D. Brunelle" <Alan.Brunelle@hp.com>
To: linux-s390@vger.kernel.org, linux-btrace@vger.kernel.org
Subject: Re: blktrace / relay: bad trace
Date: Wed, 11 Mar 2009 12:03:36 +0000 [thread overview]
Message-ID: <49B7A898.9050703@hp.com> (raw)
In-Reply-To: <1236772761.23294.5.camel@kitka.ibm.com>
Martin Peschke wrote:
> Hi Alan,
> I get bad data from relay in user space. I don't see a crash similar to
> the one you have posted. My issue appears to be older anyway.
> The last kernel I have tried out is 2.6.29-rc7.
>
> Martin
Looking like a false alarm on my part anyhow: bad firmware leading to
memory corruption(!) - amazing, but seemingly true...
Alan
prev parent reply other threads:[~2009-03-11 12:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-05 16:23 blktrace / relay: bad trace Martin Peschke
2009-03-09 5:10 ` Tom Zanussi
2009-03-09 14:23 ` Martin Peschke
2009-03-10 17:19 ` Alan D. Brunelle
2009-03-11 11:59 ` Martin Peschke
2009-03-11 12:03 ` Alan D. Brunelle [this message]
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=49B7A898.9050703@hp.com \
--to=alan.brunelle@hp.com \
--cc=linux-btrace@vger.kernel.org \
--cc=linux-s390@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.