Date: Sun, 19 Jan 2003 22:45:02 -0800 From: Terry Lambert <tlambert2@mindspring.com> To: Arun Sharma <arun@sharma-home.net> Cc: hackers@freebsd.org Subject: Re: listing sysinit order ? Message-ID: <3E2B9AEE.AF897AAB@mindspring.com> References: <20030118203706.GA21624@sharma-home.net> <3E29D775.EA2323A9@mindspring.com> <3E29DDDB.6000906@sharma-home.net> <3E2AA0A9.C8386AED@mindspring.com> <20030120030421.GA3176@sharma-home.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Arun Sharma wrote: > On Sun, Jan 19, 2003 at 04:57:13AM -0800, Terry Lambert wrote: > > You will get the information you seem to be asking for (unless I'm > > misunderstanding you, and you are trying to lead upo asking for a > > string identifier, and for some reason you don't want to come out > > and ask for a modification of the SYSINIT macro, for some reason...). > > That may be the right thing to do. I was worried about the unnecessary > bloat it would add to a non-debug kernel. > > However, I figured that I was barking up the wrong tree. To debug driver > initialization hangs, I need to put printfs in kern/subr_bus.c, not the > sysinit code. SYSINIT would at least get you to where it's hanging, and you may not need information over and above that, FWIW. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3E2B9AEE.AF897AAB>