public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Hugo Vincent <hugo.vincent@gmail.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: Preempt-RT on OMAP3?
Date: Mon, 6 Apr 2009 19:27:09 -0700	[thread overview]
Message-ID: <200904061927.09627.david-b@pacbell.net> (raw)
In-Reply-To: <5a7b8b7b0904061912i47d9f87fr507816fe3f189ecc@mail.gmail.com>


> > RX DMA is troublesome with the MUSB code, and there are some bugfixes
> > pending which should affect it.  (Posted to linux-usb over the last
> > week or two.)
> >
> > Do these problems show up with DMA disabled?
> 
> I guess you mean with CONFIG_MUSB_PIO_ONLY - yes, I've tried that. I
> don't observe the Rx DMA problems as described previously in that
> configuration, no ........ 

Good...


> However I instead I see hard-lockups with 
> no obvious cause and no messages printed to the console. (The only
> repeatable one I've found so far is exiting cyclictest with ^C. Not
> good). These lockups could well be and probably are unrelated, but
> none-the-less, it's very troubling!

Given the bootlog excerpt you posted, I'm thinking there are
still some basic goofy things with the RT patches you're using
even outside the scope of MUSB.  Basic as in timer tick and
kernel thread setup; lots of things look goofy.


 
> I've uploaded my defconfig here:
> http://hugovincent.com/files/lkml-20090407/
> along with a log of the bootup process. I've enabled a bunch of debug
> options and self-tests. You can see the rather verbose output of some
> spinlock tests (I think) failing early in the bootup process,
> somewhere in timer initialization (I think?).

Those look like lockdep things.  Get a more complete boot log
and maybe someone will be able to sort out what's up.

- Dave



> 
> Regards,
> Hugo
> 
> 



--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-04-07  2:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-06  3:25 Preempt-RT on OMAP3? Hugo Vincent
2009-04-06 10:25 ` David Brownell
2009-04-06 21:53   ` Hugo Vincent
2009-04-06 22:20     ` David Brownell
2009-04-07  2:12       ` Hugo Vincent
2009-04-07  2:27         ` David Brownell [this message]
2009-04-07  2:44           ` Hugo Vincent
2009-04-07  3:36             ` David Brownell
2009-04-07  4:19               ` Hugo Vincent
2009-04-08  1:22                 ` Hugo Vincent
2009-04-08 22:21                   ` David Brownell
2009-04-08 23:34                     ` Hugo Vincent

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=200904061927.09627.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=hugo.vincent@gmail.com \
    --cc=linux-omap@vger.kernel.org \
    /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