lkml.org 
[lkml]   [2012]   [Nov]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 21/21] TTY: move tty buffers to tty_port
On 11/03/2012 11:55 AM, Jiri Slaby wrote:
> 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@suse.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,
>

Interesting...

[ 388.783955] tty is bad=0 ops= (null)Pid: 6480, comm: kworker/1:2 Tainted: G W
3.7.0-rc3-next-20121102-sasha-00002-gbb570e0-dirty #111


Thanks,
Sasha


\
 
 \ /
  Last update: 2012-11-04 00:21    [W:0.056 / U:0.540 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site