All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Dalecki <dalecki@evision-ventures.com>
To: Sebastian Droege <sebastian.droege@gmx.de>
Cc: axboe@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] IDE TCQ #4
Date: Thu, 18 Apr 2002 13:20:15 +0200	[thread overview]
Message-ID: <3CBEABEF.1030009@evision-ventures.com> (raw)
In-Reply-To: <20020415125606.GR12608@suse.de>	<02db01c1e498$7180c170$58dc703f@bnscorp.com>	<20020416102510.GI17043@suse.de>	<20020416200051.7ae38411.sebastian.droege@gmx.de>	<20020416180914.GR1097@suse.de>	<20020416204329.4c71102f.sebastian.droege@gmx.de>	<3CBD28D1.6070702@evision-ventures.com>	<20020417132852.4cf20276.sebastian.droege@gmx.de>	<3CBD519F.7080207@evision-ventures.com> <20020418141746.2df4a948.sebastian.droege@gmx.de>

Sebastian Droege wrote:
> On Wed, 17 Apr 2002 12:42:39 +0200
> Martin Dalecki <dalecki@evision-ventures.com> wrote:
> 
> 
>>>2.
>>>when I cat /proc/ide/ide1/hdc/identify I get 2 unexpected interrupts
>>>hdc and hdd are both cdrom drives (accessed via scsi-emulation if relevant) 
>>
>> > but the problem shows up only with hdc
>>
>>Duh oh... This is actually a good hint. I will look after
>>this.
>>
>>
>>>and maybe a third problem ;)
>>>in /proc/ide/ide0/hda/tcq there is written:
>>>DMA status: not running
>>
>>This is harmless it just shows that there was no DMA transfer in flight the
>>time you have cat-ed this file.
>>
>>
>>>but DMA is explicitly enabled by hdparm and shows up in /proc/ide/ide0/hda/settings
>>>
>>>I'll do some more testings later the day
>>
> Hi again,
> after some playing with hdparm I found something bad :(
> 
> ide_tcq_intr_timeout: timeout waiting for interrupt
> ide_tcq_intr_timeout: hwgroup not busy
> hda: invalidating pending queue
> ide_tcq_invalidate_queue: done
> 
> and then... nothing works anymore -> total lockup of the IDE system
> This happens only (?) when I put hdparm -qa1 -qA1 -qc1 -qd1 -qm16 -qu1 -qW1 /dev/hda (the same with hdb) in my bootscripts
> When I start hdparm later everything works fine first, but after a while (and when I'm under X) the IDE system is crashed
> 
> I have enabled following options:
> CONFIG_BLK_DEV_IDE_TCQ=y
> CONFIG_BLK_DEV_IDE_TCQ_FULL=y
> CONFIG_BLK_DEV_IDE_TCQ_DEFAULT=y
> CONFIG_BLK_DEV_IDE_TCQ_DEPTH=32
> 
> I hope this helps somehow but I don't know what further informations I can provide
> 
> BTW: I think we should create devfs entries for ide-scsi devices (because hdparm doesn't take scdX ;) )
> 
> Bye

I don't know whatever you have already tryed the recend patches for 2.5.8.
The problem in place is presumably fixed there (tough there are still
problems with ide-cd remaining which I'm working on right now.)

BTW>  Jens: Do you have any idea what the "sector chaing" in ide-cd is
good for?! I would love to just get rid of it alltogether!




-- 
- phone: +49 214 8656 283
- job:   eVision-Ventures AG, LEV .de (MY OPINIONS ARE MY OWN!)
- langs: de_DE.ISO8859-1, en_US, pl_PL.ISO8859-2, last ressort: ru_RU.KOI8-R


  reply	other threads:[~2002-04-18 12:22 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-15 12:56 [PATCH] IDE TCQ #4 Jens Axboe
2002-04-15 12:24 ` Martin Dalecki
2002-04-15 13:33   ` Jens Axboe
2002-04-15 12:39     ` Martin Dalecki
2002-04-15 16:13 ` Aaron Tiensivu
2002-04-15 16:18   ` Jens Axboe
2002-04-15 16:44     ` Jens Axboe
2002-04-16 10:25   ` Jens Axboe
     [not found]     ` <20020416200051.7ae38411.sebastian.droege@gmx.de>
     [not found]       ` <20020416180914.GR1097@suse.de>
2002-04-16 18:43         ` Sebastian Droege
2002-04-17  7:48           ` Martin Dalecki
2002-04-17 11:28             ` Sebastian Droege
2002-04-17 10:32               ` Martin Dalecki
2002-04-17 11:40                 ` Sebastian Droege
2002-04-17 10:42               ` Martin Dalecki
2002-04-18 12:17                 ` Sebastian Droege
2002-04-18 11:20                   ` Martin Dalecki [this message]
2002-04-18 12:26                     ` Sebastian Droege
2002-04-18 12:57                       ` Jens Axboe
2002-04-18 12:57                     ` Jens Axboe
2002-04-18 11:59                       ` Martin Dalecki
2002-04-18 13:07                         ` Jens Axboe
2002-04-18 12:08                           ` Martin Dalecki
2002-04-18 13:12                             ` Jens Axboe
2002-04-18 12:16                               ` Martin Dalecki
2002-04-18 13:26                                 ` Jens Axboe
2002-04-18 12:40                                   ` Martin Dalecki
2002-04-18 12:45                                     ` Martin Dalecki
2002-04-18 14:17                               ` Alan Cox
2002-04-18 13:01                   ` Jens Axboe
2002-04-17  7:32     ` Helge Hafting
2002-04-17 13:01       ` Dave Jones
2002-04-17 13:05         ` Jens Axboe
2002-04-30 19:58     ` Martin Schewe
  -- strict thread matches above, loose matches on Subject: below --
2002-04-15 18:41 Petr Vandrovec
2002-04-15 18:26 ` Jens Axboe
2002-04-16  5:11 ` Martin Dalecki
2002-04-15 19:11 Petr Vandrovec
2002-04-15 19:28 Petr Vandrovec
2002-04-16 10:25 ` Jens Axboe
2002-04-16 11:01   ` Martin Dalecki
2002-04-16 12:28     ` Jens Axboe
2002-04-16 11:44       ` Martin Dalecki
2002-04-15 19:29 Petr Vandrovec
2002-04-15 19:00 ` Jens Axboe
2002-04-18 22:05 Andries.Brouwer

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=3CBEABEF.1030009@evision-ventures.com \
    --to=dalecki@evision-ventures.com \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sebastian.droege@gmx.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 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.