public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: martin f krafft <madduck@madduck.net>
To: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: scheduling problems in X with 2.6.0
Date: Wed, 7 Jan 2004 11:23:52 +0100	[thread overview]
Message-ID: <20040107102352.GA2954@piper.madduck.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 2070 bytes --]

Hi all,

Ever since I moved to 2.6.0, I have been experiencing something I'd
like to call scheduling problems while working in X. I have tried
using preemptive mode, and turning it off, but the symptoms are the
same:

whenever there is continuous disk access (e.g. tar, rsync, dd),
X will not respond for a couple of seconds every couple of seconds.
With that I mean that the mouse will freeze as well as all screen
output, and then resume after a couple of seconds.

I wonder if I am the only one with that problem. The machine in
question is a dual AMD 2400+ with 2Gb of RAM and a Maxtor DiamondMax
drive spinning at 7200 RPM. The drive is configured as follows
(hdparm):

 multcount    = 16 (on)
 IO_support   =  1 (32-bit)
 unmaskirq    =  0 (off)
 using_dma    =  1 (on)
 keepsettings =  0 (off)
 readonly     =  0 (off)
 readahead    = 256 (on)
 geometry     = 16383/255/63, sectors = 241254720, start = 0
 Model=IC35L120AVV207-0, FwRev=V24OA63A, SerialNo=VNVD06G4C1NXZL
 Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
 RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=52
 BuffType=DualPortCache, BuffSize=1821kB, MaxMultSect=16, MultSect=16
 CurCHS=65535/1/63, CurSects=4128705, LBA=yes, LBAsects=241254720
 IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes:  pio0 pio1 pio2 pio3 pio4 
 DMA modes:  mdma0 mdma1 mdma2 
 UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5 
 AdvancedPM=yes: disabled (255) WriteCache=enabled
 Drive conforms to: ATA/ATAPI-6 T13 1410D revision 3a: 

I would appreciate any pointers to the source of the problem, or
general hints!

-- 
martin;              (greetings from the heart of the sun.)
  \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck
 
invalid/expired pgp subkeys? use subkeys.pgp.net as keyserver!
 
"never try to explain computers to a layman.
 it's easier to explain sex to a virgin."
                                                    -- robert heinlein
 
(note, however, that virgins tend to know a lot about computers.)

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2004-01-07 10:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-07 10:23 martin f krafft [this message]
2004-01-07 15:30 ` scheduling problems in X with 2.6.0 Nick Piggin
2004-01-07 17:46   ` martin f krafft
2004-01-08 15:34     ` Nick Piggin
2004-01-08 15:41       ` martin f krafft
2004-01-08 15:47         ` Nick Piggin
2004-01-08 15:42       ` martin f krafft

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=20040107102352.GA2954@piper.madduck.net \
    --to=madduck@madduck.net \
    --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