[Bug 229682] x11/xterm (possible terminal driver problem): UTF-8 characters cause the misalignment of tabstops
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229682 Emanuel Haupt changed: What|Removed |Added Summary|x11/xterm: UTF-8 characters |x11/xterm (possible |cause the misalignment of |terminal driver problem): |tabstops|UTF-8 characters cause the ||misalignment of tabstops CC||eha...@freebsd.org Version|Latest |CURRENT Assignee|eha...@freebsd.org |b...@freebsd.org Component|Individual Port(s) |kern Severity|Affects Only Me |Affects Many People Product|Ports & Packages|Base System -- 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 229682] x11/xterm (possible terminal driver problem): UTF-8 characters cause the misalignment of tabstops
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229682 --- Comment #9 from Ed Schouten --- This can be attributed to the fact that FreeBSD's TTY layer does not implement termios IUTF8, right? -- 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 229682] x11/xterm (possible terminal driver problem): UTF-8 characters cause the misalignment of tabstops
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229682 --- Comment #10 from dic...@his.com --- iutf8 applies to input characters. The example isn't explicit, but I read it as output behavior. Drake may clarify. -- 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 231143] Ipfw fwd with route(8) RTF_BLACKHOLE and fast forwarding on FreeBSD 11
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231143 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 231143] Ipfw fwd with route(8) RTF_BLACKHOLE and fast forwarding on FreeBSD 11
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231143 Eugene Grosbein changed: What|Removed |Added CC||eu...@freebsd.org Component|misc|kern --- Comment #1 from Eugene Grosbein --- Do you use GENERIC kernel? -- 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 231144] fragmented IPv6 drops
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231144 Bug ID: 231144 Summary: fragmented IPv6 drops Product: Base System Version: 11.2-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: ad...@canmos.net Hello! I have a problem with handling fragmented IPv6 packets. Exactly: - My system is FreeBSD 11.2-RELEASE-p2 with GENERIC kernel - I have configured IPv6-only authoritative DNS server And when the oid net.inet6.ip6.forwarding is set to 1, the system stops to receive fragmented IPv6 packets. If i set net.inet6.ip6.forwarding to 0, the behavior is returning to normal. As i know IPv6 packets MUST NO be fragmented by transit gateways itself. But there is no anything said about incoming packets that are ALREADY fragmented. So could you please help me to solve this issue? For comparesion i tried to reproduce the problem under FreeBSD-10.3. There is no any issues with fragmented IPv6, all the packets were handled by system as well, regardless of meaning net.inet6.ip6.forwarding sysctl. Thank you in advance! -- 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 229745] ahcich: CAM status: Command timeout
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229745 cryx-free...@h3q.com changed: What|Removed |Added CC||cryx-free...@h3q.com --- Comment #10 from cryx-free...@h3q.com --- Affects me too. FreeBSD 11.2-RELEASE on a SuperMicro X11SSL-F with Intel Sunrise Point AHCI SATA controller and HUS722T2TALA604 disks. The vfs.zfs.cache_flush_disable=1 workaround also bypasses the problem after a power-off. -- 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 231144] fragmented IPv6 drops
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231144 Kristof Provost changed: What|Removed |Added CC||k...@freebsd.org --- Comment #1 from Kristof Provost --- I suspect you may be hitting 231045. The fix is in stable/11, and will hopefully get an EN update 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 231144] fragmented IPv6 drops
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231144 --- Comment #2 from Igor --- (In reply to Kristof Provost from comment #1) And as a dirty hack, can i just copy frag6.c from 11/STABLE to RELENG and then recompile the kernel? -- 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 231144] fragmented IPv6 drops
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231144 --- Comment #3 from Kristof Provost --- (In reply to Igor from comment #2) That should work, yes. -- 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 231144] fragmented IPv6 drops
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231144 --- Comment #4 from Igor --- (In reply to Kristof Provost from comment #3) Ok. Thank you very much for your help! -- 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 231151] ifconfig: unable to disable rxcsum, rxcsum6 and vlanhwcsum on em driver
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231151 Bug ID: 231151 Summary: ifconfig: unable to disable rxcsum, rxcsum6 and vlanhwcsum on em driver Product: Base System Version: CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: b...@freebsd.org Reporter: msh...@daemon-security.com In 12-CURRENT, I would like to be able to turn off all NIC offloading features (TSO,LRO,Checksums) to ensure I am reading everything as it appears off the wire for network security (Bro NSM). Putting all of the flags together, this is what I have as the line that should disable all of the features /sbin/ifconfig em0 -rxcsum -txcsum -tso4 -tso6 -lro -rxcsum6 -txcsum6 -vlanhwcsum -vlanhwtso It appears most work with and are enabled and disabled, the exceptions are rxcsum, rxcsum6 and vlanhwcsum. I cannot disable vlanhwcsum at all, and when you disable rxcsum, it enables rxcsum6 and vice versa. Example: # ifconfig em0 em0: flags=28943 metric 0 mtu 1500 options=810099 ether 68:05:ca:xx:xx:xx media: Ethernet autoselect (1000baseT ) status: active nd6 options=29 # ifconfig em0 -rxcsum # ifconfig em0 em0: flags=28943 metric 0 mtu 1500 options=a10098 ether 68:05:ca:xx:xx:xx media: Ethernet autoselect (1000baseT ) status: active nd6 options=29 # ifconfig em0 -rxcsum6 # ifconfig em0 em0: flags=28943 metric 0 mtu 1500 options=810099 ther 68:05:ca:xx:xx:xx media: Ethernet autoselect (1000baseT ) status: active nd6 options=29 I see the same behavior with this driver on two separate cards. em0@pci0:1:0:0: class=0x02 card=0x115e8086 chip=0x105e8086 rev=0x06 hdr=0x00 vendor = 'Intel Corporation' device = '82571EB/82571GB Gigabit Ethernet Controller D0/D1 (copper applications)' class = network subclass = ethernet em0@pci0:0:31:6:class=0x02 card=0x06d91028 chip=0x15b78086 rev=0x31 hdr=0x00 vendor = 'Intel Corporation' device = 'Ethernet Connection (2) I219-LM' class = network subclass = ethernet If this is "by design" in the driver, then this bug can be closed, but I would assume that if you want to disable all receive side offloading, you should be able to disable it for both IPv4 and IPv6. Also, if this is a driver issue (iflib), then I can move the bug to kernel component. -- 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 229745] ahcich: CAM status: Command timeout
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229745 --- Comment #11 from cryx-free...@h3q.com --- (In reply to cryx-freebsd from comment #10) Setting kern.cam.ada.write_cache=0 in loader.conf and doing a power-cycle makes the problem go away, with the obvious hits on IO performance. IHMO this shows that there is indeed a problem with the disks write-cache handling. -- 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 231144] fragmented IPv6 drops
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231144 Mark Linimon 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 231151] ifconfig: unable to disable rxcsum, rxcsum6 and vlanhwcsum on em driver
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231151 Mark Linimon changed: What|Removed |Added CC||sbr...@freebsd.org Keywords||IntelNetworking 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 215143] FreeBSD 11 install cd does not boot on macpro1,1 (32-bit efi)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215143 --- Comment #13 from Jason W. Bacon --- Finally got around to fully testing this. I did a full install with my custom ISO on a MacBook Pro 2,2. I'm using it right now to send this update. I then did a freebsd-update fetch install which updated the kernel and it did not cause any problems. Clearly from previous posts, "freebsd-update upgrade" can render the system unbootable, but I'm not sure what other conditions could cause problems. I don't understand the details of the boot process well enough. Might it be possible to patch the generic ISO to prevent the EFI boot path from being used on 32-bit EFI systems? Is there an easy way to fix an installation following "freebsd-update upgrade"? I'm not so concerned about this one as I prefer to do fresh installs when I upgrade. ( A little OCD about bit rot and keeping my installations pristine. ) -- 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 231101] -flto option breaks the build: Cannot open "/usr/bin/../lib/LLVMgold.so"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231101 --- Comment #1 from Conrad Meyer --- cmake isn't part of base. Should this be retargeted at the port? -- 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 231116] Out of bounds memory access in blist_create()
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231116 Mark Johnston changed: What|Removed |Added Assignee|b...@freebsd.org|ma...@freebsd.org Status|New |In Progress --- Comment #4 from Mark Johnston --- https://reviews.freebsd.org/D17020 -- 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 136159] [kthread] [patch] tsleep with PDROP in kthread_suspend()
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=136159 Ed Maste changed: What|Removed |Added Status|Open|Closed Resolution|--- |Overcome By Events CC||ema...@freebsd.org --- Comment #2 from Ed Maste --- changed to msleep in r202933 -- 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 229682] x11/xterm (possible terminal driver problem): UTF-8 characters cause the misalignment of tabstops
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229682 --- Comment #11 from Keegan Drake H.P. --- (In reply to Ed Schouten from comment #9) This happens because the configuration of x11/xterm in ports relies on FreeBSD's TTY layer to expand tabs, but the TTY layer expands tabs based on the column number which is updated with the byte count and so does not support multi-byte characters. To further clarify: this is about TTY output, and this would not be an issue if FreeBSD's TTY layer supported multi-byte characters or if the port was patched to disable `TAB3' when applicable. -- 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 231166] 11.1->11.2 Update brings em network link state flapping
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231166 Bug ID: 231166 Summary: 11.1->11.2 Update brings em network link state flapping Product: Base System Version: 11.2-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: steven_nik...@ertyu.org Immediately after doing an upgrade from 11.1-release to 11.2-release the network connection using em0 constantly goes up and down. It's driving an Intel 82574 card on PCI-E. I've tried rebooting, power cycling, using different cables, switch ports and a different switch with no change. Prior everything was stable for many moons in the same configuration. Switched to using the onboard Realtek in the system and that is also stable with the same cable/switch. Sep 4 20:37:20 itsirk kernel: em0: link state changed to UP Sep 4 20:37:20 itsirk kernel: em0: link state changed to DOWN Sep 4 20:37:27 itsirk kernel: em0: link state changed to UP Sep 4 20:37:27 itsirk kernel: em0: link state changed to DOWN Sep 4 20:37:31 itsirk kernel: em0: link state changed to UP Sep 4 20:37:31 itsirk kernel: em0: link state changed to DOWN em0: port 0xdf00-0xdf1f mem 0xfdcc-0xfdcd,0xfdc0-0xfdc7,0xfdcfc000-0xfdcf irq 19 at device 0.0 on pci2 em0: Using MSIX interrupts with 3 vectors em0: Ethernet address: 00:1b:21:39:dc:5f em0: netmap queues/slots: TX 1/1024, RX 1/1024 em0@pci0:3:0:0: class=0x02 card=0xa01f8086 chip=0x10d38086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = '82574L Gigabit Network Connection' class = network subclass = ethernet cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit cap 10[e0] = PCI-Express 1 endpoint max data 128(256) RO NS link x1(x1) speed 2.5(2.5) ASPM disabled(L0s/L1) cap 11[a0] = MSI-X supports 5 messages, enabled Table in map 0x1c[0x0], PBA in map 0x1c[0x2000] ecap 0001[100] = AER 1 0 fatal 0 non-fatal 0 corrected ecap 0003[140] = Serial 1 001b2139dc5f -- 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"