Date: Mon, 29 Sep 2014 10:13:42 +0200 From: "=?UTF-8?Q?Jos=C3=A9_P=C3=A9rez_Arauz?=o" <fbl@aoek.com> To: Garrett Cooper <yaneurabeya@gmail.com> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: What do you use for kernel debugging? Message-ID: <20140929081149.M42132@aoek.com> In-Reply-To: <82981B04-42EF-4F06-A01D-5465D91C2B86@gmail.com> References: <20140928071641.M7664@beckpeccoz.com> <761DF16E-5383-46BA-B886-CD3358D976AA@gmail.com> <20140929002025.M8991@aoek.com> <82981B04-42EF-4F06-A01D-5465D91C2B86@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Garrett, On Sun, 28 Sep 2014 18:43:45 -0700, Garrett Cooper wrote [...] > When I was debugging getting ACPI to work on my netbook, here were > some other things I did to get the system up and going: - Built a > stripped down kernel that just contains the essential bits (CPU, > filesystem, storage). - built one kernel with debug bits and one > with release bits (titled them differently of course). - built > networking and other components as klds and loaded them at boot. > This gave me a quick turnaround time when figuring out what was > broken suspend/resume wise. It might help you isolate which drivers > or subsystems are causing boot issues as well (at least netbook > system boot is relatively quick compared to the other systems I boot > off of with gobs of ram and storage drives...). > > HTH! > -Garrett Yes, that's gold. It might not apply to the specific case where device probe does not complete, but I'll give it a try. Give me a day or two. Thank you! BR, -- José Pérez Arauzo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140929081149.M42132>