On Tuesday, 30 of October 2007, CSights wrote: > > > > Thanks, I'll try to reproduce the problem here and fix it. > > No really, thank you! Sorry for the long delay. Can you please check if you are able to reproduce the problem with 2.6.24-rc2? Thanks, Rafael - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- References:
- cannot "hibernate" if program being debugged in gdb is paused after SIGABRT in linux 2.6.23 (but can in 2.6.22.7)
- From: CSights <[email protected]>
- Re: cannot "hibernate" if program being debugged in gdb is paused after SIGABRT in linux 2.6.23 (but can in 2.6.22.7)
- From: "Rafael J. Wysocki" <[email protected]>
- Re: cannot "hibernate" if program being debugged in gdb is paused after SIGABRT in linux 2.6.23 (but can in 2.6.22.7)
- From: CSights <[email protected]>
- cannot "hibernate" if program being debugged in gdb is paused after SIGABRT in linux 2.6.23 (but can in 2.6.22.7)
- Prev by Date: Re: Buffer overflow in CIFS VFS.
- Next by Date: Re: 2.6.23-mm1 breaks C-state support on Intel T7200 x86_64
- Previous by thread: Re: cannot "hibernate" if program being debugged in gdb is paused after SIGABRT in linux 2.6.23 (but can in 2.6.22.7)
- Next by thread: Re: cannot "hibernate" if program being debugged in gdb is paused after SIGABRT in linux 2.6.23 (but can in 2.6.22.7)
- Index(es):
 |