Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265860AbUAPUGR (ORCPT ); Fri, 16 Jan 2004 15:06:17 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265855AbUAPUEv (ORCPT ); Fri, 16 Jan 2004 15:04:51 -0500 Received: from smtp5.wanadoo.fr ([193.252.22.26]:49823 "EHLO mwinf0504.wanadoo.fr") by vger.kernel.org with ESMTP id S265846AbUAPUDG convert rfc822-to-8bit (ORCPT ); Fri, 16 Jan 2004 15:03:06 -0500 Message-ID: <4008437C.6040502@wanadoo.fr> Date: Fri, 16 Jan 2004 21:03:08 +0100 From: claude parisot Reply-To: Claude.PARISOT@wanadoo.fr Organization: none User-Agent: Mozilla/5.0 (X11; U; Linux i686; fr-FR; rv:1.5) Gecko/20031107 Debian/1.5-3 X-Accept-Language: en MIME-Version: 1.0 To: Wes Janzen , linux-kernel@vger.kernel.org Subject: Re: DMA problem References: <40083A5F.4060802@wanadoo.fr> <00cc01c3dc67$87fc58b0$02bfa8c0@kuecken> <40084086.7030108@sbcglobal.net> In-Reply-To: <40084086.7030108@sbcglobal.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3874 Lines: 102 Wes Janzen a ?crit : > If those options don't work, you might try dropping down the dma mode by > one. I have a Maxtor drive that does something like that with my > Promise PDC20269 when trying to use UDMA 2, but it works fine in UDMA 1. > > -Wes- I tried it in the bios, all sorts of DMA , but nothing is working .... > > Andreas Unterkircher wrote: > >> Is it possible that your ide-cable can't handle the higher dma speeds >> and makes errors? is it udma compatible? have you looked for a >> firmware update for the burner @ www.plextor.com? >> >> andreas >> >> >> ----- Original Message ----- From: "claude parisot" >> >> To: >> Cc: >> Sent: Friday, January 16, 2004 8:24 PM >> Subject: DMA problem >> >> >> >> >>> Hello ! >>> >>> Sorry to post a seconfd message on the list, I am only trying >>> to get an answern for this - it seems so - DMA-problem ?? >>> >>> >>> I have some >>> problems with a brand new Plextor-drive, PX-W5224TA/T3B, I cannot >>> mount any CD or burn a CDR or CD-RW, except if I disable DMA with >>> following command :# hdparm -d0 /dev/hdd , a little bit annoying, >>> isn't it ? >>> >>> If I insert a cdrom in the drive the led doesn't go out, it flashes >>> as usual but it stays green. >>> >>> It seems to be a DMA-problem or a kernel-bug ??? >>> Its only a supposition, I am a Linux-newbie, and I am looking >>> for an explanation and a solution .... >>> >>> By mounting a cdrom I get following error messages : >>> >>> Jan 11 20:46:00 ishwara kernel: scsi : aborting command due to timeout >>> : pid 102, scsi0, channel 0, id 1, lun 0 0x28 00 00 00 00 10 00 00 01 00 >>> Jan 11 20:46:00 ishwara kernel: hdd: error waiting for DMA >>> Jan 11 20:46:00 ishwara kernel: hdd: dma timeout retry: status=0x7f { >>> DriveReady DeviceFault SeekComplete DataRequest CorrectedError Index >>> Error } Jan 11 20:46:00 ishwara kernel: hdd: dma timeout retry: >>> error=0x7f Jan 11 20:46:00 ishwara kernel: hdd: DMA disabled >>> Jan 11 20:46:00 ishwara kernel: hdd: ATAPI reset complete >>> Jan 11 20:46:00 ishwara kernel: hdd: irq timeout: status=0x80 { Busy } >>> Jan 11 20:46:00 ishwara kernel: hdd: ATAPI reset complete >>> Jan 11 20:46:00 ishwara kernel: hdd: irq timeout: status=0x80 { Busy } >>> Jan 11 20:46:00 ishwara kernel: hdd: ATAPI reset complete >>> Jan 11 20:46:07 ishwara kernel: hdd: irq timeout: status=0x80 { Busy } >>> Jan 11 20:46:07 ishwara kernel: scsi0 channel 0 : resetting for second >>> half of retries. Jan 11 20:46:07 ishwara kernel: SCSI bus is being reset >>> for host 0 channel 0. Jan 11 20:46:07 ishwara kernel: hdd: status >>> timeout: status=0x80 { Busy } Jan 11 20:46:07 ishwara kernel: hdd: drive >>> not ready for command Jan 11 20:46:07 ishwara kernel: hdd: ATAPI reset >>> complete Jan 11 20:46:32 ishwara kernel: scsi : aborting command due to >>> timeout : pid 103, scsi0, channel 0, id 1, lun 0 0x28 00 00 00 00 10 00 >>> rive not ready for command >>> >>> And then I have a freeze or at least a blocking of the sysem. >>> I have to reboot. >>> >>> Could someone give me an explanation of what is happening and a way to >>> solve the problem .... is this a kernel-bug ? Or an incompatibility >>> between the motherboard and the drive ?? >>> >>> If you choose to help me, please don't be to esoteric, as I already >>> said, I am a newbie. >>> >>> Please, could you Cc all answers to the adress : >>> >>> Claude.PARISOT@wanadoo.fr >>> >>> My apologizes for my english .... >>> >>> >>> Claude >>> >>> System : Pentium 2,8C >>> Asus P4P800 DeLuxe >>> Intel I865PE >>> >>> - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/