public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Gryaznova E." <grev@namesys.botik.ru>
To: Martin Dalecki <dalecki@evision-ventures.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	Reiserfs developers mail-list <Reiserfs-Dev@namesys.com>
Subject: Re: IDE problem: linux-2.5.17
Date: Thu, 23 May 2002 21:48:35 +0400	[thread overview]
Message-ID: <3CED2B73.ABA3C95F@namesys.botik.ru> (raw)
In-Reply-To: <3CECF59B.D471F505@namesys.botik.ru> <3CECFA15.8040707@evision-ventures.com>

I have 40 wires cable. When ide=nodma is passed to 2.5.17 kernel - kernel boots.
Am I correct that it is not possible to have DMA on with such cable?
Is there any reason for doing that?

Note that bus speed is 33 MHz when kernel fails to boot. I mean - how do I specify slower bus speed: 22 MHz?

Thanks.
Lena.

Martin Dalecki wrote:

> Uz.ytkownik Gryaznova E. napisa?:
> > Hello.
> >
> > Kernel starting from 2.5.8 can not boot my Suse 6.4. Booting on those
> > kernels (tested 2.5.8, 2.5.9 and 2.5.17) I am always getting
> >
> > { dma_intr }
> > hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
> > hda: recalibrating!
> >
> > and system either hangs or falls into endless loop.
> >
> > Kernel 2.5.7 boots and works just fine.
> > The boot log containing information about hardware is attached.
> >
> > Badblock does not see any bad blocks.
> >
> > Thanks for any clue on the problem.
> > Lena.
>

[skipped]

> >
> > ------------------------------------------------------------------------
> You just have cabling problems which where previously hidden by
> the driver resorting to slower operation modes.
>
> So please first have a look at the cabling inside your system.
> (First of all plase make sure of course that you are using
> a 80 wirde cable.) Or have a look in to the host chip driver
> and penalize the transfer mode supported to lower speeds.
> You can achieve basically a similar effect by setting
> the busspeed kernel parameter to some artificially high value
> as well.




  reply	other threads:[~2002-05-23 17:40 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-23 13:58 IDE problem: linux-2.5.17 Gryaznova E.
2002-05-23 14:17 ` Martin Dalecki
2002-05-23 17:48   ` Gryaznova E. [this message]
2002-05-23 18:03     ` Tomas Szepe
2002-05-23 18:44       ` Andre Hedrick
2002-05-23 17:49         ` Martin Dalecki
2002-05-23 19:11           ` Andre Hedrick
2002-05-23 19:13           ` Andre Hedrick
2002-05-24 15:05           ` Alan Cox
2002-05-23 22:40         ` Vojtech Pavlik
2002-05-23 18:07     ` Martin Dalecki
2002-05-23 22:42       ` Vojtech Pavlik
2002-05-23 22:37     ` Vojtech Pavlik
2002-05-23 14:27 ` Martin Dalecki
2002-05-23 15:39   ` [reiserfs-dev] " Oleg Drokin
2002-05-23 14:44     ` Martin Dalecki
2002-05-23 16:00       ` Oleg Drokin
2002-05-23 22:52         ` Vojtech Pavlik
2002-05-23 21:47       ` Lionel Bouton
2002-05-23 22:55         ` Vojtech Pavlik
2002-05-24  0:23           ` Lionel Bouton
2002-05-24  1:04             ` Andre Hedrick
2002-05-24  5:56             ` Vojtech Pavlik
2002-05-24  8:53               ` Lionel Bouton
2002-05-24  4:53         ` Oleg Drokin
2002-05-23 22:50       ` Vojtech Pavlik
2002-05-24 11:03         ` Martin Dalecki
2002-05-24 13:15           ` Vojtech Pavlik
2002-05-24 12:15             ` Martin Dalecki
2002-05-24 13:20               ` Vojtech Pavlik
2002-05-24 13:40                 ` Martin Dalecki
2002-05-24 14:54                   ` Vojtech Pavlik
2002-05-23 15:52     ` Tomas Szepe
2002-05-23 16:02       ` Oleg Drokin
2002-05-23 22:45   ` Vojtech Pavlik

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=3CED2B73.ABA3C95F@namesys.botik.ru \
    --to=grev@namesys.botik.ru \
    --cc=Reiserfs-Dev@namesys.com \
    --cc=dalecki@evision-ventures.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