From owner-freebsd-scsi@FreeBSD.ORG  Thu Sep  5 02:20:28 2013
Return-Path: <owner-freebsd-scsi@FreeBSD.ORG>
Delivered-To: freebsd-scsi@freebsd.org
Received: by hub.freebsd.org (Postfix, from userid 821)
 id EA5E718C; Thu,  5 Sep 2013 02:20:28 +0000 (UTC)
Date: Thu, 5 Sep 2013 02:20:28 +0000
From: John <jwd@FreeBSD.org>
To: FreeBSD SCSI <freebsd-scsi@freebsd.org>
Subject: Hung boot - mps related?
Message-ID: <20130905022028.GA28801@FreeBSD.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: freebsd-scsi@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: SCSI subsystem <freebsd-scsi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-scsi>,
 <mailto:freebsd-scsi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-scsi>
List-Post: <mailto:freebsd-scsi@freebsd.org>
List-Help: <mailto:freebsd-scsi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
 <mailto:freebsd-scsi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Sep 2013 02:20:29 -0000

Hi Folks,

   I updated one of my servers today to the latest 9-stable. The system
starts to boot up and then hangs with the following:


mps1: _mapping_add_new_device: failed to add the device with handle 0xe1 to persistent table because there is no free space available

Note, the above cycles though many devices up to 0xe1.. Then:

run_interupt_driven_hooks: still waiting after 60 seconds for xpt_config
run_interupt_driven_hooks: still waiting after 120 seconds for xpt_config
run_interupt_driven_hooks: still waiting after 180 seconds for xpt_config
run_interupt_driven_hooks: still waiting after 240 seconds for xpt_config
run_interupt_driven_hooks: still waiting after 300 seconds for xpt_config

Nothing else after the above.

   In looking through the logs, I wonder if this could be related
to the following: 

http://svnweb.freebsd.org/changeset/base/254938

   There are a number of changes in the area that seem like they
might effect this. Note, in the past, the "failed" message are
present along with the "waiting" messages, but the system continues
to boot, not hang.

   These are the same systems I've posted about in the past. The
hardware hasn't changed (Just Stable-9 :-)  The last working dmesg
output from this system is here:

http://people.freebsd.org/~jwd/r246437/dmesg.working.txt

   For grins, I did comment out the call to mapping_add_new_device()
and the system booted up, but none of the disks showed up :-(   
Currently the system is sitting, hung at the "still waiting" msg 
to see if it might recover and finish booting overnight. Or not..

   Thoughts?

Thanks,
John