linux-kernel - Re: PROBLEM: tickless scheduling

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <AANLkTilg2cn3lAIOruz6oZE7V-9uAFDORlbvTX3qxmwF@mail.gmail.com>
Date:	Mon, 10 May 2010 21:52:21 -0400
From:	Donald Allen <donaldcallen@...il.com>
To:	john stultz <johnstul@...ibm.com>
Cc:	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>
Subject: Re: PROBLEM: tickless scheduling

On Mon, May 10, 2010 at 9:12 PM, john stultz <johnstul@...ibm.com> wrote:
> On Mon, 2010-05-10 at 20:59 -0400, Donald Allen wrote:
>> On Mon, May 10, 2010 at 8:54 PM, john stultz <johnstul@...ibm.com> wrote:
>> > On Mon, May 10, 2010 at 5:18 PM, Donald Allen <donaldcallen@...il.com> wrote:
>> >> 1. Network file transfers and fscks stop on Toshiba netbook unless
>> >> system receives external events
>> >
>> > Can you provide /proc/timer_list output?
>>
>> Attached, but again, this is from the system running with tickless disabled.
>
> Is it possible to boot with the kernel showing the issue and provide the
> details?

It's a minor pain, but I'll do it.

>
>
>> > I assume booting with nohz=off from grub resolves the issue?
>>
>> Didn't know about the boot-time option (thanks for pointing it out),
>> but I wanted to build a custom kernel anyway, so i did so and disabled
>> tickless.
>
> Ok. It may still be of value to know booting with nohz=off does avoid
> the problem.

Ok. When I've got the original kernel installed and bootable, I'll try
it. I won't be able to get to this for a day or so.

/Don

>
>
> thanks
> -john
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/