public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nss/27537] [2.33 Regression] FAIL: nss/tst-reload2
Date: Mon, 08 Mar 2021 13:11:07 +0000 [thread overview]
Message-ID: <bug-27537-131-3AtDGTAURV@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27537-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27537
--- Comment #2 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Florian Weimer from comment #1)
> Do you have any IPv6 addresses configured on your system? Thanks.
[hjl@gnu-cfl-2 ~]$ ifconfig eno1
eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1300
inet 192.168.1.17 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::b2a6:e6f1:de7a:da77 prefixlen 64 scopeid 0x20<link>
ether 94:c6:91:a4:31:be txqueuelen 1000 (Ethernet)
RX packets 11319 bytes 7199395 (6.8 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 8826 bytes 1601253 (1.5 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 16 memory 0xb0b00000-b0b20000
[hjl@gnu-cfl-2 ~]$ ping fe80::b2a6:e6f1:de7a:da77
PING fe80::b2a6:e6f1:de7a:da77(fe80::b2a6:e6f1:de7a:da77) 56 data bytes
ping: sendmsg: Invalid argument
ping: sendmsg: Invalid argument
--- fe80::b2a6:e6f1:de7a:da77 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1010ms
[hjl@gnu-cfl-2 ~]$ ping 192.168.1.17
PING 192.168.1.17 (192.168.1.17) 56(84) bytes of data.
64 bytes from 192.168.1.17: icmp_seq=1 ttl=64 time=0.032 ms
--- 192.168.1.17 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.032/0.032/0.032/0.000 ms
[hjl@gnu-cfl-2 ~]$
There is no working IPv6. The same test works on master branch.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-03-08 13:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-06 17:45 [Bug nss/27537] New: " hjl.tools at gmail dot com
2021-03-08 8:08 ` [Bug nss/27537] " fweimer at redhat dot com
2021-03-08 13:11 ` hjl.tools at gmail dot com [this message]
2021-03-08 13:34 ` fweimer at redhat dot com
2021-03-08 15:15 ` hjl.tools at gmail dot com
2021-03-08 16:17 ` skpgkp2 at gmail dot com
2021-03-08 17:39 ` skpgkp2 at gmail dot com
2021-03-08 17:57 ` schwab@linux-m68k.org
2021-03-09 19:08 ` [Bug nss/27537] [2.33/2.34 " hjl.tools at gmail dot com
2021-03-09 20:09 ` dj at redhat dot com
2021-03-09 21:06 ` hjl.tools at gmail dot com
2021-03-10 14:38 ` hjl.tools at gmail dot com
2021-03-11 8:25 ` stli at linux dot ibm.com
2021-03-11 22:08 ` dj at redhat dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-27537-131-3AtDGTAURV@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).