FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Ubuntu > Ubuntu Kernel Team

 
 
LinkBack Thread Tools
 
Old 10-09-2012, 10:31 AM
Paolo Pisati
 
Default fix usb on omap3

This bug is actually a twofold problem:

1) config for our omap kernel had a problem

enabling USB_[EHCI|OHCI]_HCD_PLATFORM we actually overwrote the OMAP EHCI/OHCI bits:

/home/ppisati/ubuntu-quantal/drivers/usb/host/ehci-hcd.c:1394:0: warning: "PLATFORM_DRIVER" redefined [enabled by default]
/home/ppisati/ubuntu-quantal/drivers/usb/host/ehci-hcd.c:1289:0: note: this is the location of the previous definition

drivers/usb/host/ehci-hcd.c:

1289:
#ifdef CONFIG_USB_EHCI_HCD_OMAP
#include "ehci-omap.c"
#define PLATFORM_DRIVER ehci_hcd_omap_driver
#endif

1394:
#ifdef CONFIG_USB_EHCI_HCD_PLATFORM
#include "ehci-platform.c"
#define PLATFORM_DRIVER ehci_platform_driver
#endif

and later in ehci_init():

#ifdef PLATFORM_DRIVER
retval = platform_driver_register(&PLATFORM_DRIVER);
if (retval < 0)
goto clean0;
#endif

While here add an enforce rule so we won't enable them ever again.

