linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Vyukov <dvyukov@google.com>
To: Shuah Khan <shuah@kernel.org>
Cc: Valentina Manea <valentina.manea.m@gmail.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	USB list <linux-usb@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: WARNING: ODEBUG bug in vudc_probe
Date: Fri, 7 Sep 2018 18:25:18 +0200	[thread overview]
Message-ID: <CACT4Y+ZV2aMWjobgV=-aUdSLnGU=_2yuf2TOx4TD8ApoVqRVYw@mail.gmail.com> (raw)
In-Reply-To: <7c37c201-8bca-ffa4-5e8d-5e0b4b268b3f@kernel.org>

On Fri, Sep 7, 2018 at 6:20 PM, Shuah Khan <shuah@kernel.org> wrote:
> On 09/07/2018 10:14 AM, Dmitry Vyukov wrote:
>> On Fri, Sep 7, 2018 at 6:03 PM, Shuah Khan <shuah@kernel.org> wrote:
>>> Hi Dmitry,
>>>
>>> On 09/07/2018 04:54 AM, Dmitry Vyukov wrote:
>>>> Hi,
>>>>
>>>> I am getting the following error while booting kernel on upstream
>>>> commit a49a9dcce802b3651013f659813df1361d306172, config is attached.
>>>> Seems there is some kind of resource leak.
>>>>
>>>> Thanks
>>>
>>> Odd. This commit has nothing to do with vudc.
>>
>> This is not the guilty commit, I just described state of my tree.
>>
>
> Can you send me the full dmesg?

Here it is:

https://gist.githubusercontent.com/dvyukov/e9dec59fb23da9cedd8ab07a7d8c78ae/raw/3ee13c7a1f406c9927ca3b16db262f2c78e84536/gistfile1.txt

  reply	other threads:[~2018-09-07 16:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-07 10:54 WARNING: ODEBUG bug in vudc_probe Dmitry Vyukov
2018-09-07 16:03 ` Shuah Khan
2018-09-07 16:14   ` Dmitry Vyukov
2018-09-07 16:20     ` Shuah Khan
2018-09-07 16:25       ` Dmitry Vyukov [this message]
2019-03-11 14:16         ` Dmitry Vyukov
2019-03-11 14:18           ` Dmitry Vyukov
2019-03-14 17:15             ` shuah
2019-03-15  8:27               ` 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='CACT4Y+ZV2aMWjobgV=-aUdSLnGU=_2yuf2TOx4TD8ApoVqRVYw@mail.gmail.com' \
    --to=dvyukov@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=valentina.manea.m@gmail.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;
as well as URLs for NNTP newsgroup(s).