public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Charles-Edouard Ruault <ce@ruault.com>
To: Marc-Christian Petersen <m.c.p@wolk-project.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [kernel 2.4.21-pre5 : process stuck in D state
Date: Thu, 13 Mar 2003 08:05:48 +0100	[thread overview]
Message-ID: <3E702DCC.9030503@ruault.com> (raw)
In-Reply-To: <200303121241.41914.m.c.p@wolk-project.de>

Marc-Christian Petersen wrote:
> On Wednesday 12 March 2003 12:27, Charles-Edouard Ruault wrote:
> 
> Hi Charles-Edouard,
> 
> 
>>i've been running kernel 2.4.21-preX series for a while on my ASUS A7V8X
>>motherboard ( with an athlon XP 2400+ )  and i've noticed the following
>>annoying problem.
>>Very often, mozilla ( 1.2.1 ) dies and is stuck in D state, waiting on a
>>semaphore, here's the output of ps :
>>
>>ps -elf | grep mozill
>>000 S userX 2615  1462  0  69   0    -   972 wait4  00:50 ?
>>00:00:00 /bin/sh /usr/local/mozilla/run-mozilla.sh
>>/usr/local/mozilla/mozilla-bin
>>000 D userX   2621  2615  0  69   0    - 13623 down   00:50 ?
>>00:00:02 /usr/local/mozilla/mozilla-bin
>>
>>Has anyone noticed the same behaviour ? Is this a well known problem ?
>>Thanks for your help.
> 
> There is a patch from Andrea for a long long time now. You may try it.
> 
> ciao, Marc
> 

Hi Marc-Christian,

i applied the patch over 2.4.21-pre5 and did some more testing.
I'm still having a problem but a different one ( i strongly suspect it's 
due to the patch since i never had this before and this occured when i 
tried to reproduce my previous problem ).
Here's a exerpt of the logs:

Mar 12 10:19:38 localhost kernel: hda: dma_timer_expiry: dma status == 
0x21
Mar 12 10:21:19 localhost kernel: hda: timeout waiting for DMA
Mar 12 10:21:19 localhost kernel: hda: timeout waiting for DMA 

Mar 12 10:21:19 localhost kernel: hda: (__ide_dma_test_irq) called while 
not waiting
Mar 12 10:21:19 localhost kernel: hda: status error: status=0x51 { 
DriveReady SeekComplete Error }
  Mar 12 10:21:19 localhost kernel: hda: status error: error=0x04 { 
DriveStatusError }
Mar 12 10:21:19 localhost kernel: hda: no DRQ after issuing MULTWRITE 

Mar 12 10:21:19 localhost kernel: hda: status error: status=0x51 { 
DriveReady SeekComplete Error }
Mar 12 10:21:19 localhost kernel: hda: status error: error=0x04 { 
DriveStatusError }
Mar 12 10:21:19 localhost kernel: hda: no DRQ after issuing MULTWRITE
Mar 12 10:21:19 localhost kernel: hda: status error: status=0x51 { 
DriveReady SeekComplete Error }
Mar 12 10:21:19 localhost kernel: hda: status error: error=0x04 { 
DriveStatusError }
Mar 12 10:21:19 localhost kernel: hda: no DRQ after issuing MULTWRITE 

Mar 12 10:21:19 localhost kernel: hda: status error: status=0x51 { 
DriveReady SeekComplete Error }
Mar 12 10:21:19 localhost kernel: hda: status error: error=0x04 { 
DriveStatusError }
  Mar 12 10:21:19 localhost kernel: hda: no DRQ after issuing WRITE
Mar 12 10:21:19 localhost kernel: ide0: reset: success 

Mar 12 10:21:19 localhost kernel: hda: dma_timer_expiry: dma status == 0x21
Mar 12 10:21:19 localhost kernel: hda: timeout waiting for DMA 

Mar 12 10:21:19 localhost kernel: hda: timeout waiting for DMA
Mar 12 10:21:19 localhost kernel: hda: (__ide_dma_test_irq) called while 
not waiting
Mar 12 10:21:19 localhost kernel: hda: status error: status=0x58 { 
DriveReady SeekComplete DataRequest } 

Mar 12 10:21:19 localhost kernel: hda: drive not ready for command
Mar 12 10:21:19 localhost kernel: hda: status timeout: status=0xd0 { 
Busy }
Mar 12 10:21:19 localhost kernel: hda: drive not ready for command 

Mar 12 10:21:19 localhost kernel: ide0: reset: success
Mar 12 10:21:19 localhost kernel: hda: dma_timer_expiry: dma status == 0x21


and basically the whole machine locked up ... reset was the only way out :-(
I have an ASUS A7V8X motherboard with a VIA Technologies, Inc. VT82C586B 
PIPC Bus Master IDE (rev 06)and a Maxtor 6Y080L0 hard drive.
Any other idea/hint to solve this ?
Thanks again for your help

-- 
Charles-Edouard Ruault
PGP Key ID 4370AF2D


      reply	other threads:[~2003-03-13  6:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-12 11:27 [kernel 2.4.21-pre5 : process stuck in D state Charles-Edouard Ruault
2003-03-12 12:59 ` Marc-Christian Petersen
2003-03-13  7:05   ` Charles-Edouard Ruault [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=3E702DCC.9030503@ruault.com \
    --to=ce@ruault.com \
    --cc=kernel@ruault.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.c.p@wolk-project.de \
    /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