mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: C.M.Caldwell@Alumni.UNH.EDU
To: linux-kernel@vger.kernel.org
Cc: c.m.caldwell@Alumni.UNH.EDU
Subject: Conflict between ntpd system calls and bttv device driver
Date: Fri, 27 May 2005 11:10:17 -0400	[thread overview]
Message-ID: <200505271510.j4RFAHYX010409@mike.caldwell.org> (raw)

Greetings,

One line:	Frame grabber times out if ntpd runs with kernel calls

Full:		We run the bttv frame grabber on a Dell-2600 running
		2.6.9-1.667smp (ala Fedora Core 3).  If we run ntpd
		normally, after a variable amount of time (seconds to
		multiple hours), ioctl(dev,VIDIOC_DQBUF,ptr) returns
		EINVAL.  After putting debug writes in the kernel,
		we determined that it is because the request timed out
		due to the fact that the interupt was blocked by a
		higher priority interupt:  the kernel logic for the ntpd
		system calls.

		This doesn't happen on all systems (e.g. a Dell-2650 doesn't
		seem to have this problem), but it will happen with earlier
		versions of the kernel.  Also, the problem occurs even if
		you have stopped ntpd and re-loaded the bttv driver.

		It may be that this can occur under more circumstances than
		outline above but that it is much rarer.  We believe that
		the Dell-2600s multiple PCI busses and its interupt structure
		may make it much more sensitive to having interupts blocked
		for long periods of time.
		
Keywords:	bttv adjtime VIDIOC_DQBUF timeout
Version:	2.6.9-1.667smp

Workaround:	Add "disable kernel" to ntp.conf file and reboot
Oops output:
Shell script:
Environment:
Software:
Processor:	i686 Genuine Intel 2.8GHZ (Dell-2600)
Modules:
Loaded drivers:
Hardware:
lspci:
SCSI:

Comments:	Considering how easy the work-around for us is, this is
		pretty low priority (though it was mighty high until we
		figured out that ntpd was the thing hogging the interupts).
		I wanted to send this in just to make people aware that
		there maybe some timing conflicts.
		sure 

             reply	other threads:[~2005-05-27 15:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-27 15:10 C.M.Caldwell [this message]
2005-05-28  2:09 ` 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=200505271510.j4RFAHYX010409@mike.caldwell.org \
    --to=c.m.caldwell@alumni.unh.edu \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®