Re: Fwd: CMD 64x regression from 2.6.21 to 2.6.22 and 2.6.23?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello.

Martin Rogge wrote:

   BTW, can you try adding #define DEBUG to the driver meanwhile?..

Yoda said: Try not. Do or do not. There is no try.

   :-)

So I did it. To be precise, I #defined both DEBUG and CMD_DEBUG. However, I am not sure the result is conclusive.

On a good kernel I get a lot of lines of the type

hda: dma_stat: 0x24 irq_stat: 0x44 mask: 0x04
hdc: dma_stat: 0x24 irq_stat: 0x5c mask: 0x10

Yeah, this is what's emitted by the dma_end() method which used CFR/ARTTIM23 PCI config. regs. to chack the interrupt status.

and variations thereof. On a broken kernel the middle part changes to

hda: dma_stat: 0x24 mrdmode: 0x00 mask: 0x04

Hm... this means that the chip doesn't work as documented in the spec, i.e. MRDMODE reg. seems write only, like on older chips. Could you post the output of 'lspci -v'?

Hope this is of any help,

   It is of great help. :-)

cu Martin

MBR, Sergei
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Filesystems]     [Linux SCSI]     [Linux RAID]     [Git]     [Kernel Newbies]     [Linux Newbie]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Samba]     [Device Mapper]

  Powered by Linux