From: David Brownell <david-b@pacbell.net>
To: Steve Sakoman <sakoman@gmail.com>
Cc: "linux-omap@vger.kernel.org List" <linux-omap@vger.kernel.org>
Subject: Re: Current git head oops'es at boot on Overo
Date: Mon, 6 Oct 2008 12:53:13 -0700 [thread overview]
Message-ID: <200810061253.13997.david-b@pacbell.net> (raw)
In-Reply-To: <5e088bd90810061126g75ff7768k8fa768751a31e379@mail.gmail.com>
On Monday 06 October 2008, Steve Sakoman wrote:
> Build is stock 62c36fdd962de2db5d62a326490913f41c442a5c, no additional patches.
>
> Without DEBUG_LL, boot silently fails. With DEBUG_LL, one can see that
> the failure is due to a NULL pointer dereference in musb.
>
> I suspect that the root cause is related to:
>
> <3>i2c_omap i2c_omap.1: controller timed out
> <4>twl4030_usb: probe of twl4030_usb failed with error -22
>
> Adding David Brownell's i2c-omap timeout workaround patch eliminates
> this error
Right. I'd suggest merging that, except that would provide
zero incentive to actually fix the i2c-omap problem.
And I *have* seen those timeout errors on other requests...
> and the boot then fails on EHCI.
>
> I disabled EHCI in defconfig and was able to get the boot to complete.
Ditto. I suspect one of those no-timeout busy-waits is just
neglecting to complete... :(
> However unlike others, I find that musb is not functional -- and the
> trick of disconnecting the USB cable and then reconnecting it does not
> work.
I observed the same thing. More specifically, no IRQs arrive at
the twl4030-usb driver.
The *very same kernel* works fine on Beagle... is there something
different about the USB setup that might explain this?
- Dave
next prev parent reply other threads:[~2008-10-06 19:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-06 18:26 Current git head oops'es at boot on Overo Steve Sakoman
2008-10-06 19:53 ` David Brownell [this message]
2008-10-06 21:04 ` Steve Sakoman
2008-10-06 21:15 ` Nathan Monson
2008-10-06 21:39 ` David Brownell
2008-10-06 21:57 ` Steve Sakoman
2008-10-06 21:34 ` David Brownell
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=200810061253.13997.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-omap@vger.kernel.org \
--cc=sakoman@gmail.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