From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sedat Dilek Subject: Re: linux-next: Tree for March 24 (BUG: soft lockup - CPU#0 stuck for 63s! [kworker/0:1:7764]) Date: Fri, 25 Mar 2011 02:40:57 +0100 Message-ID: References: <641556B1566641C0A286D4F2F1383DAD@hacdom.okisemi.com> Reply-To: sedat.dilek@gmail.com Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from mail-qy0-f174.google.com ([209.85.216.174]:63503 "EHLO mail-qy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932206Ab1CYBk6 convert rfc822-to-8bit (ORCPT ); Thu, 24 Mar 2011 21:40:58 -0400 In-Reply-To: <641556B1566641C0A286D4F2F1383DAD@hacdom.okisemi.com> Sender: linux-next-owner@vger.kernel.org List-ID: To: Tomoya MORINAGA Cc: linux-next , LKML , Stephen Rothwell , Randy Dunlap , Vinod Koul , Toshiharu Okada On Fri, Mar 25, 2011 at 1:08 AM, Tomoya MORINAGA wrote: > Hi =C2=A0Sedat, > > We have used this DMA driver(include this patch) on linux-2.6.35/37. > However I haven't seen the issue yet. > > I want to know more information. > Do you mean that it takes 63 more seconds for boot-completing > when using this patch and pch_dma is integrated as built-in ? > > Thanks, > ----------------------------------------- > Tomoya MORINAGA > OKI SEMICONDUCTOR CO., LTD. > I jumped back to the kernel from which I thought it was making problems and run it several hours. Unfortunately, I haven't seen any call-traces in the syslogs like befor= e. So, I could reproduce the errors. I am sorry for the noise abd will have an eye on the issue. ( So, reverting the patch did not really helped. ) - Sedat - >> -----Original Message----- >> From: Sedat Dilek [mailto:sedat.dilek@googlemail.com] >> Sent: Friday, March 25, 2011 12:10 AM >> To: linux-next; LKML >> Cc: Stephen Rothwell; Randy Dunlap; Vinod Koul; Tomoya MORINAGA >> Subject: Re: linux-next: Tree for March 24 (BUG: soft lockup >> - CPU#0 stuck for 63s! [kworker/0:1:7764]) > >