lkml.org 
[lkml]   [2014]   [Aug]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: About the reboot hang issue with EHCI driver on the Baytrail platform
From
Hi Alan,

On Wed, Aug 27, 2014 at 10:38 PM, Alan Stern <stern@rowland.harvard.edu> wrote:
> On Wed, 27 Aug 2014, Gavin Guo wrote:
>
>> > 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.
>
> There is no doubt that the BIOS is buggy. Your log contains this line:
>
> [ 2.804205] pci 0000:00:1d.0: EHCI: BIOS handoff failed (BIOS bug?) 01010001
>
> The only way that can happen is if the BIOS isn't working right.
> However, this may be a different bug from the crashes you've been
> seeing.

Thanks for your comments. I really appreciate your support.

Gavin Guo

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


\
 
 \ /
  Last update: 2014-08-27 19:21    [W:0.578 / U:0.064 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site