Re: cmd64x: irq 14: nobody cared - system is dreadfully slow

[David Miller <davem@davemloft.net>]

From: Frans Pop <elendil@planet.nl>
Date: Mon, 22 Jun 2009 06:28:36 +0200

> On Monday 22 June 2009, David Miller wrote:
>> +#if 1
>> +	{
>> +		static int times = 0;
>> +
>> +		if (++times <= 32)
> 
> Should this be >=32 maybe?

Yes, it should be >= 32 :-)

> If you really do want the to skip the first 32 and capture the rest, I can 
> still get it, but I'd have to split the printk as it's too wide for my 
> serial console so part gets truncated.

Sure.

> This is what I could get from the *second* series:
> IDE-DEBUG: host->host_flags[0x10] hwif(fffff8003e326800) 
> host->cur_port((null)) 
> hwif->port_ops(cmd648_port_ops+0x0/0xfffffffffffffe54 [cmd64x]) 
> hwif->hand
> 
> Rest is truncated. This first part seemed constant.

The basic gist of the problem seems to be that when the chip is
brought up, the initial request_irq() forces a lingering interrupt
status in the chip to have somewhere to go.

But the IDE layer refuses to do something to clear it because it's
not expecting any interrupts (this is the: cur_port != hwif).

Some things other than the commit in question have changed in the area
of interrupt and chip initialization and I'll try to go through
the commits to get some clues.

Thanks!