[Bug 212000] 11.0-RC1: vimage jail with ipfilter not working

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212000

Bug ID: 212000
   Summary: 11.0-RC1: vimage jail with ipfilter not working
   Product: Base System
   Version: 11.0-RC1
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: qja...@a1poweruser.com

Tested on 11.0-RC1 with only vimage compiled into the kernel.
Tested ipfilter in vnet jail and no firewall on host.
Tested ipfilter in vnet jail and on the host.

Vnet jail used this /etc/devfs.rules rule

[devfsrules_vjail_ipf=60]
add include $devfsrules_jail
add path ipl unhide
add path ipl0unhide
add path ipf unhide
add path ipauth  unhide
add path ipnat   unhide
add path ipstate unhide
# used by ipstate
#add path kmemunhide
#add path kernel  unhide


Testing no ipfilter firewall running on host, just in vnet jail.

When starting vnet jail with ipfilter, I check if ipfilter kernel modules are
loaded, if not them loads them. Auto loading of modules does not happen.

Issuing the ipfilter command "ipfstat -hnoi" from the started vnet jail 
console show this

0 @1 pass out quick on lo0 all
0 @2 block out log quick on epair17b proto tcp from any to any port = nicname
0 @3 pass out log quick on epair17b all
0 @1 pass in quick on lo0 all
0 @2 pass in log quick on epair17b all

There are 0 counts because the ipstate command is restricted from accessing
kmem & kernel. 
But this at lease seems to prove ipfilter is running in the vnet jail.

Issuing the "ping" command from the started vnet jail console works.

Issuing the "whois" command from the started vnet jail console works also,
but should not work because of the above block rule on port 43.

This indicates that the ipfilter rules in a vnet jail are not functioning.
No ipfilter log messages are posted in the vnat jail and no log messages
are posted in the hosts log.


Testing ipfilter firewall running on host and vnet jail.
Issuing the ipfilter command "ipfstat -hnoi" from the host console show this

0 @1 pass out quick on lo0 all
0 @2 pass out log quick on fxp0 all
0 @1 pass in quick on lo0 all
1 @2 pass in log quick on fxp0 all

The vnet jail results are the same as above.
But the hosts ipfilter log, logs this on vnet jail startup and keeps repeating
it for the whole time the vnet jail is running. 

fxp0 @0:2 p 10.0.10.2,67 -> 10.0.10.12,68 PR udp len 20 328 IN
fxp0 @0:2 p :: -> ff02::1:ff00:50b PR icmpv6 len 40 72 icmpv6 neighborsolicit/0
OUT multicast
fxp0 @0:2 p :: -> ff02::16 PR icmpv6 len 48 76 icmpv6 icmpv6type(143)/0 OUT
multicast
fxp0 @0:2 p :: -> ff02::16 PR icmpv6 len 48 96 icmpv6 icmpv6type(143)/0 OUT
multicast
fxp0 @0:2 p :: -> ff02::16 PR icmpv6 len 48 76 icmpv6 icmpv6type(143)/0 OUT
multicast
fxp0 @0:2 p fe80::c1:ff:fe00:50b -> ff02::16 PR icmpv6 len 48 96 icmpv6
icmpv6type(143)/0 OUT multicast
fxp0 @0:2 p fe80::d950:d6dc:db92:f20d,546 -> ff02::1:2,547 PR udp len 40 137 IN
low-ttl multicast
fxp0 @0:2 p fe80::d950:d6dc:db92:f20d,546 -> ff02::1:2,547 PR udp len 40 137 IN
low-ttl multicast
fxp0 @0:2 p fe80::d950:d6dc:db92:f20d,546 -> ff02::1:2,547 PR udp len 40 137 IN
low-ttl multicast
fxp0 @0:2 p fe80::d950:d6dc:db92:f20d,546 -> ff02::1:2,547 PR udp len 40 137 IN
low-ttl multicast
fxp0 @0:2 p fe80::d950:d6dc:db92:f20d,546 -> ff02::1:2,547 PR udp len 40 137 IN
low-ttl multicast
fxp0 @0:2 p fe80::d950:d6dc:db92:f20d,546 -> ff02::1:2,547 PR udp len 40 137 IN
low-ttl multicast
fxp0 @0:2 p fe80::d950:d6dc:db92:f20d,546 -> ff02::1:2,547 PR udp len 40 137 IN
low-ttl multicast
fxp0 @0:2 p 10.0.10.7,68 -> 255.255.255.255,67 PR udp len 20 328 IN broadcast

Issuing the "ping" command from the started vnet jail console works and the
hosts ipfilter log shows this

fxp0 @0:2 p 10.0.10.7,68 -> 255.255.255.255,67 PR udp len 20 328 IN broadcast
fxp0 @0:2 p 10.11.0.2 -> 8.8.8.8 PR icmp len 20 84 icmp echo/0 OUT
fxp0 @0:2 p 8.8.8.8 -> 10.11.0.2 PR icmp len 20 84 icmp echoreply/0 IN
fxp0 @0:2 p 10.11.0.2 -> 8.8.8.8 PR icmp len 20 84 icmp echo/0 OUT
fxp0 @0:2 p 8.8.8.8 -> 10.11.0.2 PR icmp len 20 84 icmp echoreply/0 IN
fxp0 @0:2 p 10.11.0.2 -> 8.8.8.8 PR icmp len 20 84 icmp echo/0 OUT
fxp0 @0:2 p 8.8.8.8 -> 10.11.0.2 PR icmp len 20 84 icmp echoreply/0 IN
fxp0 @0:2 p 10.11.0.2 -> 8.8.8.8 PR icmp len 20 84 icmp echo/0 OUT
fxp0 @0:2 p 8.8.8.8 -> 10.11.0.2 PR icmp len 20 84 icmp echoreply/0 IN

The hosts ipfilter firewall is logging the traffic on the fxp0 interface,
this is normal and expected.

I see 4 things that are strange.
1. Why is the vnet jail issuing all that ipv6 traffic? It should only be
   generated if the vnet jail interface has a ipv6 ip address coded.
2. Why is ipv4 & ipv6 traffic making it to the host and NOT showing up on
   the epair11b interface? 
   This is a problem if the host has a few vnet jails running at same time.
   IE: how am I going to control traffic on host to target 

[Bug 211361] suggested boot partition size is too small, bsdinstall creates unaligned partitions

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211361

--- Comment #23 from commit-h...@freebsd.org ---
A commit references this bug:

Author: des
Date: Fri Aug 19 07:05:35 UTC 2016
New revision: 304448
URL: https://svnweb.freebsd.org/changeset/base/304448

Log:
  MFH (r304142): ensure stripe size is non-zero multiple of 4096

  PR:   211361

Changes:
_U  stable/11/
  stable/11/usr.sbin/bsdinstall/partedit/gpart_ops.c

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 211965] [patch] fmodl not properly aliased on architectures where LDBL_PREC == 53 (arm, mips, powerpc)

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211965

Mark Linimon  changed:

   What|Removed |Added

   Keywords||patch

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 211361] suggested boot partition size is too small, bsdinstall creates unaligned partitions

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211361

--- Comment #24 from commit-h...@freebsd.org ---
A commit references this bug:

Author: des
Date: Fri Aug 19 09:11:50 UTC 2016
New revision: 304457
URL: https://svnweb.freebsd.org/changeset/base/304457

Log:
  MFH (r304142): ensure stripe size is non-zero multiple of 4096

  PR:   211361
  Approved by:  re (gjb)

Changes:
_U  releng/11.0/
  releng/11.0/usr.sbin/bsdinstall/partedit/gpart_ops.c

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 211361] suggested boot partition size is too small, bsdinstall creates unaligned partitions

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211361

Dag-Erling Smørgrav  changed:

   What|Removed |Added

  Flags|mfc-stable11?   |mfc-stable11+

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 211984] adding randomized MAC ifconfig option ?

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211984

Bug ID: 211984
   Summary: adding randomized MAC ifconfig option ?
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: bin
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: p...@freebsd.org

Please have a look at

https://gist.github.com/t6/05e2959c5583ecdce2487c1557f784b7

would it be possible to integrate this patch ?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 211990] iscsi fails to reconnect and does not release devices

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211990

Bug ID: 211990
   Summary: iscsi fails to reconnect and does not release devices
   Product: Base System
   Version: 10.3-RELEASE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: ben.rub...@gmail.com

Hello,

I'm facing an issue where iscsictl does not want to remove devices.
Here is how I can reproduce this.

### Initiator :
# iscsictl -Aa
iscsictl then reports the 17 targets as connected, perfect.

### Target :
Let's switch down the network interface
# ifconfig mlxen1 down

### Initiator :
iscsictl reports the 17 targets as disconnected, perfect.

### Target :
Let's switch up the network interface
# ifconfig mlxen1 up

### Initiator :
iscsictl reports the 17 targets as connected, however, for 4 devices, I get the
following :
09:59:43 srv1 kernel: WARNING: 192.168.2.2 (iqn.2012-06.srv2:lg2): timed out
waiting for iscsid(8) for 11 seconds; reconnecting
09:59:54 srv1 kernel: WARNING: 192.168.2.2 (iqn.2012-06.srv2:lg2): timed out
waiting for iscsid(8) for 11 seconds; reconnecting
09:59:57 srv1 kernel: WARNING: 192.168.2.2 (iqn.2012-06.srv2:lg2): handoff on
already connected session
07:59:57 srv1 iscsid[1372]: 192.168.2.2 (iqn.2012-06.srv2:lg2): ISCSIDHANDOFF:
Device busy
09:59:57 srv1 iscsid[581]: child process 1372 terminated with exit status 1
09:59:57 srv1 kernel: WARNING: 192.168.2.2 (iqn.2012-06.srv2:lg2): connection
error; reconnecting
09:59:57 srv1 kernel: (da21:iscsi8:0:0:0): got CAM status 0x8
09:59:57 srv1 kernel: (da21:iscsi8:0:0:0): fatal error, failed to attach to
device
10:00:07 srv1 kernel: WARNING: 192.168.2.2 (iqn.2012-06.srv2:lg2): no ping
reply (NOP-In) after 10 seconds; reconnecting
10:00:08 srv1 kernel: WARNING: 192.168.2.2 (iqn.2012-06.srv2:lg2): no ping
reply (NOP-In) after 10 seconds; reconnecting

### Target :
09:58:50 srv2 kernel: mlxen1: link state changed to DOWN
09:58:50 srv2 kernel: mlx4_en: mlxen1: Link Down
09:58:53 srv2 kernel: WARNING: 192.168.2.1 (iqn.1994-09.org.freebsd:srv1): no
ping reply (NOP-Out) after 5 seconds; dropping connection
09:58:53 srv2 last message repeated 16 times
09:59:49 srv2 kernel: mlx4_en: mlxen1: Link Up
09:59:49 srv2 kernel: mlxen1: link state changed to UP
09:59:49 srv2 devd: Executing '/etc/rc.d/dhclient quietstart mlxen1'
09:59:59 srv2 kernel: WARNING: 192.168.2.1 (iqn.1994-09.org.freebsd:srv1):
connection error; dropping connection
09:59:59 srv2 last message repeated 3 times

### Initiator :
# iscsictl -Ra
# iscsictl -L
Target nameTarget portalState
iqn.2012-06.srv2:sW1   192.168.2.2  Connected: da18 
iqn.2012-06.srv2:sW2   192.168.2.2  Connected: da23 
iqn.2012-06.srv2:rT3   192.168.2.2  Connected: da17 
iqn.2012-06.srv2:lg2   192.168.2.2  Connected: da21 

As you can see, the 4 problematic devices remain "connected", nodes exist in
/dev/, but they are unusable.

Each time I "iscsictl -Ra", I get the following on initiator side :
10:09:35 srv1 kernel: WARNING: 192.168.2.2 (iqn.2012-06.srv2:lg2): connection
error; reconnecting
10:09:35 srv1 kernel: WARNING: 192.168.2.2 (iqn.2012-06.srv2:sW1): connection
error; reconnecting
10:09:35 srv1 kernel: WARNING: 192.168.2.2 (iqn.2012-06.srv2:rT3): connection
error; reconnecting
10:09:35 srv1 kernel: WARNING: 192.168.2.2 (iqn.2012-06.srv2:sW2): connection
error; reconnecting

No logs however on target side, even if I start ctld with -d.

The only workaround I found is to reboot, or to change the target name to
properly reconnect...

# uname -v
FreeBSD 10.3-RELEASE-p7 #0: Thu Aug 11 18:38:15 UTC 2016
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC 

Thank you for your support,

Best regards,

Ben

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 211990] iscsi fails to reconnect and does not release devices

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211990

--- Comment #2 from Ben RUBSON  ---
Quite difficult to reproduce, but I managed to do it again.
This time the problematic target (only one /17) is seen as disconnected.

### Initiator :
# iscsictl -Ra
# iscsictl -L
Target name  Target portalState
iqn.2012-06.srv2:ch3 192.168.2.2  Disconnected
# netstat -an | grep 3260
// nothing returned

### Initiator logs :
12:38:02 srv1 kernel: WARNING: 192.168.2.2 (iqn.2012-06.srv2:ch3): login timed
out after 11 seconds; reconnecting
12:38:06 srv1 kernel: WARNING: 192.168.2.2 (iqn.2012-06.srv2:ch3): handoff on
already connected session
12:38:06 srv1 iscsid[7395]: 192.168.2.2 (iqn.2012-06.srv2:ch3): ISCSIDHANDOFF:
Device busy
12:38:06 srv1 iscsid[581]: child process 7395 terminated with exit status 1
12:38:06 srv1 kernel: WARNING: 192.168.2.2 (iqn.2012-06.srv2:ch3): connection
error; reconnecting
12:38:06 srv1 kernel: da8 at iscsi63 bus 0 scbus1 target 0 lun 0
12:38:06 srv1 kernel: da8:  s/n G22020PY1EZHAch detached
12:38:16 srv1 kernel: WARNING: 192.168.2.2 (iqn.2012-06.srv2:ch3): no ping
reply (NOP-In) after 10 seconds; reconnecting

### Target logs :
12:37:41 srv2 kernel: mlxen1: link state changed to DOWN
12:37:41 srv2 kernel: mlx4_en: mlxen1: Link Down
12:37:46 srv2 kernel: WARNING: 192.168.2.1 (iqn.1994-09.org.freebsd:srv1): no
ping reply (NOP-Out) after 5 seconds; dropping connection
12:37:46 srv2 last message repeated 16 times
12:38:05 srv2 kernel: mlx4_en: mlxen1: Link Up
12:38:05 srv2 kernel: mlxen1: link state changed to UP
12:38:05 srv2 devd: Executing '/etc/rc.d/dhclient quietstart mlxen1'
12:38:09 srv2 kernel: WARNING: 192.168.2.1 (iqn.1994-09.org.freebsd:srv1):
connection error; dropping connection

On initiator side, I also get the same log messages as above for the other
devices, but they correctly reconnect.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 210686] NCQ_TRIM_BROKEN quirk mismatch

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210686

--- Comment #7 from Tomoaki AOKI  ---
It should be best getting in 11.0-R but it's not mandatory
as the workaround is quite easy (just 1 line in /boot/loader.conf).

But if not got in, announcement of workaround would be needed in RELNOTES
(not only 20160414 entry of /usr/src/UPDATING) not to be missed for newbies.

Thanks.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 211990] iscsi fails to reconnect and does not release devices

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211990

--- Comment #1 from Ben RUBSON  ---
On initiator, netstat also returns the following :
tcp4   0  0 192.168.2.1.49715  192.168.2.2.3260   CLOSED
tcp4   0  0 192.168.2.1.49708  192.168.2.2.3260   CLOSED
tcp4   0  0 192.168.2.1.49707  192.168.2.2.3260   CLOSED
tcp4   0  0 192.168.2.1.49706  192.168.2.2.3260   CLOSED

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 211990] iscsi fails to reconnect and does not release devices

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211990

--- Comment #3 from Ben RUBSON  ---
(In reply to Ben RUBSON from comment #0)
>The only workaround I found is to reboot

I even have to hard-reboot, because of this never ending :
iscsi_terminate_sessions: waiting for sessions to terminate

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 211952] make buildworld fails with read-only /usr/src

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211952

Jilles Tjoelker  changed:

   What|Removed |Added

 Status|New |Open
 CC||bdrew...@freebsd.org,
   ||jil...@freebsd.org

--- Comment #1 from Jilles Tjoelker  ---
It looks like this was caused by SVN r296702. Since that revision, it attempts
to build some source files from other source files (for example
share/i18n/esdb/AST/ARMSCII-7.src from share/i18n/esdb/AST/ARMSCII-7.src). It
is probably better to move these commands to a script that is run manually if
needed, somewhat like sys/kern/makesyscalls.sh.

As a workaround, you can run one build with a read/write source tree and revert
the changes, if any. After that, the timestamps will be such that it will not
attempt to rebuild the files again.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 211952] make buildworld fails with read-only /usr/src

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211952

--- Comment #2 from Bryan Drewery  ---
Ah, share/i18n/esdb/AST/ARMSCII-7.src is modified but never has changed
content.  Really these should probably not be checked in if they match what is
generated exactly.

I'll look at this soon.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 211990] iscsi fails to reconnect and does not release devices

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211990

--- Comment #4 from Ben RUBSON  ---
One strange thing I noticed.
(I put all things that could be interesting from my troubleshooting)

As soon as I put the network interface down, I get the following message on
target side, one per target :
17:01:00 srv2 kernel: WARNING: 192.168.2.1 (iqn.1994-09.org.freebsd:srv1): no
ping reply (NOP-Out) after 5 seconds; dropping connection

Then, on initiator side, I get these messages for each target :
Aug 19 17:01:07 srv1 kernel: iscsi_maintenance_thread_reconnect: 192.168.2.2
(iqn.2012-06.srv2:hm4): connection failed, destroying devices
Aug 19 17:01:07 srv1 kernel: iscsi_session_cleanup: 192.168.2.2
(iqn.2012-06.srv2:hm4): freezing
Aug 19 17:01:07 srv1 kernel: iscsi_session_cleanup: 192.168.2.2
(iqn.2012-06.srv2:hm4): deregistering SIM

At this moment, on initiator side, one iscsid process per target appears.

10 seconds later, on initiator side, I get these messages for each target :
Aug 19 17:01:18 srv1 kernel: WARNING: 192.168.2.2 (iqn.2012-06.srv2:hm4): login
timed out after 11 seconds; reconnecting
Aug 19 17:01:18 srv1 kernel: iscsi_maintenance_thread_reconnect: 192.168.2.2
(iqn.2012-06.srv2:hm4): connection failed, destroying devices

And at the same time, a second iscsid process per target appears, so that I get
2 iscsid processes per target :
# ps auxxw | grep iscsid:
root  8660.0  0.0 16632  2144  -  I 4:58pm   0:00.00 iscsid:
192.168.2.2 (iqn.2012-06.srv2:hm4) (iscsid)
root  8810.0  0.0 16632  2144  -  I 4:58pm   0:00.00 iscsid:
192.168.2.2 (iqn.2012-06.srv2:hm4) (iscsid)
(...)
However sounds like there is a limit to 30 processes, as for 17 targets I would
have expected 34 processes, but I only get 30.

If I put the NIC up before the second process is created, I only get one
reconnection message per target in target logs.
If I put the NIC up after the second process is created, I get a lot more
reconnection messages in target logs, between 40 and 50 for 17 targets.

Do we expect these additional processes ?
I think we would only expect one process / one reconnection message per target
?
Seems strange to have all these "duplicated" connection retries.

Another related question to the "30" processes found :
Is there any limit to 30 targets ?
I found a maxproc option in ctl.conf (default to 30) but I don't exactly know
what it means (I tested values of 1 to 50 without seeing any change).
No option found however on initiator side.

I noticed that we can reproduce this bug easier when we "stress" the devices :
disconnect network as soon as targets are reconnected, and reconnect it as soon
as they are disconnected.



Additionally to this, I had 8 kernel crashes, initator or target, each time
with the same address / pointer :
kernel: Fatal trap 12: page fault while in kernel mode
kernel: fault virtual address   = 0x1e8
kernel: instruction pointer = 0x20:0x80936933

I also got a stacktrace, but did not get it's pointer address.
http://img4.hostingpics.net/pics/707217211990.png

I'm also trying to get a full dump.
However I'm not sure this kernel crash issue is related to the reconnection
issue, perhaps there are 2 issues.

# uname -v
FreeBSD 10.3-RELEASE-p7 #0: Thu Aug 11 18:38:15 UTC 2016
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC



A lot of info !
I hope we will be able to correct these issues.

Many thanks,

Ben

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 212006] Error building 11.0-RC1 from 10.2-Release

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212006

Bug ID: 212006
   Summary: Error building 11.0-RC1 from 10.2-Release
   Product: Base System
   Version: 11.0-RC1
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: bin
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: lo...@arroway.org
CC: freebsd-am...@freebsd.org
CC: freebsd-am...@freebsd.org

Created attachment 173878
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=173878=edit
script

After updating sources to 11.0-RC1, when making buildworld, I get:

1.   parser at end of file
2.  Code generation
3.  Running pass 'Function Pass Manager' on module
'/usr/src/lib/clang/libclangcodegen/../../../contrib/llvm/tools/clang/lib/CodeGen/CGBlocks.cpp'.
4.  Running pass 'X86 DAG->DAG Instruction Selection' on function
'@_ZN5clang7CodeGen15CodeGenFunction12EmitCallArgsINS_17FunctionProtoTypeEEEvRNS0_11CallArgListEPKT_N4llvm14iterator_rangeINS_4Stmt17ConstExprIteratorEEEPKNS_12FunctionDeclEj'
c++: error: unable to execute command: Segmentation fault (core dumped)
c++: error: clang frontend command failed due to signal (use -v to see
invocation)
FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
Target: x86_64-unknown-freebsd10.2
Thread model: posix
c++: note: diagnostic msg: PLEASE submit a bug report to
https://bugs.freebsd.org/submit/ and include the crash backtrace, preprocessed
source, and associated run script.
c++: note: diagnostic msg:


PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
Preprocessed source(s) and associated run script(s) are located at:
c++: note: diagnostic msg: /tmp/CGBlocks-5b9c86.cpp
c++: note: diagnostic msg: /tmp/CGBlocks-5b9c86.sh
c++: note: diagnostic msg:


*** Error code 254

Stop.
bmake[4]: stopped in /usr/src/lib/clang/libclangcodegen
*** Error code 1

Stop.
bmake[3]: stopped in /usr/src/lib/clang
*** Error code 1

Stop.
bmake[2]: stopped in /usr/src
*** Error code 1

Stop.
bmake[1]: stopped in /usr/src
*** Error code 1

Stop.
make: stopped in /usr/src

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 212006] Error building 11.0-RC1 from 10.2-Release

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212006

--- Comment #2 from lo...@arroway.org ---
Created attachment 173879
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=173879=edit
compressed code part 1

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 212006] Error building 11.0-RC1 from 10.2-Release

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212006

--- Comment #1 from lo...@arroway.org ---
Cant add the cpp file that the message says to. I get the error:

413 Request Entity Too Large

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 212006] Error building 11.0-RC1 from 10.2-Release

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212006

--- Comment #3 from lo...@arroway.org ---
Created attachment 173880
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=173880=edit
compressed code part 2

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 212006] Error building 11.0-RC1 from 10.2-Release

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212006

--- Comment #4 from lo...@arroway.org ---
Created attachment 173881
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=173881=edit
compressed code part 3

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"