Re: Regression in v4.2-rc1 caused by hierarchical irqdomain changes

2015-07-29 Thread Jiang Liu
On 2015/7/30 5:03, Thomas Gleixner wrote:
> On Mon, 27 Jul 2015, Matt Fleming wrote:
>> [BAD]
>>   3:  1  0  0  0  IR-IO-APIC   3-edge
>>   6:  0  0  0  0  IR-IO-APIC   6-edge  
>> dw_dmac
>>   7: 15  1  0  0  IR-IO-APIC   7-edge  
>> INT3432:00, INT3433:00
> 
> [GOOD]
>>   3: 16 17 49 20  IR-IO-APIC-fasteoi   
>> AudioDSP, dw_dmac
>>   6:  0  0  0  0  IR-IO-APIC-fasteoi   
>> dw_dmac
>>   7:   2662   3072  12307   5419  IR-IO-APIC-fasteoi   
>> INT3432:00, INT3433:00
> 
> So the old code uses fasteoi while the new one uses edge.
> 
> Jiang
Sorry for the slow response.
We have reproduced this regression on Surface Pro 3, but are still
trying to figure out the root cause.
Thanks!
Gerry
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: Regression in v4.2-rc1 caused by hierarchical irqdomain changes

2015-07-29 Thread Thomas Gleixner
On Mon, 27 Jul 2015, Matt Fleming wrote:
> [BAD]
>   3:  1  0  0  0  IR-IO-APIC   3-edge
>   6:  0  0  0  0  IR-IO-APIC   6-edge  
> dw_dmac
>   7: 15  1  0  0  IR-IO-APIC   7-edge  
> INT3432:00, INT3433:00

[GOOD]
>   3: 16 17 49 20  IR-IO-APIC-fasteoi   
> AudioDSP, dw_dmac
>   6:  0  0  0  0  IR-IO-APIC-fasteoi   dw_dmac
>   7:   2662   3072  12307   5419  IR-IO-APIC-fasteoi   
> INT3432:00, INT3433:00

So the old code uses fasteoi while the new one uses edge.

Jiang



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


Re: Regression in v4.2-rc1 caused by hierarchical irqdomain changes

2015-07-27 Thread Jiang Liu
On 2015/7/27 23:21, Matt Fleming wrote:
> A git bisect just pointed me at commit d32932d02e18 ("x86/irq: Convert
> IOAPIC to use hierarchical irqdomain interfaces") as the reason for why
> the trackpad on my Dell XPS13 is no longer working with v4.2-rc1.
> 
> I'm now seeing the following errors when booting,
> 
> [1.615017] i2c_designware INT3433:00: controller timed out
> [1.642496] i2c_designware INT3433:00: timeout in disabling adapter
> [1.642500] i2c_hid i2c-DLL0665:01: hid_descr_cmd failed
> 
> I tried commit d32932d02e18~1, which works, and things definitely break
> starting with commit d32932d02e18.
> 
> Any suggestions or requests to try and diagnose why the irqdomain
> changes broke this i2c controller driver?
Hi Matt,
Sorry for the regression. Could you please help to provide
more information about the regression, such dmesg, /proc/interrupts
and hardware(PCI) info from good and bad kernels?
Thanks!
Gerry

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


Regression in v4.2-rc1 caused by hierarchical irqdomain changes

2015-07-27 Thread Matt Fleming
A git bisect just pointed me at commit d32932d02e18 ("x86/irq: Convert
IOAPIC to use hierarchical irqdomain interfaces") as the reason for why
the trackpad on my Dell XPS13 is no longer working with v4.2-rc1.

I'm now seeing the following errors when booting,

[1.615017] i2c_designware INT3433:00: controller timed out
[1.642496] i2c_designware INT3433:00: timeout in disabling adapter
[1.642500] i2c_hid i2c-DLL0665:01: hid_descr_cmd failed

I tried commit d32932d02e18~1, which works, and things definitely break
starting with commit d32932d02e18.

Any suggestions or requests to try and diagnose why the irqdomain
changes broke this i2c controller driver?

-- 
Matt Fleming, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/