From: Florian Mickler <florian@mickler.org>
To: Martin Steigerwald <Martin@lichtvoll.de>
Cc: "Ted Ts'o" <tytso@mit.edu>,
linux-kernel@vger.kernel.org, Paolo Ornati <ornati@gmail.com>
Subject: Re: help with git bisecting a bug 16376: random - possibly Radeon DRM KMS related - freezes
Date: Fri, 10 Sep 2010 13:55:11 +0200 [thread overview]
Message-ID: <20100910135511.53c0089a@schatten.dmk.lab> (raw)
In-Reply-To: <201009091618.51064.Martin@lichtvoll.de>
On Thu, 9 Sep 2010 16:18:49 +0200
Martin Steigerwald <Martin@lichtvoll.de> wrote:
> Yes, I am aware that it may not be a Ext4 problem at all. Thus I said Ext4
> / readahead related (!) backtrace (! not bug) cause that was all I could
> see on the screen. How else should I have described that backtrace when I
> can't speculate on what I can not see?
I think, it is no big thing. The trick is probably to say nothing at all
about the cause, when it is not clear. It's a mind thing. As soon as the
association is brought up, everybody thinks along those lines. :)
If you leave out the "ext4/readahead related", then people will still
know that it might be ext4 readahead related because you posted the
backtrace, but they will not have their mind turned to that. Instead
they will think: oh a backtrace... there were some people shouting
about backtraces in my area, let's see if it is realted.
But of course, sometimes putting blame somewhere also does help getting
attention. After all "CORRUPTION IN FILESYSTEM XYZ" sticks out more
than "partial trace of a thing i don't know anything at all".
Cheers,
Flo
next prev parent reply other threads:[~2010-09-10 11:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-31 19:53 help with git bisecting a bug 16376: random - possibly Radeon DRM KMS related - freezes Martin Steigerwald
2010-08-31 22:39 ` Ken Moffat
2010-09-01 16:10 ` Martin Steigerwald
2010-09-01 18:13 ` Ken Moffat
2010-09-01 18:47 ` Paolo Ornati
2010-09-01 19:26 ` Martin Steigerwald
2010-09-05 7:53 ` Martin Steigerwald
2010-09-05 12:20 ` Paolo Ornati
2010-09-05 13:25 ` Martin Steigerwald
2010-09-07 2:51 ` Ted Ts'o
2010-09-09 14:18 ` Martin Steigerwald
2010-09-10 11:55 ` Florian Mickler [this message]
2010-09-10 13:49 ` Martin Steigerwald
2010-09-10 15:53 ` Theodore Tso
2010-09-10 16:18 ` Martin Steigerwald
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=20100910135511.53c0089a@schatten.dmk.lab \
--to=florian@mickler.org \
--cc=Martin@lichtvoll.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ornati@gmail.com \
--cc=tytso@mit.edu \
/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