From: DIXLOR <dixlor@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: WARNING: amd_iommu. linux-4.4.1-rt6
Date: Sat, 27 Feb 2016 14:38:47 +0300 [thread overview]
Message-ID: <56D18AC7.4090409@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1602271057270.3638@nanos>
[-- Attachment #1: Type: text/plain, Size: 2730 bytes --]
Yet another WARN
[ 2.667483] WARNING: CPU: 6 PID: 1 at drivers/iommu/amd_iommu.c:2124
0xffffffff812cd85a()
[ 2.667484] Modules linked in:
[ 2.667488] CPU: 6 PID: 1 Comm: swapper/0 Tainted: G U 4.4.2-plx+ #6
[ 2.667489] Hardware name: empty empty/S8225, BIOS 'V3.03 ' 11/01/2012
[ 2.667490] ffffffff815efa4c ffffffff8121e0d6 0000000000000000 ffffffff81033fef
[ 2.667492] ffff880422992180 ffff8804230e0098 ffff8804229c0800 ffff880423934000
[ 2.667493] ffff880422a0c000 ffffffff812cd85a ffff880422992180 ffff8804230e0098
[ 2.667495] Call Trace:
[ 2.667497] [<ffffffff8121e0d6>] ? 0xffffffff8121e0d6
[ 2.667498] [<ffffffff81033fef>] ? 0xffffffff81033fef
[ 2.667499] [<ffffffff812cd85a>] ? 0xffffffff812cd85a
[ 2.667500] [<ffffffff812cd886>] ? 0xffffffff812cd886
[ 2.667500] [<ffffffff812cd9a7>] ? 0xffffffff812cd9a7
[ 2.667501] [<ffffffff814fa559>] ? 0xffffffff814fa559
[ 2.667502] [<ffffffff812cb3aa>] ? 0xffffffff812cb3aa
[ 2.667502] [<ffffffff812cb9da>] ? 0xffffffff812cb9da
[ 2.667503] [<ffffffff812ceaa3>] ? 0xffffffff812ceaa3
[ 2.667504] [<ffffffff812ca7e8>] ? 0xffffffff812ca7e8
[ 2.667504] [<ffffffff812ca808>] ? 0xffffffff812ca808
[ 2.667505] [<ffffffff81306adf>] ? 0xffffffff81306adf
[ 2.667506] [<ffffffff812cb33a>] ? 0xffffffff812cb33a
[ 2.667507] [<ffffffff8172b08a>] ? 0xffffffff8172b08a
[ 2.667507] [<ffffffff8170c281>] ? 0xffffffff8170c281
[ 2.667508] [<ffffffff8172b1d5>] ? 0xffffffff8172b1d5
[ 2.667509] [<ffffffff8172b250>] ? 0xffffffff8172b250
[ 2.667509] [<ffffffff8170c28f>] ? 0xffffffff8170c28f
[ 2.667510] [<ffffffff810003df>] ? 0xffffffff810003df
[ 2.667511] [<ffffffff81708e04>] ? 0xffffffff81708e04
[ 2.667511] [<ffffffff814f62c8>] ? 0xffffffff814f62c8
[ 2.667512] [<ffffffff814f62cd>] ? 0xffffffff814f62cd
[ 2.667513] [<ffffffff814facef>] ? 0xffffffff814facef
[ 2.667513] [<ffffffff814f62c8>] ? 0xffffffff814f62c8
[ 2.667514] ---[ end trace 0000000000000001 ]---
27.02.2016 12:58, Thomas Gleixner пишет:
> On Sat, 27 Feb 2016, Thomas Gleixner wrote:
>> --- a/drivers/iommu/amd_iommu.c
>> +++ b/drivers/iommu/amd_iommu.c
>> @@ -1952,10 +1952,10 @@ static int __attach_device(struct iommu_
>> int ret;
>>
>> /*
>> - * Must be called with IRQs disabled. Warn here to detect early
>> - * when its not.
>> + * Must be called with IRQs disabled on a non RT kernel. Warn here to
>> + * detect early when its not.
>> */
>> - WARN_ON(!irqs_disabled());
>> + WARN_ON_NORT(!irqs_disabled());
> That wants to be
>
> + WARN_ON_NONRT(!irqs_disabled());
>
> of course.
>
> -ENOTAWAKEYET
>
[-- Attachment #2: Криптографическая подпись S/MIME --]
[-- Type: application/pkcs7-signature, Size: 3577 bytes --]
next prev parent reply other threads:[~2016-02-27 11:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 0:34 WARNING: amd_iommu. linux-4.4.1-rt6 DIXLOR
2016-02-25 8:44 ` Sebastian Andrzej Siewior
2016-02-27 9:25 ` Thomas Gleixner
2016-02-27 9:58 ` Thomas Gleixner
2016-02-27 11:38 ` DIXLOR [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-02-23 0:25 DIXLOR
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=56D18AC7.4090409@gmail.com \
--to=dixlor@gmail.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
/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.