From: Kevin Hilman <khilman@deeprootsystems.com>
To: Cliff Brake <cliff.brake@gmail.com>
Cc: rt-users <linux-rt-users@vger.kernel.org>,
Linux OMAP Users <linux-omap@vger.kernel.org>
Subject: Re: RT tests on OMAP3
Date: Thu, 03 Sep 2009 07:28:00 -0700 [thread overview]
Message-ID: <87tyzkw1an.fsf@deeprootsystems.com> (raw)
In-Reply-To: <f96d234e0908312018j5f36d6e1s95319f4669105d06@mail.gmail.com> (Cliff Brake's message of "Mon\, 31 Aug 2009 23\:18\:33 -0400")
Cliff Brake <cliff.brake@gmail.com> writes:
> On Mon, Aug 31, 2009 at 11:16 PM, Cliff Brake<cliff.brake@gmail.com> wrote:
>
>> Applying
>>
>> http://cgit.openembedded.org/cgit.cgi/openembedded/diff/recipes/linux/linux-omap-2.6.29/0001-implement-TIF_RESTORE_SIGMASK-support-and-enable-the.patch?id=1f0d91e152f16fbd40bb2fb3c44a30d774d4dede
>>
>> Seems to fix or mask the udev problems. But, with preempt-rt, and
>> EHCI enabled, I still get messages continually scrolling:
>
> A few more notes, the above patch is not required to make the PXA270
> work. Without EHCI enabled, the system boots and performs fairly
> normal (I'm able to log in, etc).
This looks to me like a case of poor (or non-existent) locking in the
USB/EHCI driver, resulting in some corruption since the PC is at a
bogus address (0x14).
Does your PXA270 use the same EHCI driver? I assume not.
I've been using -rt on a basic OMAP3 kernel, but have not enabled
EHCI so haven't seen this.
Might be useful to enable some of the in-kernel lock debugging to
see if it turns up anything.
Kevin
--
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
next prev parent reply other threads:[~2009-09-03 14:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-31 20:50 RT tests on OMAP3 Cliff Brake
2009-09-01 3:16 ` Cliff Brake
2009-09-01 3:18 ` Cliff Brake
2009-09-03 14:28 ` Kevin Hilman [this message]
2009-09-03 20:57 ` Cliff Brake
2009-09-14 17:50 ` Kevin Hilman
2009-09-03 14:44 ` Koen Kooi
2009-09-03 16:02 ` Cliff Brake
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=87tyzkw1an.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=cliff.brake@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-rt-users@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.