All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anton Ivanov <anton.ivanov@kot-begemot.co.uk>
To: Lance Roy <ldr709@gmail.com>
Cc: gregkh@linuxfoundation.org, Paul McKenney <paulmck@linux.ibm.com>,
	linux-um@lists.infradead.org
Subject: Re: 4.20-rc1 looks broken for UML
Date: Tue, 6 Nov 2018 18:12:08 +0000	[thread overview]
Message-ID: <56faa374-78f7-39ca-3fd0-dbcf2a137ac7@kot-begemot.co.uk> (raw)
In-Reply-To: <20181106180005.GA24578@E570.localdomain>


On 11/6/18 6:00 PM, Lance Roy wrote:
> CCing Paul McKenney. Any idea what I did wrong?

Nothing, problem on my end. Something wrong with my setup and rolling 
back your commit was a false-positive.

I apologize, please ignore. i will continue digging to try to figure out 
what's wrong.

A.

>
> Thanks,
> Lance
>
> On Tue, Nov 06, 2018 at 03:07:17PM +0000, Anton Ivanov wrote:
>> Resend - got Greg's address wrong and missed the commit author. Apologies.
>>
>> On 11/6/18 3:00 PM, Anton Ivanov wrote:
>>> On 11/5/18 10:07 PM, Richard Weinberger wrote:
>>>> Anton,
>>>>
>>>> Am Montag, 5. November 2018, 16:22:36 CET schrieb Anton Ivanov:
>>>>> This looks like something specific to ttys - the io there gets
>>>>> corruption and/or hangs.
>>>>>
>>>>> I cannot reproduce it when I ssh in.
>>>>>
>>>>> It does not look like it is the new write IRQ bugfix - that works fine
>>>>> over 4.19.
>>>>>
>>>>> Still debugging...
>>>> Hmm, I don't see this with my Debian userspace.
>>>> What exactly is your setup/config?
>>>
>>> Gotcha.
>>>
>>> 8ebfe885c65ec82a0b1e955cf99ed62664e84414 is the guilty party.
>>>
>>> With it, I get tty corruption on UML. Any attempt to push a large amount
>>> of data via the console results in spurious echoes or even a hang.
>>>
>>> Reverting it fixes things.
>>>
>>> Cc-ing Greg - it was merged from his tree.
>>>
>>> I will try to figure out what exactly is wrong with it in the meantime.
>>> On first reading it looked OK.
>>>
>>> A
>>>
>>>
>>>> Thanks,
>>>> //richard
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> linux-um mailing list
>>>> linux-um@lists.infradead.org
>>>> http://lists.infradead.org/mailman/listinfo/linux-um
>>>>
>>> _______________________________________________
>>> linux-um mailing list
>>> linux-um@lists.infradead.org
>>> http://lists.infradead.org/mailman/listinfo/linux-um
>>>

_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um


  reply	other threads:[~2018-11-06 18:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-05 13:13 4.20-rc1 looks broken for UML Anton Ivanov
2018-11-05 15:22 ` Anton Ivanov
2018-11-05 22:07   ` Richard Weinberger
2018-11-06  7:03     ` Anton Ivanov
2018-11-06 15:00     ` Anton Ivanov
2018-11-06 15:07       ` Anton Ivanov
2018-11-06 18:00         ` Lance Roy
2018-11-06 18:12           ` Anton Ivanov [this message]
2018-11-06 17:04       ` Richard Weinberger
2018-11-06 17:25         ` Anton Ivanov
2018-11-06 19:09           ` Anton Ivanov
2018-11-06 19:56             ` Richard Weinberger
2018-11-06 20:49               ` Richard Weinberger
2018-11-07  7:53                 ` Christoph Hellwig
2018-11-07 10:46                   ` Anton Ivanov
2018-11-07 13:33                     ` Anton Ivanov
2018-11-06 17:42         ` Anton Ivanov

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=56faa374-78f7-39ca-3fd0-dbcf2a137ac7@kot-begemot.co.uk \
    --to=anton.ivanov@kot-begemot.co.uk \
    --cc=gregkh@linuxfoundation.org \
    --cc=ldr709@gmail.com \
    --cc=linux-um@lists.infradead.org \
    --cc=paulmck@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.