public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Jeff Wiegley <jeffw@cyte.com>
Cc: B.Zolnierkiewicz@elka.pw.edu.pl, linux-kernel@vger.kernel.org,
	akpm@osdl.org, Jens Axboe <axboe@suse.de>
Subject: Re: amd64 cdrom access locks system
Date: Tue, 14 Jun 2005 09:55:08 +0200	[thread overview]
Message-ID: <58cb370e05061400555407d144@mail.gmail.com> (raw)
In-Reply-To: <42ADB5B4.1020704@cyte.com>

[ Jens added to cc: ]

On 6/13/05, Jeff Wiegley <jeffw@cyte.com> wrote:
> Andrew Morton said I should carbon copy the IDE developer on this
> issue so I have in the hopes of re-opening this issue and making
> some progress since I'm still unable to write anything with my
> cd-burner.
> 
> Here's what I know to date:
> 
>     I have the alim15x3 IDE driver installed and running.
>     I do NOT have any of the generic IDE drivers installed or
>        even compiled as they grossly interfere with the alim15x3
>        and cause a kernel panic.
>     My hardware is an AMD64 FX55 in a Shuttle ST20G5 case with a
>        serial ATA harddrive.
>     I'm using a stock 2.6.12-rc6 kernel.
>     Debian unstable distribution.
> 
> At first I can read from the drive fine.
>     For instance I did two "cdparanoia -B -d /dev/hda" without
>     a hitch. Nothing was reported in /var/log/kernel as a result.
> 
> The problem is that I can't write to the drive (burn cds with
> cdrecord) with causing a lost interrupt and then nothing works;
> even reads don't respond.
> 
> When I do:
>     cdrecord -v -tao dev=ATAPI:/dev/hda something.iso
> 
> I get this output:
>    Cdrecord-Clone 2.01.01a01 (x86_64-unknown-linux-gnu) Copyright (C)
> 1995-2004 Joerg Schilling
>    NOTE: this version of cdrecord is an inofficial (modified) release of
> cdrecord
>          and thus may have bugs that are not present in the original
> version.
>          Please send bug reports and support requests to
> <cdrtools@packages.debian.org>.
>          The original author should not be bothered with problems of
> this version.
> 
>    cdrecord: Warning: Running on Linux-2.6.12-rc6-jw14
>    cdrecord: There are unsettled issues with Linux-2.5 and newer.
>    cdrecord: If you have unexpected problems, please try Linux-2.4 or
> Solaris.
>    TOC Type: 1 = CD-ROM
>    scsidev: 'ATAPI:/dev/hda'
>    devname: 'ATAPI:/dev/hda'
>    scsibus: -2 target: -2 lun: -2
>    Warning: Using ATA Packet interface.
>    Warning: The related Linux kernel interface code seems to be
> unmaintained.

^^^

>    Warning: There is absolutely NO DMA, operations thus are slow.

^^^

What is the result of using "dev=/dev/hda" interface instead
(as suggested by Robert)?

Bartlomiej

  reply	other threads:[~2005-06-14  7:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-08  1:09 amd64 cdrom access locks system Jeff Wiegley
2005-06-08 12:23 ` Andrew Morton
2005-06-09 15:36   ` Jeff Wiegley
2005-06-09 23:00     ` Andrew Morton
2005-06-09 19:38       ` Jeff Wiegley
2005-06-09 21:58       ` Jeff Wiegley
2005-06-09 23:32       ` Venkatesh Pallipadi
2005-06-09 18:23         ` Jeff Wiegley
2005-06-13 16:35       ` Jeff Wiegley
2005-06-14  7:55         ` Bartlomiej Zolnierkiewicz [this message]
2005-06-14 10:35           ` Jeff Wiegley
2005-06-14 18:16             ` Bartlomiej Zolnierkiewicz
2005-12-15  9:15               ` Aric Cyr
     [not found] <4d3Xi-33s-31@gated-at.bofh.it>
     [not found] ` <4d7Rk-6fq-49@gated-at.bofh.it>
     [not found]   ` <4dE0F-77V-17@gated-at.bofh.it>
     [not found]     ` <4dEk0-7ua-1@gated-at.bofh.it>
     [not found]       ` <4dJWr-38Z-33@gated-at.bofh.it>
2005-06-11 16:02         ` Robert Hancock
  -- strict thread matches above, loose matches on Subject: below --
2005-08-09  7:47 David C. Young
     [not found] <S1750841AbWAQXWc/20060117232242Z+104@vger.kernel.org>
2006-01-18  0:31 ` Christer Bäckström
2006-01-18  9:18   ` Alan Cox
2006-01-18 12:15     ` Christer Bäckström
2006-01-18 10:01   ` Bartlomiej Zolnierkiewicz
2006-02-05 12:14   ` Erwin Rol

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=58cb370e05061400555407d144@mail.gmail.com \
    --to=bzolnier@gmail.com \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=akpm@osdl.org \
    --cc=axboe@suse.de \
    --cc=jeffw@cyte.com \
    --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