Hi! On 29/07/13 19:00, Christoph Egger wrote: > [...] IIRC it happens to me both, on the 9.1 and the > 10 kernel but only recently.
It could be due to GCC-4.8 and/or use of -O2 compiler optimisations, which were enabled only in the most recent upload of each. > Any other suggestions on how one would get at the stack trace? I guess modern notebooks don't have a real serial port any more, so I suppose serial console is not an option. (And USB-based serial ports probably stop working during a crash like this). It is possible to use a dump disk, but AFAIK we don't have the necessary GDB support or wrapper to be able to read it yet. In case you want to try anyway, this worked for me in the past: * dumpon -v /dev/adX (I think an active swap partition can be used) * partition type must be 'FreeBSD' (and not 'Linux swap' for example) * kernel core will be dumped there on most types of crash, and then: * savecore -v -C /var/crash /dev/adX Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org