Bug#645547: working with vesa

[Kjö Hansi Glaz <kjo@a4nancy.net.eu.org>]

Hi,

I tried appending `i915.modeset=0` and thus falling back to vesa makes
hibremation/resume working.

I also tested 3.2.0-rc4 from experimetal (with modesetting enabled) and
experience the same kind of problems that with 3.1.0. Sometimes
processes segfault, sometimes the whole kernel hangs.

Below are some call traces under 3.2.0 (copied by hand so not complete, but
I can copy next one if it helps.

Please ask for any other useful information I could provide.

1st crash
=========

gnome-panel: __find_get_block_slow

Call Trace:
__find_get_block
___getblk
__breadahead
__ext4_get_inode_loc
ext4_iget
ext4_lookup
d_alloc_and_lookup
walk_component
path_lookupat
do_path_lookup
user_path_at_empty
user_path_at_empty
vfs_fstatat
generic_permission
sys_newstat
__call_rcu
sys_faccessat
system_call_fastpath

Segfault after resume
=====================

[27139.171820] nautilus[2973]: segfault at 200000054 ip 00007f404317337a
sp 00007fff94f81008 error 4 in libglib-2.0.so.0.3000.2[7f404313e000+f6000]

2nd crash
=========

squid3: kmem_cache_alloc 0x9c/0xea

Call trace:
alloc_buffer_head
alloc_page_buffers
__get_blkid
ext4_getblk
ext4_bread
__dentry_open
htree_dirblock_to_tree
dput
ext4_htree_fill_free
ext4_readdir
ext4_readdir
ext4_readdir
do_flip_open
fillonedir
fillonedir
kmem_cache_free
sys_getdents
system_call_fastpath