Re: Please test EARLY_AP_STARTUP
On Wed, Nov 30, 2016 at 9:59 AM, Sepherosa Ziehau wrote: > 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. I tried add VERBOSE_SYSINIT option in order to get a rough location of this delay, but the system boots just fine w/ VERBOSE_SYSINIT option, sigh. 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: CURRENT: pkg broken on r309320
On Wed, Nov 30, 2016 at 09:46:37PM +0100, Hartmann, O. wrote: > ... > I'm now on re09332. The problem still persists. It is serious, no > packages can be installed and kernel building fails due to modules set > to be rebuild every time kernel is built in /etc/src.conf. > > Unfortunately, building kernel AND having x11/nvidia-driver being built > every time kernel is build, makes the port x11/nvidia-driver vanish. It > is reported installed (check via pkg info), but there are no binaries! > > This is a serious situation. > > Thanks in advance, > > Oliver This also bit me (@r309324), building the kmod for nvidia-driver-340. So I applied the patch from https://reviews.freebsd.org/D8677, and tried again -- worked. Peace, david -- David H. Wolfskill da...@catwhisker.org Ref. 08 Nov 2016, let's see if the "winners" actually deliver on their slogans. See http://www.catwhisker.org/~david/publickey.gpg for my public key. signature.asc Description: PGP signature
Re: CURRENT: pkg broken on r309320
On Wed, 30 Nov 2016 12:10:31 + Matthew Seaman wrote: > On 2016/11/30 10:14, Baptiste Daroussin wrote: > > revert r309314 the issue is there: > > > > The ports tree defines PKG_CMD as pkg register but now bsd.own.mk > > predefines it to simply pkg. > > > > There is a collision there. > > > > Pointy hat to me. I'll revert that commit. > > Matthew > > I'm now on re09332. The problem still persists. It is serious, no packages can be installed and kernel building fails due to modules set to be rebuild every time kernel is built in /etc/src.conf. Unfortunately, building kernel AND having x11/nvidia-driver being built every time kernel is build, makes the port x11/nvidia-driver vanish. It is reported installed (check via pkg info), but there are no binaries! This is a serious situation. Thanks in advance, Oliver ___ 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: CURRENT: pkg broken on r309320
On 2016/11/30 12:14, Baptiste Daroussin wrote: > On Wed, Nov 30, 2016 at 12:10:31PM +, Matthew Seaman wrote: >> On 2016/11/30 10:14, Baptiste Daroussin wrote: >>> revert r309314 the issue is there: >>> >>> The ports tree defines PKG_CMD as pkg register but now bsd.own.mk >>> predefines it >>> to simply pkg. >>> >>> There is a collision there. >>> >> >> Pointy hat to me. I'll revert that commit. >> >> Matthew >> > > I have proposed https://reviews.freebsd.org/D8677 instead which make sense and > does not require your to modify bsd.own.mk OK, I'll wait and see what the outcome of D8677 is. Cheers, Matthew signature.asc Description: OpenPGP digital signature
Re: CURRENT: pkg broken on r309320
On Wed, Nov 30, 2016 at 12:10:31PM +, Matthew Seaman wrote: > On 2016/11/30 10:14, Baptiste Daroussin wrote: > > revert r309314 the issue is there: > > > > The ports tree defines PKG_CMD as pkg register but now bsd.own.mk > > predefines it > > to simply pkg. > > > > There is a collision there. > > > > Pointy hat to me. I'll revert that commit. > > Matthew > I have proposed https://reviews.freebsd.org/D8677 instead which make sense and does not require your to modify bsd.own.mk Best regards, Bapt signature.asc Description: PGP signature
Re: CURRENT: pkg broken on r309320
On 2016/11/30 10:14, Baptiste Daroussin wrote: > revert r309314 the issue is there: > > The ports tree defines PKG_CMD as pkg register but now bsd.own.mk predefines > it > to simply pkg. > > There is a collision there. > Pointy hat to me. I'll revert that commit. Matthew signature.asc Description: OpenPGP digital signature
Re: CURRENT: pkg broken on r309320
On Wed, Nov 30, 2016 at 10:22:28AM +0100, O. Hartmann wrote: > Running CURRENT, r309320 and try to update ports. After the port has been > build, pkg > fails to install the port quitting with: > > pkg: illegal option -- i > DBG(1)[67562]> pkg initialized > pkg: unknown command: /usr/ports/www/libwww/work/stage > > For more information on available commands and options see 'pkg help'. > *** Error code 64 > > Stop. > make: stopped in /usr/ports/www/libwww > > Seems there has been introduced a bug since rr309298 > > Kind regards, > Oliver revert r309314 the issue is there: The ports tree defines PKG_CMD as pkg register but now bsd.own.mk predefines it to simply pkg. There is a collision there. Best regards, Bapt signature.asc Description: PGP signature
CURRENT: pkg broken on r309320
Running CURRENT, r309320 and try to update ports. After the port has been build, pkg fails to install the port quitting with: pkg: illegal option -- i DBG(1)[67562]> pkg initialized pkg: unknown command: /usr/ports/www/libwww/work/stage For more information on available commands and options see 'pkg help'. *** Error code 64 Stop. make: stopped in /usr/ports/www/libwww Seems there has been introduced a bug since rr309298 Kind regards, Oliver -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG). pgpW6XU9FbgqO.pgp Description: OpenPGP digital signature
