On 04.07.16 16:51, Wan Zongshun wrote:
>
>
> 在 7/4/2016 4:48 AM, sunnydrake 写道:
>> Thanks for reply.
>> On 03.07.16 17:26, Wan Zongshun wrote:
>>>
>>>
>>> 在 7/3/2016 8:59 AM, sunnydrake 写道:
>>>> [description]
>>>> working in kernel 3.9
>>>> Oops in current 4.4.0-28,4.7.0-040700rc5
>>>> kernel options ivrs_ioapic[7]=00:14.0 ivrs_ioapic[8]=00:00.1 
>>>> workaround to fix ivrs table
>>>> cause kernel Oops on boot
>>> Do you mean "ivrs_ioapic[7]=00:14.0  ivrs_ioapic[8]=00:00.1" are 
>>> workable at kernel-3.9 but failed in kernel-4.4?
>> 1)yes kernel 3.9 boots ok with ivrs_ioapic[7]=00:14.0 
>> ivrs_ioapic[8]=00:00.1
>> kernels 4.4 and 4.7 fall to Oops
>>>
>>>>
>>>> [bug]
>>>> oops:
>>>> short oops text
>>>> AMD-Vi: Completion_wait loop timed Out
>>>> BUG: unable to handle kernel NULL pointer dereference at 000..03e
>>>> ... irq_pm_install_action+0x1c/0xd0
>>>> full oops image text
>>>> http://img.ctrlv.in/img/16/07/03/577863055370c.jpg
>>>>
>>>> [additional info]
>>>> dmesg|grep AMD-Vi without ivrs_ioapic[8]=00:00.1
>>> This log is from the kernel print without ivrs_ioapic[8]=00:00.1?
>>> Why not provide your kernel log with "ivrs_ioapic[7]=00:14.0 
>>> ivrs_ioapic[8]=00:00.1" ?
>>> Full kernel log is better.
>>>
>>
>> 2) yes,  because with ivrs_ioapic[7]=00:14.0 ivrs_ioapic[8]=00:00.1 
>> kernels are not bootable. Screen of Oops 
>> http://img.ctrlv.in/img/16/07/03/577863055370c.jpg (this with params 
>> ivrs_ioapic[7]=00:14.0  ivrs_ioapic[8]=00:00.1 ). if you need 
>> something another like kdump, i can provide.
>
> If you can provide a full kernel log with ivrs_ioapic[7]=00:14.0 
> ivrs_ioapic[8]=00:00.1, that is better.
> I checked your crash log, and find some things related to i8042 maybe 
> wrong, it is ps2 relation driver, is it necessary in your system? can 
> you disable this i8042 firsty to check if your issue is reasoned from it?
i have serial port disabled in bios and booting with i8042.no_acpi=1 
does not fix problem. I don't think i8042 related, because 
i8042_panic_blink  is caps lock blinking when kernel crash (std behavior)

here is more detailed image of crash 
http://img.ctrlv.in/img/16/07/05/577b0ec96746e.jpg
Unable to handle null pointer reference at irq_pm_install_action...
ok i will setup linux-crashdump and report logs