[Bug 204593] Add a sysctl to enable display of IPv4 ICMP handling in the kernel
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204593 Andrey V. Elsukovchanged: What|Removed |Added CC||a...@freebsd.org --- Comment #1 from Andrey V. Elsukov --- (In reply to Hellmuth Michaelis from comment #0) > Currently it only possible to follow IPv4 ICMP handling in/of the kernel by > recompiling the kernel and adding a define for "ICMPPRINTFS" to enable > kernel console messages for ICMP handling in /usr/src/sys/netinet/ip_icmp.c. You can get the most of these printfs using dtrace fbt probes. To get more, I prefer add ICMP_PROBE() dtrace probe, similar to that we have for IP, UDP and TCP. -- 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 204568] gif(4) interface remembers configuration after being destroyed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204568 cr...@rlwinm.de changed: What|Removed |Added CC||cr...@rlwinm.de --- Comment #2 from cr...@rlwinm.de --- Creating the gif1 interface triggers a LINK_UP event on /dev/devctl and the default devd configuration reacts to this event by running /etc/rc.d/netif start $interface. Please provide the output of `grep gif1 /etc/rc.conf`. -- 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 204340] [panic] nfsd, em, msix, fatal trap 9
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 Kubilay Kocakchanged: What|Removed |Added Flags||mfc-stable9?, mfc-stable10? Keywords||crash -- You are receiving this mail because: You are on the CC list 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 --- Comment #3 from mar...@sugioarto.com --- I want to confirm that the workaround works. Thank you Peter. -- 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 204340] [panic] nfsd, em, msix, fatal trap 9
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 --- Comment #3 from g_amana...@yahoo.com --- (In reply to Rick Macklem from comment #2) Thanks for the insight. However, I just tried the patch proposed and it still crashes. -- You are receiving this mail because: You are on the CC list 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 204602] parse() in boot loader interp_parse.c is too naive about quotes
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204602 Bug ID: 204602 Summary: parse() in boot loader interp_parse.c is too naive about quotes Product: Base System Version: 11.0-CURRENT Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: tso...@me.com Created attachment 163200 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=163200=edit udiff of inter_parse.c current logic how the quotes (both ' and ") are managed is a bit too relaxed, allowing wierd constructs like set name="value' also usual single quote semantics is not possible and, the code does not check if the quoted string actually has ending quote. I'm adding here diff for possible update, which implements: 1. distinguishing single and double quote 2. variable expansion will not be done inside single quote protected area 3. will preserve inner quote for values like "value 'some list'" 4. ending quote check. however, this diff does not implement ending quote order check - it shouldn't be too hard, needs some improvements on parser state machine. -- 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 204568] gif(4) interface remembers configuration after being destroyed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204568 Mark Linimonchanged: 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 204545] Adding quirk entry for some C720p firmware in keyboard module.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204545 Mark Linimonchanged: 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 204602] parse() in boot loader interp_parse.c is too naive about quotes
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204602 Mark Linimonchanged: 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 204593] Add a sysctl to enable display of IPv4 ICMP handling in the kernel
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204593 Mark Linimonchanged: 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 204614] LOR In mpr(4)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204614 --- Comment #1 from p...@nomadlogic.org --- full dmsesg: Copyright (c) 1992-2015 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 11.0-CURRENT #2 r290942: Mon Nov 16 12:01:20 PST 2015 root@srd0013:/usr/obj/usr/src/sys/GENERIC amd64 FreeBSD clang version 3.7.0 (tags/RELEASE_370/final 246257) 20150906 WARNING: WITNESS option enabled, expect reduced performance. VT(efifb): resolution 1024x768 CPU: Intel(R) Xeon(R) CPU E5-2603 v3 @ 1.60GHz (1596.34-MHz K8-class CPU) Origin="GenuineIntel" Id=0x306f2 Family=0x6 Model=0x3f Stepping=2 Features=0xbfebfbffFeatures2=0x7ffefbff AMD Features=0x2c100800 AMD Features2=0x21 Structured Extended Features=0x37ab XSAVE Features=0x1 VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr TSC: P-state invariant, performance statistics real memory = 17179869184 (16384 MB) avail memory = 16436211712 (15674 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 12 CPUs FreeBSD/SMP: 2 package(s) x 6 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 2 cpu2 (AP): APIC ID: 4 cpu3 (AP): APIC ID: 6 cpu4 (AP): APIC ID: 8 cpu5 (AP): APIC ID: 10 cpu6 (AP): APIC ID: 16 cpu7 (AP): APIC ID: 18 cpu8 (AP): APIC ID: 20 cpu9 (AP): APIC ID: 22 cpu10 (AP): APIC ID: 24 cpu11 (AP): APIC ID: 26 random: unblocking device. ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard ioapic2 irqs 48-71 on motherboard random: entropy device external interface kbd0 at kbdmux0 netmap: loaded module module_register_init: MOD_LOAD (vesa, 0x80edc540, 0) error 19 random: registering fast source Intel Secure Key RNG random: fast provider: "Intel Secure Key RNG" cryptosoft0: on motherboard acpi0: on motherboard acpi0: Power Button (fixed) cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 cpu4: on acpi0 cpu5: on acpi0 cpu6: on acpi0 cpu7: on acpi0 cpu8: on acpi0 cpu9: on acpi0 cpu10: on acpi0 cpu11: on acpi0 atrtc0: port 0x70-0x71,0x74-0x77 irq 8 on acpi0 Event timer "RTC" frequency 32768 Hz quality 0 attimer0: port 0x40-0x43,0x50-0x53 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 hpet0: iomem 0xfed0-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 950 Event timer "HPET" frequency 14318180 Hz quality 350 Event timer "HPET1" frequency 14318180 Hz quality 340 Event timer "HPET2" frequency 14318180 Hz quality 340 Event timer "HPET3" frequency 14318180 Hz quality 340 Event timer "HPET4" frequency 14318180 Hz quality 340 Event timer "HPET5" frequency 14318180 Hz quality 340 Event timer "HPET6" frequency 14318180 Hz quality 340 Event timer "HPET7" frequency 14318180 Hz quality 340 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 pcib0: on acpi0 pci0: on pcib0 pcib1: on acpi0 pci1: on pcib1 pcib2: port 0xcf8-0xcff on acpi0 pci2: on pcib2 pcib3: irq 26 at device 1.0 on pci2 pci3: on pcib3 igb0: port 0x6020-0x603f mem 0xc7b8-0xc7bf,0xc7c04000-0xc7c07fff irq 26 at device 0.0 on pci3 igb0: Using MSIX interrupts with 9 vectors igb0: Ethernet address: 2c:60:0c:3c:c3:4b igb0: Bound queue 0 to cpu 0 igb0: Bound queue 1 to cpu 1 igb0: Bound queue 2 to cpu 2 igb0: Bound queue 3 to cpu 3 igb0: Bound queue 4 to cpu 4 igb0: Bound queue 5 to cpu 5 igb0: Bound queue 6 to cpu 6 igb0: Bound queue 7 to cpu 7 igb0: netmap queues/slots: TX 8/1024, RX 8/1024 igb1: port 0x6000-0x601f mem 0xc7a8-0xc7af,0xc7c0-0xc7c03fff irq 28 at device 0.1 on pci3 igb1: Using MSIX interrupts with 9 vectors igb1: Ethernet address: 2c:60:0c:3c:c3:4c igb1: Bound queue 0 to cpu 8 igb1: Bound queue 1 to cpu 9 igb1: Bound queue 2 to cpu 10 igb1: Bound queue 3 to cpu 11 igb1: Bound queue 4 to cpu 0 igb1: Bound queue 5 to cpu 1 igb1: Bound queue 6 to cpu 2 igb1: Bound queue 7 to cpu 3 igb1: netmap queues/slots: TX 8/1024, RX 8/1024 pcib4: irq 32 at device 2.0 on pci2 pci4: on pcib4 pci4: at device 0.0 (no driver attached) pcib5: irq 42 at device 3.0 on pci2 pci5: on pcib5 pcib6: irq 42 at device 3.1 on pci2 pci6: on pcib6 pcib7: irq 42 at device 3.2 on pci2 pci7: on pcib7 mpr0: port 0x5000-0x50ff mem
[Bug 204614] LOR In mpr(4)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204614 Bug ID: 204614 Summary: LOR In mpr(4) Product: Base System Version: 11.0-CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: p...@nomadlogic.org I am seeing the following LOR on 11.0-CURRENT: lock order reversal: 1st 0xf8000d26bc60 CAM device lock (CAM device lock) @ /usr/src/sys/cam/cam_xpt.c:784 2nd 0xfe00012911c0 MPR lock (MPR lock) @ /usr/src/sys/cam/cam_xpt.c:2620 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe04608ec890 witness_checkorder() at witness_checkorder+0xe79/frame 0xfe04608ec910 __mtx_lock_flags() at __mtx_lock_flags+0xa4/frame 0xfe04608ec960 xpt_action_default() at xpt_action_default+0xb6c/frame 0xfe04608ec9b0 scsi_scan_bus() at scsi_scan_bus+0x1d5/frame 0xfe04608eca20 xpt_scanner_thread() at xpt_scanner_thread+0x15c/frame 0xfe04608eca70 fork_exit() at fork_exit+0x84/frame 0xfe04608ecab0 fork_trampoline() at fork_trampoline+0xe/frame 0xfe04608ecab0 --- trap 0, rip = 0, rsp = 0, rbp = 0 --- Here is my system info: [pwright@srd0013 ~]$ uname -ar FreeBSD srd0013 11.0-CURRENT FreeBSD 11.0-CURRENT #2 r290942: Mon Nov 16 12:01:20 PST 2015 root@srd0013:/usr/obj/usr/src/sys/GENERIC amd64 [pwright@srd0013 ~]$ cd /usr/src/ && svn info Path: . Working Copy Root Path: /usr/src URL: https://svn.freebsd.org/base/head Relative URL: ^/head Repository Root: https://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 290942 Node Kind: directory Schedule: normal Last Changed Author: rodrigc Last Changed Rev: 290942 Last Changed Date: 2015-11-16 09:28:04 -0800 (Mon, 16 Nov 2015) I have rebuild kernel+world several times over the past week and can reproduce this. -- 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 204593] Add a sysctl to enable display of IPv4 ICMP handling in the kernel
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204593 Andrey V. Elsukovchanged: 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 204340] [panic] nfsd, em, msix, fatal trap 9
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 Rick Macklemchanged: What|Removed |Added Attachment #163160|0 |1 is obsolete|| --- Comment #4 from Rick Macklem --- Created attachment 163217 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=163217=edit Patch to fix sg_threadcount++ so the mutex is held when done I took a closer look at svc.c and the only way that the race I think might have happened can occur is if svc_run() doesn't wait for all threads to terminate. I also can now see that the first patch wouldn't have fixed anything, so I'm not surprised it didn't work. The only thing I can see that is broken in the code and might allow svc_run() to return before all threads have terminated is: - The thread count sg_threadcount is incremented when the sg_lock mutex isn't held. --> This could conceivably result in a corrupted sg_threadcount, which would allow svc_run() to return before all threads have terminated. This second patch fixes the code so that sg_threadcount++ is always done when the sg_lock mutex is held. If you can test this one instead of the last one, that would be appreciated. I do know this patch fixes the above problem, but I don't know if this is the cause of your crashes. Also, this bug seems to have existed in the code forever and all that r267228 did was switch from not holding the pool mutex to not holding the group mutex. So Alexander, you are off the hook, I think.;-) I've left you on the cc, since you probably know this code better than anyone else and might have some insight w.r.t. this crash. -- You are receiving this mail because: You are on the CC list 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 31981] [libc] [patch] (mis)feature in getnetent parsing -- comments affect parsing results
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=31981 Marcelo Araujochanged: What|Removed |Added CC||ara...@freebsd.org Assignee|freebsd-bugs@FreeBSD.org|ara...@freebsd.org --- Comment #3 from Marcelo Araujo --- I will take 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 204593] Add a sysctl to enable display of IPv4 ICMP handling in the kernel
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204593 Bug ID: 204593 Summary: Add a sysctl to enable display of IPv4 ICMP handling in the kernel Product: Base System Version: 10.2-STABLE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: h...@hellmuth-michaelis.de Created attachment 163185 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=163185=edit 10.2-stable unified diff for /usr/src/sys/netinet/ip_icmp.c Currently it only possible to follow IPv4 ICMP handling in/of the kernel by recompiling the kernel and adding a define for "ICMPPRINTFS" to enable kernel console messages for ICMP handling in /usr/src/sys/netinet/ip_icmp.c. The attached patch converts this into a sysctl variable "net.inet.icmp.log_icmps" to enable/disable debugging output without recompilation. As an add-on, the FIB number is displayed for rx'd/tx'd ICMP packets. -- 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 194766] [drm:pid12:i915_hangcheck_elapsed] [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194766 Ivan Klymenkochanged: What|Removed |Added Severity|Affects Some People |Affects Many People -- 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 194766] [drm:pid12:i915_hangcheck_elapsed] [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194766 m...@netfence.it changed: What|Removed |Added CC||m...@netfence.it --- Comment #32 from m...@netfence.it --- Just a me too... The hardware is an Acer TM-B113: agp0: on vgapci0 agp0: aperture size is 256M, detected 131068k stolen memory info: [drm] Initialized drm 1.1.0 20060810 drmn0: on vgapci0 info: [drm] MSI enabled 1 message(s) info: [drm] AGP at 0xb000 256MB I'm running 10.1/amd64 with: libdrm-2.4.65_1,1 xf86-video-intel-2.21.15_9 xorg-server-1.17.4,1 The hang has started recently (or at least its incidence has increased a lot). There is no day I can work with this laptop without one/two hangs. This is very annoying, so I'm looking for help on one side and offering to do any testing on the other. 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"