All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Merkey <linux.mdb@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
	John Stultz <john.stultz@linaro.org>
Subject: Re: [BUG REPORT] ktime_get_ts64 causes Hard Lockup
Date: Wed, 20 Jan 2016 12:59:52 -0700	[thread overview]
Message-ID: <CAO6TR8VtFQG19ZNmCYh3_-snANRE1D71LNHgw6ooAkCte_HV=g@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1601202029480.3575@nanos>

On 1/20/16, Thomas Gleixner <tglx@linutronix.de> wrote:
> Jeff,
>
> On Wed, 20 Jan 2016, Jeff Merkey wrote:
>> Thomas, so far the only thing I've gotten from you are whining
>> diatribes about email ettiquette and today is the FIRST time you have
>> responded to me with any arguments that have technical merit and
>> actually address the problem.    That's what I am here for, not
>> anything else.  As Linus has said repeatedly, being nice doesn't seem
>> to get results.    Being direct and honest does.
>>
>> I am here to make MDB run as well as I can make it on Linux and to
>> help make it run as well as possible on c86_64 and ia32.  That's my
>> only objective here.   That being said,  I am still wanting to get
>> this fixed.
>>
>> Will you help me?
>
> If you accept, that you are not setting the tone of the conversation as you
> think it fits you.
>
> I started to give you technical answers way before you started your
> completely
> unjustified ranting. And I have done so before.
>
> I'm neither going to cope with random emails in my private inbox nor with
> top-posting and non-trimmed replies simply because that wastes my time. And
> certainly I'm not going to cope with your assumption that not being nice is
> the right way to go.
>
> It's your decision, not mine.
>
> Thanks,
>
> 	tglx
>

Oh good grief -- I guess we all have our days me included.  I am sorry
to have offended you.    Turn the page, next chapter.    I am already
past this.  BTW, I am preparing my report.  Results same as before
with CONFIG_DEBUG_TIMEKEEPING, Hard Lockup again.  I am running a
trace right now to see just how big RAX was this time with the
nanoseconds count.

Jeff

  reply	other threads:[~2016-01-20 19:59 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-19  1:59 [BUG REPORT] ktime_get_ts64 causes Hard Lockup Jeff Merkey
2016-01-19  2:16 ` Jeff Merkey
2016-01-19  2:31   ` Jeff Merkey
2016-01-19  9:50 ` Thomas Gleixner
2016-01-19 15:37 ` Jeff Merkey
2016-01-19 22:00   ` Jeff Merkey
2016-01-20  0:59     ` Jeff Merkey
2016-01-20  9:21     ` Thomas Gleixner
2016-01-20 14:26       ` Thomas Gleixner
2016-01-20 16:40         ` Jeff Merkey
2016-01-20 16:53       ` Jeff Merkey
2016-01-20 17:16         ` Jeff Merkey
2016-01-20 17:32           ` John Stultz
2016-01-20 17:36             ` Jeff Merkey
2016-01-20 17:42             ` Thomas Gleixner
2016-01-20 17:59               ` John Stultz
2016-01-20 18:03                 ` Jeff Merkey
2016-01-20 17:21         ` Thomas Gleixner
2016-01-20 17:33           ` Jeff Merkey
2016-01-20 19:34             ` Thomas Gleixner
2016-01-20 19:59               ` Jeff Merkey [this message]
2016-01-21  7:09                 ` Jeff Merkey
2016-01-21  8:18                   ` Jeff Merkey
2016-01-21  9:08                     ` Jeff Merkey
2016-01-21 10:12                   ` Thomas Gleixner
2016-01-21 15:46                     ` Jeff Merkey
2016-01-21 16:57                       ` Jeff Merkey
2016-01-21 17:00                         ` Jeff Merkey
2016-01-21 17:07                           ` Jeff Merkey

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='CAO6TR8VtFQG19ZNmCYh3_-snANRE1D71LNHgw6ooAkCte_HV=g@mail.gmail.com' \
    --to=linux.mdb@gmail.com \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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.