[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <48743A1A.2010304@gmail.com>
Date: Wed, 09 Jul 2008 13:10:02 +0900
From: Tejun Heo <htejun@...il.com>
To: Komuro <komurojun-mbn@...ty.com>
CC: Jeff Garzik <jeff@...zik.org>,
linux-pcmcia <linux-pcmcia@...ts.infradead.org>,
linux-kernel@...r.kernel.org,
Dominik Brodowski <linux@...inikbrodowski.net>,
linux-ide@...r.kernel.org,
Kristoffer Ericson <kristoffer.ericson@...il.com>,
jgarzik@...hat.com, rjw@...k.pl
Subject: Re: [KERNEL 2.6.26-rc4] bugreport : pata_pcmcia with Sandisk Extreme
III 8GB
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists