On Thu, Nov 03, 2016 at 11:28:52AM +0100, Martin Pieuchot wrote:
> >
> > First, I didn't reproduced the panic on ping with GENERIC.MP. But while
> > running GENERIC, I triggered it.
> >
> > # ifconfig vether0 create
> > # ifconfig vether0 rdomain 20
> > # ifconfig vether0 inet 192.168.20.99
> > # ifconfig vether0 up
> > # ping -V 20 192.168.20.99
> > <panic>
>
> Could you send me your full configuration because this snippet is not
> enough to trigger the bug. Something must have been corrupted earlier.
>
I think this panic is unrelated to previous bug: it am able to panic
without playing with rdomain: just running "ping 127.0.0.1" is enough.
This host is a laptop I use for building -current and testing. Normally
it runs GENERIC.MP and I just switched it to GENERIC to testing the
panic I saw on my other i386 host. The whole network configuration for
this host is really simple (except maybe ipv6 configuration).
# cat /etc/hostname.bce0
dhcp
up
rtsol
# ifconfig -a
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 32768
index 4 priority 0 llprio 3
groups: lo
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
inet 127.0.0.1 netmask 0xff000000
wpi0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
lladdr 00:13:02:2e:8b:46
index 1 priority 4 llprio 3
groups: wlan
media: IEEE802.11 autoselect
status: no network
ieee80211: nwid ""
bce0: flags=208a43<UP,BROADCAST,RUNNING,ALLMULTI,SIMPLEX,MULTICAST,AUTOCONF6>
mtu 1500
lladdr 00:15:c5:0b:8b:7a
index 2 priority 0 llprio 3
groups: egress
media: Ethernet autoselect (100baseTX full-duplex)
status: active
inet 192.168.92.11 netmask 0xffffff00 broadcast 192.168.92.255
inet6 fe80::215:c5ff:fe0b:8b7a%bce0 prefixlen 64 scopeid 0x2
inet6 2001:41d0:fe39:c05c:215:c5ff:fe0b:8b7a prefixlen 64 autoconf
pltime 0 vltime 2591999
inet6 2001:41d0:fe39:c05c:2808:19e:33a:93a3 prefixlen 64 autoconf
autoconfprivacy pltime 0 vltime 604663
enc0: flags=0<>
index 3 priority 0 llprio 3
groups: enc
status: active
pflog0: flags=141<UP,RUNNING,PROMISC> mtu 33188
index 5 priority 0 llprio 3
groups: pflog
# dmesg -s
Automatic boot in progress: starting file system checks.
/dev/wd0a (055d82c92ce5e61f.a): 1772 files, 36979 used, 93556 free (180 frags,
11672 blocks, 0.1% fragmentation)
/dev/wd0a (055d82c92ce5e61f.a): MARKING FILE SYSTEM CLEAN
/dev/wd0g (055d82c92ce5e61f.g): 10 files, 7 used, 512016 free (40 frags, 63997
blocks, 0.0% fragmentation)
/dev/wd0g (055d82c92ce5e61f.g): MARKING FILE SYSTEM CLEAN
/dev/wd0d (055d82c92ce5e61f.d): 23442 files, 251340 used, 523891 free (4123
frags, 64971 blocks, 0.5% fragmentation)
/dev/wd0d (055d82c92ce5e61f.d): MARKING FILE SYSTEM CLEAN
/dev/wd0e (055d82c92ce5e61f.e): 5420 files, 56740 used, 7680067 free (251
frags, 959977 blocks, 0.0% fragmentation)
/dev/wd0e (055d82c92ce5e61f.e): MARKING FILE SYSTEM CLEAN
/dev/wd0f (055d82c92ce5e61f.f): FREE BLK COUNT(S) WRONG IN SUPERBLK (SALVAGED)
/dev/wd0f (055d82c92ce5e61f.f): SUMMARY INFORMATION BAD (SALVAGED)
/dev/wd0f (055d82c92ce5e61f.f): BLK(S) MISSING IN BIT MAPS (SALVAGED)
/dev/wd0f (055d82c92ce5e61f.f): 547 files, 3687 used, 2060472 free (200 frags,
257534 blocks, 0.0% fragmentation)
/dev/wd0f (055d82c92ce5e61f.f): MARKING FILE SYSTEM CLEAN
/dev/wd0h (055d82c92ce5e61f.h): 331014 files, 6224799 used, 8686055 free (14367
frags, 1083961 blocks, 0.1% fragmentation)
/dev/wd0h (055d82c92ce5e61f.h): MARKING FILE SYSTEM CLEAN
setting tty flags
kbd: keyboard mapping set to fr
pf enabled
ddb.panic: 1 -> 1
ddb.log: 1 -> 1
net.inet.ip.forwarding: 0 -> 0
net.inet6.ip6.forwarding: 0 -> 0
starting network
DHCPREQUEST on bce0 to 255.255.255.255
DHCPACK from 192.168.92.2 (c8:be:19:e2:2c:ed)
bound to 192.168.92.11 -- renewal in 21600 seconds.
reordering libraries: done.
starting early daemons: syslogd pflogd ntpd.
starting RPC daemons:.
savecore: no core dump
checking quotas: done.
clearing /tmp
kern.allowkmem: 0 -> 1
kern.securelevel: 0 -> 1
creating runtime link editor directory cache.
preserving editor files.
starting network daemons: sshd smtpd sndiod.
starting local daemons: cron xdm.
Thu Nov 3 11:35:01 CET 2016
# ping 127.0.0.1
<panic>
# ping 192.168.92.11
<panic>
I will try several configurations (like removing rtsol or manually
configuring the interface) in order to isolate the problem.
--
Sebastien Marie
