Hello, Komuro wrote: >> How come ap->lock can get set to bogus address? Can you please printk >> &host->lock and ap->lock after ata_host_alloc() without the patch? > > Here is the output of printk. > Strangely, without the patch, the pata_pcmcia problem happens again.
Ah... super strange. Can you please try to swap memory sticks around and see whether anything changes to rule out bad memory? Another possibility is DMA corrupting the memory and printk makes the timing different and dodges the bullet. Does putting msleep(100) in the pata_pcmcia init_one make any difference? Thanks. -- tejun _______________________________________________ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia
