I hate to "bump" my own message, but I'm making some progress and I'm wondering if anyone can help me further debug. My initial message: On Mon, Jan 24, 2011 at 10:31 PM, Arturo R. <jaquer@gmail.com> wrote: > Hi all. > > Per the title, I'd love to get your input on how to debug/fix this > particular issue. A description of my setup: > > Asus UL30A-X5 Laptop > 1.3GHz Intel SU7300 Core 2 Duo > 4GB of DDR3 RAM > 500GB SATA > Intel GMA 4500MHD > > 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, or point me in the direction of the proper mailing list > to direct my question? > > My apologies if I've left out any important detail. Please let me know > if you have any questions. I've since followed the advise of a poster to colinux-users and built init and all the libraries it depends on with debugging symbols. I'm able to get a backtrace of the crash (see gdb.log, attached), but I still don't know how to pinpoint why the system crashes. I've commented out the apparent offending function in init.c and the error is indeed suppressed, but the system still hangs (no core dumped). Any help is greatly appreciated. -- Arturo R.
Attachment:
gdb.log
Description: Binary data