linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Karsten Keil <kkeil@suse.de>
To: Stephan von Krawczynski <skraw@ithnet.com>
Cc: alan@lxorguk.ukuu.org.uk, kai@tp1.ruhr-uni-bochum.de,
	linux-kernel@vger.kernel.org
Subject: Re: ISDN massive packet drops while DVD burn/verify
Date: Mon, 5 May 2003 20:31:23 +0200	[thread overview]
Message-ID: <20030505183123.GA31871@pingi3.kke.suse.de> (raw)
In-Reply-To: <20030505192652.7f17ea9e.skraw@ithnet.com>

On Mon, May 05, 2003 at 07:26:52PM +0200, Stephan von Krawczynski wrote:
> On Mon, 5 May 2003 18:46:53 +0200
> Karsten Keil <kkeil@suse.de> wrote:
> 
> > > How did we manage to become that bad?
> > 
> > Its not so bad, the problem is how do you tune the system. If you prefer to
> > not interrupt the IDE transfers, which seems to be the default case, you
> > loose IRQ latency, which doesn't matter in much cases, but not on
> > this. You can tune it (hdparm work also with cdwriters, since
> > even if it use ide-scsi, the underlying driver is the ide driver.
> 
> You mean UDMA 2 does not make it (which I had in the test case)?
> 
> # hdparm -i /dev/hdc
> 
> /dev/hdc:
> 
>  Model=SONY DVD RW DRU-500A, FwRev=2.0c, SerialNo=DA5B9D3D
>  Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic }
>  RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
>  BuffType=unknown, BuffSize=0kB, MaxMultSect=0
>  (maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
>  IORDY=on/off, tPIO={min:180,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 
>  AdvancedPM=no
>  Drive conforms to: device does not report version:  4 5 6
> 

No the mode doesn't matter so much here, what give

hdparm -v /dev/hdc


> > This all don't say that here maybe also other problems around, but I have no
> > better explanation.
> 
> Hm, this looks like the unresolved sleeping AVM Fritz2 syndrome to me: no idea
> of what's really going on ...

Hmm, don't remember this issue at the moment.

-- 
Karsten Keil
SuSE Labs
ISDN development

  reply	other threads:[~2003-05-05 18:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-16 13:12 ISDN massive packet drops while DVD burn/verify Stephan von Krawczynski
2003-04-18 14:25 ` Kai Germaschewski
2003-04-19 17:38   ` Stephan von Krawczynski
     [not found]     ` <20030419205000.A3541@skunk.physik.uni-erlangen.de>
2003-04-19 20:23       ` Stephan von Krawczynski
2003-04-19 22:01     ` Alan Cox
2003-04-20 16:18       ` Stephan von Krawczynski
2003-04-20 18:53         ` Alan Cox
2003-05-05 14:23         ` Karsten Keil
2003-05-05 15:32           ` Stephan von Krawczynski
2003-05-05 16:46             ` Karsten Keil
2003-05-05 17:26               ` Stephan von Krawczynski
2003-05-05 18:31                 ` Karsten Keil [this message]
2003-05-06 10:53                 ` Alan Cox
2003-05-06 12:39                   ` Stephan von Krawczynski
2003-05-06 12:56                     ` Alan Cox
2003-05-06 14:01                       ` Stephan von Krawczynski
2003-05-06 16:46                         ` Wolfgang Fritz
2003-05-06 14:13                       ` Mike Dresser
2003-05-06 13:06                     ` Karsten Keil
2003-05-06  9:52             ` Alan Cox

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=20030505183123.GA31871@pingi3.kke.suse.de \
    --to=kkeil@suse.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=kai@tp1.ruhr-uni-bochum.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skraw@ithnet.com \
    /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;
as well as URLs for NNTP newsgroup(s).