From: Takashi Iwai <tiwai@suse.de>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: Dmitry Vyukov <dvyukov@google.com>,
syzbot
<bot+63583aefef5457348dcfa06b87d4fd1378b26b09@syzkaller.appspotmail.com>,
aaron.lu@intel.com, alsa-devel@alsa-project.org,
Michal Hocko <mhocko@suse.com>, Jan Kara <jack@suse.cz>,
Minchan Kim <minchan@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
ying.huang@intel.com, syzkaller-bugs@googlegroups.com,
LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
shli@fb.com, David Rientjes <rientjes@google.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Andrew Morton <akpm@linux-foundation.org>,
zi.yan@cs.rutgers.edu, Matthew Wilcox <willy@linux.intel.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Subject: Re: [alsa-devel] BUG: soft lockup
Date: Mon, 06 Nov 2017 11:39:41 +0100 [thread overview]
Message-ID: <s5hy3njlmhe.wl-tiwai@suse.de> (raw)
In-Reply-To: <20171102090951.drjf7wc2urcmtla5@node.shutemov.name>
On Thu, 02 Nov 2017 10:09:51 +0100,
Kirill A. Shutemov wrote:
>
> On Thu, Nov 02, 2017 at 09:23:58AM +0100, Takashi Iwai wrote:
> >
> > Currently the least ALSA timer interrupt period is limited to 1ms.
> > Does it still too much?
> >
> > Can the reproducer triggers it reliably? If yes, could you forward
> > it, too (and config as well), so that I'll try to dig down more exact
> > code paths?
>
> All of that is part of original report:
>
> http://lkml.kernel.org/r/94eb2c19df188b1926055cf13c21@google.com
>
> marc.info hasn't stored repro.c for some reasone. Attached.
>
> I've just check it reproduces reliably for me in KVM.
>
> I also checked that it's not specific to THP -- still trigirable with huge
> pages disabled.
I guess this is the same issue Jerome forwarded recently, and it was
fixed by limiting the amount of ALSA timer instances. I queued the
fix in sound git tree for-linus branch, commit
9b7d869ee5a77ed4a462372bb89af622e705bfb8
ALSA: timer: Limit max instances per timer
It'll be likely included in 4.14 final.
thanks,
Takashi
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-11-06 10:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 19:54 syzbot
2017-11-01 19:57 ` Dmitry Vyukov
2017-11-02 8:23 ` [alsa-devel] " Takashi Iwai
2017-11-02 9:09 ` Kirill A. Shutemov
2017-11-06 10:39 ` Takashi Iwai [this message]
2017-11-06 10:42 ` Dmitry Vyukov
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=s5hy3njlmhe.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=aaron.lu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=alsa-devel@alsa-project.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=bot+63583aefef5457348dcfa06b87d4fd1378b26b09@syzkaller.appspotmail.com \
--cc=dvyukov@google.com \
--cc=jack@suse.cz \
--cc=kirill.shutemov@linux.intel.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=minchan@kernel.org \
--cc=peterz@infradead.org \
--cc=rientjes@google.com \
--cc=sfr@canb.auug.org.au \
--cc=shli@fb.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=willy@linux.intel.com \
--cc=ying.huang@intel.com \
--cc=zi.yan@cs.rutgers.edu \
/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