From: Felipe Balbi <balbi@ti.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Felipe Balbi <balbi@ti.com>, linux-omap@vger.kernel.org
Subject: Re: Panda: USB crash with today's linux-next
Date: Mon, 14 May 2012 15:15:28 +0300 [thread overview]
Message-ID: <20120514121527.GF22242@arwen.pp.htv.fi> (raw)
In-Reply-To: <1336996151.2333.3.camel@deskari>
[-- Attachment #1: Type: text/plain, Size: 3977 bytes --]
Hi,
On Mon, May 14, 2012 at 02:49:11PM +0300, Tomi Valkeinen wrote:
> Hi Felipe,
>
> I'm seeing the following crash on Panda, when booting with today's
> linux-next, using the attached config.
>
> Tomi
>
>
> [ 1.923400] musb-hdrc: version 6.0, ?dma?, otg (peripheral+host)
> [ 1.923400] Unable to handle kernel NULL pointer dereference at virtual address 00000036
> [ 1.938171] pgd = c0004000
> [ 1.941009] [00000036] *pgd=00000000
> [ 1.944763] Internal error: Oops: 5 [#1] SMP ARM
> [ 1.949584] Modules linked in:
> [ 1.952789] CPU: 0 Not tainted (3.4.0-rc7-next-20120514-10436-g7769ab8 #450)
> [ 1.960540] PC is at kobject_get+0xc/0x4c
> [ 1.964721] LR is at get_device+0x14/0x1c
> [ 1.968933] pc : [<c0250d60>] lr : [<c02ac47c>] psr: 20000113
> sp : ebc31d98 ip : 00000003 fp : eb36d1dc
> [ 1.979553] r10: eb36c128 r9 : eb349880 r8 : fc0ab000
> [ 1.985015] r7 : eb348408 r6 : c06f2830 r5 : eb348408 r4 : 0000001a
> [ 1.991851] r3 : eb349880 r2 : 00000000 r1 : c04bf2b4 r0 : 0000001a
> [ 1.998687] Flags: nzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel
> [ 2.006317] Control: 10c53c7d Table: 8000404a DAC: 00000017
> [ 2.012329] Process swapper/0 (pid: 1, stack limit = 0xebc302f8)
> [ 2.018615] Stack: (0xebc31d98 to 0xebc32000)
> [ 2.023162] 1d80: eb349880 c0c788f4
> [ 2.031707] 1da0: eb348408 c02ac47c eb349880 c033d604 eb36c128 c035bdc8 c035bdb0 0000007c
> [ 2.040283] 1dc0: eb348400 00000010 eb348408 c047dddc ebeba630 00000000 c0c76fd8 eb348408
> [ 2.048828] 1de0: c0c76fd8 c0c76fe8 00000000 c071c0ac 00000000 c0728b80 0000009e c02b0e68
> [ 2.057373] 1e00: c02b0e50 c02afab8 c02b10f0 eb348408 c02afcd0 00000000 00000000 c0c76f94
> [ 2.065948] 1e20: c0728b80 c02ae1dc ebc412d8 ebebbe94 eb348408 eb34843c c070fbc0 c02af9dc
> [ 2.074493] 1e40: eb348408 eb348408 c070fbc0 c02aefb8 eb348408 eb348410 ebd7c808 c02ad840
> [ 2.083038] 1e60: c06f8438 00000000 ebebbd78 eb3498c0 ebebbd40 c0690444 00000000 eb348400
> [ 2.091583] 1e80: eb348408 00000003 eb3498c0 ebebbd40 c0690444 c0728b80 0000009e c02b1480
> [ 2.100158] 1ea0: eb348400 00000000 ebd7c808 eb3498c0 ebd7dd00 c047e7a0 ebd7c808 c0c76fd8
> [ 2.108703] 1ec0: c0c76fe8 00000000 c071c16c c02b0e68 c02b0e50 c02afab8 22222222 ebd7c808
> [ 2.117248] 1ee0: c071c16c ebd7c83c 00000000 c067882c c0728b80 c02afccc c071c16c c02afc38
> [ 2.125793] 1f00: 00000000 c02ae258 ebc412a8 ebd76790 c071c16c c070fbc0 ebebbdc0 c02af16c
> [ 2.134368] 1f20: c0598c20 00000000 ebc489c0 c071c16c c0728b80 ebc30000 00000000 c067882c
> [ 2.142913] 1f40: c0690444 c0728b80 0000009e c02b0200 00000000 c0678844 c0728b80 ebc30000
> [ 2.151458] 1f60: 00000000 c067882c c0728b80 c0008730 c061fe04 c06207e4 c149014e c066dbe4
> [ 2.160003] 1f80: c0678850 00000000 c05dc310 00000001 00000006 00000006 c058cec4 c0678844
> [ 2.168579] 1fa0: 0000001c 00000006 c0678850 c067882c c0690444 c0728b80 0000009e c0647928
> [ 2.177124] 1fc0: 00000006 00000006 c06471c4 00000000 00000000 00000000 c0647810 c0014f34
> [ 2.185668] 1fe0: 00000013 00000000 00000000 00000000 00000000 c0014f34 81aaaa8a 3a80a8aa
> [ 2.194244] [<c0250d60>] (kobject_get+0xc/0x4c) from [<c02ac47c>] (get_device+0x14/0x1c)
> [ 2.202697] [<c02ac47c>] (get_device+0x14/0x1c) from [<c033d604>] (usb_get_transceiver+0x1c/0x28)
> [ 2.212005] [<c033d604>] (usb_get_transceiver+0x1c/0x28) from [<c035bdc8>] (omap2430_musb_init+0x
> 18/0x184)
> [ 2.222106] [<c035bdc8>] (omap2430_musb_init+0x18/0x184) from [<c047dddc>] (musb_probe+0x1bc/0x5a
> 0)
> [ 2.231567] [<c047dddc>] (musb_probe+0x1bc/0x5a0) from [<c02b0e68>] (platform_drv_probe+0x18/0x1c
looks like MUSB is probing before transceiver driver... could it be ?
Can you check transceiver has actually probed ? I guess panda's using
twl6030-usb.c
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next parent reply other threads:[~2012-05-14 12:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1336996151.2333.3.camel@deskari>
2012-05-14 12:15 ` Felipe Balbi [this message]
2012-05-14 12:24 ` Panda: USB crash with today's linux-next Tomi Valkeinen
2012-05-14 12:29 ` Felipe Balbi
2012-05-14 12:47 ` Felipe Balbi
2012-05-14 17:06 ` Cousson, Benoit
2012-05-14 17:58 ` Felipe Balbi
2012-05-14 18:14 ` Tony Lindgren
2012-05-14 18:37 ` Tony Lindgren
2012-05-14 19:35 ` Felipe Balbi
2012-05-15 20:14 ` Tony Lindgren
2012-05-16 8:39 ` Felipe Balbi
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=20120514121527.GF22242@arwen.pp.htv.fi \
--to=balbi@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=tomi.valkeinen@ti.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