I discussed this issue with jcristau and wferi a few days ago. It is not easy to know how to debug this, but one idea is to modify the initrd.gz content load netconsole and use this to get kernel messages from the crash. When the system crash, the keyboard is dead (Alt-F4 or Alt-Ctrl-F4 do not work), and there seem to be no way to get information out at this point.
To set up a netconsole, code like this would need to be added somewhere, for example in /lib/debian-installer-startup.d/ before starting X: modprobe netconsole netconsole=@/,@1.2.3.4/00:11:22:33:44:55 1.2.3.4 is the target ip, where an udp receiver need to be set up and 00:11:22:33:44:55 is the gateway mac, if needed. I hope to find time to set up such test, but do not expect it to happen any time soon. :( Christian Perrier mentioned on IRC that he is also using a D505 as a test laptop, and he do not have the same problem with g-i. He do not use PXE, but I do not belive that matter. I tried to boot a isohybrid ISO image from a USB stick, and it had the same problem with g-i. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
