[Bug 1826684] Re: containerd is polling on a pselect every 20, 000 nanoseconds causing rapid system wakeup events

2021-01-04 Thread Tomas Janousek
@paride I'm seeing cca 20 wakeups/s in eventstat and strace shows some nanosleeps and epoll_waits which I think is the modern equivalent of pselect6. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1826684] Re: containerd is polling on a pselect every 20, 000 nanoseconds causing rapid system wakeup events

2020-12-23 Thread Tomas Janousek
It's definitely reproducible with the latest 1.4.3~ds1-1 in Debian so I don't think it's likely to be fixed in other versions either. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826684 Title:

[Bug 1727662]

2019-11-17 Thread Tomas Janousek
I was experiencing the same issue with a ThinkPad 25 (which is almost the same thing as T470) and I implemented these precautions as a workaround: - disable DPMS when docked and external monitors enabled - never switch VTs with external monitors enabled - always disable external monitors before

[Bug 1626436] Re: [4.8 regression] boot has become very slow

2017-02-02 Thread Tomas Janousek
So I did a little bisecting today on mainline x86_64 kernels with CONFIG_SLUB: v4.4 Startup finished in 2.718s (kernel) + 11.831s (userspace) = 14.549s v4.5 Startup finished in 2.707s (kernel) + 12.777s (userspace) = 15.484s

[Bug 1626436] Re: [4.8 regression] boot has become very slow

2017-02-01 Thread Tomas Janousek
Are you guys aware of any other patches that went to mainline and may affect this? I've been hit by this issue since 4.6/4.7-ish days and can still reproduce it with 4.9.7. The two patches do help, but it's far from perfect: 4.9.7: Startup finished in 3.498s (kernel) + 20.462s (userspace) =

[Bug 815148] Re: iwlagn wifi driver in wpa mode corrupts processes' memory

2012-04-02 Thread Tomas Janousek
This was fixed in upstream 3.3-rc4 — the FP corruption bug. (I have no idea about Ubuntu though, sorry.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/815148 Title: iwlagn wifi driver in wpa mode

[Bug 815148] Re: iwlagn wifi driver in wpa mode corrupts processes' memory

2011-11-17 Thread Tomas Janousek
Marvin, are you running a 64-bit system? Did you run 32-bit before? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/815148 Title: iwlagn wifi driver in wpa mode corrupts processes' memory To manage

[Bug 815148] Re: iwlagn wifi driver in wpa mode corrupts processes' memory

2011-10-29 Thread Tomas Janousek
I am experiencing the same error on Debian with manually compiled upstream kernel 3.1 (and with 3.0 as well, including distro kernel). Any ideas what might have changed in Oneric Ocelot that fixed the issue? For example the firmware? Could you please tell me what this does for you: $ dmesg | grep

[Bug 815148] Re: iwlagn wifi driver in wpa mode corrupts processes' memory

2011-10-29 Thread Tomas Janousek
Well, I guess I can just try the 17.168.5.3 firmware from upstream and test whether that works. Sorry for the noise. :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/815148 Title: iwlagn wifi

[Bug 815148] Re: iwlagn wifi driver in wpa mode corrupts processes' memory

2011-10-29 Thread Tomas Janousek
Well, new firmware doesn't help. It must be something else, then. Anyway, I have this problem only with WPA-EAP networks — my home WPA2-PSK works well. I'm not sure about WPA2, but I guess that would be problematic too. Perhaps it might help to explain the issue. -- You received this bug

[Bug 815148] Re: iwlagn wifi driver in wpa mode corrupts processes' memory

2011-10-29 Thread Tomas Janousek
And pulling in davem's net-next (networking changes scheduled for linux 3.2) doesn't help either. Seriously guys, are you sure it works for you? :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 523558] Re: Synaptics cursor speed is not screen-dependent - speed on small screen is too high after connecting big external monitor

2010-11-11 Thread Tomas Janousek
As far as I know, this behaviour is more or less intentional and the _bug_ is that it can't be turned off, even in the newest versions of X and synaptics. A hackish workaround is here: https://github.com/liskin/patches/blob/master/hacks/xserver-xorg-input-

[Bug 523558] Re: Synaptics cursor speed is not screen-dependent - speed on small screen is too high after connecting big external monitor

2010-11-11 Thread Tomas Janousek
Oh. Could you perhaph give me a link to that patch? I guess it's less hacky than this patch of mine. Thanks. -- Synaptics cursor speed is not screen-dependent - speed on small screen is too high after connecting big external monitor https://bugs.launchpad.net/bugs/523558 You received this bug

[Bug 334626] Re: Xorg intermittent segv in XkbSendMap in ProcXkbGetKbdByName

2009-05-19 Thread Tomas Janousek
This looks very similar to https://bugs.freedesktop.org/show_bug.cgi?id=21464 ** Bug watch added: freedesktop.org Bugzilla #21464 https://bugs.freedesktop.org/show_bug.cgi?id=21464 -- Xorg intermittent segv in XkbSendMap in ProcXkbGetKbdByName https://bugs.launchpad.net/bugs/334626 You