Date: Fri, 13 Jan 2017 23:23:13 -0700 From: Alan Somers <asomers@freebsd.org> To: lidl@freebsd.org Cc: FreeBSD-Current <freebsd-current@freebsd.org> Subject: Re: xpt related hang on sparc64 Message-ID: <CAOtMX2jZm0hKdVnZhU9HfkdvzijPz6Kru4m_%2BHDeec9wFq5r=w@mail.gmail.com> In-Reply-To: <8881811d-0102-0598-3dae-3063c614985e@FreeBSD.org> References: <8881811d-0102-0598-3dae-3063c614985e@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jan 13, 2017 at 9:49 PM, Kurt Lidl <lidl@freebsd.org> wrote: > Greetings. > > I updated my dual-processor V240 the other day: > > FreeBSD 12.0-CURRENT #26 r311929: Wed Jan 11 18:52:46 EST 2017 > lidl@spork.pix.net:/usr/obj/usr/src/sys/GENERIC sparc64 > > It works fine. > > I update a uniprocessor V120 today, to a slightly newer tree, > and it hangs when attempting to boot the new kernel: > > FreeBSD 12.0-CURRENT #27 f72e57262fe(master): Fri Jan 13 17:25:40 EST 2017 > lidl@ton.pix.net:/usr/obj/usr/src/sys/V120 sparc64 > uhub0: 4 ports with 4 removable, self powered > uhub1: 4 ports with 4 removable, self powered > run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config > run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config > run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config > run_interrupt_driven_hooks: still waiting after 240 seconds for xpt_config > run_interrupt_driven_hooks: still waiting after 300 seconds for xpt_config > > GIT hash f72e57262fe == svn r312003 > > I haven't had a chance to look into this any more deeply... > > -Kurt That error message can mean many different things. You need to boot in verbose mode to get a better idea. -Alan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOtMX2jZm0hKdVnZhU9HfkdvzijPz6Kru4m_%2BHDeec9wFq5r=w>