10.1 hangs during boot on Intel DP35DP board

[Christopher R. Bowman]

> On Dec 8, 2014, at 10:32 AM, John Baldwin <jhb at freebsd.org> wrote:
> 
> On Saturday, December 06, 2014 01:37:09 PM Christopher R. Bowman wrote:
>> John,
>> Its still sitting but I turned on verbose output and it's been sitting for
>> 10 minutes so far without any further output. Christopher.
> 
> Grrr, then it might be stuck elsewhere than the interrupt config hooks.  
> Unfortunately we'd really need to find a way to get into DDB.  I think GENERIC 
> doesn't include BREAK_TO_DEBUGGER by default, so Ctrl-Alt-Esc doesn't work out 
> of the box.  Can you break into the loader prompt and type 'set 
> debug.kdb.break_to_debugger=1' before booting?  Ctrl-Alt-Esc should then work 
> when it hangs.  Once that happens, please get the output of 'ps' from DDB.
> 
>> --
>> Christopher R. Bowman
>> 
>>> On Dec 5, 2014, at 7:20 AM, John Baldwin <jhb at freebsd.org> wrote:
>>> 
>>> On Thursday, December 04, 2014 07:42:48 PM Christopher R. Bowman wrote:
>>>>> On Dec 4, 2014, at 8:39 AM, John Baldwin <jhb at freebsd.org> wrote:
>>>>>> On Wednesday, December 03, 2014 9:36:01 am Adrian Chadd wrote:
>>>>>> Hi,
>>>>>> 
>>>>>> I'm not sure - it may be that the timekeeping stuff is a bit confused.
>>>>>> Maybe it's now time to file a bug and see if we can loop the
>>>>>> timekeeping folk into it.
>>>>> 
>>>>> This is probably not timekeeping.  That message is just the last thing
>>>>> printed before the interrupt-driven hooks are run.  If you booted a HEAD
>>>>> snapshot the kernel should have DDB compiled in.  Please drop into DDB
>>>>> using Ctrl-Alt-Esc and then run 'show conifhk' and reply here with the
>>>>> output please.
>>>> 
>>>> John,
>>>> 
>>>>   Thank you for responding.  I tried that but the machine seemed wedged
>>>>   at
>>>> 
>>>> that point.  I can’t drop into DDB using Ctrl-Alt-Esc nor can I do
>>>> Ctrl-Alt-Del to reboot.  All I can do it push the reset button.
>>>> Christopher
>>> 
>>> If you let it sit for 60 seconds it should print out a message telling you
>>> what it is waiting on.
> 
> 
> -- 
> John Baldwin


John,
	I tried this twice on the off chance I typed it wrong once.  This had no effect.  After letting the machine sit for 5 minutes there was no further output or prompt.  Doesn’t look like it dropped into the debugger.  Any more suggestion?
Christopher