x1 gen3 long boot with usb errors

2021-02-02 Thread Pavel Timofeev 
Hi
I have Lenovo X1 Carbon Gen 3 laptop and I'm suffering from long boot with
lots of repeating
> Root mount waiting for: usbus0
messages on FreeBSD 13.0-ALPHA3 stable/13-c256238-g3f185aacc58.
Some googling told me it's a common issue with FreeBSD's xhci driver.
I'm wondering what can be done to fix or workaround this.


---<>---
APIC: Using the MADT enumerator.
Copyright (c) 1992-2021 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 13.0-ALPHA3 #0 stable/13-c256238-g3f185aacc58: Sun Jan 31 23:03:32
MST 2021
pavel.timofeev@carbon:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64
FreeBSD clang version 11.0.1 (g...@github.com:llvm/llvm-project.git
llvmorg-11.0.1-0-g43ff75f2c3fe)
PPIM 0: PA=0xc000, VA=0x8291, size=0x7e9000, mode=0x1
pmap: large map 8 PML4 slots (4096 GB)
VT(efifb): resolution 1920x1080
Preloaded elf kernel "/boot/kernel/kernel" at 0x827af000.
Preloaded elf obj module "/boot/kernel/cryptodev.ko" at 0x827b8718.
Preloaded elf obj module "/boot/kernel/coretemp.ko" at 0x827b8e88.
Preloaded boot_entropy_cache "/boot/entropy" at 0x827b9478.
Preloaded elf obj module "/boot/kernel/acpi_ibm.ko" at 0x827b94d0.
Preloaded elf obj module "/boot/kernel/cuse.ko" at 0x827b9b40.
Preloaded elf obj module "/boot/kernel/zfs.ko" at 0x827ba228.
Preloaded hostuuid "/etc/hostid" at 0x827baa10.
Calibrating TSC clock ... TSC clock: 2194973264 Hz
CPU: Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz (2194.97-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x306d4  Family=0x6  Model=0x3d  Stepping=4

Features=0xbfebfbff

Features2=0x7ffafbbf
  AMD Features=0x2c100800
  AMD Features2=0x121
  Structured Extended
Features=0x21c27ab
  Structured Extended
Features3=0x9c000600
  XSAVE Features=0x1
  VT-x: Basic Features=0xda0400
Pin-Based Controls=0x7f
Primary Processor
Controls=0xfff9fffe
Secondary Processor
Controls=0x53cff
Exit Controls=0xda0400
Entry Controls=0xda0400
EPT Features=0x6334141
VPID Features=0xf01
  TSC: P-state invariant, performance statistics
Data TLB: 2 MByte or 4 MByte pages, 4-way set associative, 32 entries and a
separate array with 1 GByte pages, 4-way set associative, 4 entries
Data TLB: 4 KB pages, 4-way set associative, 64 entries
Instruction TLB: 2M/4M pages, fully associative, 8 entries
Instruction TLB: 4KByte pages, 8-way set associative, 64 entries
64-Byte prefetching
Shared 2nd-Level TLB: 4 KByte /2 MByte pages, 6-way associative, 1536
entries. Also 1GBbyte pages, 4-way, 16 entries
L2 cache: 256 kbytes, 8-way associative, 64 bytes/line
real memory  = 8589934592 (8192 MB)
Physical memory chunk(s):
0x0001 - 0x00057fff, 294912 bytes (72 pages)
0x00059000 - 0x0009bfff, 274432 bytes (67 pages)
0x00104000 - 0x001f, 1032192 bytes (252 pages)
0x02901000 - 0xaa7a4fff, 2817146880 bytes (687780 pages)
0xacdff000 - 0xacdf, 4096 bytes (1 pages)
0x00011000 - 0x00023ed46fff, 5349072896 bytes (1305926 pages)
0x00024de0 - 0x00024dfa7fff, 1736704 bytes (424 pages)
avail memory = 8140484608 (7763 MB)
intel stolen mem: base 0xae00 size 32 MB
x2APIC available but disabled by DMAR table
MADT: Found CPU APIC ID 0 ACPI ID 1: enabled
SMP: Added CPU 0 (AP)
MADT: Found CPU APIC ID 1 ACPI ID 2: enabled
SMP: Added CPU 1 (AP)
MADT: Found CPU APIC ID 2 ACPI ID 3: enabled
SMP: Added CPU 2 (AP)
MADT: Found CPU APIC ID 3 ACPI ID 4: enabled
SMP: Added CPU 3 (AP)
MADT: Found CPU APIC ID 0 ACPI ID 5: disabled
MADT: Found CPU APIC ID 0 ACPI ID 6: disabled
MADT: Found CPU APIC ID 0 ACPI ID 7: disabled
MADT: Found CPU APIC ID 0 ACPI ID 8: disabled
Event timer "LAPIC" quality 600
LAPIC: ipi_wait() us multiplier 38 (r 5657252 tsc 2194973264)
ACPI APIC Table: 
Package ID shift: 4
L3 cache ID shift: 4
L2 cache ID shift: 1
L1 cache ID shift: 1
Core ID shift: 1
INTR: Adding local APIC 2 as a target
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
FreeBSD/SMP: 1 package(s) x 2 core(s) x 2 hardware threads
Package HW ID = 0
Core HW ID = 0
CPU0 (BSP): APIC ID: 0
CPU1 (AP/HT): APIC ID: 1
Core HW ID = 1
CPU2 (AP): APIC ID: 2
CPU3 (AP/HT): APIC ID: 3
APIC: CPU 0 has ACPI ID 1
APIC: CPU 1 has ACPI ID 2
APIC: CPU 2 has ACPI ID 3
APIC: CPU 3 has ACPI ID 4
lapic0: CMCI unmasked
Pentium Pro MTRR support enabled
x86bios:  IVT 0x00-0x0004ff at 0xf800
x86bios: SSEG 0x059000-0x059fff at 0xfe0010a25000
x86bios:  ROM 0x0a-0x0fefff at 0xf80a
random: registering fast source Intel Secure Key RNG
random: fast provider: "Intel Secure Key RNG"
random: read 4096 bytes from preloaded cache
random: unblocking device.
VIMAGE (virtualized network stack) enabled
hostuuid: using 184c4101-53f3-11cb-917e-f03a6d130

Re: latest stable13.0-ALPHA3 can not start varnish anymore.

2021-02-02 Thread Johan Hendriks 


On 02/02/2021 19:20, Mateusz Guzik wrote:

I fixed the problem and given the impending builds merged it
immediately. Can be seen here:
https://cgit.freebsd.org/src/commit/?id=4e29933d0936fd053f7591ee118dc1fc42617514

Should you run into any other problems, they can be temporarily worked
around with:
sysctl vfs.cache_fast_lookup=0

For problem reports in the area please collect:
dtrace -n 'vfs:fplookup:lookup:done { @[arg1, arg2,
stringof(args[0].ni_cnd.cn_pnbuf)] = count(); }' -c "failing command"

