[Bug 202968] Add support for Huawei ME909u LET modem
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202968 Bug ID: 202968 Summary: Add support for Huawei ME909u LET modem Product: Base System Version: 10.2-STABLE Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: free...@sb-soft.net u3g patch for Huawei ME909u LTE modem. I have pulled my change to Github. https://github.com/freebsd/freebsd/pull/45 -- 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 201461] vt(4) VT Switching drops into blank screen after X closes on NVIDIA
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201461 Edward Tomasz Napierala changed: What|Removed |Added CC||tr...@freebsd.org --- Comment #3 from Edward Tomasz Napierala --- Does it happen only with vt(4), or also when running with sc(4) driver instead? -- 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 173454] [patch] service(8) does not respect /etc/rc.conf.d/name
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=173454 Allan Jude changed: What|Removed |Added CC||allanj...@freebsd.org Assignee|freebsd-bugs@FreeBSD.org|allanj...@freebsd.org -- 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 201461] vt(4) VT Switching drops into blank screen after X closes on NVIDIA
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201461 --- Comment #4 from Tony Narlock --- (In reply to Edward Tomasz Napierala from comment #3) How do I switch to sc(4)? What do I run to detect if I'm running vt(4) or sc(4) -- 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 161401] [patch] have service(8) run scripts with the same resource limits as init(8)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=161401 Allan Jude changed: What|Removed |Added CC||allanj...@freebsd.org Assignee|freebsd-bugs@FreeBSD.org|allanj...@freebsd.org -- 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 161028] [PATCH] service(8) -- Minor improvements
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=161028 Allan Jude changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org|allanj...@freebsd.org CC||allanj...@freebsd.org -- 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 201461] vt(4) VT Switching drops into blank screen after X closes on NVIDIA
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201461 --- Comment #5 from Ed Maste --- (In reply to Tony Narlock from comment #4) > How do I switch to sc(4)? You can add kern.vty=sc to /boot/loader.conf, or set it from the loader prompt. > What do I run to detect if I'm running vt(4) or sc(4) sysctl kern.vty will show you: % sysctl kern.vty kern.vty: vt -- 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 201461] vt(4) VT Switching drops into blank screen after X closes on NVIDIA
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201461 --- Comment #6 from Tony Narlock --- (In reply to Ed Maste from comment #5) Hi again Ed, Ok, I updated /boot/loader.conf and sc(4) is loading. # sysctl kern.vty kern.vy: sc So, I get a black screen again with sc(4). Just like with vt(4) I do notice I can go back to X fine with I switch between (F1, F2... back to the console X is on). I haven't tried doing this with vt, but I'll go back and report my progress. Another note: earlier I was using 10.1 RELEASE. I am producing the same behavior on 11-CURRENT. $ freebsd-version -ku; uname -apKU 11.0-CURRENT 11.0-CURRENT FreeBSD z600 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r286893: Tue Aug 18 18:44:28 UTC 2015 r...@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 amd64 1100079 1100079 -- 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 201461] vt(4) VT Switching drops into blank screen after X closes on NVIDIA
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201461 --- Comment #7 from Tony Narlock --- (In reply to Tony Narlock from comment #6) To follow up - I rebooted back into vt(4) and confirm I get the same behavior on sc(4). I get a black screen. I can (blindly) enter keyboard commands. For instance, if I were to exit out of X, I could restart X by typing into the keyboard (startxfce4, startx, service slim start). If I keep X open and go to Ctrl-Alt-F1F8, It will black screen. Alt-F9 brings me back into X. -- 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 202307] panic: ARM64TODO: pmap_mincore from lib/libc/sys/mincore_test:mincore_err test
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202307 --- Comment #2 from commit-h...@freebsd.org --- A commit references this bug: Author: andrew Date: Tue Sep 8 18:41:07 UTC 2015 New revision: 287570 URL: https://svnweb.freebsd.org/changeset/base/287570 Log: Add support for pmap_mincore on arm64 by walking the page tables to find the details for the requested address. PR:202307 Obtained from:ABT Systems Ltd Sponsored by:The FreeBSD Foundation Changes: head/sys/arm64/arm64/pmap.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 202307] panic: ARM64TODO: pmap_mincore from lib/libc/sys/mincore_test:mincore_err test
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202307 --- Comment #3 from commit-h...@freebsd.org --- A commit references this bug: Author: andrew Date: Tue Sep 8 18:44:13 UTC 2015 New revision: 287571 URL: https://svnweb.freebsd.org/changeset/base/287571 Log: Enable mincore_test on arm64, we now have a working pmap_mincore. PR:202307 Obtained from:ABT Systems Ltd Sponsored by:The FreeBSD Foundation Changes: head/lib/libc/tests/sys/Makefile -- 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 202978] After upgrade of net/syncthing 0.11.18 -> 0.11.23 in jail, the jail causes entire host to crash
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202978 Bug ID: 202978 Summary: After upgrade of net/syncthing 0.11.18 -> 0.11.23 in jail, the jail causes entire host to crash Product: Base System Version: 10.1-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: nikl...@kulturflatrate.net Created attachment 160845 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=160845&action=edit /var/log/messages of the jail and its host with comments In reference to the thread related to this issue in freebsd-questi...@freebsd.org, see http://docs.freebsd.org/cgi/getmsg.cgi?fetch=130033+0+current/freebsd-questions. After upgrading a package (net/syncthing) in a jail I experienced that the host system rebooted. It seems because the jail starts at each boot running net/syncthing again, the host system rebooted each time it started the jail. A vicious circle. Because of this, I was nearly unable to connect to the server. By continuously pinging the server and sending a ssh ezjail-admin config -r norun once I knew the server is online again, I could stop the circle and finally log into the server again. I guess that something's wrong with net/syncthing (or its configuration) but what worries me more is how a userspace program in a malfunctioning jail can cause an entire host system to reboot? (Please also see the discussion in the mailinglist.) The upgrade of net/syncthing was 0.11.18 -> 0.11.23 $ uname -a FreeBSD tank. 10.1-RELEASE-p19 FreeBSD 10.1-RELEASE-p19 #0: Sat Aug 22 03:55:09 UTC 2015 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 I am able to reproduce the behaviour by simply starting the jail. Shortly after that the system crashes. This made it possible for me to get some coredumps: $ ls -hl /var/crash total 11552056 -rw-r--r-- 1 root wheel 2B Sep 8 21:15 bounds -rw--- 1 root wheel 357K Sep 8 21:09 core.txt.0 -rw--- 1 root wheel 176K Sep 8 21:12 core.txt.1 -rw--- 1 root wheel 193K Sep 8 21:16 core.txt.2 -rw--- 1 root wheel 502B Sep 8 21:08 info.0 -rw--- 1 root wheel 502B Sep 8 21:11 info.1 -rw--- 1 root wheel 501B Sep 8 21:15 info.2 lrwxr-xr-x 1 root wheel 6B Sep 8 21:15 info.last -> info.2 -rw-r--r-- 1 root wheel 5B Jan 16 2014 minfree -rw--- 1 root wheel 2.0G Sep 8 21:09 vmcore.0 -rw--- 1 root wheel 1.9G Sep 8 21:12 vmcore.1 -rw--- 1 root wheel 1.9G Sep 8 21:15 vmcore.2 lrwxr-xr-x 1 root wheel 8B Sep 8 21:15 vmcore.last -> vmcore.2 Please find attached `/var/log/messages` of the jail and its host. These are extracted from the very first failure. I have also a backup of `/var/log/messages` of the crash that I just "forced" this evening. I can also share the coredumps but would need some advice on how to do so without disclosing sensitive information. -- 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 202978] After upgrade of net/syncthing 0.11.18 -> 0.11.23 in jail, the jail causes entire host to crash
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202978 Peter Wemm changed: What|Removed |Added CC||pe...@freebsd.org --- Comment #1 from Peter Wemm --- syncthing does something strange with its use of local ipv6 multicast and crashes the kernel when it exits. This is definitely a kernel bug - userland apps should not be able to crash the kernel, even if they are doing something odd. In the meantime, you can work around it by DISABLING local announce. If you can't do it through the UI, you can do it by editing the config.xml while syncthing is not running. Normally it is in ~/.config/syncthing/config.xml but you can configure it to be elsewhere. change: true to false When you next start up syncthing, it won't do the weird thing with this line: [ff32::5222]:21026 .. which is causing the kernel panic. -- 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 201913] Kernel panic during stopping syncthing daemon
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201913 Peter Wemm changed: What|Removed |Added CC||pe...@freebsd.org --- Comment #2 from Peter Wemm --- FWIW; duplicate of bug #202978 There is a workaround there; the problem is 'local announce' is triggering an ipv6 multicast kernel bug. -- 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 202978] After upgrade of net/syncthing 0.11.18 -> 0.11.23 in jail, the jail causes entire host to crash
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202978 --- Comment #2 from Peter Wemm --- There's a panic trace in bug #201913 -- 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 202978] After upgrade of net/syncthing 0.11.18 -> 0.11.23 in jail, the jail causes entire host to crash
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202978 --- Comment #3 from Peter Wemm --- There's several upstream bugs, but this one has discussion of using the wrong address: https://github.com/syncthing/syncthing/issues/2090 There's a few others.. if you search the issues list for multicast, you'll see that you can also delete the contents of and leave localannounce enabled - that limits syncthing local announce on ipv4, and as a side effect to one daemon per machine - and it can't run like that in a jail anyway as jails can't bind to interface broadcast addresses. Anyway, I'm mentioning it here because it is possible to do limited ipv4 local announce if you need it. -- 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 148581] [libc] fopen(3) fails with EMFILE if there are more than SHORT_MAX fds open
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=148581 Karl Young changed: What|Removed |Added CC||free...@kipshouse.org --- Comment #3 from Karl Young --- We've run into this on 9.2. We're using OpenSource software that uses popen() to run external commands. Since popen() returns FILE*, it fails when we get to 32K open files. This seems to be rarely hit (no comments since 2011), but it can be a show-stopper. The only workaround I see in our case is to roll our own popen(). BTW in comment 1: > with a 32-bit file descriptor field. If the file descriptor exceeds 32767, > the 16-bit > field then contains -1 and fileno() in old binaries will return > that. I think this fails when FD gets to 64K and the short version starts counting up from 0 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 202968] Add support for Huawei ME909u LET modem
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202968 Mark Linimon changed: What|Removed |Added Component|kern|usb Assignee|freebsd-bugs@FreeBSD.org|freebsd-...@freebsd.org 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 202960] Kernel panic when bridging e1000 NIC with pf rules
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202960 Mark Linimon changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org|freebsd-...@freebsd.org Keywords||IntelNetworking -- 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 202983] ixv driver in 11.0-CURRENT(10.1 & 10.2 RELEASE) doesn't pass traffic using XEN hypervisor(AWS EC2)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202983 Bug ID: 202983 Summary: ixv driver in 11.0-CURRENT(10.1 & 10.2 RELEASE) doesn't pass traffic using XEN hypervisor(AWS EC2) Product: Base System Version: 11.0-CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: jlp...@gmail.com Created attachment 160852 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=160852&action=edit 10.2 dmesg Similar problem to Bug 202875 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202875 Only the Hypervisor host is Xen+Qemu/EC2 I have ready access to AWS for testing of a guest ixv(Xen DomU) http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html. The driver detects the hardware correctly and sets everything up. But DHCP fails as there is no received packets(created guest packet capture in rc.d) from the the host Dom0. Unfortunately I can't check the host system with a packet capture as this is a IaaS platform. But on the upside you can be pretty much be guaranteed the host is setup fine for the guest as Linux/Windows work fine. I have spoken with both Colin Percival, Jack Vogel(Intel), George Neville-Neil and Jeffrey Pieper about this previously but never filed a bug for it. https://lists.freebsd.org/pipermail/freebsd-xen/2014-May/002114.html The last I heard on this was that it wass suspected to be a Xen+Qemu issue since KVM was working. However it seems more likely to be a that different host drivers as incompatible with certain guest drivers(based on below) and the fact KVM also has a bug report now(Bug 202875)? -- > Since KVM works and Xen does not, this is basically a qemu issue. I'll > cut and paste my original findings: > > All, > > I was able to reproduce the failure Colin was seeing on SRIOV with Xen > and FreeBSD 9.2/ixgbe-2.5.15. I used SLES11-SP3 w/ Xen. I could not > acquire a dhcp license and nor could I pass traffic through the VF > with > a manually assigned IP address. I tested this with the driver both > compiled in and out of the kernel. The interesting point is that the > exact same configuration works on RHEL 6.5 KVM. > > The good news, however is that FreeBSD 10.0/ixgbe-2.5.18 DOES work, > with > the driver compiled both in and out of the kernel. I am able to > acquire > a dhcp license at boot as well as pass traffic with a manually > assigned > IP address. Another interesting data point is that with both > 9.2/ixgbe-2.5.18 and 10.0/2.5.18 both running in VMs and each > assigned a > VF belonging to the same PF, 10.0/ixgbe-2.5.18 did not work either. > > I also attempted to use our out-of-tree ixgbe-2.5.18 on 9.2, but I get > SIOCGIF: ix0 no such device errors when attempting to acquire a dhcp > address or even assign an address manually. > > > Jeff -- -- 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 202983] ixv driver in 11.0-CURRENT(10.1 & 10.2 RELEASE) doesn't pass traffic using XEN hypervisor(AWS EC2)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202983 Mark Linimon changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org|freebsd-...@freebsd.org -- 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 202978] After upgrade of net/syncthing 0.11.18 -> 0.11.23 in jail, the jail causes entire host to crash
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202978 --- Comment #4 from Niklaas Baudet von Gersdorff --- Thank you for the workaround. It works. In case you need further information to debug please don't hesitate to contact me. -- 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"
