public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kenneth Johansson <ken@kenjo.org>
To: linux-kernel@vger.kernel.org
Subject: [BUG] DVD writing in 2.6.6-rc2
Date: Tue, 27 Apr 2004 19:59:33 +0200	[thread overview]
Message-ID: <1083088772.2679.11.camel@tiger> (raw)

I have a problem when using growisofs version 5.19.

The problem is that in the very end when gowisofs tries to flush the
cache. When stracing the process I can see it sits in a call to poll
that never returns. 

I noticed that if I start growisofs and later attach to it with "strace
-p" I can make it continue with killing the strace process. just to see
it hang in the next poll. But re attaching then killing the strace again
a few times and growisofs finally dose a normal exit.

This happens every time. 

The only unusual thing with my setup is that I only have the DVD burner
on the IDE controller no disks so I guess it's some type of missed
interrupt. 

I looked at the drivers/ide/pci/via82cxxx.c but that one did not do much
apart from setting a few configurations so I guess it's some generic
code that dose the real work. 

----------VIA BusMastering IDE Configuration----------------
Driver Version:                     3.38
South Bridge:                       VIA vt8233a
Revision:                           ISA 0x0 IDE 0x6
Highest DMA rate:                   UDMA133
BM-DMA base:                        0x9800
PCI clock:                          33.3MHz
Master Read  Cycle IRDY:            0ws
Master Write Cycle IRDY:            0ws
BM IDE Status Register Read Retry:  yes
Max DRDY Pulse Width:               No limit
-----------------------Primary IDE-------Secondary IDE------
Read DMA FIFO flush:          yes                 yes
End Sector FIFO flush:         no                  no
Prefetch Buffer:               no                  no
Post Write Buffer:             no                  no
Enabled:                      yes                 yes
Simplex only:                  no                  no
Cable Type:                   80w                 80w
-------------------drive0----drive1----drive2----drive3-----
Transfer Mode:        PIO       PIO      UDMA      UDMA
Address Setup:      120ns     120ns     120ns     120ns
Cmd Active:         360ns     360ns      90ns      90ns
Cmd Recovery:       210ns     210ns      30ns      30ns
Data Active:        330ns     330ns      90ns      90ns
Data Recovery:      270ns     270ns      30ns      30ns
Cycle Time:         600ns     600ns      60ns      60ns
Transfer Rate:    3.3MB/s   3.3MB/s  33.3MB/s  33.3MB/s





             reply	other threads:[~2004-04-27 18:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-27 17:59 Kenneth Johansson [this message]
2004-04-27 18:36 ` [BUG] DVD writing in 2.6.6-rc2 Jens Axboe
2004-04-27 22:16   ` Moritz Muehlenhoff
2004-04-28 11:30     ` Jens Axboe
2004-04-28 18:29       ` Kenneth Johansson
2004-04-28 20:09         ` Jens Axboe
2004-04-28 22:13           ` Chris Wedgwood
2004-04-29  6:19             ` Jens Axboe
2004-04-29  6:24               ` Chris Wedgwood
2004-04-29  6:29                 ` Jens Axboe
2004-04-28 19:20       ` Moritz Muehlenhoff
2004-04-27 22:24 ` Panagiotis Papadakos

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=1083088772.2679.11.camel@tiger \
    --to=ken@kenjo.org \
    --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