From: Jaswinder Singh Rajput <jaswinder@perfectintelligent.com>
To: mika.kahola@intel.com, linux-kernel@vger.kernel.org,
ville.syrjala@linux.intel.com, ramalingam.c@intel.com,
jani.nikula@linux.intel.com, joonas.lahtinen@linux.intel.com,
rodrigo.vivi@intel.com, intel-gfx@lists.freedesktop.org
Subject: Re: Warning in i915/intel_audio.c
Date: Fri, 15 Dec 2017 20:35:12 +0530 [thread overview]
Message-ID: <1513350312.13113.3.camel@perfectintelligent.com> (raw)
In-Reply-To: <1513347838.6882.104.camel@intel.com>
On Fri, 2017-12-15 at 16:23 +0200, Mika Kahola wrote:
> On Fri, 2017-12-15 at 19:20 +0530, Jaswinder Singh Rajput wrote:
> >
> > On Fri, 2017-12-15 at 14:44 +0200, Mika Kahola wrote:
> > >
> > >
> > > Hi,
> > >
> > > This is a known issue. Could you try out this patch to see if
> > > that
> > > would fix this issue for you?
> > >
> > > https://patchwork.freedesktop.org/series/35389/
> > >
> > Yes, Thanks. It works :-)
> Great that it worked for you!
>
> >
> >
> > When this patch will merge with linus kernel.
> If you can, you may add a Tested-by tag on the patch. It will help
> the
> review process. This patch needs a review before its merged to our
> drm-
> tip tree and eventually further on to Linus tree.
>
Sure, kindly add me in CC and add my tag to the patch:
Tested-by: Jaswinder Singh Rajput <jaswinder@perfectintelligent.com>
> >
> >
> > Thanks,
> > --
> > Jaswinder Singh Rajput
> >
> > >
> > >
> > > On Fri, 2017-12-15 at 17:08 +0530, Jaswinder Singh Rajput wrote:
> > > >
> > > >
> > > >
> > > > Hello friends,
> > > >
> > > > I am getting multiple warnings in i915/intel_audio.c . I am
> > > > attaching
> > > > dmesg, config and lsmod for your reference.
> > > >
> > > >
> > > > [ 0.390606] WARN_ON(pipe >= intel_info((dev_priv))-
> > > > >num_pipes)
> > > > [ 0.390619] WARNING: CPU: 1 PID: 1051 at
> > > > drivers/gpu/drm/i915/intel_audio.c:757 get_saved_enc+0x74/0x80
> > > > [ 0.390620] Modules linked in:
> > > > [ 0.390621] CPU: 1 PID: 1051 Comm: kworker/1:2 Not tainted
> > > > 4.15.0-rc3+ #13
> > > > [ 0.390622] Hardware name: Gigabyte Technology Co., Ltd.
> > > > H81M-S/H81M-S, BIOS F2 08/19/2015
> > > > [ 0.390624] Workqueue: events azx_probe_work
> > > > [ 0.390625] RIP: 0010:get_saved_enc+0x74/0x80
> > > > [ 0.390626] RSP: 0018:ffff9b650061fba8 EFLAGS: 00010292
> > > > [ 0.390627] RAX: 0000000000000032 RBX: ffff888e17384cb8
> > > > RCX:
> > > > 0000000000000000
> > > > [ 0.390627] RDX: 0000000000000001 RSI: 0000000000000002
> > > > RDI:
> > > > ffffffff97032bb0
> > > > [ 0.390627] RBP: ffff888e17380000 R08: 0000000000000032
> > > > R09:
> > > > 0000000000000032
> > > > [ 0.390628] R10: ffff888e19cc3840 R11: 00000000000344e0
> > > > R12:
> > > > 0000000000000100
> > > > [ 0.390628] R13: 0000000000000001 R14: ffff888e168fba08
> > > > R15:
> > > > ffff888e168fba10
> > > > [ 0.390629] FS: 0000000000000000(0000)
> > > > GS:ffff888e1f300000(0000)
> > > > knlGS:0000000000000000
> > > > [ 0.390629] CS: 0010 DS: 0000 ES: 0000 CR0:
> > > > 0000000080050033
> > > > [ 0.390630] CR2: 00007f7dd01c6914 CR3: 000000003da0a001
> > > > CR4:
> > > > 00000000000606e0
> > > > [ 0.390630] Call Trace:
> > > > [ 0.390633] i915_audio_component_get_eld+0x43/0xe0
> > > > [ 0.390635] hdmi_present_sense+0x95/0x330
> > > > [ 0.390636] generic_hdmi_build_controls+0x143/0x1e0
> > > > [ 0.390638] snd_hda_codec_build_controls+0x178/0x1c0
> > > > [ 0.390639] ? snd_hda_codec_build_pcms+0x14f/0x1a0
> > > > [ 0.390641] hda_codec_driver_probe+0x76/0x100
> > > > [ 0.390644] driver_probe_device+0x27d/0x310
> > > > [ 0.390645] ? __driver_attach+0xa0/0xa0
> > > > [ 0.390646] bus_for_each_drv+0x50/0x80
> > > > [ 0.390647] __device_attach+0xb0/0x110
> > > > [ 0.390649] bus_probe_device+0x82/0x90
> > > > [ 0.390650] device_add+0x2dc/0x570
> > > > [ 0.390652] snd_hdac_device_register+0xd/0x40
> > > > [ 0.390654] snd_hda_codec_configure+0x32/0x120
> > > > [ 0.390655] azx_codec_configure+0x2a/0x60
> > > > [ 0.390656] azx_probe_work+0x40c/0x860
> > > > [ 0.390659] process_one_work+0x1d2/0x3c0
> > > > [ 0.390660] worker_thread+0x42/0x3e0
> > > > [ 0.390661] kthread+0xf0/0x130
> > > > [ 0.390663] ?
> > > > trace_event_raw_event_workqueue_work+0x80/0x80
> > > > [ 0.390664] ? kthread_create_worker_on_cpu+0x40/0x40
> > > > [ 0.390665] ? call_usermodehelper_exec_async+0x11c/0x120
> > > > [ 0.390667] ret_from_fork+0x1f/0x30
> > > > [ 0.390668] Code: 83 c2 01 39 d1 7f e0 31 c0 c3 83 78 70 0b
> > > > 74
> > > > f9
> > > > 31
> > > > c0 85 d2 74 cb eb f1 48 c7 c6 d0 c0 df 96 48 c7 c7 57 dd db 96
> > > > e8
> > > > 9c
> > > > 2d
> > > > bf ff <0f> ff 31 c0 c3 0f 1f 80 00 00 00 00 41 57 4d 89 c7 41
> > > > 56
> > > > 49
> > > > 89
> > > > [ 0.390679] ---[ end trace 9a14f34c58dc94ff ]---
> > > >
> > > >
> > > > Thanks,
> > > > --
> > > > Jaswinder Singh Rajput
> > > >
prev parent reply other threads:[~2017-12-15 15:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 11:38 Warning in i915/intel_audio.c Jaswinder Singh Rajput
2017-12-15 12:44 ` Mika Kahola
2017-12-15 13:50 ` Jaswinder Singh Rajput
2017-12-15 14:23 ` Mika Kahola
2017-12-15 15:05 ` Jaswinder Singh Rajput [this message]
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=1513350312.13113.3.camel@perfectintelligent.com \
--to=jaswinder@perfectintelligent.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.kahola@intel.com \
--cc=ramalingam.c@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=ville.syrjala@linux.intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox