From: "Prakash K. Cheemplavam" <prakashpublic@gmx.de>
To: Krisztian VASAS <iron@ironiq.hu>, linux-kernel@vger.kernel.org
Subject: Re: Problem in 2.6.0-test9-mm1 with siimage+hdparm
Date: Wed, 05 Nov 2003 22:34:17 +0100 [thread overview]
Message-ID: <3FA96CD9.5020403@gmx.de> (raw)
In-Reply-To: <1068060376.757.44.camel@localhost.localdomain>
Krisztian VASAS wrote:
> Hello all...
>
> I've got an Abit NF7-S v2.0 mainboard with an Athlon XP 2000+ CPU.
>
> Yesterday I've compiled the 2.6.0-test9 kernel with -mm1 patch. My
> system is on the first sata device (/dev/hde).
>
> After reboot I've noticed an Oops after setting dma and other settings
> with hdparm. Without -mm1 patch the machine works well.
>
> After the oops I've tried to find what the problem was.
>
> hdparm -c1 /dev/hde -> nothing was happened, switched off...
> hdparm -d1 /dev/hde -> Oops...
>
> I've got this messages:
>
> hde: DMA timeout retry status error: status=0x58 { DriveReady
> SeekComplete DataRequest }
>
> ide2: reset phy, status=0x00000113 siimage_reset
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...
Prakash
next prev parent reply other threads:[~2003-11-05 21:32 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 [this message]
2003-11-05 22:16 ` Krisztian VASAS
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=3FA96CD9.5020403@gmx.de \
--to=prakashpublic@gmx.de \
--cc=iron@ironiq.hu \
--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