From: Theodore Ts'o <tytso@mit.edu>
To: Stefan Priebe <s.priebe@profihost.ag>
Cc: linux-ext4@vger.kernel.org,
"p.herz@profihost.ag >> Philipp Herz - Profihost AG"
<p.herz@profihost.ag>,
stable@vger.kernel.org
Subject: Re: Call trace in ext4_es_lru_add on 3.10 stable
Date: Thu, 18 Sep 2014 15:43:11 -0400 [thread overview]
Message-ID: <20140918194311.GE19520@thunk.org> (raw)
In-Reply-To: <541B32A1.3080706@profihost.ag>
On Thu, Sep 18, 2014 at 09:29:37PM +0200, Stefan Priebe wrote:
>
> Sorry but whole output is:
> 2014-09-18 02:30:34 0000000000000000 ffff881021663b20 ffff881021663b08
> ffffffffa02d66b3
...
That's not the whole message; you just weren't able to capture it all.
How are you capturing these messages, by the way? Serial console?
It this reproducible? Can you try a newer kernel?
Cheers,
- Ted
next prev parent reply other threads:[~2014-09-18 19:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 13:08 Call trace in ext4_es_lru_add on 3.10 stable Stefan Priebe - Profihost AG
2014-09-18 19:21 ` Theodore Ts'o
2014-09-18 19:29 ` Stefan Priebe
2014-09-18 19:43 ` Theodore Ts'o [this message]
2014-09-22 6:56 ` Stefan Priebe
2014-09-22 16:47 ` Theodore Ts'o
2014-09-22 18:29 ` Stefan Priebe
2014-09-22 20:20 ` Theodore Ts'o
2014-09-23 7:50 ` Stefan Priebe - Profihost AG
2014-09-23 9:42 ` Jan Kara
2014-09-23 12:23 ` Stefan Priebe
2014-09-23 14:43 ` Jan Kara
2014-11-26 8:06 ` Stefan Priebe - Profihost AG
2014-11-26 8:25 ` Jan Kara
2014-11-26 10:28 ` Stefan Priebe - Profihost AG
2014-11-26 10:38 ` Jan Kara
2014-11-26 15:11 ` Stefan Priebe - Profihost AG
2014-11-26 20:26 ` Jan Kara
2014-11-26 20:33 ` Stefan Priebe
2014-12-04 15:06 ` Stefan Priebe - Profihost AG
2014-12-04 18:35 ` Jan Kara
2014-12-15 9:48 ` Stefan Priebe - Profihost AG
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=20140918194311.GE19520@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=p.herz@profihost.ag \
--cc=s.priebe@profihost.ag \
--cc=stable@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.