On 2/2/21, Kyle Evans  wrote:

On Tue, Feb 2, 2021 at 10:42 AM Kristof Provost  wrote:

On 2 Feb 2021, at 14:05, Johan Hendriks wrote:

On 01/02/2021 22:48, Johan Hendriks wrote:

I just updated my FreeBSD 13.0-APLPHA3 to the latest revision and now
i can not start varnish anymore.
This is on two machines.

if i start varnish it errors out as the startup script does a config
file check.
If i try to do a test of the config file i get the following error.

root@jhost002:~ # varnishd -C -f /usr/local/etc/varnish/default.vcl
Error: Cannot create working directory '/tmp/varnishd_C_dwbl7mn/': Is
a directory
Error: Cannot create working directory (/tmp/varnishd_C_dwbl7mn/): No
error: 0
(-? gives usage)
root@jhost002:~ #

This is on:
FreeBSD jhost002.mydomain.nl 13.0-ALPHA3 FreeBSD 13.0-ALPHA3 #35
stable/13-c256281-gc415d0df47fc: Mon Feb  1 17:04:49 CET 2021
r...@srv-01.home.local:/usr/obj/usr/src/amd64.amd64/sys/KRNL amd64

I did not update the package or installed any other software besides
the buildworld.

regards,
Johan



I have tried some bisecting as far as my understanding of git goes. I
do not know which one is the latest, but on these revisions varnish
works.

FreeBSD jhost002 13.0-ALPHA3 FreeBSD 13.0-ALPHA3 #8
c256261-g9375a93b6c22: Tue Feb  2 13:33:05 CET 2021
root@jhost002:/usr/obj/usr/src/amd64.amd64/sys/GENERIC  amd64

uname -a
FreeBSD jhost002 13.0-ALPHA3 FreeBSD 13.0-ALPHA3 #7
c256260-g247f652e622d: Tue Feb  2 13:07:37 CET 2021
root@jhost002:/usr/obj/usr/src/amd64.amd64/sys/GENERIC  amd64


Can you try setting `sysctl vfs.cache_fast_lookup=0` ?

(As suggested by Mateusz elsewhere.)


