mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* Problem with read blocking for a long time on /dev/scd1
@ 2002-12-21  0:49 Gregory Stark
  2002-12-21  1:28 ` Greg Stark
                   ` (2 more replies)
  0 siblings, 3 replies; 10+ messages in thread
From: Gregory Stark @ 2002-12-21  0:49 UTC (permalink / raw)
  To: linux-kernel


I'm having a problem with ogle that seems to be being caused by the scsi or
ide-scsi driver. The video playback freezes for a second or randomly,
sometimes every few seconds, sometimes not for several minutes. Every such
glitch is correlated perfectly with a read syscall reading on /dev/scd1
blocking for an inordinate amount of time.

Most read syscalls from ogle seem to take between 30us to 100ms depending on
the size of the read. In fact plotting the time taken reported by strace -T vs
the size of the read in gnuplot produces a nice obvious linear correlation.

However occasionally there are outlier samples where the read call blocks for
between 150ms up to 1s or more. I've seen it block for about 10s once.

I've tried this on a machine that was essentially in single-user mode. The
only processes running were X, ogle, an xterm, and not much else. I'll include
my normal lsmod output below but the problem still occurred when playing with
hardly any modules loaded.

There's an FAQ about ogle glitching like this when something tries to probe
the cd drive, but nothing like that is running. And the glitches aren't
periodic like that FAQ describes.

The problem is definitely that the kernel simply doesn't schedule the process
calling read for over a second. 

There are no dmesg messages or other indication of problems in the ide-scsi or scsi
drivers.

Where would I start to track down what is preventing the kernel from
scheduling this process? It's presumably some problem in the ide or ide-scsi
driver, but I'm not sure where to start.

[I'm having trouble sending messages to the list, my ISPs mail server didn't
seem to deliver it the first time. My apologies if it finally makes it through
and this is a duplicate]

--
greg


^ permalink raw reply	[flat|nested] 10+ messages in thread
* Problem with read blocking for a long time on /dev/scd1
@ 2002-12-21  0:51 Gregory Stark
  0 siblings, 0 replies; 10+ messages in thread
From: Gregory Stark @ 2002-12-21  0:51 UTC (permalink / raw)
  To: linux-kernel


I'm having a problem with ogle that seems to be being caused by the scsi or
ide-scsi driver. The video playback freezes for a second or randomly,
sometimes every few seconds, sometimes not for several minutes. Every such
glitch is correlated perfectly with a read syscall reading on /dev/scd1
blocking for an inordinate amount of time.

Most read syscalls from ogle seem to take between 30us to 100ms depending on
the size of the read. In fact plotting the time taken reported by strace -T vs
the size of the read in gnuplot produces a nice obvious linear correlation.

However occasionally there are outlier samples where the read call blocks for
between 150ms up to 1s or more. I've seen it block for about 10s once.

I've tried this on a machine that was essentially in single-user mode. The
only processes running were X, ogle, an xterm, and not much else. I'll include
my normal lsmod output below but the problem still occurred when playing with
hardly any modules loaded.

There's an FAQ about ogle glitching like this when something tries to probe
the cd drive, but nothing like that is running. And the glitches aren't
periodic like that FAQ describes.

The problem is definitely that the kernel simply doesn't schedule the process
calling read for over a second. 

There are no dmesg messages or other indication of problems in the ide-scsi or scsi
drivers.

Where would I start to track down what is preventing the kernel from
scheduling this process? It's presumably some problem in the ide or ide-scsi
driver, but I'm not sure where to start.

[I'm having trouble sending messages to the list, my ISPs mail server didn't
seem to deliver it the first time. My apologies if it finally makes it through
and this is a duplicate]

--
greg


^ permalink raw reply	[flat|nested] 10+ messages in thread
end of thread, other threads:[~2003-01-08  3:54 UTC | newest]

Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-12-21  0:49 Problem with read blocking for a long time on /dev/scd1 Gregory Stark
2002-12-21  1:28 ` Greg Stark
2002-12-21  6:14 ` Greg Stark
2002-12-22 16:13   ` More tests [Was: Problem with read blocking for a long time on /dev/scd1] Greg Stark
2002-12-22 20:13     ` Jakob Oestergaard
2002-12-23  8:58       ` Greg Stark
2002-12-27 15:36         ` Jakob Oestergaard
2003-01-08  4:03         ` Jakob Oestergaard
2002-12-23 18:02 ` Problem with read blocking for a long time on /dev/scd1 Krzysztof Halasa
2002-12-21  0:51 Gregory Stark

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®