[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100910135511.53c0089a@schatten.dmk.lab>
Date: Fri, 10 Sep 2010 13:55:11 +0200
From: Florian Mickler <florian@...kler.org>
To: linux-kernel@...r.kernel.org
Cc: "Ted Ts'o" <tytso@....edu>, linux-kernel@...r.kernel.org,
Paolo Ornati <ornati@...il.com>
Subject: Re: help with git bisecting a bug 16376: random - possibly Radeon
DRM KMS related - freezes
On Thu, 9 Sep 2010 16:18:49 +0200
Martin Steigerwald <Martin@...htvoll.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists