From: Felipe Balbi <balbi@ti.com>
To: Cliff Brake <cliff.brake@gmail.com>
Cc: Linux OMAP Mailing List <linux-omap@vger.kernel.org>
Subject: Re: musb crash on suspend
Date: Fri, 12 Aug 2011 12:51:16 +0300 [thread overview]
Message-ID: <20110812095115.GS19467@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <CAOd_LFxPcid8rL8v_n6Q0E9u0iV9aKLmbYiVLFXQYoJfkUhB5Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3873 bytes --]
Hi,
On Thu, Jul 28, 2011 at 05:05:13PM -0400, Cliff Brake wrote:
> Hello, I'm running 2.6.39 on omap3530 with a number of patches and am
> seeing the below crash on suspend. Questions:
>
> 1) does anyone have musb suspending with 2.6.39?
> 2) are there any fixes or suggestions?
>
> Thanks,
> Cliff
>
> musb-hdrc musb-hdrc: suspend
> Unhandled fault: external abort on non-linefetch (0x1028) at 0xfa0ab00c
> Internal error: : 1028 [#1] PREEMPT
> last sysfs file: /sys/power/state
> Modules linked in: mac80211 cfg80211
> CPU: 0 Tainted: G W (2.6.39+ #182)
> PC is at musb_save_context+0x14/0x150
> LR is at musb_suspend+0x2c/0x60
> pc : [<c02b18c8>] lr : [<c02b1bd8>] psr: 20000093
> sp : cc26de48 ip : fb020000 fp : c05c34d8
> r10: c06124d4 r9 : 00000000 r8 : 00000002
> r7 : 00000000 r6 : 00000000 r5 : cc8d3e08 r4 : a0000013
> r3 : 00000003 r2 : 00000001 r1 : fa0ab000 r0 : cc9380ec
> Flags: nzCv IRQs off FIQs on Mode SVC_32 ISA ARM Segment user
> Control: 10c5387d Table: 8c014019 DAC: 00000015
> Process sh (pid: 1884, stack limit = 0xcc26c2e8)
> Stack: (0xcc26de48 to 0xcc26e000)
> de40: a0000013 cc8d3e08 00000000 00000000 00000002 00000000
> de60: c06124d4 c02b1bd8 cc842640 c023d948 cc842640 c0240a94 cc8d3e08 cc842640
> de80: 00000000 00000000 cc8d3e08 00000002 00000000 cc8d3e3c c06124d4 c02414cc
> dea0: cc8d3e08 00000002 cc8d3e08 00000000 cc8d3e68 00000002 c05e00d4 c0241918
> dec0: 0bead162 00000007 0bead162 00000007 00000000 00000000 00000003 00000003
> dee0: 00000004 c0413714 00000004 c0506ab1 000a3008 c0090ad4 c0506ab1 00000003
> df00: 00000000 c0090d50 cc10f000 00000003 00000003 c0090364 cc812908 ccb3f818
> df20: cc26df80 c042e650 ccb3f800 00000004 cc820b00 c01e00ec cc812908 c0118350
> df40: 00000004 cc33db40 4006c000 cc26df80 00000004 cc26c000 00000000 c00c4a2c
> df60: cc33db40 4006c000 cc33db40 4006c000 00000000 00000000 00000004 c00c4b60
> df80: 00000000 00000000 00000004 00000000 00000004 4006c000 403525d0 00000004
> dfa0: c003cf68 c003cdc0 00000004 4006c000 00000001 4006c000 00000004 00000000
> dfc0: 00000004 4006c000 403525d0 00000004 00000004 000a33f0 00000001 000a3008
> dfe0: 00000000 beff85c0 40290028 402e332c 60000010 00000001 80000801 10000500
> [<c02b18c8>] (musb_save_context+0x14/0x150) from [<c02b1bd8>]
> (musb_suspend+0x2c/0x60)
> [<c02b1bd8>] (musb_suspend+0x2c/0x60) from [<c023d948>]
> (platform_pm_suspend+0x2c/0x54)
> [<c023d948>] (platform_pm_suspend+0x2c/0x54) from [<c0240a94>] (pm_op+0x4c/0xb4)
> [<c0240a94>] (pm_op+0x4c/0xb4) from [<c02414cc>] (__device_suspend+0x134/0x1f0)
> [<c02414cc>] (__device_suspend+0x134/0x1f0) from [<c0241918>]
> (dpm_suspend_start+0x34c/0x458)
> [<c0241918>] (dpm_suspend_start+0x34c/0x458) from [<c0090ad4>]
> (suspend_devices_and_enter+0x3c/0x1f8)
> [<c0090ad4>] (suspend_devices_and_enter+0x3c/0x1f8) from [<c0090d50>]
> (enter_state+0xc0/0x128)
> [<c0090d50>] (enter_state+0xc0/0x128) from [<c0090364>] (state_store+0xa0/0xb4)
> [<c0090364>] (state_store+0xa0/0xb4) from [<c01e00ec>]
> (kobj_attr_store+0x18/0x1c)
> [<c01e00ec>] (kobj_attr_store+0x18/0x1c) from [<c0118350>]
> (sysfs_write_file+0x108/0x13c)
> [<c0118350>] (sysfs_write_file+0x108/0x13c) from [<c00c4a2c>]
> (vfs_write+0xac/0x134)
> [<c00c4a2c>] (vfs_write+0xac/0x134) from [<c00c4b60>] (sys_write+0x3c/0x68)
> [<c00c4b60>] (sys_write+0x3c/0x68) from [<c003cdc0>] (ret_fast_syscall+0x0/0x30)
> Code: e92d47f0 e3530002 e5901208 0a000005 (e1d130bc)
> ------------[ cut here ]------------
> WARNING: at arch/arm/mach-omap2/omap_l3_smx.c:162 omap3_l3_app_irq+0xf8/0x150()
> In-band Error Error seen by MPU at address 0
quite interesting that you got In-band Error...
oh well, you say it's already fixed, but if you see again errors from
omap3_l3, let us know again ;-)
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
prev parent reply other threads:[~2011-08-12 9:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 21:05 musb crash on suspend Cliff Brake
2011-07-28 21:13 ` Cliff Brake
2011-09-13 14:26 ` Dat
[not found] ` <CAFm6cryzdBT0XF7w3PzGU=BZ0h_T3gF6ogN8ijqv8hd50DE7Gw@mail.gmail.com>
2011-07-28 21:32 ` Cliff Brake
2011-07-29 2:06 ` Felipe Balbi
2011-08-12 9:51 ` Felipe Balbi [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=20110812095115.GS19467@legolas.emea.dhcp.ti.com \
--to=balbi@ti.com \
--cc=cliff.brake@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;
as well as URLs for NNTP newsgroup(s).