diff options
| author | Neil Horman <nhorman@tuxdriver.com> | 2013-09-27 12:53:35 -0400 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2013-12-08 07:29:27 -0800 |
| commit | 645451235dc5098f08cc51e2f1205d9fa9ca8262 (patch) | |
| tree | cda7543cacde4da5e038628d53f8b065c2f4ed22 /block/blk-timeout.c | |
| parent | 3de762b3d32ff3d0440ca809e1ba084c682f0ca7 (diff) | |
| download | linux-3.10-645451235dc5098f08cc51e2f1205d9fa9ca8262.tar.gz linux-3.10-645451235dc5098f08cc51e2f1205d9fa9ca8262.tar.bz2 linux-3.10-645451235dc5098f08cc51e2f1205d9fa9ca8262.zip | |
iommu: Remove stack trace from broken irq remapping warning
commit 05104a4e8713b27291c7bb49c1e7e68b4e243571 upstream.
The warning for the irq remapping broken check in intel_irq_remapping.c is
pretty pointless. We need the warning, but we know where its comming from, the
stack trace will always be the same, and it needlessly triggers things like
Abrt. This changes the warning to just print a text warning about BIOS being
broken, without the stack trace, then sets the appropriate taint bit. Since we
automatically disable irq remapping, theres no need to contiue making Abrt jump
at this problem
Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
CC: Joerg Roedel <joro@8bytes.org>
CC: Bjorn Helgaas <bhelgaas@google.com>
CC: Andy Lutomirski <luto@amacapital.net>
CC: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
CC: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
Signed-off-by: Joerg Roedel <joro@8bytes.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'block/blk-timeout.c')
0 files changed, 0 insertions, 0 deletions