On Tue, 2003-07-08 at 01:02, Benjamin Herrenschmidt wrote:
Weird... Can you try that patch and let me know ?
Ben. The patch worked. I've attached the relavent dmesg. But the Timeout
is still 500 (because I changed that), so if things screw up after
changing to 100, I'll let you know.
Thanks a
On Mon, 2003-07-07 at 05:37, Benjamin Herrenschmidt wrote:
looks like multcount is the key.
Does it work better if you use hdparm to switch multcount back
to 0 ?
On my onboard pmac controller, it either hangs, with lost interrupt
being repeated, or resets ide0.
I thought that it might be
On Mon, 2003-07-07 at 12:06, Menaka Lashitha Bandara wrote:
On Mon, 2003-07-07 at 05:37, Benjamin Herrenschmidt wrote:
looks like multcount is the key.
Does it work better if you use hdparm to switch multcount back
to 0 ?
On my onboard pmac controller, it either hangs, with lost
On Mon, 2003-07-07 at 12:06, Menaka Lashitha Bandara wrote:
On my onboard pmac controller, it either hangs, with lost interrupt
being repeated, or resets ide0.
I thought that it might be because you've changed DMA_TIMEOUT to 100
from 500. When I recompiled with 500 again, it didn't change
On Mon, 2003-07-07 at 21:16, Benjamin Herrenschmidt wrote:
And tell me the messages displayed about the timing register setting ?
Okay Ben. I've compiled the two kernels in question, 2.4.20-ben8-xfs and
2.4.21-ben2-xfs. The relavent dmesg output is attached (ie, of the ide
output). If you need
Weird... Can you try that patch and let me know ?
= drivers/ide/ppc/pmac.c 1.62 vs edited =
--- 1.62/drivers/ide/ppc/pmac.c Mon Jun 16 10:26:40 2003
+++ edited/drivers/ide/ppc/pmac.c Mon Jul 7 17:02:14 2003
@@ -543,7 +543,7 @@
ide_hwif_t *hwif = HWIF(drive);
int
hmmm...
as far as i can tell, the CONFIG_AEC62XX_TUNING option is no longer
there in 2.4.21. the file aec62XX.c has moved (to drivers/ide/pci/) and
is now at version 0.11 (compared to 0.09 in 2.4.21).
well, i reverted back to 2.4.20-ben10 and everything works fine, so
it's not really an
On Sun, 2003-07-06 at 01:36, dorian wrote:
however, in 2.4.21-ben2, the latter option seems to have disapeared and
i get (again) lots of
hdX: dma_timer_expiry: dma status == 0x24
hdX: lost interrupt
hdX: dma_intr: bad DMA status (dma_stat=30)
hdX: dma_intr: status=0x50 { DriveReady
Hi,
Whoops my tree is 2.4.21-ben1 and I just looked in drivers/ide/pci and sure
enough there are actually two aec62xx drivers in that tree (one there and one
in drivers/ide).
So the update to the new driver in ide/pci seems to have broken this driver
for us.
Will you please file a breakage
This is pretty much the same message I got from my built in controller
for my ibook. The hard disks seem to go without DMA, but it's dog slow.
I've been trying to debug this problem, but with little success.
What does your /sbin/hdparm /dev/hdX say?
2.4.21ben2: (lots of lost interrupts)
hi,
i mailed the info to Andre. in the meantime i am going to try to
compile a 2.4.21 kernel with the 0.09 version of the aec62XX.c driver.
greetings,
-dorian
Hi,
Whoops my tree is 2.4.21-ben1 and I just looked in drivers/ide/pci and
sure
enough there are actually two aec62xx drivers in
On Sat, 2003-07-05 at 18:22, Kevin B. Hendricks wrote:
Hi,
Yes the CONFIG_AEC62XX_TUNING *must* be set for that driver to work for ppc.
Without tuning it will not properly work for ppc linux and you get either
partition check problems or:
I wonder what driver you are using...
There is
looks like multcount is the key.
Does it work better if you use hdparm to switch multcount back
to 0 ?
Ben.
Hi,
I was looking at 2.4.21-ben1 and there is a old driver in
drivers/ide/aec62xx.c and one in drivers/ide/pci/aec62xx.[hc]
So I was looking at the old driver source and not the new.
I have both drivers and will try to figure out what changed and is messing us
up and send it to the list.
i got 2.4.20-ben8 to work with my aec6280m by setting
CONFIG_BLK_DEV_AEC62XX=y
CONFIG_AEC62XX_TUNING=y
however, in 2.4.21-ben2, the latter option seems to have disapeared and
i get (again) lots of
hdX: dma_timer_expiry: dma status == 0x24
hdX: lost interrupt
hdX: dma_intr: bad DMA status
Hi,
Yes the CONFIG_AEC62XX_TUNING *must* be set for that driver to work for ppc.
Without tuning it will not properly work for ppc linux and you get either
partition check problems or:
hdX: dma_timer_expiry: dma status == 0x24
hdX: lost interrupt
hdX: dma_intr: bad DMA status (dma_stat=30)
16 matches
Mail list logo
