linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Clark Williams <williams@redhat.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: RT <linux-rt-users@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RT] oops in 4.1.3-rt3
Date: Thu, 4 Feb 2016 14:59:31 -0600	[thread overview]
Message-ID: <20160204145931.47dd616d@sluggy.hsv.redhat.com> (raw)
In-Reply-To: <20150803142700.1de720e4@sluggy>

[-- Attachment #1: Type: text/plain, Size: 791 bytes --]

On Mon, 3 Aug 2015 14:27:00 -0500
Clark Williams <williams@redhat.com> wrote:

> Sebastian,
> 
> Below is a traceback I hit while running 4.1.3-rt3 on my Lenovo T530.
> 
> I was doing my normal, play music, copy files over the lan, do compiles,
> do email, etc., so I I can't really point you at a reproducer. The graphics
> system stayed up somewhat but the actual trace I hit scrolled off. This was
> extracted from the syslog with 'journalctl'. 
> 
> If I encounter it again, I'll see if I can force a kdump. 
> 

I have been unable to reproduce this bug. It happened during normal use and I haven't changed work habits, so I'd say drop this from the -rt open-issues section until we can get an actual reproducer or at least until the frequency goes up.

Thanks,
Clark

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  parent reply	other threads:[~2016-02-04 20:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-03 19:27 [RT] oops in 4.1.3-rt3 Clark Williams
2015-08-04  8:08 ` Nicholas Mc Guire
2015-08-04 12:05   ` Thomas Gleixner
2015-08-16 11:58     ` Sebastian Andrzej Siewior
2015-08-17  3:33       ` Alex Goebel
2015-08-19 20:58       ` Thomas Gleixner
2015-08-16 11:33 ` Sebastian Andrzej Siewior
2016-02-04 20:59 ` Clark Williams [this message]
2016-03-09 13:21   ` Sebastian Andrzej Siewior

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=20160204145931.47dd616d@sluggy.hsv.redhat.com \
    --to=williams@redhat.com \
    --cc=bigeasy@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).