2) upstream broke ehci implementation since 3.5 (and it's still broken ATM)

Since the 3.5 tree, usb ehci for omap3 has been plagued with problems up to the point that it was disabled upstream:

[flag@newluxor linux-2.6]$ git show 06b4ba5
commit 06b4ba529528fbf9c24ce37b7618f4b0264750e2
Author: Kevin Hilman <khilman@ti.com>
Date: Fri Jul 6 11:20:28 2012 -0700

ARM: OMAP2+: omap2plus_defconfig: EHCI driver is not stable, disable it

The EHCI driver is not stable enough to be enabled by default. In v3.5,
it has at least the following problems:

- warning dump during bootup
- hang during suspend
- prevents CORE powerdomain from entering retention during idle (even
when no USB devices connected.)

This demonstrates that this driver has not been thoroughly tested and
therfore should not be enabled in the default defconfig.

In addition, the problems above cause new PM regressions which need be
addressed before this driver should be enabled in the default
defconfig.

Signed-off-by: Kevin Hilman <khilman@ti.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>

and lately this situation has spiraled down to the point where enabling it at boot triggers an oops and a subsequent dead usb hub:

vanilla 3.5 omap2plus_defconfig + ehci:

...
[ 4.200103] omap_wdt: OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec
[ 4.208526] twl4030_wdt twl4030_wdt: Failed to register misc device
[ 4.215240] twl4030_wdt: probe of twl4030_wdt failed with error -16
[ 4.225860] omap_hsmmc omap_hsmmc.0: Failed to get debounce clk
[ 4.262084] hub 1-0:1.0: state 7 ports 3 chg 0004 evt 0000
[ 4.267913] hub 1-0:1.0: port 2, status 0501, change 0000, 480 Mb/s
[ 4.332305] platform ehci-omap.0: port 2 reset complete, port enabled
[ 4.339050] platform ehci-omap.0: GetStatus port:2 status 001005 0 ACK POWER sig=se0 PE CONNECT
[ 4.410400] Unable to handle kernel NULL pointer dereference at virtual address 00000000
[ 4.418884] pgd = c0004000
[ 4.421722] [00000000] *pgd=00000000
[ 4.425476] Internal error: Oops: 5 [#1] SMP ARM
[ 4.430297] Modules linked in:
[ 4.433471] CPU: 0 Not tainted (3.5.0 #16)
[ 4.438110] PC is at hub_port_init+0x28c/0x968
[ 4.442749] LR is at hub_port_init+0xc4/0x968
[ 4.447296] pc : [<c030b2bc>] lr : [<c030b0f4>] psr: 60000013
[ 4.447296] sp : df905eb8 ip : c05a9eb4 fp : 00000000
[ 4.459259] r10: 00000000 r9 : df306400 r8 : 00000032
[ 4.464691] r7 : df30ac00 r6 : 00000002 r5 : 00000000 r4 : df2a7400
[ 4.471496] r3 : 00000000 r2 : c059e324 r1 : c059e348 r0 : df2a7468
[ 4.478302] Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel
[ 4.485900] Control: 10c5387d Table: 80004019 DAC: 00000017
[ 4.491912] Process khubd (pid: 236, stack limit = 0xdf9042f8)
[ 4.497985] Stack: (0xdf905eb8 to 0xdf906000)
[ 4.502532] 5ea0: 00000002 df306400
[ 4.511047] 5ec0: 00000002 00000000 00000004 c008a078 00000001 00000002 00000003 df300400
[ 4.519561] 5ee0: 00000000 c044acb0 00000001 df2a7400 df30ac00 df300400 df300418 df306400
[ 4.528106] 5f00: 00000002 00000000 00000002 c030eb30 00000501 00000000 c059f090 c0656600
[ 4.536621] 5f20: 107e9dd6 00000000 df306408 df30a820 df30ac9c df30a800 00000004 df306401
[ 4.545135] 5f40: df306470 df30ac00 df306468 df30ac00 df30a820 df300400 00000009 c0065144
[ 4.553680] 5f60: 00000000 df904000 00000000 df88c100 c005cff4 df905f74 df905f74 00000000
[ 4.562194] 5f80: 00000501 c008a078 df82ff20 df82fef8 00000000 c030e4c0 00000013 00000000
[ 4.570709] 5fa0: 00000000 00000000 00000000 c005c8f8 00000000 00000000 00000000 00000000
[ 4.579254] 5fc0: 00000000 dead4ead ffffffff ffffffff c0700330 00000000 00000000 c0561550
[ 4.587768] 5fe0: df905fe0 df905fe0 df82fef8 c005c874 c0014154 c0014154 00000000 00000000
[ 4.596313] [<c030b2bc>] (hub_port_init+0x28c/0x968) from [<c030eb30>] (hub_thread+0x670/0x13d8)
[ 4.605468] [<c030eb30>] (hub_thread+0x670/0x13d8) from [<c005c8f8>] (kthread+0x84/0x90)
[ 4.613922] [<c005c8f8>] (kthread+0x84/0x90) from [<c0014154>] (kernel_thread_exit+0x0/0x8)
[ 4.622619] Code: e59f2690 e5933080 e2840068 e59f1688 (e593e000)
[ 4.629089] ---[ end trace 6fcdeaed28ce1f31 ]---
[ 4.790161] usbcore: registered new interface driver usbhid
...

ATM there's no activity upstream to resolve this bug in a sound way but a patch was posted to linux-omap that resolves it:

http://www.mail-archive.com/linux-omap@vger.kernel.org/msg73115.html

While it's not upstream, the patch touches only omap3 clock code so it's safe for all the other flavours and it's the only
option we have right now.

The aforementioned patch coupled with disabling the generic ehci/ohci driver implementation fix the usb bus on omap3.

BugLink: http://bugs.launchpad.net/bugs/1061599

Paolo Pisati (3):
UBUNTU: SAUCE: omap3 clocks .dev_id = NULL
UBUNTU: [Config] disable USB_[EHCI|OHCI]_HCD_PLATFORM
UBUNTU: [Config] enforce USB_[EHCI|OHCI]_HCD_PLATFORM=n on arm[el|hf]

arch/arm/mach-omap2/clock3xxx_data.c | 20 ++++++++++----------
debian.master/config/amd64/config.common.amd64 | 4 ++++
debian.master/config/armel/config.common.armel | 4 ++++
debian.master/config/armhf/config.common.armhf | 2 ++
debian.master/config/armhf/config.flavour.highbank | 2 ++
debian.master/config/armhf/config.flavour.omap | 2 ++
debian.master/config/config.common.ubuntu | 4 ----
debian.master/config/enforce | 3 +++
debian.master/config/i386/config.common.i386 | 4 ++++
debian.master/config/powerpc/config.common.powerpc | 4 ++++
debian.master/config/ppc64/config.common.ppc64 | 4 ++++
11 files changed, 39 insertions(+), 14 deletions(-)

--
1.7.10.4


--
kernel-team mailing list
kernel-team@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kernel-team
 
Old 10-09-2012, 11:43 AM
Andy Whitcroft
 
Default fix usb on omap3

On Tue, Oct 09, 2012 at 12:31:26PM +0200, Paolo Pisati wrote:

> and lately this situation has spiraled down to the point where enabling it at boot triggers an oops and a subsequent dead usb hub:
>
> vanilla 3.5 omap2plus_defconfig + ehci:
>
> ...
> [ 4.200103] omap_wdt: OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec
> [ 4.208526] twl4030_wdt twl4030_wdt: Failed to register misc device

Does this imply that the kernel as it is in the archive will panic on
boot due to the USB hub? If so I assume that is generally fatal as that
is where your disks are likely to be?

-apw

--
kernel-team mailing list
kernel-team@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kernel-team
 
Old 10-09-2012, 11:52 AM
Paolo Pisati
 
Default fix usb on omap3

On 10/09/2012 01:43 PM, Andy Whitcroft wrote:

On Tue, Oct 09, 2012 at 12:31:26PM +0200, Paolo Pisati wrote:


and lately this situation has spiraled down to the point where enabling it at boot triggers an oops and a subsequent dead usb hub:

vanilla 3.5 omap2plus_defconfig + ehci:

...
[ 4.200103] omap_wdt: OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec
[ 4.208526] twl4030_wdt twl4030_wdt: Failed to register misc device


Does this imply that the kernel as it is in the archive will panic on
boot due to the USB hub? If so I assume that is generally fatal as that
is where your disks are likely to be?


in our case (different config&c) the usb is simply dead (no panic): it
won't recognize any usb devices attached to it. in my case, with my
beagle, i boot off the sd only (i leave the usb disk for my omap4) but
yes is still a fatal IMO since these boards have evreyrhing attached to
the usb bus.


the problem with omap3 is that no one is actually using it for real in
our community (everyone moved to omap4) and people that do some testing
use the emulated beagle via qemu (that didn't show this bug), i stumbled
on this bug last week when i tried Q by myself.

--
bye,
p.

--
kernel-team mailing list
kernel-team@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kernel-team
 
Old 10-09-2012, 12:32 PM
Stefan Bader
 
Default fix usb on omap3

On 09.10.2012 12:31, Paolo Pisati wrote:
> This bug is actually a twofold problem:
>
> 1) config for our omap kernel had a problem
>
> enabling USB_[EHCI|OHCI]_HCD_PLATFORM we actually overwrote the OMAP EHCI/OHCI bits:
>
> /home/ppisati/ubuntu-quantal/drivers/usb/host/ehci-hcd.c:1394:0: warning: "PLATFORM_DRIVER" redefined [enabled by default]
> /home/ppisati/ubuntu-quantal/drivers/usb/host/ehci-hcd.c:1289:0: note: this is the location of the previous definition
>
> drivers/usb/host/ehci-hcd.c:
>
> 1289:
> #ifdef CONFIG_USB_EHCI_HCD_OMAP
> #include "ehci-omap.c"
> #define PLATFORM_DRIVER ehci_hcd_omap_driver
> #endif
>
> 1394:
> #ifdef CONFIG_USB_EHCI_HCD_PLATFORM
> #include "ehci-platform.c"
> #define PLATFORM_DRIVER ehci_platform_driver
> #endif
>
> and later in ehci_init():
>
> #ifdef PLATFORM_DRIVER
> retval = platform_driver_register(&PLATFORM_DRIVER);
> if (retval < 0)
> goto clean0;
> #endif
>
> While here add an enforce rule so we won't enable them ever again.
>
> 2) upstream broke ehci implementation since 3.5 (and it's still broken ATM)
>
> Since the 3.5 tree, usb ehci for omap3 has been plagued with problems up to the point that it was disabled upstream:
>
> [flag@newluxor linux-2.6]$ git show 06b4ba5
> commit 06b4ba529528fbf9c24ce37b7618f4b0264750e2
> Author: Kevin Hilman <khilman@ti.com>
> Date: Fri Jul 6 11:20:28 2012 -0700
>
> ARM: OMAP2+: omap2plus_defconfig: EHCI driver is not stable, disable it
>
> The EHCI driver is not stable enough to be enabled by default. In v3.5,
> it has at least the following problems:
>
> - warning dump during bootup
> - hang during suspend
> - prevents CORE powerdomain from entering retention during idle (even
> when no USB devices connected.)
>
> This demonstrates that this driver has not been thoroughly tested and
> therfore should not be enabled in the default defconfig.
>
> In addition, the problems above cause new PM regressions which need be
> addressed before this driver should be enabled in the default
> defconfig.
>
> Signed-off-by: Kevin Hilman <khilman@ti.com>
> Signed-off-by: Tony Lindgren <tony@atomide.com>
>
> and lately this situation has spiraled down to the point where enabling it at boot triggers an oops and a subsequent dead usb hub:
>
> vanilla 3.5 omap2plus_defconfig + ehci:
>
> ...
> [ 4.200103] omap_wdt: OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec
> [ 4.208526] twl4030_wdt twl4030_wdt: Failed to register misc device
> [ 4.215240] twl4030_wdt: probe of twl4030_wdt failed with error -16
> [ 4.225860] omap_hsmmc omap_hsmmc.0: Failed to get debounce clk
> [ 4.262084] hub 1-0:1.0: state 7 ports 3 chg 0004 evt 0000
> [ 4.267913] hub 1-0:1.0: port 2, status 0501, change 0000, 480 Mb/s
> [ 4.332305] platform ehci-omap.0: port 2 reset complete, port enabled
> [ 4.339050] platform ehci-omap.0: GetStatus port:2 status 001005 0 ACK POWER sig=se0 PE CONNECT
> [ 4.410400] Unable to handle kernel NULL pointer dereference at virtual address 00000000
> [ 4.418884] pgd = c0004000
> [ 4.421722] [00000000] *pgd=00000000
> [ 4.425476] Internal error: Oops: 5 [#1] SMP ARM
> [ 4.430297] Modules linked in:
> [ 4.433471] CPU: 0 Not tainted (3.5.0 #16)
> [ 4.438110] PC is at hub_port_init+0x28c/0x968
> [ 4.442749] LR is at hub_port_init+0xc4/0x968
> [ 4.447296] pc : [<c030b2bc>] lr : [<c030b0f4>] psr: 60000013
> [ 4.447296] sp : df905eb8 ip : c05a9eb4 fp : 00000000
> [ 4.459259] r10: 00000000 r9 : df306400 r8 : 00000032
> [ 4.464691] r7 : df30ac00 r6 : 00000002 r5 : 00000000 r4 : df2a7400
> [ 4.471496] r3 : 00000000 r2 : c059e324 r1 : c059e348 r0 : df2a7468
> [ 4.478302] Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel
> [ 4.485900] Control: 10c5387d Table: 80004019 DAC: 00000017
> [ 4.491912] Process khubd (pid: 236, stack limit = 0xdf9042f8)
> [ 4.497985] Stack: (0xdf905eb8 to 0xdf906000)
> [ 4.502532] 5ea0: 00000002 df306400
> [ 4.511047] 5ec0: 00000002 00000000 00000004 c008a078 00000001 00000002 00000003 df300400
> [ 4.519561] 5ee0: 00000000 c044acb0 00000001 df2a7400 df30ac00 df300400 df300418 df306400
> [ 4.528106] 5f00: 00000002 00000000 00000002 c030eb30 00000501 00000000 c059f090 c0656600
> [ 4.536621] 5f20: 107e9dd6 00000000 df306408 df30a820 df30ac9c df30a800 00000004 df306401
> [ 4.545135] 5f40: df306470 df30ac00 df306468 df30ac00 df30a820 df300400 00000009 c0065144
> [ 4.553680] 5f60: 00000000 df904000 00000000 df88c100 c005cff4 df905f74 df905f74 00000000
> [ 4.562194] 5f80: 00000501 c008a078 df82ff20 df82fef8 00000000 c030e4c0 00000013 00000000
> [ 4.570709] 5fa0: 00000000 00000000 00000000 c005c8f8 00000000 00000000 00000000 00000000
> [ 4.579254] 5fc0: 00000000 dead4ead ffffffff ffffffff c0700330 00000000 00000000 c0561550
> [ 4.587768] 5fe0: df905fe0 df905fe0 df82fef8 c005c874 c0014154 c0014154 00000000 00000000
> [ 4.596313] [<c030b2bc>] (hub_port_init+0x28c/0x968) from [<c030eb30>] (hub_thread+0x670/0x13d8)
> [ 4.605468] [<c030eb30>] (hub_thread+0x670/0x13d8) from [<c005c8f8>] (kthread+0x84/0x90)
> [ 4.613922] [<c005c8f8>] (kthread+0x84/0x90) from [<c0014154>] (kernel_thread_exit+0x0/0x8)
> [ 4.622619] Code: e59f2690 e5933080 e2840068 e59f1688 (e593e000)
> [ 4.629089] ---[ end trace 6fcdeaed28ce1f31 ]---
> [ 4.790161] usbcore: registered new interface driver usbhid
> ...
>
> ATM there's no activity upstream to resolve this bug in a sound way but a patch was posted to linux-omap that resolves it:
>
> http://www.mail-archive.com/linux-omap@vger.kernel.org/msg73115.html
>
> While it's not upstream, the patch touches only omap3 clock code so it's safe for all the other flavours and it's the only
> option we have right now.
>
> The aforementioned patch coupled with disabling the generic ehci/ohci driver implementation fix the usb bus on omap3.
>
> BugLink: http://bugs.launchpad.net/bugs/1061599
>

Not strictly opposed, just a few questions/remarks:

> Paolo Pisati (3):

> UBUNTU: SAUCE: omap3 clocks .dev_id = NULL

Would it be possible to be a bit more verbose about what this one fixes and if
possible how. Just to have that documented in the change itself.

> UBUNTU: [Config] disable USB_[EHCI|OHCI]_HCD_PLATFORM

> UBUNTU: [Config] enforce USB_[EHCI|OHCI]_HCD_PLATFORM=n on arm[el|hf]

Would we need (or maybe we already have) something to enforce it being y on
other architectures?

-Stefan


>
> arch/arm/mach-omap2/clock3xxx_data.c | 20 ++++++++++----------
> debian.master/config/amd64/config.common.amd64 | 4 ++++
> debian.master/config/armel/config.common.armel | 4 ++++
> debian.master/config/armhf/config.common.armhf | 2 ++
> debian.master/config/armhf/config.flavour.highbank | 2 ++
> debian.master/config/armhf/config.flavour.omap | 2 ++
> debian.master/config/config.common.ubuntu | 4 ----
> debian.master/config/enforce | 3 +++
> debian.master/config/i386/config.common.i386 | 4 ++++
> debian.master/config/powerpc/config.common.powerpc | 4 ++++
> debian.master/config/ppc64/config.common.ppc64 | 4 ++++
> 11 files changed, 39 insertions(+), 14 deletions(-)
>


--
kernel-team mailing list
kernel-team@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kernel-team
 
Old 10-10-2012, 05:15 AM
Robert Nelson
 
Default fix usb on omap3

On Tue, Oct 9, 2012 at 6:52 AM, Paolo Pisati <paolo.pisati@canonical.com> wrote:
> On 10/09/2012 01:43 PM, Andy Whitcroft wrote:
>>
>> On Tue, Oct 09, 2012 at 12:31:26PM +0200, Paolo Pisati wrote:
>>
>>> and lately this situation has spiraled down to the point where enabling
>>> it at boot triggers an oops and a subsequent dead usb hub:
>>>
>>> vanilla 3.5 omap2plus_defconfig + ehci:
>>>
>>> ...
>>> [ 4.200103] omap_wdt: OMAP Watchdog Timer Rev 0x31: initial timeout 60
>>> sec
>>> [ 4.208526] twl4030_wdt twl4030_wdt: Failed to register misc device
>>
>>
>> Does this imply that the kernel as it is in the archive will panic on
>> boot due to the USB hub? If so I assume that is generally fatal as that
>> is where your disks are likely to be?
>
>
> in our case (different config&c) the usb is simply dead (no panic): it won't
> recognize any usb devices attached to it. in my case, with my beagle, i boot
> off the sd only (i leave the usb disk for my omap4) but yes is still a fatal
> IMO since these boards have evreyrhing attached to the usb bus.
>
> the problem with omap3 is that no one is actually using it for real in our
> community (everyone moved to omap4) and people that do some testing use the
> emulated beagle via qemu (that didn't show this bug), i stumbled on this bug
> last week when i tried Q by myself.

Hi Paolo,

For mainline v3.5.x, give this patch a try on your Beagle/omap3 device...

https://github.com/RobertCNelson/stable-kernel/blob/v3.5.x/patches/beagle/0005-OMAP3-USB-EHCI-fix.patch

It should fix it and make the usb usable, see the http mailing list
link in the patch for the discussion... Kevin's ehci disable in
omap2plus_defconfig commit was more of lack of non-working power
management caused by the current status of ehci in v3.5.x, then
non-working ehci in general..

It was fixed with another commit in v3.6.x, I personally never looked
at what commit fixed it in v3.6.x as i moved that that base pretty
quickly..

Regards,

--
Robert Nelson
http://www.rcn-ee.com/

--
kernel-team mailing list
kernel-team@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kernel-team
 
Old 10-10-2012, 07:20 AM
Paolo Pisati
 
Default fix usb on omap3

On 10/10/2012 07:15 AM, Robert Nelson wrote:


https://github.com/RobertCNelson/stable-kernel/blob/v3.5.x/patches/beagle/0005-OMAP3-USB-EHCI-fix.patch


that's what we imported: same commit, same thread conversation.


It was fixed with another commit in v3.6.x, I personally never looked
at what commit fixed it in v3.6.x as i moved that that base pretty
quickly..


i tried with v3.6 and it was still broken, good to know it was fixed in
v3.6.y, i'll give it a try.


thanks
--
bye,
p.

--
kernel-team mailing list
kernel-team@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kernel-team
 
Old 10-10-2012, 12:24 PM
Robert Nelson
 
Default fix usb on omap3

On Wed, Oct 10, 2012 at 2:20 AM, Paolo Pisati
<paolo.pisati@canonical.com> wrote:
> On 10/10/2012 07:15 AM, Robert Nelson wrote:
>>
>>
>>
>> https://github.com/RobertCNelson/stable-kernel/blob/v3.5.x/patches/beagle/0005-OMAP3-USB-EHCI-fix.patch
>
>
> that's what we imported: same commit, same thread conversation.

Yeah, i see that now too, I shouldn't be coding/emailing late at night>

>> It was fixed with another commit in v3.6.x, I personally never looked
>> at what commit fixed it in v3.6.x as i moved that that base pretty
>> quickly..
>
>
> i tried with v3.6 and it was still broken, good to know it was fixed in
> v3.6.y, i'll give it a try.

Strange, are you guys running any usb patch/sauce on v3.6.x? The usb
pretty much as worked fine with v3.6-rc7..v3.6.1 on my xM..

with these config options:

voodoo@a53t:/opt/github/stable-kernel$ cat patches/defconfig | grep EHCI
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB_EHCI_HCD=y
# CONFIG_USB_EHCI_ROOT_HUB_TT is not set
CONFIG_USB_EHCI_TT_NEWSCHED=y
CONFIG_USB_EHCI_HCD_OMAP=y
# CONFIG_USB_EHCI_HCD_PLATFORM is not set
voodoo@a53t:/opt/github/stable-kernel$ cat patches/defconfig | grep OMAP_USB
CONFIG_MFD_OMAP_USB_HOST=y

Regards,

--
Robert Nelson
http://www.rcn-ee.com/

--
kernel-team mailing list
kernel-team@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kernel-team
 
Old 10-10-2012, 01:36 PM
Paolo Pisati
 
Default fix usb on omap3

On Wed, Oct 10, 2012 at 07:24:45AM -0500, Robert Nelson wrote:
>
> Strange, are you guys running any usb patch/sauce on v3.6.x? The usb
> pretty much as worked fine with v3.6-rc7..v3.6.1 on my xM..

i tested v3.6 on my xm using omap2plus_defconfig plus :

CONFIG_USB_EHCI_HCD=y
# CONFIG_USB_EHCI_ROOT_HUB_TT is not set
CONFIG_USB_EHCI_TT_NEWSCHED=y
CONFIG_USB_EHCI_HCD_OMAP=y
...
# CONFIG_USB_EHCI_HCD_PLATFORM is not set
...
CONFIG_MFD_OMAP_USB_HOST=y

and i hit the oops on boot as described here:

http://bugs.launchpad.net/bugs/1061599

see the 3.6 part.

--
bye,
p.

--
kernel-team mailing list
kernel-team@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kernel-team
 
Old 10-10-2012, 05:10 PM
Robert Nelson
 
Default fix usb on omap3

On Wed, Oct 10, 2012 at 8:36 AM, Paolo Pisati
<paolo.pisati@canonical.com> wrote:
> On Wed, Oct 10, 2012 at 07:24:45AM -0500, Robert Nelson wrote:
>>
>> Strange, are you guys running any usb patch/sauce on v3.6.x? The usb
>> pretty much as worked fine with v3.6-rc7..v3.6.1 on my xM..
>
> i tested v3.6 on my xm using omap2plus_defconfig plus :
>
> CONFIG_USB_EHCI_HCD=y
> # CONFIG_USB_EHCI_ROOT_HUB_TT is not set
> CONFIG_USB_EHCI_TT_NEWSCHED=y
> CONFIG_USB_EHCI_HCD_OMAP=y
> ...
> # CONFIG_USB_EHCI_HCD_PLATFORM is not set
> ...
> CONFIG_MFD_OMAP_USB_HOST=y
>
> and i hit the oops on boot as described here:
>
> http://bugs.launchpad.net/bugs/1061599
>
> see the 3.6 part.

Weird, on my Beagle xM C, 3.6.1 is fine...

[ 3.532897] usb 1-2: new high-speed USB device number 2 using ehci-omap
[ 3.697723] usb 1-2: New USB device found, idVendor=0424, idProduct=9514
[ 3.704803] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 3.715301] hub 1-2:1.0: USB hub found
[ 3.719573] hub 1-2:1.0: 5 ports detected

[ 4.215881] usb 1-2.1: New USB device found, idVendor=0424, idProduct=ec00
[ 4.223266] usb 1-2.1: New USB device strings: Mfr=0, Product=0,
SerialNumber=0
[ 4.254730] smsc95xx v1.0.4
[ 4.376892] smsc95xx 1-2.1:1.0: eth0: register 'smsc95xx' at
usb-ehci-omap.0-2.1, smsc95xx USB 2.0 Ethernet, 0a:53:b3:c3:15:84
[ 4.603668] usb 1-2.2: new high-speed USB device number 4 using ehci-omap
[ 4.787231] usb 1-2.2: New USB device found, idVendor=0204, idProduct=6025
[ 4.794647] usb 1-2.2: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[ 4.802368] usb 1-2.2: Product: Flash Disk
[ 4.807250] usb 1-2.2: Manufacturer: USB 2.0
[ 4.811828] usb 1-2.2: SerialNumber: 326439604372
[ 5.244567] scsi0 : usb-storage 1-2.2:1.0
[ 5.376922] usb 1-2.3: new low-speed USB device number 5 using ehci-omap
[ 5.547943] usb 1-2.3: New USB device found, idVendor=413c, idProduct=2003
[ 5.555328] usb 1-2.3: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[ 5.563049] usb 1-2.3: Product: Dell USB Keyboard
[ 5.568023] usb 1-2.3: Manufacturer: Dell
[ 5.649414] input: Dell Dell USB Keyboard as
/devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.3/1-2.3:1.0/input/input2

omap2plus_defconfig + those ehci options listed above:
http://paste.debian.net/198630/

It does eventually crash:
[ 7.261474] Kernel panic - not syncing: Attempted to kill init!
exitcode=0x00000b00

But it's more due to the other missing modules that
omap2plus_defconfig doesn't provide..

Regards,

--
Robert Nelson
http://www.rcn-ee.com/

--
kernel-team mailing list
kernel-team@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kernel-team
 

Thread Tools




All times are GMT. The time now is 07:25 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org