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: <c43b2e150902071452o3853d534qfda0a4ebe66e835d@mail.gmail.com>
Date:	Sat, 7 Feb 2009 23:52:06 +0100
From:	wixor <wixorpeek@...il.com>
To:	Alexey Dobriyan <adobriyan@...il.com>
Cc:	JosephChan@....com.tw, linux-kernel@...r.kernel.org
Subject: Re: viafb triggers BUG at mm/vmalloc.c:294 [kernel 2.6.28.3]

No idea how revelant is this: machine has physically 1gb of ram (two
512 modules). 256megs are delegated to video card by bios (and I
cannot change this) and kernel reports only 7xx megs available. Then
kernel complains that it cannot allocate memory resource for device
0000:01:00.0 at 0xc0000000-0xbfffffff which looks like that video ram.
Xorg 2d video driver (the via open source one) runs smoothly (of
course i'm not testing viafb with x running). It says things about
mapping memory at 0xc[something]. Attaching my Xorg.0.log, maybe it's
useful. Will try that vmalloc trick tomorrow.

--
wixor

Download attachment "Xorg.0.log" of type "application/octet-stream" (41352 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