[14:25] <apw> jibel, ... come tell me all about it
[14:26] <apw> jibel, ok and does hitting esc or alt-tab do anything, can you get to the text screen there ?
[14:28] <jibel> apw, esc and alt-tab do not do anything. I cannot get to the text screen. If I close the VM and reboot it displays the grub menu then the text screen
[14:28] <jibel> apw, typing on the text screen works fine
[14:28] <apw> yeah that is normal behaviour, because boot failed i guess
[14:28] <jibel> apw, using -vga cirrus instead of std works fine
[14:28] <jibel> right
[14:28] <apw> ok when these installs finish i'll try and repro it firstly, and see what i can find
[14:29] <jibel> thanks
[14:30] <apw> jibel, ok that install you reported against also had the plymouth bug which didn't let you type the password reliably
[14:30] <apw> so it could easly be two issues interacting too, sigh
[14:32] <jibel> apw, I tried on latest build too and result is the same, no input
[14:33] <apw> ack
[15:03] <apw> jibel, ok i see the same here, so i cna play with it a bit
[18:55] <leitao> rtg_, hi
[20:13] <rtg_> leitao, saw the bug response
[20:13] <bms20> Evening all (from the uk): I'm wondering if you can help: I'm using ubuntu 14.04 kernel version 3.13.0-36 - I have problems where the kernel panics regularly due to graphics issues.  Now I'd like the system to reboot when this happens.  Is it correct that setting /proc/sys/kernel/panic to something like 10 should cause a reboot?  If so, then why do I not see a reboot when I force a panic?
[20:15] <bms20> is it possible that the drm_kms_helper cannot swith or locks up somehow in switching back to text console?
[20:43] <bms20> Ok - indeed I suspect that the kernel is crashing in switching drm back to text mode.  My work around for this will be to use a negative number, hence bypassing the drm switch on line 345 of drm_fb_helper.c