Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 22 Nov 2019 14:07:42 -0500
From:      Alexander Motin <mav@FreeBSD.org>
To:        Ian Lepore <ian@freebsd.org>, src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org
Subject:   Re: svn commit: r355010 - in head/sys/cam: . scsi
Message-ID:  <ac1542ca-1ed4-dd38-b035-77b29c9b7c60@FreeBSD.org>
In-Reply-To: <512688616ef83a24a907a8ba3cee76cb9d53490b.camel@freebsd.org>
References:  <201911221839.xAMIdpMa056572@repo.freebsd.org> <512688616ef83a24a907a8ba3cee76cb9d53490b.camel@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 22.11.2019 14:00, Ian Lepore wrote:
> On Fri, 2019-11-22 at 18:39 +0000, Alexander Motin wrote:
>> Author: mav
>> Date: Fri Nov 22 18:39:51 2019
>> New Revision: 355010
>> URL: https://svnweb.freebsd.org/changeset/base/355010
>>
>> Log:
>>   Make CAM use root_mount_hold_token() to delay boot.
>>   
>>   Before this change CAM used config_intrhook_establish() for this
>> purpose,
>>   but that approach does not allow to delay it again after releasing
>> once.
>>   
>>   USB stack uses root_mount_hold() to delay boot until bus scan is
>> complete.
>>   But once it is, CAM had no time to scan SCSI bus, registered by
>> umass(4),
>>   if it already done other scans and called
>> config_intrhook_disestablish().
>>   The new approach makes it work smooth, assuming the USB device is
>> found
>>   during the initial bus scan.  Devices appearing on USB bus later
>> may still
>>   require setting kern.cam.boot_delay, but hopefully those are
>> minority.
>>   
>>   MFC after:	2 weeks
>>   Sponsored by:	iXsystems, Inc.
>>
> 
> This is probably the fix for this PR?
> 
>   https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=144824

Probably.  It is a very old issue.  I've taken the PR.

-- 
Alexander Motin



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ac1542ca-1ed4-dd38-b035-77b29c9b7c60>