public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: DOSProfi <DOSProfi@web.de>
To: Claude.PARISOT@wanadoo.fr
Cc: linux-kernel@vger.kernel.org
Subject: Re: DMA problem
Date: Fri, 16 Jan 2004 22:03:51 +0100	[thread overview]
Message-ID: <200401162203.51615.DOSProfi@web.de> (raw)
In-Reply-To: <40083EAB.2070906@wanadoo.fr>

I don't know if this works, but I have found a new BIOS for that board:

http://www.asus.com.tw/support/download/item.aspx?ModelName=P4P800

In the notes are many "DMA"s inside.



On Friday 16 January 2004 20:42, claude parisot wrote:
> Andreas Unterkircher a écrit :
> > 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?
>
> Firmware is up to date ....
> I tried it with an other cable , UDMA 100 certified,
> I tried all kind of things, putting the drive as master
> but nothing has worked till yet.
>
>
> Thanks for your answer
>
>   also zu Deutsch - sprech' ich viel besser als Englisch.
>
>
> mfG
>
> Claude
>
> > andreas
> >
> >
> > ----- Original Message -----
> > From: "claude parisot" <Claude.PARISOT@wanadoo.fr>
> > To: <linux-kernel@vger.kernel.org>
> > Cc: <Claude.PARISOT@wanadoo.fr>
> > 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/
>
> -
> 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/


  reply	other threads:[~2004-01-16 20:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-16 19:24 DMA problem claude parisot
2004-01-16 19:32 ` Andreas Unterkircher
2004-01-16 19:42   ` claude parisot
2004-01-16 21:03     ` DOSProfi [this message]
2004-01-16 20:18       ` claude parisot
2004-01-16 19:50   ` Wes Janzen
2004-01-16 20:03     ` claude parisot
  -- strict thread matches above, loose matches on Subject: below --
2004-01-16 20:45 DOSProfi

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=200401162203.51615.DOSProfi@web.de \
    --to=dosprofi@web.de \
    --cc=Claude.PARISOT@wanadoo.fr \
    --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