We confirmed that reverting 006ec2ed fixes it, I'm still trying to get
an idea of what's happening. My initial analysis suggests that
fplookup hits the trailing slash and aborts, leaving us at the
degenerate state back up in the slow-path.

I have a small reproducer that I'm working with:
https://people.freebsd.org/~kevans/namereg.c

Just did a full rebuild for stable 13 and i can run varnishd -C -f 
/usr/local/etc/varnish/default.vcl again.


FreeBSD jhost002 13.0-ALPHA3 FreeBSD 13.0-ALPHA3 #14 
stable/13-n244422-4e29933d0936: Tue Feb  2 20:49:09 CET 2021 
root@jhost002:/usr/obj/usr/src/amd64.amd64/sys/GENERIC  amd64


Thank you all for your time and work.


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

Re: pkgbase: Missing /etc/master.passwd in FreeBSD-runtime 12-stable pkg

2021-02-02 Thread mj-mailinglist 
>>
>> On 1/31/21 12:04 PM, mj-mailingl...@gmx.de wrote:
>>> I noticed that my jails, build from a recent pkg base don't start:
>>> ...
>>> Starting jails: cannot start jail  "j6":
>>> 7
>>> jail: j6: getpwnam root: No such file or directory
>>> jail: j6: /bin/sh /etc/rc: failed
>>> .
>>>
>>
>> [snip]
>>
>> Just a thought, did you run
>>
>> make distribution DESTDIR=
>
> This shouldn't be necessary with pkgbase, but I haven't looked at
> pkgbase in 12 on a long time -- it sounds like we managed to regress
> it somewhere.

The last step in my weekly system rebuild is "make packages" to create a pkgbase
repository from the newly build system. The last build, i could use to create
jails is r368786M, with "stable/12-c58-g53bc32215" the jails are broken.
I didn't check since which commit the error occurs. Reading the commit logs
doesn't show anything obvious to me.

Should pkgbase be operational in stable/12? If the consensus is no, i just skip
it and concentrate on 13. Will pkgbase be a supported (and working) feature on 
13?

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

Re: Setting for displaying utf8 characters on all vt consoles results in panic on 14-CURRENT and 13.0-ALPHA3

2021-02-02 Thread Toomas Soome via freebsd-stable 


