| Summary: | [CI][DRMTIP] igt@gem_exec_suspend@basic-s4-devices - dmesg-warn - irq \d+: nobody cared (try booting with the "irqpoll" option) | ||
|---|---|---|---|
| Product: | DRI | Reporter: | Lakshmi <lakshminarayana.vudum> |
| Component: | DRM/Intel | Assignee: | Tomi Sarvela <tomi.p.sarvela> |
| Status: | RESOLVED NOTOURBUG | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
| Severity: | normal | ||
| Priority: | medium | CC: | intel-gfx-bugs, martin.peres, sudeep.dutt |
| Version: | DRI git | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | ReadyForDev | ||
| i915 platform: | ICL | i915 features: | CI Infra |
|
Description
Lakshmi
2019-02-15 09:28:10 UTC
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * ICL: igt@gem_exec_suspend@basic-* - dmesg-warn - irq \d+: nobody cared \(try booting with the "irqpoll" option\) - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_218/fi-icl-u2/igt@gem_exec_suspend@basic-s4-devices.html This message was repeated for both IRQ#32 and IRQ#33, I'm not sure what those IRQs are tied to so it would be helpful to see /proc/interrupts. That said, the handler is 'i2c_dw_isr' so unless the i915 is using i2c -- is it? -- this may be unrelated. <3>[ 291.460222] irq 32: nobody cared (try booting with the "irqpoll" option) ... <3>[ 291.460288] handlers: <3>[ 291.460305] [<00000000456b355a>] i2c_dw_isr <0>[ 291.460317] Disabling IRQ #32 ... <3>[ 291.801786] irq 33: nobody cared (try booting with the "irqpoll" option) .. <3>[ 291.802051] handlers: <3>[ 291.802060] [<00000000456b355a>] i2c_dw_isr <0>[ 291.802146] Disabling IRQ #33 (In reply to Don Hiatt from comment #2) > This message was repeated for both IRQ#32 and IRQ#33, I'm not sure what > those IRQs are tied to so it would be helpful to see /proc/interrupts. That > said, the handler is 'i2c_dw_isr' so unless the i915 is using i2c -- is it? > -- this may be unrelated. Well, there is an 'intel_i2c.c' driver so that answers that. :) Not our interrupt; this is designware-i2c. BHai awaz aa rahi hay meri? Jai Hind *** Bug 109965 has been marked as a duplicate of this bug. *** A CI Bug Log filter associated to this bug has been updated:
{- ICL: igt@gem_exec_suspend@basic-* - dmesg-warn - irq \d+: nobody cared \(try booting with the "irqpoll" option\) -}
{+ ICL: all tests - dmesg-warn - irq \d+: nobody cared \(try booting with the "irqpoll" option\) +}
New failures caught by the filter:
* https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_237/fi-icl-y/igt@gem_create@create-clear.html
(In reply to CI Bug Log from comment #8) > A CI Bug Log filter associated to this bug has been updated: > > {- ICL: igt@gem_exec_suspend@basic-* - dmesg-warn - irq \d+: nobody cared > \(try booting with the "irqpoll" option\) -} > {+ ICL: all tests - dmesg-warn - irq \d+: nobody cared \(try booting with > the "irqpoll" option\) +} > > New failures caught by the filter: > > * > https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_237/fi-icl-y/ > igt@gem_create@create-clear.html + issues from https://bugs.freedesktop.org/show_bug.cgi?id=109965: - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_2534/fi-icl-y/igt@gem_mmap_gtt@basic.html - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12358/fi-icl-y/igt@gem_mmap_gtt@basic-copy.html - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5708/fi-icl-y/igt@gem_mmap@basic-small-bo.html A CI Bug Log filter associated to this bug has been updated:
{- ICL: all tests - dmesg-warn - irq \d+: nobody cared \(try booting with the "irqpoll" option\) -}
{+ ICL: all tests - dmesg-warn - irq \d+: nobody cared \(try booting with the "irqpoll" option\) +}
No new failures caught with the new filter
Hi Lakshmi, according to Chris (Comment #4) this interrupt belongs to designware-i2c so is not related to our driver. Can you please close or advise on how you'd like to handle this? (In reply to Don Hiatt from comment #11) > Hi Lakshmi, according to Chris (Comment #4) this interrupt belongs to > designware-i2c so is not related to our driver. Can you please close or > advise on how you'd like to handle this? Assigning Tomi, and moving to CI infra to blacklist the module! @Tomi, any update here? If the Intel RVP hardware has anything that can use this particular driver (designware-i2c), I'd rather not blacklist it. Would it be better to make it NOTOURBUG and plunk the bugreports to the maintainer of the driver? |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.