All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kilobug <kilobug@freesurf.fr>
To: vda@port.imtp.ilyichevsk.odessa.ua
Cc: linux-kernel@vger.kernel.org, lkml@ohdarn.net
Subject: Re: [2.4.18-pre3-mjc3] heavy disk load and non-killable process
Date: Tue, 05 Feb 2002 20:51:18 +0100	[thread overview]
Message-ID: <3C6037B6.208@freesurf.fr> (raw)
In-Reply-To: <3C5F24A1.1060401@freesurf.fr> <200202050826.g158QVt18059@Port.imtp.ilyichevsk.odessa.ua>

Denis Vlasenko wrote:
> On 4 February 2002 22:17, Kilobug wrote:
> 
>>Hello,
>>	I've a 2.4.18-pre3-mjc3 kernel, with preempt enabled. I was testing
>>relative performance of DMA and non-DMA IDE hard disk access,
>>and I did the following as root:
>>
>>~ # hdparm -X67 -d1 /dev/hdb
>>~ # time /bin/sh -c "cp foo bar; sync"
>>~ # time /bin/sh -c "cp foo bar; sync"
>>~ # time /bin/sh -c "cp foo bar; sync"
>>~ # hdparm -X12 -d0 /dev/hdb
>>~ # time /bin/sh -c "cp foo bar; sync"
>>~ # time /bin/sh -c "cp foo bar; sync"
>>~ # time /bin/sh -c "cp foo bar; sync"
>>(foo is a 64Mb large regular file)
>>
>>I had xmms running, and during the first two tests of the non-DMA
>>version, the sound stops and then restarts, but it didn't restart after
>>the last cp.
>>
>>What is strange (and may be a kernel bug IMHO) is that the xmms process
>>stays running and non-killable:
>>
> 
> SysRq-T, isolate xmms part, ksymoops it, send result here and CC maintainers 
> (or who you think might be interested (Andrea/Alan/...))

SysRq-T and ksymoops:
Call Trace: [<c010ac83>] [<c0114e59>] [<c01164d4>] [<c011dc05>] 
[<e486f91f>] [<c013d69d>] [<c0121d99>] [<c013c1e9>] [<c013c297>] 
[<c010702b>]
Warning (Oops_read): Code line not seen, dumping what data is available

Trace; c010ac82 <call_do_IRQ+4/a>
Trace; c0114e58 <do_schedule+58/3e0>
Trace; c01164d4 <sys_sched_yield+a4/e0>
Trace; c011dc04 <tasklet_kill+54/80>
Trace; e486f91e <[emu10k1]emu10k1_audio_release+be/230>
Trace; c013d69c <fput+4c/100>
Trace; c0121d98 <schedule_timeout+58/a0>
Trace; c013c1e8 <filp_close+68/c0>
Trace; c013c296 <sys_close+56/b0>
Trace; c010702a <system_call+32/38>


-- 
** Gael Le Mignot "Kilobug", Ing3 EPITA - http://kilobug.free.fr **
Home Mail   : kilobug@freesurf.fr          Work Mail : le-mig_g@epita.fr
GSM         : 06.71.47.18.22 (in France)   ICQ UIN   : 7299959
Fingerprint : 1F2C 9804 7505 79DF 95E6 7323 B66B F67B 7103 C5DA

"Software is like sex it's better when it's free.", Linus Torvalds


      parent reply	other threads:[~2002-02-05 19:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-05  0:17 [2.4.18-pre3-mjc3] heavy disk load and non-killable process Kilobug
     [not found] ` <200202050826.g158QVt18059@Port.imtp.ilyichevsk.odessa.ua>
2002-02-05 19:51   ` Kilobug [this message]

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=3C6037B6.208@freesurf.fr \
    --to=kilobug@freesurf.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@ohdarn.net \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.