Date: Fri, 6 Dec 2019 15:14:58 -0800 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Warner Losh <imp@bsdimp.com> Cc: Alexander Motin <mav@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: CAM breaks USB [was Re: USB causing boot to hang] Message-ID: <20191206231458.GA1187@troutmask.apl.washington.edu> In-Reply-To: <20191206225231.GA949@troutmask.apl.washington.edu> References: <20191206202316.GA1053@troutmask.apl.washington.edu> <20191206223144.GA3224@troutmask.apl.washington.edu> <CANCZdfrvTmb0xfQ_A6vLdzgNziSHSsD5TBiC1DCnriTaWcr-nw@mail.gmail.com> <20191206225231.GA949@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Dec 06, 2019 at 02:52:31PM -0800, Steve Kargl wrote: > > The commit message for 355010 states: > > Devices appearing on USB bus later may still require setting > kern.cam.boot_delay, but hopefully those are minority. > > There is no statement about "where" kern.cam.boot_delay should be set. > There is no statement about "what" value(s) kern.cam.boot_delay should be. > > For the record add kern.cam.boot_delay to /boot/loader.conf with the > values 0, 1, and "1" did not allow the system to boot. The system > will not boot with or without > Do I need to rebuild my kernel with the undocumented CAM_BOOT_DELAY? -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20191206231458.GA1187>