From: Henry N. <hen...@ar...> - 2011-01-27 00:15:05
|
Hello Arturo, On 25.01.2011 18:46, Arturo R. wrote: > Running Debian sid on a coLinux 0.7.8 (uname -a: "Linux colinux > 2.6.33.5-co-0.7.8 #1 PREEMPT Wed Sep 1 22:49:51 UTC 2010 i686 > GNU/Linux") inside of Windows XP Pro SP3. The error is reproducible > 100% of the time. When the machine goes into standby, either > automatically or manually, init (or something else? see below), > crashes and takes the system down with it. > > I've read that gdb can't attach to init by design, so I tried strace. > Output is attached as strace.log > > Now, since I assumed the problem was with init, I switched to upstart, > but that's not working either. See upstart.log, attached. > > I've also ruled out coLinux (and with it, its kernel) by trying one of > the filesystem images they provide. When using that, there is no > problem bringing the machine in and out of standby repeatedly. > > Does anyone have any idea of how I could further narrow down where the > problem lies You should have debug symbols for init, or an init with debug symbols. Than you can load init into gdb and locate the code snip for address 0xb766d417, or you can run "objdump -Dr /sbin/init >dump.txt" and find out the address manually. The addr2line should also work for this. -- Henry N. |