linux-kernel - Re: PROBLEM: oom killer and swap weirdness on 2.6.3* kernels

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]

Date:	Wed, 28 Jul 2010 17:14:52 +1000
From:	dave b <db.pub.mail@...il.com>
To:	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
Cc:	David Rientjes <rientjes@...gle.com>,
	Hugh Dickins <hughd@...gle.com>, linux-kernel@...r.kernel.org,
	linux-mm@...ck.org
Subject: Re: PROBLEM: oom killer and swap weirdness on 2.6.3* kernels

On 28 July 2010 15:06, KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com> wrote:
>> On 27 July 2010 21:14, KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com> wrote:
>> >> On 27 July 2010 18:09, dave b <db.pub.mail@...il.com> wrote:
>> >> > On 27 July 2010 16:09, KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com> wrote:
>> >> >>> > Do you mean the issue will be gone if disabling intel graphics?
>> >> >>> It may be a general issue or it could just be specific :)
>> >> >
>> >> > I will try with the latest ubuntu and report how that goes (that will
>> >> > be using fairly new xorg etc.) it is likely to be hidden issue just
>> >> > with the intel graphics driver. However, my concern is that it isn't -
>> >> > and it is about how shared graphics memory is handled :)
>> >>
>> >>
>> >> Ok my desktop still stalled and no oom killer was invoked when I added
>> >> swap to a live-cd of 10.04 amd64.
>> >>
>> >> *Without* *swap* *on* - the oom killer was invoked - here is a copy of it.
>> >
>> > This stack seems similar following bug. can you please try to disable intel graphics
>> > driver?
>> >
>> > https://bugzilla.kernel.org/show_bug.cgi?id=14933
>>
>> Ok I am not sure how to do that :)
>> I could revert the patch and see if it 'fixes' this :)
>
> Oops, no, revert is not good action. the patch is correct.
> probably my explanation was not clear. sorry.
>
> I did hope to disable 'driver' (i.e. using vga), not disable the patch.

Oh you mean in xorg, I will also blacklist the module. Sure that patch
might not it but in 2.6.26 the problem isn't there :)
--
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/