Date: Mon, 29 Jun 2009 04:18:37 +0400 From: Anonymous <swell.k@gmail.com> To: Ryan Stone <rysto32@gmail.com> Cc: Kostik Belousov <kostikbel@gmail.com>, Hans Ottevanger <hansot@iae.nl>, Norikatsu Shigemura <nork@freebsd.org>, Robert Noland <rnoland@freebsd.org>, freebsd-current@freebsd.org Subject: Re: panic on acpi_cpu_c1() Message-ID: <86vdmfnb8i.fsf@gmail.com> References: <20090628034654.bdb728c4.nork@FreeBSD.org> <4A47A681.3040100@iae.nl> <86bpo8b3y8.fsf@gmail.com> <1246220306.1759.43.camel@balrog.2hip.net> <20090628202739.GQ2884@deviant.kiev.zoral.com.ua> <1246230266.1759.45.camel@balrog.2hip.net> <bc2d970906281619g51e65aecn812071da6ebf5d20@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Ryan Stone <rysto32@gmail.com> writes: > Is the drm module getting loaded by the bootloader, or might a startup > script be doing it? If the module gets loaded later in the boot > process that could account for the difference. In my case with nouveau drm kernel panics either when - drm loaded with kernel at boot time - drm compiled in And panic message either about acpi_cpu_c1 or sched_idletd. I'm not sure why it changes sometimes. The kernel doesn't panic if I load drm later in boot process after kernel initialized, e.g. in single user mode or multiuser mode. > > Ryan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86vdmfnb8i.fsf>