From: Marek Szyprowski <m.szyprowski@samsung.com>
To: Saravana Kannan <saravanak@google.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
John Stultz <john.stultz@linaro.org>,
Android Kernel Team <kernel-team@android.com>,
Linux Samsung SOC <linux-samsung-soc@vger.kernel.org>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Subject: Re: [PATCH v3 0/3] driver core: Add device link related sysfs files
Date: Wed, 15 Jul 2020 11:02:47 +0200 [thread overview]
Message-ID: <14bafea4-3cf3-91ea-2c82-c9917ac100f1@samsung.com> (raw)
In-Reply-To: <CAGETcx9EnpxV_zKQtVToGvq5NQZJNNTCHrssEOKvkt5srYagsA@mail.gmail.com>
Hi Saravana,
On 15.07.2020 10:53, Saravana Kannan wrote:
> On Wed, Jul 15, 2020 at 1:22 AM Marek Szyprowski
> <m.szyprowski@samsung.com> wrote:
>> On 10.07.2020 15:23, Greg Kroah-Hartman wrote:
>>> On Mon, Jul 06, 2020 at 03:45:02PM -0700, Saravana Kannan wrote:
>>>> On Tue, Jun 16, 2020 at 8:45 PM Saravana Kannan <saravanak@google.com> wrote:
>>>>> On Fri, May 29, 2020 at 5:30 AM Greg Kroah-Hartman
>>>>> <gregkh@linuxfoundation.org> wrote:
>>>>>> Looks semi-sane, but it's too close to the merge window at the moment
>>>>>> for me to take this. If there's no objections by the time 5.8-rc1 is
>>>>>> out, I'll queue it up in my tree for 5.9-rc1.
>>>>> Another friendly reminder :)
>>>> *nudge* *nudge*
>>> Looks sane, given no objections, let's see what linux-next thinks about
>>> it...
>> linux-next is not very happy from this patchset... Starting from
>> next-20200713 I see a few new issues on various Samsung Exynos based
>> boards. Here are examples from Exynos4412-based Odroid U3 board (ARM
>> 32bit, kernel compiled from exynos_defconfig):
> Thanks for the bug reports.
>
>> BUG: sleeping function called from invalid context at
>> kernel/locking/mutex.c:935
>> in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 12, name: kworker/0:1
>> 2 locks held by kworker/0:1/12:
>> #0: ee8074a8 ((wq_completion)rcu_gp){+.+.}-{0:0}, at:
>> process_one_work+0x174/0x7dc
>> #1: ee921f20 ((work_completion)(&sdp->work)){+.+.}-{0:0}, at:
>> process_one_work+0x174/0x7dc
>> Preemption disabled at:
>> [<c01b10f0>] srcu_invoke_callbacks+0xc0/0x154
> Sigh... probably some SRCU screw up when the device link is deleted.
> I'll look at it by the end of this week. If you don't mind, what SRCU
> debug config caught this for you? That way, I can reproduce it on my
> end.
Just the options enabled in the default exynos_defconfig in current
linux-next. I didn't check any particular options yet.
Best regards
--
Marek Szyprowski, PhD
Samsung R&D Institute Poland
prev parent reply other threads:[~2020-07-15 9:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 19:17 Saravana Kannan
2020-05-21 19:17 ` [PATCH v3 1/3] driver core: Expose device link details in sysfs Saravana Kannan
2020-07-15 22:13 ` Guenter Roeck
2020-07-15 22:36 ` Saravana Kannan
2020-05-21 19:17 ` [PATCH v3 2/3] driver core: Add state_synced sysfs file for devices that support it Saravana Kannan
2020-05-21 19:18 ` [PATCH v3 3/3] driver core: Add waiting_for_supplier sysfs file for devices Saravana Kannan
2020-05-28 21:18 ` [PATCH v3 0/3] driver core: Add device link related sysfs files Saravana Kannan
2020-05-29 12:30 ` Greg Kroah-Hartman
2020-06-17 3:45 ` Saravana Kannan
2020-07-06 22:45 ` Saravana Kannan
2020-07-10 13:23 ` Greg Kroah-Hartman
2020-07-10 20:39 ` Saravana Kannan
[not found] ` <CGME20200715082233eucas1p261d4c5133226b800c3656c9010aa5940@eucas1p2.samsung.com>
2020-07-15 8:22 ` Marek Szyprowski
2020-07-15 8:53 ` Saravana Kannan
2020-07-15 9:02 ` Marek Szyprowski [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=14bafea4-3cf3-91ea-2c82-c9917ac100f1@samsung.com \
--to=m.szyprowski@samsung.com \
--cc=b.zolnierkie@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=john.stultz@linaro.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=saravanak@google.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
all inboxes | Powered by JetHome®