> On 1. Feb 2021, at 05:35, Yasuhiro Kimura  wrote:
> 
> From: Yasuhiro Kimura mailto:y...@utahime.org>>
> Subject: Setting for displaying utf8 characters on all vt consoles results in 
> panic on 14-CURRENT and 13.0-ALPHA3
> Date: Mon, 01 Feb 2021 11:41:35 +0900 (JST)
> 
>> To display utf8 characters on all vt console I did following settings.
>> 
>> 1. Download GNU Unifont BDF file
>>   
>> (http://unifoundry.com/pub/unifont/unifont-13.0.05/font-builds/unifont-13.0.05.bdf.gz)
>> 2. gunzip unifont-13.0.05.bdf.gz
>> 3. vtfontcvt unifont-13.0.05.bdf unifont.fnt
>> 4. cp unifont.fnt /usr/share/vt/fonts
>> 5. Add 'allscreens_flags="-f 8x16 unifont.fnt"' to /etc/rc.conf
>> 6. Add 'hw.vga.textmode=0' to /boot/loader.conf.local
>> 7. shutdown -r now
>> 
>> On 12.2-RELEASE and 11.4-RELEASE it works as is expected. But on
>> 14-CURRENT(man) and 13.0-ALPHA3(stable/13) it result in kernel panic.
>> 
>> Screen shot of 14-CURRENT.
>> https://www.utahime.org/FreeBSD/panic.20210201.14-CURRENT.png
>> 
>> 14-CURRENT(main):
>> yasu@rolling-vm-freebsd1[1006]% uname -a
>> FreeBSD rolling-vm-freebsd1.home.utahime.org 14.0-CURRENT FreeBSD 
>> 14.0-CURRENT #0 main-n244517-f17fc5439f5: Mon Feb  1 10:55:51 JST 2021 
>> ro...@rolling-vm-freebsd1.home.utahime.org:/usr0/freebsd/src/obj/usr0/freebsd/src/git/amd64.amd64/sys/GENERIC
>>   amd64
>> 
>> 13.0-ALPHA3(stable/13):
>> yasu@rolling-vm-freebsd5[1005]% uname -a
>> FreeBSD rolling-vm-freebsd5.home.utahime.org 13.0-ALPHA3 FreeBSD 13.0-ALPHA3 
>> #0 stable/13-c256214-g40cb0344eb2: Mon Feb  1 11:30:28 JST 2021 
>> ro...@rolling-vm-freebsd5.home.utahime.org:/usr0/freebsd/src/obj/usr0/freebsd/src/git/amd64.amd64/sys/GENERIC
>>   amd64
> 
> I submitted this problem to Bugzilla.
> 
> Bug 253147 - Setting for displaying utf8 characters on all vt consoles
> results in panic on 14-CURRENT and 13.0-ALPHA3
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253147 
> 
> 
> ---
> Yasuhiro Kimura

Should be fixed on current now.

thanks,
toomas


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

Re: latest stable13.0-ALPHA3 can not start varnish anymore.

2021-02-02 Thread Kyle Evans 
On Tue, Feb 2, 2021 at 10:42 AM Kristof Provost  wrote:
>
> On 2 Feb 2021, at 14:05, Johan Hendriks wrote:
> > On 01/02/2021 22:48, Johan Hendriks wrote:
> >> I just updated my FreeBSD 13.0-APLPHA3 to the latest revision and now
> >> i can not start varnish anymore.
> >> This is on two machines.
> >>
> >> if i start varnish it errors out as the startup script does a config
> >> file check.
> >> If i try to do a test of the config file i get the following error.
> >>
> >> root@jhost002:~ # varnishd -C -f /usr/local/etc/varnish/default.vcl
> >> Error: Cannot create working directory '/tmp/varnishd_C_dwbl7mn/': Is
> >> a directory
> >> Error: Cannot create working directory (/tmp/varnishd_C_dwbl7mn/): No
> >> error: 0
> >> (-? gives usage)
> >> root@jhost002:~ #
> >>
> >> This is on:
> >> FreeBSD jhost002.mydomain.nl 13.0-ALPHA3 FreeBSD 13.0-ALPHA3 #35
> >> stable/13-c256281-gc415d0df47fc: Mon Feb  1 17:04:49 CET 2021
> >> r...@srv-01.home.local:/usr/obj/usr/src/amd64.amd64/sys/KRNL amd64
> >>
> >> I did not update the package or installed any other software besides
> >> the buildworld.
> >>
> >> regards,
> >> Johan
> >>
> >>
> > I have tried some bisecting as far as my understanding of git goes. I
> > do not know which one is the latest, but on these revisions varnish
> > works.
> >
> > FreeBSD jhost002 13.0-ALPHA3 FreeBSD 13.0-ALPHA3 #8
> > c256261-g9375a93b6c22: Tue Feb  2 13:33:05 CET 2021
> > root@jhost002:/usr/obj/usr/src/amd64.amd64/sys/GENERIC  amd64
> >
> > uname -a
> > FreeBSD jhost002 13.0-ALPHA3 FreeBSD 13.0-ALPHA3 #7
> > c256260-g247f652e622d: Tue Feb  2 13:07:37 CET 2021
> > root@jhost002:/usr/obj/usr/src/amd64.amd64/sys/GENERIC  amd64
> >
> Can you try setting `sysctl vfs.cache_fast_lookup=0` ?
>
> (As suggested by Mateusz elsewhere.)
>

We confirmed that reverting 006ec2ed fixes it, I'm still trying to get
an idea of what's happening. My initial analysis suggests that
fplookup hits the trailing slash and aborts, leaving us at the
degenerate state back up in the slow-path.

I have a small reproducer that I'm working with:
https://people.freebsd.org/~kevans/namereg.c
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: latest stable13.0-ALPHA3 can not start varnish anymore.

2021-02-02 Thread Kristof Provost 

On 2 Feb 2021, at 14:05, Johan Hendriks wrote:

On 01/02/2021 22:48, Johan Hendriks wrote:
I just updated my FreeBSD 13.0-APLPHA3 to the latest revision and now 
i can not start varnish anymore.

This is on two machines.

if i start varnish it errors out as the startup script does a config 
file check.

If i try to do a test of the config file i get the following error.

root@jhost002:~ # varnishd -C -f /usr/local/etc/varnish/default.vcl
Error: Cannot create working directory '/tmp/varnishd_C_dwbl7mn/': Is 
a directory
Error: Cannot create working directory (/tmp/varnishd_C_dwbl7mn/): No 
error: 0

(-? gives usage)
root@jhost002:~ #

This is on:
FreeBSD jhost002.mydomain.nl 13.0-ALPHA3 FreeBSD 13.0-ALPHA3 #35 
stable/13-c256281-gc415d0df47fc: Mon Feb  1 17:04:49 CET 2021 
r...@srv-01.home.local:/usr/obj/usr/src/amd64.amd64/sys/KRNL amd64


I did not update the package or installed any other software besides 
the buildworld.


regards,
Johan


I have tried some bisecting as far as my understanding of git goes. I 
do not know which one is the latest, but on these revisions varnish 
works.


FreeBSD jhost002 13.0-ALPHA3 FreeBSD 13.0-ALPHA3 #8 
c256261-g9375a93b6c22: Tue Feb  2 13:33:05 CET 2021 
root@jhost002:/usr/obj/usr/src/amd64.amd64/sys/GENERIC  amd64


uname -a
FreeBSD jhost002 13.0-ALPHA3 FreeBSD 13.0-ALPHA3 #7 
c256260-g247f652e622d: Tue Feb  2 13:07:37 CET 2021 
root@jhost002:/usr/obj/usr/src/amd64.amd64/sys/GENERIC  amd64



Can you try setting `sysctl vfs.cache_fast_lookup=0` ?

(As suggested by Mateusz elsewhere.)

Best regards,
Kristof
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: latest stable13.0-ALPHA3 can not start varnish anymore.

2021-02-02 Thread Johan Hendriks 

On 01/02/2021 22:48, Johan Hendriks wrote:
I just updated my FreeBSD 13.0-APLPHA3 to the latest revision and now 
i can not start varnish anymore.

This is on two machines.

if i start varnish it errors out as the startup script does a config 
file check.

If i try to do a test of the config file i get the following error.

root@jhost002:~ # varnishd -C -f /usr/local/etc/varnish/default.vcl
Error: Cannot create working directory '/tmp/varnishd_C_dwbl7mn/': Is 
a directory
Error: Cannot create working directory (/tmp/varnishd_C_dwbl7mn/): No 
error: 0

(-? gives usage)
root@jhost002:~ #

This is on:
FreeBSD jhost002.mydomain.nl 13.0-ALPHA3 FreeBSD 13.0-ALPHA3 #35 
stable/13-c256281-gc415d0df47fc: Mon Feb  1 17:04:49 CET 2021 
r...@srv-01.home.local:/usr/obj/usr/src/amd64.amd64/sys/KRNL amd64


I did not update the package or installed any other software besides 
the buildworld.


regards,
Johan


I have tried some bisecting as far as my understanding of git goes. I do 
not know which one is the latest, but on these revisions varnish works.


FreeBSD jhost002 13.0-ALPHA3 FreeBSD 13.0-ALPHA3 #8 
c256261-g9375a93b6c22: Tue Feb  2 13:33:05 CET 2021 
root@jhost002:/usr/obj/usr/src/amd64.amd64/sys/GENERIC  amd64


uname -a
FreeBSD jhost002 13.0-ALPHA3 FreeBSD 13.0-ALPHA3 #7 
c256260-g247f652e622d: Tue Feb  2 13:07:37 CET 2021 
root@jhost002:/usr/obj/usr/src/amd64.amd64/sys/GENERIC  amd64







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

Re: latest stable13.0-ALPHA3 can not start varnish anymore.

2021-02-02 Thread Johan Hendriks 

On 01/02/2021 22:48, Johan Hendriks wrote:
I just updated my FreeBSD 13.0-APLPHA3 to the latest revision and now 
i can not start varnish anymore.

This is on two machines.

if i start varnish it errors out as the startup script does a config 
file check.

If i try to do a test of the config file i get the following error.

root@jhost002:~ # varnishd -C -f /usr/local/etc/varnish/default.vcl
Error: Cannot create working directory '/tmp/varnishd_C_dwbl7mn/': Is 
a directory
Error: Cannot create working directory (/tmp/varnishd_C_dwbl7mn/): No 
error: 0

(-? gives usage)
root@jhost002:~ #

This is on:
FreeBSD jhost002.mydomain.nl 13.0-ALPHA3 FreeBSD 13.0-ALPHA3 #35 
stable/13-c256281-gc415d0df47fc: Mon Feb  1 17:04:49 CET 2021 
r...@srv-01.home.local:/usr/obj/usr/src/amd64.amd64/sys/KRNL amd64


I did not update the package or installed any other software besides 
the buildworld.


regards,
Johan



Without the check, varnish fails to start all together.

root@jhost002:/usr/local/etc/varnish # /usr/local/etc/rc.d/varnishd start
Performing sanity check on varnishd configuration:
Starting varnishd.
Warnings:
VCL compiled.

Debug: Version: varnish-6.5.1 revision NOGIT
Debug: Platform: 
FreeBSD,13.0-ALPHA3,amd64,-junix,-smalloc,-sdefault,-hcritbit

Debug: Child (78795) Started
eval: 000: not found
/usr/local/etc/rc.d/varnishd: WARNING: failed to start varnishd

I have tested this on a new machine updated to the same revision, same 
result.


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