Issues with PM Branch

Issues with PM Branch

[Abraham Arce]

Hi,

I am having some hangs using origin/pm branch. SDPs used to test, same
behaviour:

 SDP3430 PROCESSOR BD, ES2.0
 SDP3430 PROCESSOR BD III, OMAP3430 ES3.0 EMU(MT), TWL5030 ES1.0

The commit taken is latest:

 commit	9d76f46e79302058464b569dbad9af8c594dbe53
 author	Roger Quadros <ext-roger.quadros@nokia.com>
 PM: OMAP: Fix build with CONFIG_OMAP_PM_NONE set

If default configuration is used (omap_3430sdp_defconfig) then a
kernel panic will occur:

 <7>Switched to high resolution mode on CPU 0
 <6>musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0
 <1>Unhandled fault: external abort on non-linefetch (0x1028) at 0xd80ab404
 Internal error: : 1028 [#1]
 Modules linked in:
 CPU: 0    Not tainted  (2.6.29-omap1-05686-g9d76f46 #1)
 PC is at musb_platform_init+0x5c/0xf8
 LR is at omap2_clk_enable+0x114/0x184
 pc : [<c001f6d0>]    lr : [<c003b84c>]    psr: 40000013
 sp : c7817d50  ip : 00000001  fp : c7817d64
 r10: 00000000  r9 : c78281f0  r8 : c03ad128
 r7 : c7831240  r6 : c78280d8  r5 : 00000000  r4 : c78280d8
 r3 : d80ab000  r2 : 00000200  r1 : 00000000  r0 : 00000000
 Flags: nZcv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment kernel
 Control: 10c5387d  Table: 80004019  DAC: 00000017
 Process swapper (pid: 1, stack limit = 0xc78162e0)
 Stack: (0xc7817d50 to 0xc7818000)
 ...
 [<c001f674>] (musb_platform_init+0x0/0xf8) from [<c001ecd0>]
(musb_probe+0x244/0xbe8) r5:00000000 r4:c0394db8
 [<c001ea8c>] (musb_probe+0x0/0xbe8) from [<c01c0930>]
(platform_drv_probe+0x20/0x24)
 [<c01c0910>] (platform_drv_probe+0x0/0x24) from [<c01bfb20>]
(driver_probe_device+0xd4/0x180)

If USB is disabled then a hang now will be present in Power Management
for TI OMAP3

 <6>RPC: Registered udp transport module.
 RPC: Registered udp transport module.
 <6>RPC: Registered tcp transport module.
 RPC: Registered tcp transport module.
 <3>Power Management for TI OMAP3.
 Power Management for TI OMAP3.
 <ö

To avoid this last hang going back to the previous commit is needed,
after this, the boot is Ok

 commit 90c3bdfb394ff2ddd87a72defb49c2f2456dd621
 Author: Rajendra Nayak <rnayak@ti.com>
     OMAP3 clock: Update cpufreq driver

If minimal defconfig (omap_3430sdp_min_defconfig) is used, boot will be ok.

Has anyone faced same issue?

Best Regards
Abraham
--
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

Re: Issues with PM Branch

[Kevin Hilman]

Abraham Arce <abraham.arce.moreno@gmail.com> writes:

> Hi,
>
> I am having some hangs using origin/pm branch. SDPs used to test, same
> behaviour:
>
>  SDP3430 PROCESSOR BD, ES2.0
>  SDP3430 PROCESSOR BD III, OMAP3430 ES3.0 EMU(MT), TWL5030 ES1.0
>
> The commit taken is latest:
>
>  commit	9d76f46e79302058464b569dbad9af8c594dbe53
>  author	Roger Quadros <ext-roger.quadros@nokia.com>
>  PM: OMAP: Fix build with CONFIG_OMAP_PM_NONE set
>
> If default configuration is used (omap_3430sdp_defconfig) then a
> kernel panic will occur:
>
>  <7>Switched to high resolution mode on CPU 0
>  <6>musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0
>  <1>Unhandled fault: external abort on non-linefetch (0x1028) at 0xd80ab404
>  Internal error: : 1028 [#1]
>  Modules linked in:
>  CPU: 0    Not tainted  (2.6.29-omap1-05686-g9d76f46 #1)
>  PC is at musb_platform_init+0x5c/0xf8
>  LR is at omap2_clk_enable+0x114/0x184
>  pc : [<c001f6d0>]    lr : [<c003b84c>]    psr: 40000013
>  sp : c7817d50  ip : 00000001  fp : c7817d64
>  r10: 00000000  r9 : c78281f0  r8 : c03ad128
>  r7 : c7831240  r6 : c78280d8  r5 : 00000000  r4 : c78280d8
>  r3 : d80ab000  r2 : 00000200  r1 : 00000000  r0 : 00000000
>  Flags: nZcv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment kernel
>  Control: 10c5387d  Table: 80004019  DAC: 00000017
>  Process swapper (pid: 1, stack limit = 0xc78162e0)
>  Stack: (0xc7817d50 to 0xc7818000)
>  ...
>  [<c001f674>] (musb_platform_init+0x0/0xf8) from [<c001ecd0>]
> (musb_probe+0x244/0xbe8) r5:00000000 r4:c0394db8
>  [<c001ea8c>] (musb_probe+0x0/0xbe8) from [<c01c0930>]
> (platform_drv_probe+0x20/0x24)
>  [<c01c0910>] (platform_drv_probe+0x0/0x24) from [<c01bfb20>]
> (driver_probe_device+0xd4/0x180)
>
> If USB is disabled then a hang now will be present in Power Management
> for TI OMAP3
>
>  <6>RPC: Registered udp transport module.
>  RPC: Registered udp transport module.
>  <6>RPC: Registered tcp transport module.
>  RPC: Registered tcp transport module.
>  <3>Power Management for TI OMAP3.
>  Power Management for TI OMAP3.
>  <ö
>
> To avoid this last hang going back to the previous commit is needed,
> after this, the boot is Ok
>
>  commit 90c3bdfb394ff2ddd87a72defb49c2f2456dd621
>  Author: Rajendra Nayak <rnayak@ti.com>
>      OMAP3 clock: Update cpufreq driver
>
> If minimal defconfig (omap_3430sdp_min_defconfig) is used, boot will be ok.
>
> Has anyone faced same issue?
>

The non-USB related hang looks like the problem when using smartreflex
without SRF.  If you disable smartreflex, or use smartreflex with SRF
you should boot past that hang.

For MUSB, it has not yet been validated on the PM branch.

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

Re: Issues with PM Branch

[Abraham Arce]

> The non-USB related hang looks like the problem when using smartreflex
> without SRF.  If you disable smartreflex, or use smartreflex with SRF
> you should boot past that hang.
>
> For MUSB, it has not yet been validated on the PM branch.

Thanks Kevin... I have disabled SmartReflex, it is booting now but
after some time of interaction, console will become unresponsive,
commands won't be executed

 # ps -aux
 ^C

Is there any setting I should set up before in menuconfig? sysfs?

Abraham
--
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

RE: Issues with PM Branch

[Menon, Nishanth]

> -----Original Message-----
> From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-
> owner@vger.kernel.org] On Behalf Of Abraham Arce
> 
> > The non-USB related hang looks like the problem when using smartreflex
> > without SRF.  If you disable smartreflex, or use smartreflex with SRF
> > you should boot past that hang.
> >
> > For MUSB, it has not yet been validated on the PM branch.
> 
> Thanks Kevin... I have disabled SmartReflex, it is booting now but
> after some time of interaction, console will become unresponsive,
> commands won't be executed
> 
>  # ps -aux
>  ^C
> 
> Is there any setting I should set up before in menuconfig? sysfs?
> 
You may want to check with a ramdisk first -> just to ensure you are not mixing up any NFS server timeouts

Regards,
Nishanth Menon
--
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