On Fri, Aug 23, 2013 at 7:06 AM, Jaehoon Chung wrote:
> Hi Grant,
>
> I will check this.
Hi Jaehoon! Thanks for looking into this!
Do you have any comments on the problem?
My impression is the mmcqd thread and DW tasklet are racing but I'm
not able to pin down exactly how we end up waiting for
Hi Grant,
I will check this.
Best Regards,
Jaehoon Chung
On 08/22/2013 05:18 AM, Grant Grundler wrote:
> On Mon, Aug 12, 2013 at 4:45 PM, Grant Grundler wrote:
>> I've been working on an "task mmcqd/0:84 blocked for more than 120
>> seconds" panic for the past month or so in the chromeos-3.4 ke
On Mon, Aug 12, 2013 at 4:45 PM, Grant Grundler wrote:
> I've been working on an "task mmcqd/0:84 blocked for more than 120
> seconds" panic for the past month or so in the chromeos-3.4 kernel
> tree. Stack trace below. Feel free to tell me "fixed in v3.x". :)
I've added this change:
diff --git a
I've been working on an "task mmcqd/0:84 blocked for more than 120
seconds" panic for the past month or so in the chromeos-3.4 kernel
tree. Stack trace below. Feel free to tell me "fixed in v3.x". :)
After staring at the 14 MMC and DW driver data structures, I now
think dw_mmc driver is accessing
