(In reply to comment #5) >How do things go if you take the advice the > kernel gives and add "vmalloc=256M" to your kernel commandline?
After adding vmalloc=256M in kernel commandline, 2 gpu work well in kernel-PAE-2.6.29-0.267.rc8.git4.fc11.i686.
$ dmesg | grep vmalloc Kernel command line: ro root=UUID=7fb39964-2a89-4978-87a5-deca9f9b732b vmalloc=256M vmalloc : 0xef7fe000 - 0xff7fe000 ( 256 MB) swap_cgroup: uses 1008 bytes of vmalloc for pointer array space and 1032192 bytes to hold mem_cgroup pointers on swap
(In reply to comment #5)
>How do things go if you take the advice the
> kernel gives and add "vmalloc=256M" to your kernel commandline?
After adding vmalloc=256M in kernel commandline, 2 gpu work well in kernel- PAE-2.6. 29-0.267. rc8.git4. fc11.i686.
$ dmesg | grep vmalloc 7fb39964- 2a89-4978- 87a5-deca9f9b73 2b vmalloc=256M
Kernel command line: ro root=UUID=
vmalloc : 0xef7fe000 - 0xff7fe000 ( 256 MB)
swap_cgroup: uses 1008 bytes of vmalloc for pointer array space and 1032192 bytes to hold mem_cgroup pointers on swap