public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Krisztian VASAS <iron@ironiq.hu>
To: "Prakash K. Cheemplavam" <prakashpublic@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problem in 2.6.0-test9-mm1 with siimage+hdparm
Date: 05 Nov 2003 23:16:42 +0100	[thread overview]
Message-ID: <1068070602.753.56.camel@localhost.localdomain> (raw)
In-Reply-To: <3FA96CD9.5020403@gmx.de>

On 2003-11-05 Prakash K. Cheemplavam wrote:
> Strange enough I have an Abit NF7-s Rev2.0 as well, but for me the 
> driver works - somehow. I havbe latest bios 1.9 (modified with latest 
> silicon image bios). Since siimage 1.06 drvier. I have DMA without using 
> hdparm, but it is not as fast as in windows. With kernel 2.6 tranfer 
> dropped very much to about 20mb/s (playing with read-aheed didn't help). 
> But I am getting this error messages in dmesg and at boot up (that's why 
> I commented it out in siimage.c):
> 
> hde: sata_error = 0x00000000, watchdog = 0, siimage_mmio_ide_dma_test_irq
> 
> Other than that it runs fine - forgetting that performance it bad right 
> now. Tried various shedulers, but didn't help. With kernel 2.4.22-ac4 I 
> had about 37mb/sec, now only 20mb/sec...

I haven't problem with the speed. I'd like to set up DMA to the disk and
the -d switch (using_dma) causes the panic. With vanilla 2.6.0-test9
everything works fine, no speed problem. But if I boot up with -mm1, I
have to work without DMA on hde. And another interesting thing: hdparm
-d1 /dev/hdd works fine, so the problem is somewhere in the siimage
driver. I don't know exactly what changed, but something has been
corrupted around the driver. 


IroNiQ
-- 
Krisztian VASAS <iron@ironiq.hu>


      reply	other threads:[~2003-11-05 22:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-05 19:26 Problem in 2.6.0-test9-mm1 with siimage+hdparm Krisztian VASAS
2003-11-05 21:34 ` Prakash K. Cheemplavam
2003-11-05 22:16   ` Krisztian VASAS [this message]

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=1068070602.753.56.camel@localhost.localdomain \
    --to=iron@ironiq.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=prakashpublic@gmx.de \
    /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