nvme0: Missing interrupt on powerpc64
Hello, I'm running FreeBSD 12.0-ALPHA5 on Talos Lite (Power9). I have / on NVME drive. During boot, I'm getting: nvme0: Missing interrupt It happens when /etc/rc.d/kldxref runs. If I press ^C, booting goes on. -- ___ / A committee is a group that keeps the \ | minutes and loses hours. | | | \ -- Milton Berle / --- \ ^__^ \ (oo)\___ (__)\ )\/\ ||w | || || signature.asc Description: PGP signature
ppp.linkup: How is the !bg argument expanded and substituted?
Hello list,
my question may sound blunt but I miss something with the documentation
of ppp(8).
Background: My homeoffice is running a network and server
infrastructure I'd like to access from the internet, therefore, I use a
DDNS service. My gateway is a FreeBSD based small, efficient NanoBSD
based system acting as firewall, router and performing some gatewaying
stuff. Recently the usually used dns/ddclient stopped working on
recent CURRENT running on that gateway (FreeBSD 12.0-ALPHA5 #32
r338541: Sun Sep 9 09:27:47 CEST 2018 amd64, NETINET6 enabled,
secureretylevel=1, all NICs have only IPv6 linklocal, exterior IF is
tun0 with a regular IPv4 assign by my ISP and only linklocal IPv6).
dns/ddclient stopped working out of the blue and I need an alternative
to update my IP (ipv4) at my DDNS provider.
To achiev the requested IPv4 updates as done via ddclient I
used /etc/ppp/ppp.linkup with a !bg command this way:
!bg /usr/local/bin/curl -v -X PUT -u \
\"em...@host.de:SOME_TOKEN_GIVEN_BY_PROVIDER\" \
-d '{\"ip_address\": \"auto\"}' https://api.twodns.de/hosts/all
It is ONE ROW, I broke it up for presentation here.
Somehow I needed to escape some quotes like \"; I tried to check how
ppp would emmit the !bg command via a logger statement with the very
same line - the reason is I can't see what ppp is doing and since DDNS
updates never were performed so far via ppp.linkup I consider some
mistakes here.
For the JSON data (after -d '{...}'), quoted tags are requisite.
When I issue the command on the gateway without the escaped quotes to
achieve the command line:
/usr/local/bin/curl -v -X PUT -u \
"em...@host.de:SOME_TOKEN_GIVEN_BY_PROVIDER" \
-d '{"ip_address": "auto"}' https://api.twodns.de/hosts/all
everythings works perfect: the IP gets updated, the DDNS provider
respons with status code "200 OK". So far.
But somehow this never happens or is successful with the !bg statement
from ppp.linkup when the IP changes on that link and ppp.linkup is
triggered. Since I do not see why (it seems that the response from
the !bg command is lost), I need to check the substitutions.
Can someone enlighted please shed some illumination on that problem? It
would really help to hint me to the doc were I can read about the way
the command string is parsed/interpreted by ppp (I only found the
substitutions for MYADDR, MYADDR6 and so on in man ppp(8)).
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"
WiFi QCA986x/988x 802.11ac Wireless Network Adapter support?
For a while 802.11ac adapters are out and some of them made by Qualcomm/Atheros are considered useful for building accesspoints, like the QCA9882. Running revent 12-ALPHA6 on an APU from PCengines equipted with such an WiFi adaptor (I think this product is named Compex WLE600V) and ath/ath_hal driver loaded still gives me: none1@pci0:1:0:0: class=0x028000 card=0x chip=0x003c168c rev=0x00 hdr=0x00 vendor = 'Atheros' device = 'QCA986x/988x 802.11ac Wireless Network Adapter' class = network bar [10] = type Memory, range 64, base 0xfe20, size 2097152, enabled Linux ath10k driver claims to support this specific chipset (never tried Linux on our PCengines APU2!), and I was wondering if there is support for FreeBSD as well? Since this WiFi adaptor seems to have similar reputations for being used as hostapd AP devices for WiFi routers on FreeBSD as several older ath 802.11bg/n devices, I was wondering whether development of a suitable driver is planned or has been started for FreeBSD. Thanks in advance, oh ___ 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: WiFi QCA986x/988x 802.11ac Wireless Network Adapter support?
On 09/14, Hartmann, O. wrote: For a while 802.11ac adapters are out and some of them made by Qualcomm/Atheros are considered useful for building accesspoints, like the QCA9882. Running revent 12-ALPHA6 on an APU from PCengines equipted with such an WiFi adaptor (I think this product is named Compex WLE600V) and ath/ath_hal driver loaded still gives me: [...] Linux ath10k driver claims to support this specific chipset (never tried Linux on our PCengines APU2!), and I was wondering if there is support for FreeBSD as well? Hi, adrian@ has been working on ath10k: https://github.com/erikarn/athp ___ 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: ppp.linkup: How is the !bg argument expanded and substituted?
On Fri, Sep 14, 2018 at 01:34:33PM +0200, Hartmann, O. wrote:
> Hello list,
>
> my question may sound blunt but I miss something with the documentation
> of ppp(8).
>
> Background: My homeoffice is running a network and server
> infrastructure I'd like to access from the internet, therefore, I use a
> DDNS service. My gateway is a FreeBSD based small, efficient NanoBSD
> based system acting as firewall, router and performing some gatewaying
> stuff. Recently the usually used dns/ddclient stopped working on
> recent CURRENT running on that gateway (FreeBSD 12.0-ALPHA5 #32
> r338541: Sun Sep 9 09:27:47 CEST 2018 amd64, NETINET6 enabled,
> secureretylevel=1, all NICs have only IPv6 linklocal, exterior IF is
> tun0 with a regular IPv4 assign by my ISP and only linklocal IPv6).
> dns/ddclient stopped working out of the blue and I need an alternative
> to update my IP (ipv4) at my DDNS provider.
>
> To achiev the requested IPv4 updates as done via ddclient I
> used /etc/ppp/ppp.linkup with a !bg command this way:
>
> !bg /usr/local/bin/curl -v -X PUT -u \
> \"em...@host.de:SOME_TOKEN_GIVEN_BY_PROVIDER\" \
> -d '{\"ip_address\": \"auto\"}' https://api.twodns.de/hosts/all
>
> It is ONE ROW, I broke it up for presentation here.
>
> Somehow I needed to escape some quotes like \"; I tried to check how
> ppp would emmit the !bg command via a logger statement with the very
> same line - the reason is I can't see what ppp is doing and since DDNS
> updates never were performed so far via ppp.linkup I consider some
> mistakes here.
>
> For the JSON data (after -d '{...}'), quoted tags are requisite.
>
> When I issue the command on the gateway without the escaped quotes to
> achieve the command line:
>
> /usr/local/bin/curl -v -X PUT -u \
> "em...@host.de:SOME_TOKEN_GIVEN_BY_PROVIDER" \
> -d '{"ip_address": "auto"}' https://api.twodns.de/hosts/all
>
> everythings works perfect: the IP gets updated, the DDNS provider
> respons with status code "200 OK". So far.
>
> But somehow this never happens or is successful with the !bg statement
> from ppp.linkup when the IP changes on that link and ppp.linkup is
> triggered. Since I do not see why (it seems that the response from
> the !bg command is lost), I need to check the substitutions.
>
> Can someone enlighted please shed some illumination on that problem? It
> would really help to hint me to the doc were I can read about the way
> the command string is parsed/interpreted by ppp (I only found the
> substitutions for MYADDR, MYADDR6 and so on in man ppp(8)).
I'd skip the above and put the CURL command into a small script
which is run from the !bg command
Regards,
Gary
___
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"
devd on head -r338675 on aarch64 (Pine64+ 2GB example) gets during booting: "sh: /usr/libexec/hyperv/hyperv_vfattach: not found"
>From the boot of the Pine64+ 2GB for -r338675: . . . Starting devd. sh: /usr/libexec/hyperv/hyperv_vfattach: not found add host 127.0.0.1: gateway lo0 fib 0: route already in table . . . This seems to result from: # grep -r hyperv_vfattach /etc/ | more /etc/devd/hyperv.conf:# For transparent network VF, hyperv_vfattach does nothing and /etc/devd/hyperv.conf: action "/usr/libexec/hyperv/hyperv_vfattach $subsystem 0"; But for the aarch64/pine64+ context there is only: # ls -a /usr/libexec/hyperv/ . .. On amd64 that directory has content, including the file referenced. aarch64/pine64+ is likely not unique in missing the files in /usr/libexec/hyperv/ . Context: uname output: # uname -apKU FreeBSD pine64 12.0-ALPHA6 FreeBSD 12.0-ALPHA6 #6 r338675M: Thu Sep 13 18:48:05 PDT 2018 markmi@pine64:/usr/obj/cortexA53_clang/arm64.aarch64/usr/src/arm64.aarch64/sys/GENERIC-NODBG arm64 aarch64 1200084 1200084 === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ 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"
FreeBSD 12 regression: unable to boot in UEFI/bhyve: blank screen after loader
The problem started before FreeBSD 12 ALPHA1 but still exist in ALPHA6. If you try to run FreeBSD 12 (e.g. FreeBSD-12.0-ALPHA6-amd64-20180914-r338675-disc1.iso from ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/amd64/amd64/ISO-IMAGES/12.0/ ) in bhyve UEFI mode with command from handbook (https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/virtualization-host-bhyve.html) in chapter "21.7.5. Graphical UEFI Framebuffer for bhyve Guests" you will see a black screen after loader: https://pasteboard.co/HDSVqEE.png Apparently, this is due to recent changes in the [lua]loader. How to reproduce: 1) fetch -o /tmp/FreeBSD-12.0-ALPHA6-amd64-20180914-r338675-disc1.iso ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/amd64/amd64/ISO-IMAGES/12.0/FreeBSD-12.0-ALPHA6-amd64-20180914-r338675-disc1.iso 2) truncate -s1g /tmp/guest.img 3) ifconfig tap1 create 4) kldload vmm 5) pkg install -y uefi-edk2-bhyve 6) bhyve -AHP -s 0:0,hostbridge -s 31:0,lpc \ -s 2:0,virtio-net,tap1 -s 3:0,virtio-blk,/tmp/guest.img \ -s 4:0,ahci-cd,/tmp/FreeBSD-12.0-ALPHA6-amd64-20180914-r338675-disc1.iso -c 4 -m 1024M \ -s 29,fbuf,tcp=0.0.0.0:5900,w=800,h=600,wait \ -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd \ 7) vncviewer :5900 ___ 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: SD card reader only works after a suspend/resume
On 9/13/18 6:11 PM, Jakob Alvermark wrote:
On 9/13/18 12:13 AM, Marius Strobl wrote:
On Fri, Sep 07, 2018 at 04:52:12PM +0200, Jakob Alvermark wrote:
On 9/7/18 12:41 AM, Marius Strobl wrote:
On Thu, Sep 06, 2018 at 12:33:39PM +0200, Jakob Alvermark wrote:
Hi,
I discovered this by chance.
The SD card reader in my laptop has never worked, but now I
noticed it
does after suspending and resuming.
The controller is probed and attached on boot:
sdhci_acpi1: iomem
0x90a0-0x90a00fff irq 47 on acpi0
But nothing happens if I put a card in. Unless I suspend and resume:
mmc1: on sdhci_acpi1
mmcsd0: 32GB at mmc1
50.0MHz/4bit/65535-block
Then I can remove and replug cards and it seems to work just fine.
I believe that making SD card insertion/removal with the integrated
SDHCI controlers of newer Intel SoCs work out-of-the-box requires
support for ACPI GPE interrupts and ACPI GPIO events respectively to
be added to FreeBSD. Otherwise insertion/removal interrutps/events
aren't reported and polling the card present state doesn't generally
work as a workaround with these controllers either, unfortunately.
I'm not aware of anyone working on the former, though.
Polling the card present state happens to work one time after SDHCI
initialization with these controllers which is why a card will be
attached when inserted as part of a suspend/resume cycle (resume of
mmc(4) had some bugs until some months ago, which probably explains
why that procedure hasn't worked as a workaround for you in the past).
Inserting the card before boot, unloading/loading sdhci_acpi.ko or
triggering detach/attach of sdhci_acpi(4) via devctl(8) should allow
to attach a card, too.
If a card is inserted before booting it is not detected.
Removing and inserting card after boot is not detected unless I suspend
and resume.
After I have suspended and resumed once, cards are detected. Removals
and insertions are detected as they happen.
Okay, then you are seeing somewhat different behavior than I do. What
SoC model is this?
CPU: Intel(R) Pentium(R) CPU N3540 @ 2.16GHz (2166.73-MHz K8-class CPU)
Are you loading a GPIO controller driver such as
bytgpio(4) or chvgpio(4)? Doing so might be sufficient to kick ACPI
GPIO events into working but would be missing dependency information
between drivers (which might explain what you are experiencing if
sdhci_acpi1 attaches first) and some other bits to do it properly.
I have bytgpio_load="YES" in /boot/loader.conf
But I tried removing it, doesn't change the behavior.
With or without the bytgpio driver, inserting or removing cards is
only detected after a suspend/resume cycle of the computer.
Also, could you please try whether doing a suspend/resume cycle of
sdhci_acpi1 via devctl(8) only kicks the card detection into working?
That test should indicate whether the firmware plays a role in making
the latter work.
Tried that.
devctl suspend sdhci_acpi1
devctl resume sdhci_acpi1
Doesn't make any difference.
Also tried devctl disable/enable. No change.
Additional research:
After boot, before any suspend/resume:
From acpidump -d
Device (SDHC)
{
Name (_ADR, Zero) // _ADR: Address
Name (_HID, "80860F16") // _HID: Hardware ID
Name (_CID, "PNP0D40" /* SDA Standard Compliant SD Host
Controller */) // _CID: Compatible ID
Name (_DDN, "Intel(R) SD Card Controller - 80860F16") //
_DDN: DOS Device Name
Name (_UID, 0x03) // _UID: Unique ID
Name (RBUF, ResourceTemplate ()
{
Memory32Fixed (ReadWrite,
0x, // Address Base
0x1000, // Address Length
_Y04)
Interrupt (ResourceConsumer, Level, ActiveLow,
Exclusive, ,, )
{
0x002F,
}
GpioInt (Edge, ActiveBoth, SharedAndWake, PullNone, 0x2710,
"\\_SB.GPO0", 0x00, ResourceConsumer, ,
)
{ // Pin list
0x0026
}
GpioIo (Shared, PullDefault, 0x, 0x,
IoRestrictionInputOnly,
"\\_SB.GPO0", 0x00, ResourceConsumer, ,
)
{ // Pin list
0x0026
}
})
And indeed card detection is GPIO pin 38 (0x26):
No card:
gpioctl -l | grep "pin 38"
pin 38: 1 GPIO_S0_SC38
Card inserted:
gpioctl -l | grep "pin 38"
pin 38: 0 GPIO_S0_SC38
After suspend/resume card detection works:
mmc1: on sdhci_acpi1
mmcsd0: 32GB at mmc1
50.0MHz/4bit/65535-block
But pin 38 is always 1, regardless if a card is inserted or not:
gpioctl -l | grep "pin 38"
pin 38: 1 GPIO_S0_SC38
And 'acpidump -d' fails:
acpidump: RSDT entry 12 is corrupt
Any clue on what's going on here?
Jakob
_
Re: devd on head -r338675 on aarch64 (Pine64+ 2GB example) gets during booting: "sh: /usr/libexec/hyperv/hyperv_vfattach: not found"
On 9/14/18 11:24 AM, Mark Millard via freebsd-arm wrote: > From the boot of the Pine64+ 2GB for -r338675: > > . . . > Starting devd. > sh: /usr/libexec/hyperv/hyperv_vfattach: not found > add host 127.0.0.1: gateway lo0 fib 0: route already in table > . . . I got the same error booting FreeBSD/riscv in qemu. -- 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"
Bad DHCP Checksums over VLANs
Folks, I'm running head (ALPHA4-ish) on a DHCP server and a client. DHCP works fine on the physical interfaces, but when I run it on a VLAN, I get 5 bad udp checksums in 5 packets from dhclient. Full details here: https://people.freebsd.org/~vangyzen/dhcp_vlan/ This happens for /all/ clients. This is a new setup, so I don't know when it got broken, and I can't bisect. The server NIC is common (I211), so maybe it's easy to reproduce. I'll help as much as I can, of course. Eric ___ 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: Bad DHCP Checksums over VLANs
Hi! > The server NIC is common (I211), so maybe it's easy to reproduce. I'll > help as much as I can, of course. Can you disable all the options of the NIC ? ifconfig igb0 -rxcsum -txcsum -wol -tso4 -vlanmtu -vlanhwtag -vlanhwcsum -vlanhwtso Try to disable everything that can be disabled, e.g. LRO etc. -- p...@freebsd.org +49 171 3101372 2 years to go ! ___ 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"
