[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50953E8D.9000504@suse.cz>
Date: Sat, 03 Nov 2012 16:55:57 +0100
From: Jiri Slaby <jslaby@...e.cz>
To: Sasha Levin <levinsasha928@...il.com>
CC: Jiri Slaby <jirislaby@...il.com>, gregkh@...uxfoundation.org,
alan@...ux.intel.com, linux-kernel@...r.kernel.org,
Dave Jones <davej@...hat.com>
Subject: Re: [PATCH 21/21] TTY: move tty buffers to tty_port
On 11/03/2012 03:03 AM, Sasha Levin wrote:
> On 11/02/2012 12:18 PM, Jiri Slaby wrote:
>> On 11/02/2012 05:07 PM, Sasha Levin wrote:
>>> On Fri, Nov 2, 2012 at 11:51 AM, Jiri Slaby <jslaby@...e.cz> wrote:
>>>> On 10/31/2012 04:59 PM, Sasha Levin wrote:
>>>>> So you probably want a lot more than 100k syscalls, why limit it at
>>>>> all actually?
>>>>
>>>> I unset the limit but I still can't reproduce...
>>>>
>>>>> I've attached my .config for the guest kernel as reference.
>>>>
>>>> Even using this config does not help to reproduce that.
>>>>
>>>> Do you use some special trinity params?
>>>
>>> Not really:
>>>
>>> ./trinity -m --quiet --dangerous -l off
>>
>> Oh, you run that as root??
>>
>>> Can I add something to my kernel to provide more info when it happens?
>>
>> Maybe the attached patch can tell us more...
>>
>
> Nope, I see the warnings mentioned before, without the new 'HUH' warnings.
Actually it does. It is exactly as you wrote some time earlier. The work
is scheduled after is was cancelled and should not trigger anymore. Or,
it is scheduled before it is supposed to do. Could you try the attached
patch and report what happens with that patch?
PS I can't reproduce by whatever I tried.
thanks,
--
js
suse labs
View attachment "0001-tty-debug-part-2.patch" of type "text/x-patch" (1617 bytes)
Powered by blists - more mailing lists