Re: pkg with an ssh repo crashes CURRENT

2015-08-25 Thread Konstantin Belousov
On Mon, Aug 24, 2015 at 03:20:26PM -0500, Mark Felder wrote: On Thu, Aug 20, 2015, at 17:18, Konstantin Belousov wrote: I guess the process 666 was current when the panic occured ? Basically, what I want is to see the p_reaper value for the process with the pid 667. Even just

Re: ipfw rules for connect port 993

2015-08-25 Thread Petr Chocholáč
Hello , thank you for your answer. ad1. i send my current firewall rules and record from tcpdump on re0 . My LAN is 172.16.0.0/22 (10... it was easy. I think it does not matter) My second LAN is 192.168.1.0/24(on this network connection to the IMAP port 993 works) My public IP is 86.49.91.98

Re: Kernel panic with fresh current, probably nfs related

2015-08-25 Thread Joel Dahl
On Mon, Aug 24, 2015 at 11:18:00AM -0700, Sean Bruno wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 08/23/15 18:36, Yonghyeon PYUN wrote: Index: sys/dev/e1000/if_em.c === - --- sys/dev/e1000/if_em.c

Jenkins build is back to normal : Build-UFS-image #2191

2015-08-25 Thread jenkins-admin
See https://jenkins.FreeBSD.org/job/Build-UFS-image/2191/ ___ 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: ipfw rules for connect port 993

2015-08-25 Thread Julian Elischer
On 8/25/15 4:02 PM, Petr Chocholáč wrote: Hello , ignore my previous email, you have answered my questions here. the firewall set you show is pretty horrible. It really needs a rewrite. do you want to block the two LANs from each other or block any machines on the LANs from reaching the

Re: ipfw rules for connect port 993

2015-08-25 Thread Julian Elischer
On 8/24/15 9:05 PM, Petr Chocholáč wrote: Hello, I would like to ask you for advice. I can not connect to imap.gmail.com on port 993 from my local network. My LAN is behind freeBSD server with IPFW. Server has two network cards rl0=Internet and re0=LAN(10.0.0.0/16). Tcpdump on re0 shows

Re: Read-only /usr/obj/ no longer kosher?

2015-08-25 Thread Pawel Jakub Dawidek
On Tue, Aug 25, 2015 at 11:04:37PM +0200, Pawel Jakub Dawidek wrote: On Sun, Aug 23, 2015 at 03:29:01PM -0700, Xin Li wrote: On 8/23/15 14:55, Pawel Jakub Dawidek wrote: I used to build world and kernel on one machine and export both /usr/src/ and /usr/obj read-only to other

Re: Read-only /usr/obj/ no longer kosher?

2015-08-25 Thread Pawel Jakub Dawidek
On Tue, Aug 25, 2015 at 11:53:47PM +0200, Pawel Jakub Dawidek wrote: On Tue, Aug 25, 2015 at 11:04:37PM +0200, Pawel Jakub Dawidek wrote: On Sun, Aug 23, 2015 at 03:29:01PM -0700, Xin Li wrote: On 8/23/15 14:55, Pawel Jakub Dawidek wrote: I used to build world and kernel on one

Re: Read-only /usr/obj/ no longer kosher?

2015-08-25 Thread Xin Li
On 08/25/15 14:55, Pawel Jakub Dawidek wrote: Now that I think of it, it might have been that I did buildworld/buildkernel before -p1. Then freebsd-update updated newvers.sh and then I was trying to do installworld. Yes, I can now reproduce it with source updated to -p2. Yes, that's because

Re: Read-only /usr/obj/ no longer kosher?

2015-08-25 Thread NGie Cooper
On Tue, Aug 25, 2015 at 3:21 PM, Xin Li delp...@delphij.net wrote: On 08/25/15 14:55, Pawel Jakub Dawidek wrote: Now that I think of it, it might have been that I did buildworld/buildkernel before -p1. Then freebsd-update updated newvers.sh and then I was trying to do installworld. Yes, I

Re: Kernel panic with fresh current, probably nfs related

2015-08-25 Thread Sean Bruno
On 08/25/15 12:10, Joel Dahl wrote: Seems to work. However, I cannot reproduce the user panic in the first place. What's the scenario that seems to work here? NFS seems happy with/without the patch so I'm not confident in anything we are doing her e. I see several patches here. Which

Panic on boot during scan with pmspcv

2015-08-25 Thread Conrad Meyer
For some reason, it only crops up on UEFI boot. Legacy boot just works. It looks like we're locking a mutex in a struct at NULL. (trap) __mtx_assert+0xdb agtiapi_cam_action+0x45 xpt_action_default+0xbe3(?) scsi_scan_bus+0x1cd xpt_scanner_thread+0x15c ... Fault is at 0x18.

Re: Read-only /usr/obj/ no longer kosher?

2015-08-25 Thread Pawel Jakub Dawidek
On Sun, Aug 23, 2015 at 03:29:01PM -0700, Xin Li wrote: On 8/23/15 14:55, Pawel Jakub Dawidek wrote: I used to build world and kernel on one machine and export both /usr/src/ and /usr/obj read-only to other machines. It doesn't work anymore (this is from 'make installworld'):