Comment 14 for bug 754711

Hi Seth,

Yes, I apologize, I guess I panicked about being unable to switch consoles so I started doing nonsense.

So let's go one step at a time:

here's vmalloc (top offenders) and meminfo from a boot without xforcevesa and nomodeset (i.e. using the nouveau driver as during the observed failures).

0xf845e000-0xf8481000 143360 kvmalloc+0x3f/0x50 pages=34 vmalloc
0xf8482000-0xf84a5000 143360 kvmalloc+0x3f/0x50 pages=34 vmalloc
0xf8303000-0xf832b000 163840 module_alloc_update_bounds+0x19/0x70 pages=39 vmalloc
0xf84da000-0xf8507000 184320 module_alloc_update_bounds+0x19/0x70 pages=44 vmalloc
0xf83ef000-0xf842f000 262144 module_alloc_update_bounds+0x19/0x70 pages=63 vmalloc
0xf839b000-0xf83e5000 303104 module_alloc_update_bounds+0x19/0x70 pages=73 vmalloc
0xf86a4000-0xf873d000 626688 module_alloc_update_bounds+0x19/0x70 pages=152 vmalloc
0xf8201000-0xf82b2000 724992 sys_swapon+0x428/0x8a0 pages=176 vmalloc
0xf87fc000-0xf89fd000 2101248 drm_ht_create+0x54/0xd0 [drm] pages=512 vmalloc
0xfb602000-0xfb803000 2101248 drm_ht_create+0x54/0xd0 [drm] pages=512 vmalloc
0xfed76000-0xfef77000 2101248 snd_malloc_sgbuf_pages+0x1a5/0x202 [snd_page_alloc] vmap
0xfb300000-0xfb601000 3149824 ttm_bo_kmap+0xff/0x120 [ttm] phys=d000c000 ioremap
0xfe180000-0xfe571000 4132864 ttm_bo_kmap+0xff/0x120 [ttm] phys=b000c000 ioremap
0xff000000-0xff400000 4194304 pcpu_get_vm_areas+0x0/0x4c0 vmalloc
0xfe572000-0xfe973000 4198400 snd_malloc_sgbuf_pages+0x1a5/0x202 [snd_page_alloc] vmap
0xfe974000-0xfed75000 4198400 snd_malloc_sgbuf_pages+0x1a5/0x202 [snd_page_alloc] vmap
0xf8a00000-0xf9201000 8392704 nouveau_load+0x9c/0x4f0 [nouveau] phys=ae000000 ioremap
0xfb880000-0xfc081000 8392704 nouveau_load+0x9c/0x4f0 [nouveau] phys=aa000000 ioremap
0xf9280000-0xfb281000 33558528 nouveau_load+0x2a9/0x4f0 [nouveau] phys=ac000000 ioremap
0xfc100000-0xfe101000 33558528 nouveau_load+0x2a9/0x4f0 [nouveau] phys=cc000000 ioremap

VmallocTotal: 122880 kB
VmallocUsed: 112688 kB
VmallocChunk: 4088 kB

I will test the mainline build you suggested and report back as soon as I have something.

Finally, for the vt switching problem, I ran the command you suggested and I had the same behavior (i.e. can't switch to the vt). However, I've seen this on one other system (a Dell Vostro 3400 with dual graphics which is using the intel driver), so I think I'll do some more testing about that and report it as a different bug.

Thanks so much for your help!