Date: Thu, 4 Nov 2010 21:37:22 -0600 From: Scott Long <scottl@samsco.org> To: Alexander Best <arundel@freebsd.org> Cc: freebsd-scsi@freebsd.org Subject: Re: panic with high kern.cam.boot_delay value Message-ID: <580A1CEB-4217-4BE6-89BF-BF309C9EF2A4@samsco.org> In-Reply-To: <20101105012902.GA27499@freebsd.org> References: <20101105012902.GA27499@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Nov 4, 2010, at 7:29 PM, Alexander Best wrote: > hi there, >=20 > i just stumbled upon a panic in connection with a very high = kern.cam.boot_delay > value (=3D100000). this is on HEAD (r214809; amd64). unfortunately i = couldn't > enter the debugger, because the panic occured before my usb keyboard = attached. >=20 options DDB options KDB options KDB_UNATTENDED Do you have the ability to attach a serial console? > the panic however occured in sched_priority(). can anybody reproduce = this? just > before the panic i saw some xpt_* message in connection with a 60 = second delay. >=20 The 60 second message might have something to do with the = config_intrhook service complaining about the long delay that you've = imposed on the boot process. It'll panic if you have INVARIANTS set and = it waits for five 60 second intervals. Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?580A1CEB-4217-4BE6-89BF-BF309C9EF2A4>