linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sedat Dilek <sedat.dilek@googlemail.com>
To: Tomoya MORINAGA <tomoya-linux@dsn.okisemi.com>
Cc: linux-next <linux-next@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Randy Dunlap <randy.dunlap@oracle.com>,
	Vinod Koul <vinod.koul@intel.com>,
	Toshiharu Okada <toshiharu-linux@dsn.okisemi.com>
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	[thread overview]
Message-ID: <AANLkTimhvxO=5GOenagc=F2hyzt-7yLSgDhQbWVuffsD@mail.gmail.com> (raw)
In-Reply-To: <641556B1566641C0A286D4F2F1383DAD@hacdom.okisemi.com>

On Fri, Mar 25, 2011 at 1:08 AM, Tomoya MORINAGA
<tomoya-linux@dsn.okisemi.com> wrote:
> Hi  Sedat,
>
> 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 before.
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])
>
>

      reply	other threads:[~2011-03-25  1:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-24 10:25 linux-next: Tree for March 24 (BUG: soft lockup - CPU#0 stuck for 63s! [kworker/0:1:7764]) Sedat Dilek
2011-03-24 15:09 ` Sedat Dilek
2011-03-25  0:08   ` Tomoya MORINAGA
2011-03-25  1:40     ` Sedat Dilek [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='AANLkTimhvxO=5GOenagc=F2hyzt-7yLSgDhQbWVuffsD@mail.gmail.com' \
    --to=sedat.dilek@googlemail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=sedat.dilek@gmail.com \
    --cc=sfr@canb.auug.org.au \
    --cc=tomoya-linux@dsn.okisemi.com \
    --cc=toshiharu-linux@dsn.okisemi.com \
    --cc=vinod.koul@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).