Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 30 Nov 2016 09:59:27 +0800
From:      Sepherosa Ziehau <sepherosa@gmail.com>
To:        John Baldwin <jhb@freebsd.org>
Cc:        "freebsd-current@freebsd.org" <current@freebsd.org>
Subject:   Re: Please test EARLY_AP_STARTUP
Message-ID:  <CAMOc5cz_KzkJnh-QDTWhpr%2BF0nOPcp9YF3YLseUJ=qQQvW_-EA@mail.gmail.com>
In-Reply-To: <5196546.NF2ntCjvkx@ralph.baldwin.cx>
References:  <7005233.xZtqgRZ2t6@ralph.baldwin.cx> <CAMOc5czd5LF5pGmgVeEgp4N-SqCh26a4LFo96Jxhi4wHFQehFw@mail.gmail.com> <5196546.NF2ntCjvkx@ralph.baldwin.cx>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Nov 29, 2016 at 2:27 AM, John Baldwin <jhb@freebsd.org> wrote:
> On Monday, November 28, 2016 02:35:07 PM Sepherosa Ziehau wrote:
>> Hi John,
>>
>> fdc seems to cause panic on Hyper-V:
>> https://people.freebsd.org/~sephe/fdc_panic.png
>
> You shouldn't get this panic in latest HEAD (post-r309148).


The base of my kernel tree is ~20 days old :)


>
>> I then commented out device fdc, and I fixed one panic on Hyper-V here:
>> https://reviews.freebsd.org/D8656
>
> Replied to the review.
>
>> After fdc is disabled and hyperv/storvsc is fixed, it seems to boot
>> fine, except a long delay (28~30seconds) here:
>> ....
>> Timecounters tick every 1.000 msec
>> -----
>> 28 ~ 30 seconds delay
>> -----
>> vlan: initialized, using hash tables with chaining
>> ....
>>
>> I have the bootverbose dmesg here:
>> https://people.freebsd.org/~sephe/dmesg_earlyap.txt
>>
>> I booted 10 times, only one boot does not suffer this 30 seconds
>> delay.  It sounds like some races to me.  Any hints?
>
> It is likely a race as we start running things sooner now, yes.  Can you
> break into DDB during the hang and see what thread0 is waiting on?  If
> it is in the interrupt hooks you can use 'show conifhk' in DDB to see the
> list of pending interrupt hooks.  That provides a list of candidate drivers
> to inspect (e.g. stack traces of relevant kthreads) for what is actually
> waiting (and what it is waiting on)

Just tried, but I failed to break into DDB during the 30 seconds
delay.  DDB was entered after the 30 seconds delay, though I press the
break key when the delay started.

Thanks,
sephe

-- 
Tomorrow Will Never Die



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAMOc5cz_KzkJnh-QDTWhpr%2BF0nOPcp9YF3YLseUJ=qQQvW_-EA>