kdump regression compared to v2.6.35

[Tejun Heo]

Hello,

On 08/29/2010 01:24 PM, CAI Qian wrote:
>> On 08/29/2010 09:01 AM, caiqian at redhat.com wrote:
>>> Further bisect indicated this bad commit from the merge. Given kdump
>>> kernel was running with maxcpus=1, I guess this work caused fs/bio.c
>>> hung in the workqueue on UP. Reverted the whole merge let kdump work
>>> again.
>>
>> Can you please pull from the following git tree and see whether it
>> fixes the problem?  There was a bug in nr_active accounting.
>
> It had the same problem.

I see.  Hmm... a different issue then.  Can you please tell me how to
reproduce the problem?

Thanks.

-- 
tejun