Re: About the reboot hang issue with EHCI driver on the Baytrail platform

[Gavin Guo]

Hi Alan,

On Wed, Aug 27, 2014 at 1:26 AM, Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote:
> On Wed, 27 Aug 2014, Gavin Guo wrote:
>
>> >>  And IIRC, there is only one host controller within
>> >> EHCI and XHCI can be enabled in the Baytrail platform. I'm also trying
>> >> to find out the kernel parameters to disable the EHCI driver, but
>> >> currently there is no available one.
>> >
>> > It's not a kernel parameter.  You can blacklist the ehci-pci and
>> > ehci-hcd modules in /etc/modprobe.d/local.conf.
>> >
>> > Or you can turn off CONFIG_USB_EHCI_HCD in your .config and build a
>> > kernel with no EHCI support at all.
>>
>> Thanks for your response, I'm sorry that I didn't describe the
>> question clearly. Because the EHCI support is built-in with Ubuntu
>> kernel. I tried to find a way to disable that. Unfortunately, I only
>> found "nousb" can disable it. But it will disable all the USB
>> subsystem. Don't know if there is any chance to disable EHCI only.
>
> I see.  No, there isn't any way to disable EHCI support at boot time if
> it is built into the kernel.  The best you can do is use the sysfs
> "unbind" attribute, and that may not always be good enough for what you
> want.
>
> Still, why not use the BIOS setting to disable EHCI?

It's hardware enablement policy. By default, we can't change the BIOS
setting to make the bug disappear until we find out the bug is due to
BIOS's bug. Add kernel parameters is the temporary solution for the
platform can ship. And if the bug is from kernel, we need to send
patches to upstream and pull back to Ubuntu kernel or send to Ubuntu
Kernel directly if it's a trivial solution like adding device id.
However, as you said, in this case about the bug the root may be from
BIOS code. So, we can coordinate with the OEM BIOS team to modify the
default BIOS setting.

>
> Alan Stern
>

Gavin Guo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/