LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andrew Bird <ajb@spheresystems.co.uk>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Spinlock debugging
Date: Mon, 11 Sep 2006 17:38:21 +0100	[thread overview]
Message-ID: <200609111738.21818.ajb@spheresystems.co.uk> (raw)
In-Reply-To: <1157992570.23085.169.camel@localhost.localdomain>

Alan
	Yes, I have low_latency set for kernels lower than 2.6.17. I'm currently 
testing using 2.6.15. When you mention 'write method for flow control' do you 
mean for software XON/XOFF etc?
	On a more generic note, is the spinlock debug output read as a stack and what 
do the '=======' line breaks signify, looping?

Thanks


Andrew

On Monday 11 September 2006 17:36, Alan Cox wrote:
> Ar Llu, 2006-09-11 am 16:32 +0100, ysgrifennodd Andrew Bird (Sphere
>
> Systems):
> > will be lost. But if I comment out the line that tells the tty layer that
> > it's implemented, I end up with a BUG - spinlock recursion. Can anybody
> > tell me how to interpret the output?
>
> Looks like your driver calls flush_to_ldisc with low latency set and
> then can't handle the flush_to_ldisc causing n_tty to call back into the
> write method for flow control.
>
> Alan

  reply	other threads:[~2006-09-11 16:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-11 15:32 Andrew Bird (Sphere Systems)
2006-09-11 16:36 ` Alan Cox
2006-09-11 16:38   ` Andrew Bird [this message]
2006-09-11 17:24     ` Alan Cox
2006-09-12  7:47       ` Andrew Bird
2006-09-12 13:43         ` Alan Cox
2006-09-12 13:31           ` Sergei Organov
2006-09-12 14:04             ` Alan Cox

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=200609111738.21818.ajb@spheresystems.co.uk \
    --to=ajb@spheresystems.co.uk \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: Spinlock debugging' \
    /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

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).