linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Peter Hurley <peter@hurleysoftware.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiri Slaby <jslaby@suse.cz>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Alan Cox <alan@linux.intel.com>
Subject: Re: WARNING: at drivers/tty/tty_buffer.c:476 flush_to_ldisc+0x1de/0x1f0()
Date: Sat, 15 Dec 2012 11:17:34 -0500	[thread overview]
Message-ID: <20121215161734.GA6218@redhat.com> (raw)
In-Reply-To: <1355543596.3837.10.camel@thor>

On Fri, Dec 14, 2012 at 10:53:16PM -0500, Peter Hurley wrote:
 > On Fri, 2012-12-14 at 18:29 -0800, Greg Kroah-Hartman wrote:
 > > On Tue, Dec 11, 2012 at 10:01:24PM -0500, Dave Jones wrote:
 > > > Fuzz-testing fallout from post 3.7 tree as of commit 414a6750e59b0b687034764c464e9ddecac0f7a6
 > > > 
 > > > [ 2181.230579] ------------[ cut here ]------------
 > > > [ 2181.231277] WARNING: at drivers/tty/tty_buffer.c:476 flush_to_ldisc+0x1de/0x1f0()
 > > > [ 2181.232358] Hardware name: GA-MA78GM-S2H
 > > > [ 2181.232925] tty is NULL
 > 
 > Dave, how do you have your trinity command line + kvm configured? I had
 > to write a test jig to get this to happen but I'd prefer to reproduce it
 > in trinity.
 
no special params, though te first time I saw this it 
happened quickly as you see from the timestamp.
Yesterday I hit it a second time after fuzzing for
the better psrt of a day.

	Dave



  reply	other threads:[~2012-12-15 16:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-12  3:01 WARNING: at drivers/tty/tty_buffer.c:476 flush_to_ldisc+0x1de/0x1f0() Dave Jones
2012-12-15  2:29 ` Greg Kroah-Hartman
2012-12-15  3:53   ` Peter Hurley
2012-12-15 16:17     ` Dave Jones [this message]
2012-12-15 17:25     ` Greg Kroah-Hartman

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=20121215161734.GA6218@redhat.com \
    --to=davej@redhat.com \
    --cc=alan@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter@hurleysoftware.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;
as well as URLs for NNTP newsgroup(s).