Re: Please test EARLY_AP_STARTUP

[Sepherosa Ziehau]

On Tue, Nov 29, 2016 at 2:27 AM, John Baldwin  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
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: boot fails on Table SSDT at 0x...

[Julian H. Stacey]

John Baldwin wrote:
> On Tuesday, November 29, 2016 11:49:32 PM Julian H. Stacey wrote:
> > > Thanks for the Q. John,
> > > It hangs.
> > > I'm refining down which line of the custom config triggers the hang
> > > & will post when Ive found it.
> > 
> > Sorry, after lots of kernel variants & reboots I failed to get it
> > to hang on boot.  Eventually with same src/ I reverted to original
> > bad config. Even that wouldn't hang on boot, so I've given up ! :-/
> 
> Perhaps a stale .o wasn't being recompiled?  None of your kernel option
> changes seemed to be related, so I suspect it was something oddball like that.

Yes, good guess, (I'd even wondered about bad sectors, heat etc,
not ntpd as all local FS  .. ). 

PS at least it got me to review my config, drop & adopt some options,
& get all in the same order as GENERIC.

Thanks!

Cheers,
Julian
--
Julian Stacey, BSD Linux Unix Sys Eng Consultant Munich
 Reply below, Prefix '> '. Plain text, No .doc, base64, HTML, quoted-printable.
 http://berklix.eu/brexit/#stolen_votes
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: boot fails on Table SSDT at 0x...

[John Baldwin]

On Tuesday, November 29, 2016 11:49:32 PM Julian H. Stacey wrote:
> > Thanks for the Q. John,
> > It hangs.
> > I'm refining down which line of the custom config triggers the hang
> > & will post when Ive found it.
> 
> Sorry, after lots of kernel variants & reboots I failed to get it
> to hang on boot.  Eventually with same src/ I reverted to original
> bad config. Even that wouldn't hang on boot, so I've given up ! :-/

Perhaps a stale .o wasn't being recompiled?  None of your kernel option
changes seemed to be related, so I suspect it was something oddball like that.

-- 
John Baldwin
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: boot fails on Table SSDT at 0x...

[Julian H. Stacey]

> Thanks for the Q. John,
> It hangs.
> I'm refining down which line of the custom config triggers the hang
> & will post when Ive found it.

Sorry, after lots of kernel variants & reboots I failed to get it
to hang on boot.  Eventually with same src/ I reverted to original
bad config. Even that wouldn't hang on boot, so I've given up ! :-/

Cheers,
Julian
--
Julian Stacey, BSD Linux Unix Sys Eng Consultant Munich
 Reply below, Prefix '> '. Plain text, No .doc, base64, HTML, quoted-printable.
 http://berklix.eu/brexit/#stolen_votes
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Optimising generated rules for SAT solving (5/12 are duplicates)

[David Chisnall]

On 23 Nov 2016, at 18:11, A. Wilcox  wrote:
> 
> Or you could just, I don't know, email the diff as a patch using git
> send-email like normal people instead of using GitHub's walled garden.
> That way, people without GitHub accounts can still comment on it.

GitHub pull requests are branches in the recipient’s git repo.  Anyone can see 
the patch without logging in, either via the web interface or by pulling the 
relevant branch.  If you want to send comments via email based on this copy of 
the patch, then that’s up to you, though personally I’d much prefer the GitHub 
code review interface to anything email based.

David



smime.p7s
Description: S/MIME cryptographic signature

Re: Optimising generated rules for SAT solving (5/12 are duplicates)

[A. Wilcox]

On 23/11/16 10:47, Ed Schouten wrote:
> 2016-11-23 17:41 GMT+01:00 Hans Petter Selasky :
>> GitHub wouldn't allow me to make a .diff attachment.
> 
> But there's absolutely no need for doing that in the first place! :-)
> 
> 1. Go to https://github.com/freebsd/pkg
> 2. Click 'Fork' on the top right. This will probably create a
> https://github.com/hselasky/pkg
> 3. Check out that repository using git(1), create a separate branch
> and commit the changes to the SAT solver.
> 4. Go to https://github.com/hselasky/pkg and click on 'New pull request'.
> 5. Fill in the form.
> 

Or you could just, I don't know, email the diff as a patch using git
send-email like normal people instead of using GitHub's walled garden.
That way, people without GitHub accounts can still comment on it.

Just my 2¢.

--arw
-- 
A. Wilcox (awilfox)
Open-source programmer (C, C++, Python)
https://code.foxkit.us/u/awilfox/



signature.asc
Description: OpenPGP digital signature