From: sunnydrake <sunnydrake7-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Wan Zongshun <vw-6ukY98dZOFrYtjvyW6yDsg@public.gmane.org>,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: [Regression] Amd-Vi + ivrs_ioapic cause kernel oops (4.4, 4.7 fail 3.9 works)
Date: Tue, 5 Jul 2016 04:56:37 +0300 [thread overview]
Message-ID: <577B13D5.7030200@gmail.com> (raw)
In-Reply-To: <6a84fd9d-6897-2b19-de87-be09722593dc-6ukY98dZOFrYtjvyW6yDsg@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 2353 bytes --]
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
[-- Attachment #1.2: Type: text/html, Size: 4212 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2016-07-05 1:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-03 0:59 [Regression] Amd-Vi + ivrs_ioapic cause kernel oops (4.4, 4.7 fail 3.9 works) sunnydrake
[not found] ` <57786362.1010702-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-07-03 14:26 ` Wan Zongshun
[not found] ` <790da4e5-985a-a4f5-1ead-b4fa1f37e8a4-6ukY98dZOFrYtjvyW6yDsg@public.gmane.org>
2016-07-03 20:48 ` sunnydrake
[not found] ` <57797A37.4030805-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-07-04 13:51 ` Wan Zongshun
[not found] ` <6a84fd9d-6897-2b19-de87-be09722593dc-6ukY98dZOFrYtjvyW6yDsg@public.gmane.org>
2016-07-05 1:56 ` sunnydrake [this message]
[not found] ` <577B13D5.7030200-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-07-05 3:17 ` Wan Zongshun
[not found] ` <577B26C3.6040108-6ukY98dZOFrYtjvyW6yDsg@public.gmane.org>
2016-07-05 7:46 ` sunnydrake
2016-07-10 8:48 ` sunnydrake
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=577B13D5.7030200@gmail.com \
--to=sunnydrake7-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=vw-6ukY98dZOFrYtjvyW6yDsg@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.