From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Nick Krause <xerofoify@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Bug on Kernel 3.16 r6: Sound and Buffering in Clementine with Files are Transferring to Music Directory
Date: Sun, 27 Jul 2014 08:36:48 +0200 [thread overview]
Message-ID: <1406443008.5115.117.camel@marge.simpson.net> (raw)
In-Reply-To: <CAPDOMViYi_rg_cGp_SgZVqX6pw+SB=CVbr1kFn5WG481s4tz5A@mail.gmail.com>
On Sat, 2014-07-26 at 23:41 -0400, Nick Krause wrote:
> Hey Guys,
> I seem to be hitting my first kernel bug in the kernel stated in my
> subject line.
> When I transfer a lot of music for a brtfs external hard drive I have the music
> in clementine I am listening to is stopped for a few seconds and then continues.
The thing to do now is to collect solid data for a proper bug report.
How to reproduce etc. See REPORTING-BUGS.
For a guy interested in kernel hacking, this is the perfect opportunity
to sink your teeth into a bug that you can reproduce on your box.
If you go there...
You could use perf sched record/lat and/or ftrace to trace/identify the
event, analyze what's going on in the kernel while the bad thing is
happening. If you manage to get the root cause properly nailed down,
you will have dug out highly useful information.
Um, don't be surprised and appalled if you find that you're not up to
fixing this. A more realistic goal is to capture some high quality
information, and learn how to use the tools to _chase_ bugs. Once you
get a firm grip on a bug, you can always holler "Help, it's got me!" if
it's a serious bug.
-Mike
next prev parent reply other threads:[~2014-07-27 6:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-27 3:41 Bug on Kernel 3.16 r6: Sound and Buffering in Clementine with Files are Transferring to Music Directory Nick Krause
2014-07-27 5:07 ` Matt Joras
2014-07-27 6:50 ` Mike Galbraith
2014-07-27 6:36 ` Mike Galbraith [this message]
[not found] ` <20140727083758.GA4834@fancy-poultry.org>
2014-07-27 20:18 ` Nick Krause
2014-07-27 20:37 ` Nick Krause
2014-07-28 9:54 ` Heinz Diehl
2014-07-28 15:09 ` Nick Krause
2014-07-28 20:13 ` Heinz Diehl
2014-07-28 22:24 ` Nick Krause
2014-07-29 5:37 ` Nick Krause
2014-07-29 5:57 ` Nick Krause
[not found] ` <2b1c82c0922238cbceabae6b6dc056f9@mjoras.com>
[not found] ` <CAPDOMVh7DnV4r=aLbReb8KATW_6u_PVKX-CfnSQ3Q2WxpSbzMw@mail.gmail.com>
2014-07-29 17:34 ` Nick Krause
2014-07-30 5:00 ` Nick Krause
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=1406443008.5115.117.camel@marge.simpson.net \
--to=umgwanakikbuti@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xerofoify@gmail.com \
/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