[Bug 233022] [em][netmap] 12-BETA2 can not finish netmap transmission
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233022 Bug ID: 233022 Summary: [em][netmap] 12-BETA2 can not finish netmap transmission Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: l...@freebsd.org netmap's pkt-gen can not finish transmission of configured number of packaets on I219-V (em0) at 12-BETA2. It stucks with non-flushed queue forever: 236.545902 main_thread [2605] 0 pps (0 pkts 0 bps in 1031501 usec) 0.00 avg_batch 9 min_space 237.00 sender_body [1687] pending tx tail 446 head 448 on ring 0 237.07 sender_body [1687] pending tx tail 446 head 448 on ring 0 237.11 sender_body [1687] pending tx tail 446 head 448 on ring 0 237.16 sender_body [1687] pending tx tail 446 head 448 on ring 0 237.20 sender_body [1687] pending tx tail 446 head 448 on ring 0 237.607508 main_thread [2605] 0 pps (0 pkts 0 bps in 1061606 usec) 0.00 avg_batch 9 min_space 238.00 sender_body [1687] pending tx tail 446 head 448 on ring 0 238.05 sender_body [1687] pending tx tail 446 head 448 on ring 0 238.09 sender_body [1687] pending tx tail 446 head 448 on ring 0 238.13 sender_body [1687] pending tx tail 446 head 448 on ring 0 238.17 sender_body [1687] pending tx tail 446 head 448 on ring 0 -- 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 233022] [em][netmap] 12-BETA2 can not finish netmap transmission
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233022 Lev A. Serebryakov changed: What|Removed |Added Assignee|b...@freebsd.org|n...@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 11294] [patch] logger(1) direct logging to other hosts
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=11294 Eugene Grosbein changed: What|Removed |Added Resolution|--- |Feedback Timeout Status|Open|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 35568] make(1) declares target out of date, but $? is empty
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=35568 Eugene Grosbein changed: What|Removed |Added Status|Open|Closed Resolution|--- |Feedback Timeout -- 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 71469] default route to internet magically disappears with multihomed server
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=71469 Eugene Grosbein changed: What|Removed |Added Resolution|--- |Feedback Timeout Status|Open|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 75873] Usability problem with non-RFC-compliant IP spoof protection implementation
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=75873 Eugene Grosbein changed: What|Removed |Added Resolution|--- |Feedback Timeout Status|Open|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 76398] [libc] stdio can lose data in the presence of signals
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=76398 Eugene Grosbein changed: What|Removed |Added Status|In Progress |Closed Resolution|--- |Feedback Timeout -- 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 151264] bsnmpd(1): pf counters aren't updated on some SNMP queries
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=151264 Eugene Grosbein changed: What|Removed |Added Resolution|--- |Feedback Timeout Status|Open|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 219918] [patch] LibAlias: implement RFC 4787 REQ 1 and 3 (full cone NAT)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219918 Eugene Grosbein changed: What|Removed |Added Assignee|b...@freebsd.org|n...@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 233031] Better support for danish keyboard layout
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233031 Bug ID: 233031 Summary: Better support for danish keyboard layout Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: misc Assignee: b...@freebsd.org Reporter: scootergri...@gmail.com I am trying to get better support for danish keyboard layout in TTY (or whatever its called, not X11). In kbdmod i see 3 danish keyboard layouts to choose from (dk.kbd, dk.acc.kbd, dk.macbook.kbd). But they don't seem to work correctly. I'm not sure how much is the keyboard layout and how much is the characters not being in the font or whatever the problem is. The following is tested with "dk.acc.kbd". If i create a file in vi and type æøåÆØÅé it shows: \xc3\xa6\xc3\xb8\xc3\xa5\xc3\x86\xc3\x98\xc3\x85\xc3\xa9 If i save the file and do cat filename it shows: æøåÆ?Åé If i open it in ee it shows: æøå~F~X~Eé In the terminal (TTY): I can only write accent keys (dead keys) like ´ and ¨ alone. I can not combine them with another keys so i can not write éóëöêôèò etc. Also i can not write æøåÆØÅ with any of the 3 danish keyboard layouts. Nothing is written if i type æøåÆØÅ. Testing FreeBSD-13.0-CURRENT-amd64.vhd (r339979)in VirtualBox. -- 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 232975] periodic: missing script 130.clean-msgs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232975 rozhuk...@gmail.com changed: What|Removed |Added Status|New |Closed Resolution|--- |Works As Intended --- Comment #3 from rozhuk...@gmail.com --- Sorry for noise, in /etc/src.conf set WITHOUT_MAIL= and file removed on world update. -- 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 233038] bhyve: fails with "device emulation initialization error: Bad file descriptor"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233038 Bug ID: 233038 Summary: bhyve: fails with "device emulation initialization error: Bad file descriptor" Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: bin Assignee: b...@freebsd.org Reporter: jwm...@gmail.com After updating to r340179+755e0ab1085 I was unable to start my windows vm with a fbuf device. e.g -s 7,fbuf,tcp=127.0.0.1:5900,w=1024,h=768 Output: getaddrinfo: hostname nor servname provided, or not known device emulation initialization error: Bad file descriptor after doing a little debugging; It looks as though bhyve is passing in freed pointers in the arguments to to rfb_init due to the change in base r340044 removing the added free in pci_fbuf.c, fixed the issue for 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"
[Bug 232675] Regression of dtrace on 13-CURRENT
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232675 Mark Johnston changed: What|Removed |Added Assignee|b...@freebsd.org|ma...@freebsd.org Status|New |In Progress --- Comment #16 from Mark Johnston --- (In reply to Dimitry Andric from comment #15) With this commit I see many more duplicate type definitions than before. This seems to be a bug in ctfmerge; if I merge all object files at once, the problem occurs, but if I incrementally merge one object at a time, it does not. -- 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 233038] bhyve: fails with "device emulation initialization error: Bad file descriptor"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233038 --- Comment #1 from Wes Maag --- (In reply to Wes Maag from comment #0) Hm, looks as though my revision was off by one should be base r340045 -- 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 197256] [PATCH] ip6(4): missing IPV6_RECVHOPLIMIT and other RFC3542 API documentation
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197256 Oleksandr Tymoshenko changed: What|Removed |Added Assignee|d...@freebsd.org |b...@freebsd.org CC||d...@freebsd.org Component|Documentation |Manual Pages guy...@gmail.com changed: What|Removed |Added Attachment #152458|0 |1 is obsolete|| --- Comment #2 from guy...@gmail.com --- Comment on attachment 152458 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=152458 ip6(4) update from OpenBSD marked old attached patch as obsolete patches in github rebased after r339985 For reference, the openbsd changes can be seen here: http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/share/man/man4/ip6.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 232483] loader crashes on "lsdev" command
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232483 --- Comment #4 from Lev A. Serebryakov --- gpart show => 63 30031187 da0 MBR (14G) 63 1 - free - (512B) 64 10602321 freebsd (518M) 1060296 10602322 freebsd [active] (518M) 2120528 163843 freebsd (8.0M) 2136912 83886084 freebsd (4.0G) 10525520 19505730 - free - (9.3G) => 0 1060232 da0s1 BSD (518M) 0 16 - free - (8.0K) 16 1060216 1 !0 (518M) => 0 1060232 da0s2 BSD (518M) 0 16 - free - (8.0K) 16 1060216 1 !0 (518M) lsdev -v crashes after showing 3 partitions (slices) too, with exactly same message. I've tried /boot/loader (which is loader_lua), /boot/loader_4th and /boot/loader_simp, results are exactly the same, with and without "-v" flag to lsdev. All three crashes at same place with same message (6 crashes in total). Now I'm running 13.0-CURRENT r340152, but as far as I can see, nothing has been changed in this area beteween new 12 branch and head. I could build loaded with any additional custom diagnostics, if it is needed. And, BTW, here is my /boot/loader.conf: # We don't have writeable / FS entropy_cache_load="NO" beastie_disable="YES" autoboot_delay="3" # Use serial #boot_serial="YES" #boot_multicons="YES" #console="comconsole,vidconsole" #comconsole_speed="115200" kern.geom.label.disk_ident.enable=0 dumpdev="/dev/da0s4" net.link.ifqmaxlen=16384 net.isr.maxthreads=2 net.isr.numthreads=2 net.isr.dispatch="direct" net.graph.maxdata=4096 hw.em.max_interrupt_rate=32000 hint.acpi_throttle.0.disabled=1 hint.acpi_throttle.1.disabled=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 195882] Local DoS from unprivileged user
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195882 --- Comment #10 from Mark Millard --- (In reply to rozhuk.im from comment #8) One difference in my test context and yours appears to be that I'm not using any encryption layer but the .eli in: /dev/gptid/0714a812-b98e-11e8-a831-7085c2375722.eli suggests that you are using geli-based encryption. My context is basic, simple UFS. In my context the I/O is fairly low latency and fairly high rate (an SSD). So, for example, the fsync activity does not last long. I have no experience with such issues for geli encryption and have no clue how your I/O subsystem latency and bandwidth might compare. I'm also probably less likely to see the file system try to allocate memory during its attempt to fsync or otherwise write out dirty RAM pages (making them clean). All of this may make it harder for me to replicate the behavior that you would see for the same test program run the same way but in your context. -- 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 211713] NVME controller failure: resetting (Samsung SM961 SSD Drives)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211713 David changed: What|Removed |Added CC||mentalbarc...@fastest.cc --- Comment #67 from David --- Created attachment 199031 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=199031&action=edit dmesg output -- 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 211713] NVME controller failure: resetting (Samsung SM961 SSD Drives)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211713 --- Comment #68 from David --- I'm testing FreeBSD 12.0-BETA3 r340039 GENERIC, and I have an PM961 PCIe NVMe m.2 1TB drive that came with my Lenovo ThinkPad P50. P/N: MZSLW1T0HMLH-000L1 Produced Oct 2016 That drive is recognized by FreeBSD 12, but is not usable whatsoever (can't read/write to it). I've used this drive with Debian testing since 2016 without trouble on my ThinkPad P50. I installed FreeBSD 12 on an internal 2TB HDD in the ThinkPad in order to test FreeBSD, but the PM961 continued to cause boot delays -- I would see "nvme0: Missing interrupt" messages until the system finally gave up and continued with the boot process. I attempted to install FreeBSD 11 on the 2TB HDD but the install failed when it had trouble recognizing the nvme drive. Initially I thought the missing interrupt problem with FreeBSD was caused by the LUKS encryption on the nvme drive because I had not formatted that drive yet since I was dual booting. So I purchased another Samsung NVMe SSD 960 PRO m.2 1TB drive P/N: MZVKP1T0HMJP, and that drive works with FreeBSD 12. The new nvme was installed in the ThinkPad along with the original nvme and HDD drive. The 2TB HDD and the new 1TB nvme drives are dedicated to FreeBSD using ZFS. I attempted to create a ZFS mirror using the two nvme drives and FreeBSD successfully wrote to the original nvme drive (because it overwrote my Linux partitions) but the overall `zfs_create_diskpart` process failed and I had to start over using only the new nvme drive, which worked. I eventually removed the original nvme drive from my laptop because of the constant "missing interrupt" delays. However, after removing the original nmve drive and while installing a virtual machine in VirtualBox on my new nvme, my laptop went into (what seemed to be) ACPI S3 suspended mode, and after I woke the machine the laptop rebooted itself. Thinking the problem was VirtualBox, I removed that software and setup Bhyve instead. During a virtual machine install in Bhyve, the laptop went into an S3-style suspended mode again, and this time when I woke the machine I noticed the nvme0 resetting controller, write, read, and aborted-by-request messages in `dmesg` (output attached above). For the most part, the new nvme device seems stable with FreeBSD 12. I haven't test it with FreeBSD 11. I don't know if KDE's baloo service crashing and creating a 256GB core dump every single time I login is part of the problem using this drive. Today I disabled Baloo file indexing and installed another virtual machine using Bhyve and the system hasn't reported any problems with the nvme. I also used `dd` to create some 10GB and 100GB files using input from /dev/urandom, and that didn't cause any issues so far. Lastly, cold boots on the new nvme (without the old nvme installed in the laptop) are normal. However, reboots can take literally 2 minutes to complete. This includes an extended delay on the BIOS screen before reaching the GELI password prompt, and a delay after loading the kernel before moving on to the ---<>--- screen, and the entire boot process is sluggish until finally reaching the login prompt. I've never experienced this with Debian testing and I suspect the FreeBSD nvme driver is leaving the system in a weird state. IIRC setting hw.nvme.enable_aborts=1 while the original nvme drive is still in the laptop causes a kernel panic while booting. I haven't tried setting hw.nvme.per_cpu_io_queues=0 since the system is usable and not completely instable. Hardware details: # nvmecontrol devlist nvme0: SAMSUNG MZSLW1T0HMLH-000L1 nvme0ns1 (976762MB) nvme1: Samsung SSD 960 PRO 1TB nvme1ns1 (976762MB) # pciconf -lbace nvme0 nvme0@pci0:2:0:0: class=0x010802 card=0xa801144d chip=0xa804144d rev=0x00 hdr=0x00 bar [10] = type Memory, range 64, base 0xd440, size 16384, enabled cap 01[40] = powerspec 3 supports D0 D3 current D0 cap 05[50] = MSI supports 32 messages, 64 bit cap 10[70] = PCI-Express 2 endpoint max data 256(256) FLR RO NS link x4(x4) speed 8.0(8.0) ASPM L1(L1) cap 11[b0] = MSI-X supports 33 messages, enabled Table in map 0x10[0x3000], PBA in map 0x10[0x2000] ecap 0001[100] = AER 2 0 fatal 0 non-fatal 1 corrected ecap 0003[148] = Serial 1 ecap 0004[158] = Power Budgeting 1 ecap 0019[168] = PCIe Sec 1 lane errors 0 ecap 0018[188] = LTR 1 ecap 001e[190] = unknown 1 PCI-e errors = Correctable Error Detected Unsupported Request Detected Corrected = Advisory Non-Fatal Error # pciconf -lbace nvme1 nvme1@pci0:62:0:0: class=0x010802 card=0xa801144d chip=0xa804144d rev=0x00 hdr=0x00 bar [10] = type Memory, range 64, base 0xd420, size 16384, enabled cap 01[40] = powerspec 3 supports D0 D3 current D0 cap 05[50] = MSI supports 32 messages, 64 bit cap 10[70] = PCI-Express 2 endpoint max data 2
[Bug 195882] Local DoS from unprivileged user
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195882 --- Comment #11 from Mark Millard --- (In reply to Mark Johnston from comment #5) Thanks for that note. The caching status after unmap and after close and after process deletion has helped clear out bad assumptions of mine, including just what top's Active, Inact, and Buf mean in various contexts. My assumptions were tied to the observed behavior of the limited range of my typical workloads. -- 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 233038] bhyve: fails with "device emulation initialization error: Bad file descriptor"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233038 Mark Johnston changed: What|Removed |Added CC||ara...@freebsd.org, ||ma...@freebsd.org --- Comment #2 from Mark Johnston --- Indeed, r340045 is bogus. Either the assignments to rfb_host and rfb_password should be strdup()ing the value, or the commit should simply be reverted. -- 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 233046] tools/build/mk/OptionalObsoleteFiles.inc: clean rc.d and periodic files
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233046 Bug ID: 233046 Summary: tools/build/mk/OptionalObsoleteFiles.inc: clean rc.d and periodic files Product: Base System Version: 11.2-STABLE Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: conf Assignee: b...@freebsd.org Reporter: rozhuk...@gmail.com Created attachment 199032 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=199032&action=edit patch After set some WITHOUT_ options in /etc/src.conf some csripts not deleted, but files that should rum from this scripts is deleted. Clean unneded files. -- 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 233046] tools/build/mk/OptionalObsoleteFiles.inc: clean rc.d and periodic files
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233046 rozhuk...@gmail.com changed: What|Removed |Added Blocks||227984 CC||rozhuk...@gmail.com Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227984 [Bug 227984] WITHOUT_AUDIT does not function as expected -- 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 227984] WITHOUT_AUDIT does not function as expected
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227984 rozhuk...@gmail.com changed: What|Removed |Added Depends on||233046 Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233046 [Bug 233046] tools/build/mk/OptionalObsoleteFiles.inc: clean rc.d and periodic files -- 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 232978] /etc/rc.d/ntpdate - not removed with ntp
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232978 rozhuk...@gmail.com changed: What|Removed |Added Depends on||233046 Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233046 [Bug 233046] tools/build/mk/OptionalObsoleteFiles.inc: clean rc.d and periodic files -- 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 233046] tools/build/mk/OptionalObsoleteFiles.inc: clean rc.d and periodic files
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233046 rozhuk...@gmail.com changed: What|Removed |Added Blocks||232978 Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232978 [Bug 232978] /etc/rc.d/ntpdate - not removed with ntp -- 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 233046] [PATCH] tools/build/mk/OptionalObsoleteFiles.inc: clean rc.d and periodic files
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233046 rozhuk...@gmail.com changed: What|Removed |Added Summary|tools/build/mk/OptionalObso |[PATCH] |leteFiles.inc: clean rc.d |tools/build/mk/OptionalObso |and periodic files |leteFiles.inc: clean rc.d ||and periodic files -- 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 231296] smartpqi - and/or ZFS - related kernel panics
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231296 --- Comment #16 from rai...@ultra-secure.de --- OK, as soon as some load is on the system (in this case, 10mbit UDP syslog traffic, it panics again. supervisor write data, page not present. How do I install and activate the debug-kernel from the kernel-dbg.txz archive? -- 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 231296] smartpqi - and/or ZFS - related kernel panics
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231296 --- Comment #17 from Mark Johnston --- (In reply to rainer from comment #16) kernel-dbg just contains kernel symbols. If you crash a kernel and get a vmcore in /var/crash, then the symbols can be used to examine the vmcore. The kernel-dbg set needs to match the kernel from the corresponding kernel.txz archive. -- 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 231296] smartpqi - and/or ZFS - related kernel panics
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231296 --- Comment #18 from rai...@ultra-secure.de --- log02-prod ) 0 # kgdb /boot/kernel/kernel /var/crash/vmcore.last GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"... Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode cpuid = 2; apic id = 02 fault virtual address = 0x0 fault code = supervisor write data, page not present instruction pointer = 0x20:0x80aacfae stack pointer = 0x28:0xfe103c5e8f60 frame pointer = 0x28:0xfe103c5e9130 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 87490 (syslog-ng) trap number = 12 panic: page fault cpuid = 2 KDB: stack backtrace: #0 0x80b3d587 at kdb_backtrace+0x67 #1 0x80af6b27 at vpanic+0x177 #2 0x80af69a3 at panic+0x43 #3 0x80f77fdf at trap_fatal+0x35f #4 0x80f78039 at trap_pfault+0x49 #5 0x80f77807 at trap+0x2c7 #6 0x80f57fbc at calltrap+0x8 #7 0x80aac905 at kern_kevent+0xb5 #8 0x80aac794 at sys_kevent+0xa4 #9 0x80f79068 at amd64_syscall+0xa38 #10 0x80f5880d at fast_syscall_common+0x101 Uptime: 45m56s Dumping 2959 out of 65147 MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91% Reading symbols from /boot/kernel/geom_mirror.ko...Reading symbols from /usr/lib/debug//boot/kernel/geom_mirror.ko.debug...done. done. Loaded symbols for /boot/kernel/geom_mirror.ko Reading symbols from /boot/kernel/zfs.ko...Reading symbols from /usr/lib/debug//boot/kernel/zfs.ko.debug...done. done. Loaded symbols for /boot/kernel/zfs.ko Reading symbols from /boot/kernel/opensolaris.ko...Reading symbols from /usr/lib/debug//boot/kernel/opensolaris.ko.debug...done. done. Loaded symbols for /boot/kernel/opensolaris.ko Reading symbols from /boot/kernel/accf_data.ko...Reading symbols from /usr/lib/debug//boot/kernel/accf_data.ko.debug...done. done. Loaded symbols for /boot/kernel/accf_data.ko Reading symbols from /boot/kernel/accf_http.ko...Reading symbols from /usr/lib/debug//boot/kernel/accf_http.ko.debug...done. done. Loaded symbols for /boot/kernel/accf_http.ko Reading symbols from /boot/kernel/cc_htcp.ko...Reading symbols from /usr/lib/debug//boot/kernel/cc_htcp.ko.debug...done. done. Loaded symbols for /boot/kernel/cc_htcp.ko Reading symbols from /boot/kernel/tmpfs.ko...Reading symbols from /usr/lib/debug//boot/kernel/tmpfs.ko.debug...done. done. Loaded symbols for /boot/kernel/tmpfs.ko #0 doadump (textdump=) at pcpu.h:229 229 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt #0 doadump (textdump=) at pcpu.h:229 #1 0x80af673b in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:383 #2 0x80af6b61 in vpanic (fmt=, ap=) at /usr/src/sys/kern/kern_shutdown.c:776 #3 0x80af69a3 in panic (fmt=) at /usr/src/sys/kern/kern_shutdown.c:707 #4 0x80f77fdf in trap_fatal (frame=0xfe103c5e8ea0, eva=0) at /usr/src/sys/amd64/amd64/trap.c:875 #5 0x80f78039 in trap_pfault (frame=0xfe103c5e8ea0, usermode=0) at pcpu.h:229 #6 0x80f77807 in trap (frame=0xfe103c5e8ea0) at /usr/src/sys/amd64/amd64/trap.c:415 #7 0x80f57fbc in calltrap () at /usr/src/sys/amd64/amd64/exception.S:231 #8 0x80aacfae in kqueue_kevent (kq=0xf801cb5a4a00, td=0xf801e3b34000, nchanges=, nevents=1, k_ops=0xfe103c5e91c0, timeout=0xfe10) at /usr/src/sys/kern/kern_event.c:1623 #9 0x80aac905 in kern_kevent (td=0xf801e3b34000, fd=, nchanges=0, nevents=1, k_ops=0xfe103c5e91c0, timeout=0xfe103c5e91b0) at /usr/src/sys/kern/kern_event.c:1023 #10 0x80aac794 in sys_kevent (td=0xf801e3b34000, uap=0xf801e3b34538) at /usr/src/sys/kern/kern_event.c:901 #11 0x80f79068 in amd64_syscall (td=0xf801e3b34000, traced=0) at subr_syscall.c:132 #12 0x80f5880d in fast_syscall_common () at /usr/src/sys/amd64/amd64/exception.S:479 #13 0x00080222b81a in ?? () Previous frame inner to this frame (corrupt stack?) Current language: auto; currently minimal (kgdb) -- 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 231296] smartpqi - and/or ZFS - related kernel panics
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231296 --- Comment #19 from rai...@ultra-secure.de --- It had only booted a couple of minutes at that point. I had rm -rf'ed /var/db/freebsd-update/* in order to update the debug-symbols to the current kernel-level. And bang, it panic'ed again. This is really weird. But shows that most of my systems aren't really stressed at all, apparently. -- 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 231296] smartpqi - and/or ZFS - related kernel panics
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231296 --- Comment #20 from Mark Johnston --- Hmm, this seems to be unrelated to ZFS - it's a panic in kevent(). Would you be willing to share the vmcore with me so that I can try and find the bug? Please mail me if so. -- 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 233038] bhyve: fails with "device emulation initialization error: Bad file descriptor"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233038 --- Comment #3 from commit-h...@freebsd.org --- A commit references this bug: Author: araujo Date: Wed Nov 7 04:20:29 UTC 2018 New revision: 340210 URL: https://svnweb.freebsd.org/changeset/base/340210 Log: Revert my bogus attempt to silence coverity on r340045, it created more bad side effects than good. PR: 233038 Submitted by: We Maag Changes: head/usr.sbin/bhyve/pci_fbuf.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 233038] bhyve: fails with "device emulation initialization error: Bad file descriptor"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233038 Marcelo Araujo changed: What|Removed |Added Resolution|--- |FIXED Status|New |Closed --- Comment #4 from Marcelo Araujo --- Thank you all and sorry the breakage!!! I have reverted the commit till I figure out a better way to fix the Coverity issue. Best, -- 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"
