public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Christer Bäckström" <cbackstrom@letterboxes.org>
To: linux-kernel@vger.kernel.org
Subject: Re: amd64 cdrom access locks system
Date: Wed, 18 Jan 2006 01:31:32 +0100	[thread overview]
Message-ID: <43CD8C64.4080909@letterboxes.org> (raw)
In-Reply-To: <S1750841AbWAQXWc/20060117232242Z+104@vger.kernel.org>

 > Aric Cyr <Aric.Cyr () gmail ! com> writes:
> > Bartlomiej Zolnierkiewicz <bzolnier <at> gmail.com> writes:
> 
>> 
>> On 6/14/05, Jeff Wiegley <jeffw <at> cyte.com> wrote:
>> > using "dev=/dev/hda" yeilds the exact same behavior...
>> > 
>> >    Jun 14 03:21:50 localhost kernel: ide-cd: cmd 0x3 timed out
>> >    Jun 14 03:21:50 localhost kernel: hda: lost interrupt
>> >    Jun 14 03:22:50 localhost kernel: ide-cd: cmd 0x3 timed out
>> >    Jun 14 03:22:50 localhost kernel: hda: lost interrupt
>> >    Jun 14 03:23:30 localhost kernel: hda: lost interrupt
>> 
>> Jens, any idea?
>> 
>> > And I'm a little confused by Robert's suggestion... Should it
>> > ever be possible for a user-space application to cause lost
>> > interrupts and other kernel state problems regardless of what
>> > "interface" is used?? Sure, if the application uses the wrong
>> > interface it should get spanked somehow but should it be able to
>> > mess up the kernel for other applications as well? (Like now
>> > I can't read or eject.)
>> 
>> It shouldn't be possible unless it is "raw" interface
>> (requires CAP_SYS_RAWIO) w/o checking all possible
>> parameters (it is not always possible) or device is buggy.
>> 
>> Also it is quite unlikely that somebody will fix obsolete
>> interface (hey, it got obsoleted for some reason .
>> 
>> Bartlomiej
>> 
> 
> Has this problem been fixed at all or any workarounds known?  I am having the
> exact same issue with similar hardware and the alim15x3 driver.  In my case it
> does not matter which method I use for cdrecord (ATA:, ATAPI: or dev=/dev/hda),
> I will always get the lost interrupts from the command "cdrecord -atip".  I have
> tried other drives without success so I don't believe that is the problem. 
> Interestingly cdrdao does not have any problems at all and burns perfectly, so I
> suspect that cdrecord might be throwing some command that ide-cd or the IDE
> drive doesn't like and fails to recover from.  However, disabling DMA on the
> drive via hdparm makes cdrecord work perfectly, so I suspect the alim15x3 driver
> more than anything else.  I can play DVDs for hours with DMA enabled just fine
> though... go figure.  My current kernel is 2.6.14-gentoo-r6, but I have had this
> problem since I first had got the system (around 2.6.12).

Exactly the same problems here, on a laptop (Amd64, Mandriva 2006, 
linux-2.6.15) with an:

ALi Corporation M5229 IDE (rev c7)

The cd-writer locks up if the DMA is enabled, as above. But the drive is 
usable if it is disabled.

The only other potential problem I've found is that the UDMA timings for 
the /dev/hda is "???" (see below).

----------------------------------------------
#> cat /proc/ide/ali

                                 Ali M15x3 Chipset.
                                 ------------------
PCI Clock: 0.
CD_ROM FIFO:No , CD_ROM DMA:Yes
FIFO Status: contains 1 Words, runs.

----------------primary channel---------secondary channel---------

channel status:       Off			Off
both channels togth:  Yes			Yes
Channel state:        busy			OK
Add. Setup Timing:    1T			1T
Command Act. Count:   3T			3T
Command Rec. Count:   1T			1T

----------------drive0----------drive1----------drive0----------drive1------

DMA enabled:	Yes		No		Yes		No
FIFO threshold:	4 Words		4 Words		4 Words		4 Words
FIFO mode:	FIFO Off	FIFO Off	FIFO Off	FIFO Off
Dt RW act. Cnt	3T		8T		3T		8T
Dt RW rec. Cnt	1T		16T		1T		16T

-----------------------------------UDMATimings--------------------------------

UDMA:		OK		No		OK		No
UDMA timings:	???		1.5T		2.5T		1.5T

--------------------------------------

> 
> I'm really anxious to track this down so if anyone has any information, or need
> something from me (logs or debugging) please don't hesitate to ask.
> 

The same situation here. I've seen a few reports about this behaviour 
with the alim15x3 driver before, so I just wanted to report my problems 
too. If someone has any idea what's happening I'd be glad to try out any 
patches. Please CC me, as I am not subscribed to the list.

/Chris
> Regards,
>   Aric
> 

       reply	other threads:[~2006-01-18  0:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <S1750841AbWAQXWc/20060117232242Z+104@vger.kernel.org>
2006-01-18  0:31 ` Christer Bäckström [this message]
2006-01-18  9:18   ` amd64 cdrom access locks system 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
2005-08-09  7:47 David C. Young
     [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-06-08  1:09 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
2005-06-14 10:35           ` Jeff Wiegley
2005-06-14 18:16             ` Bartlomiej Zolnierkiewicz
2005-12-15  9:15               ` Aric Cyr

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=43CD8C64.4080909@letterboxes.org \
    --to=cbackstrom@letterboxes.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