RE: spin lock panic ...
On Fri, 23 Mar 2001, John Baldwin wrote: > > On 24-Mar-01 The Hermit Hacker wrote: > > On Fri, 23 Mar 2001, John Baldwin wrote: > > > >> > >> On 24-Mar-01 The Hermit Hacker wrote: > >> > > >> > Over the past few days, I reformatted my computer clean, installed > >> > 4.2-RELEASE onto her and just finished upgrading to the latest 5.x kernel > >> > and world ... went to ports/x11/XFree86-4 and did a 'make install' ... > >> > after awhile, it panic'd as below: > >> > > >> > panic: spin lock sched lock held by 0xcb332840 for > 5 seconds > >> > cpuid = 1; lapic.id = 0100 > >> > Debugger("panic") > >> > > >> > CPU1 stopping CPUs: 0x0001... stopped. > >> > > >> > Now, I do have DDB enabled in the kernel ... but, for the life of me, I > >> > can't seem to find any docs on the keystroke required to drop into it :( > >> > 'man ddb' doesn't document it that I can find, nor does LINT ... > >> > >> Uhh, if it panic'd, it should already be in ddb at a db> prompt assuming you > >> have DDB in your kernel. > > > > didn't ... last line was as above ... I've even tested my DDB to make sure > > I can get to the db> prompt after alfred reminded me of the ctl-alt-esc to > > get there, and it works ... > > Well, that meants it most likely deadlocked trying to get into the debugger. I > haven't seen any deadlocks like this in months though. I swear, my compuer is just so special :) it hasn't happened since ... re started the X compile, it finished fine and installed .. *shrug* To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: spin lock panic ...
On 24-Mar-01 The Hermit Hacker wrote: > On Fri, 23 Mar 2001, John Baldwin wrote: > >> >> On 24-Mar-01 The Hermit Hacker wrote: >> > >> > Over the past few days, I reformatted my computer clean, installed >> > 4.2-RELEASE onto her and just finished upgrading to the latest 5.x kernel >> > and world ... went to ports/x11/XFree86-4 and did a 'make install' ... >> > after awhile, it panic'd as below: >> > >> > panic: spin lock sched lock held by 0xcb332840 for > 5 seconds >> > cpuid = 1; lapic.id = 0100 >> > Debugger("panic") >> > >> > CPU1 stopping CPUs: 0x0001... stopped. >> > >> > Now, I do have DDB enabled in the kernel ... but, for the life of me, I >> > can't seem to find any docs on the keystroke required to drop into it :( >> > 'man ddb' doesn't document it that I can find, nor does LINT ... >> >> Uhh, if it panic'd, it should already be in ddb at a db> prompt assuming you >> have DDB in your kernel. > > didn't ... last line was as above ... I've even tested my DDB to make sure > I can get to the db> prompt after alfred reminded me of the ctl-alt-esc to > get there, and it works ... Well, that meants it most likely deadlocked trying to get into the debugger. I haven't seen any deadlocks like this in months though. -- John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: spin lock panic ...
On Fri, 23 Mar 2001, John Baldwin wrote: > > On 24-Mar-01 The Hermit Hacker wrote: > > > > Over the past few days, I reformatted my computer clean, installed > > 4.2-RELEASE onto her and just finished upgrading to the latest 5.x kernel > > and world ... went to ports/x11/XFree86-4 and did a 'make install' ... > > after awhile, it panic'd as below: > > > > panic: spin lock sched lock held by 0xcb332840 for > 5 seconds > > cpuid = 1; lapic.id = 0100 > > Debugger("panic") > > > > CPU1 stopping CPUs: 0x0001... stopped. > > > > Now, I do have DDB enabled in the kernel ... but, for the life of me, I > > can't seem to find any docs on the keystroke required to drop into it :( > > 'man ddb' doesn't document it that I can find, nor does LINT ... > > Uhh, if it panic'd, it should already be in ddb at a db> prompt assuming you > have DDB in your kernel. didn't ... last line was as above ... I've even tested my DDB to make sure I can get to the db> prompt after alfred reminded me of the ctl-alt-esc to get there, and it works ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: spin lock panic ...
On 24-Mar-01 The Hermit Hacker wrote: > > Over the past few days, I reformatted my computer clean, installed > 4.2-RELEASE onto her and just finished upgrading to the latest 5.x kernel > and world ... went to ports/x11/XFree86-4 and did a 'make install' ... > after awhile, it panic'd as below: > > panic: spin lock sched lock held by 0xcb332840 for > 5 seconds > cpuid = 1; lapic.id = 0100 > Debugger("panic") > > CPU1 stopping CPUs: 0x0001... stopped. > > Now, I do have DDB enabled in the kernel ... but, for the life of me, I > can't seem to find any docs on the keystroke required to drop into it :( > 'man ddb' doesn't document it that I can find, nor does LINT ... Uhh, if it panic'd, it should already be in ddb at a db> prompt assuming you have DDB in your kernel. -- John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: spin lock panic ...
* The Hermit Hacker <[EMAIL PROTECTED]> [010323 16:17] wrote: > On Fri, 23 Mar 2001, Alfred Perlstein wrote: > > > * The Hermit Hacker <[EMAIL PROTECTED]> [010323 16:09] wrote: > > > > > > Now, I do have DDB enabled in the kernel ... but, for the life of me, I > > > can't seem to find any docs on the keystroke required to drop into it :( > > > 'man ddb' doesn't document it that I can find, nor does LINT ... > > > > ctrl+alt+esc. > > perfect, thanks ... is this actually documented somewhere that I'm > forgetting to look? :( /usr/src/sys/ ? :) http://www.freebsd.org/handbook/x18709.html -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] Daemon News Magazine in your snail-mail! http://magazine.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: spin lock panic ...
On Fri, 23 Mar 2001, Alfred Perlstein wrote: > * The Hermit Hacker <[EMAIL PROTECTED]> [010323 16:09] wrote: > > > > Now, I do have DDB enabled in the kernel ... but, for the life of me, I > > can't seem to find any docs on the keystroke required to drop into it :( > > 'man ddb' doesn't document it that I can find, nor does LINT ... > > ctrl+alt+esc. perfect, thanks ... is this actually documented somewhere that I'm forgetting to look? :( To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: spin lock panic ...
* The Hermit Hacker <[EMAIL PROTECTED]> [010323 16:09] wrote: > > Now, I do have DDB enabled in the kernel ... but, for the life of me, I > can't seem to find any docs on the keystroke required to drop into it :( > 'man ddb' doesn't document it that I can find, nor does LINT ... ctrl+alt+esc. -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message