-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jason Wessel wrote: > Pete/Piet Delaney wrote: >> Sounds great to me; avoiding spin locks() is a hassle. >> >> Ever noticed a problem with kgdb surviving a weekend of non-use? >> >> I hit a breakpoint on Saturday and hoped to continue looking at it >> today but the kgdb-stub, as usual, got out of phase and I had >> to re-do the test that caused the breakpoint; I've seen it happen >> many times. >> >> - -piet >> > > Do you have a gdb serial log that shows the connection was actually > still alive?
I do keep a bit of kgdb stub logging enabled but looking back through my console log don't see anything. I wouldn't worry about it. I was using my modified 2.6.12 patch. > > Depending on what you are debugging the state of timers and real-time > clock could have something to do with it, when leaving the system paused > for that length of time. As you probably know KGDB will busy spin the > processors the whole time that KGDB is active. Yea, that's most of what I what I log even when using kgdb. - ---------------------------------------------------------------------------- [ 367.070848] L:8 <cpu:0> kgdb_handle_exception: debugger_step:1, kgdb_contthread:00000000 [ 367.134134] L:9 <cpu:0> kgdb_roundup_cpus(flags:2): processor:0 Calling send_IPI_allbutself(APIC_DM_NMI); [ 367.207688] L:10 <cpu:0> kgdb_handle_exception: procindebug[procid:0]:0 = 1; [Wait for other CPU's] [ 367.503034] L:11 <cpu:0> kgdb_notify: return NOTIFY_STOP [ 367.699547] L:14 <cpu:0> kgdb_notify: Calling kgdb_handle_exception(); [ 367.753713] L:15 <cpu:0> kgdb_handle_exception: debugger_step:1, kgdb_contthread:00000000 [ 367.819281] L:16 <cpu:0> kgdb_roundup_cpus(flags:2): processor:0 Calling send_IPI_allbutself(APIC_DM_NMI); [ 367.895116] L:17 <cpu:0> kgdb_handle_exception: procindebug[procid:0]:0 = 1; [Wait for other CPU's] [ 368.014918] L:18 <cpu:0> kgdb_notify: return NOTIFY_STOP [ 368.211423] L:21 <cpu:0> kgdb_notify: Calling kgdb_handle_exception(); [ 368.265059] L:22 <cpu:0> kgdb_handle_exception: debugger_step:1, kgdb_contthread:00000000 [ 368.330057] L:23 <cpu:0> kgdb_roundup_cpus(flags:2): processor:0 Calling send_IPI_allbutself(APIC_DM_NMI); [ 368.405322] L:24 <cpu:0> kgdb_handle_exception: procindebug[procid:0]:0 = 1; [Wait for other CPU's] [ 368.529410] L:25 <cpu:0> kgdb_notify: return NOTIFY_STOP - ------------------------------------------------------------------------------- > It is also plausible > that the system's NET_POLL driver had a failure as it would certainly > continue to transmit and receive response for ARP requests. I may have modified that for vmware to avoid a deadlock. > > I have not seen this type of failure first hand, but I am interested if > there is a way to further characterize what is going on, as well as > understanding how the kernel was configured and what hardware it is > running on. If I hit it again I'll send you the console log. Perhaps it's worthwhile to add a few more debug printf's and enable them when I leave kgdb running over night. I use multiple debug level to trace the stub so I'd just have to increase it just before leaving. - -piet > > Jason. > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGSmd0JICwm/rv3hoRAn7RAJwLKWOsrFRKuPwR2gSIp067x1EkXQCfe2d0 SO8ovvpjB/P8qTkFgSVuMVo= =Nw7o -----END PGP SIGNATURE----- ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Kgdb-bugreport mailing list Kgdb-bugreport@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport
