mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Lee Revell <rlrevell@joe-job.com>
Cc: linux1394-devel@lists.sourceforge.net,
	Andrew Morton <akpm@osdl.org>, Miles Lane <miles.lane@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.16-rc2-mm1 -- BUG: warning at	drivers/ieee1394/ohci1394.c:235/get_phy_reg()
Date: Sat, 11 Feb 2006 09:39:01 +0100	[thread overview]
Message-ID: <43EDA2A5.6000901@s5r6.in-berlin.de> (raw)
In-Reply-To: <1139625039.19342.49.camel@mindpipe>

Lee Revell wrote:
> On Sat, 2006-02-11 at 01:31 +0100, Stefan Richter wrote:
>>Andrew Morton wrote:
>>>That's a -mm-only warning telling you that get_phy_reg() is doing a
>>>one-millisecond-or-more busywait while local interrupts are disabled.
>>
>>Same with set_phy_reg, ohci_soft_reset, ohci_hw_csr_reg.
[...]
> In fact I'm pretty sure we have seen reports on the linux-audio-user
> list of apps reporting underruns when a 1394 drive is accessed.

These might have different causes. The 1394 storage driver, sbp2, 
performs quite a lot of protocol handling in IRQ or soft IRQ context. I 
have been planning to move this off into process context -- not really 
because of potential latency issues but for sake of more reliable 
protocol handling. I hope I get to it RSN.

AFAICS the offending ohci1394 functions mentioned above are never called 
during normal access to an SBP-2 device. They only happen when a host 
adapter is initialized or shut down or whenever a 1394 device is plugged 
in or out (actually whenever self ID reception is completed).
-- 
Stefan Richter
-=====-=-==- --=- -=-==
http://arcgraph.de/sr/

  reply	other threads:[~2006-02-11  8:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-10 20:07 Miles Lane
2006-02-10 20:21 ` Andrew Morton
2006-02-11  0:31   ` Stefan Richter
2006-02-11  2:30     ` Lee Revell
2006-02-11  8:39       ` Stefan Richter [this message]
2006-02-11  2:28   ` Lee Revell
2006-02-11  4:37     ` Andrew Morton
2006-02-11  8:50       ` Stefan Richter
2006-02-11  9:03         ` Andrew Morton

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=43EDA2A5.6000901@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=miles.lane@gmail.com \
    --cc=rlrevell@joe-job.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

all inboxes | Powered by JetHome®