Date: Sat, 26 Jan 2008 14:49:28 -0800 From: Nate Lawson <nate@root.org> To: Mark Linimon <linimon@lonesome.com> Cc: freebsd-bugbusters@FreeBSD.org Subject: Re: upcoming bugathon this weekend Message-ID: <479BB8F8.1060103@root.org> In-Reply-To: <20080125230209.GD15402@soaustin.net> References: <20080125183914.GC21911@soaustin.net> <479A2F84.5060707@root.org> <20080125192729.GA3521@soaustin.net> <479A3A67.5070401@root.org> <20080125230209.GD15402@soaustin.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Mark Linimon wrote: > On Fri, Jan 25, 2008 at 11:37:11AM -0800, Nate Lawson wrote: >> Ok by me. The only problem I have is that a lot of people blame acpi >> when it's really a driver problem. The best acid test is to boot with >> acpi disabled and show the feature works whereas with it enabled, it fails. > > It would be great if you could write up some notes on "how to debug if > you think you are having an acpi problem". If you can do that, I'll write > them up and either put them in the wiki, or the Developer's Handbook, as > you think appropriate. > > I'm sure you'd rather have more than one person able to walk people > through debugging these problems :-) Already happened, improvements welcome: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/acpi-debug.html -- Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?479BB8F8.1060103>