[Bug 219935] Kernel panic in getnewvnode (possibly ZFS related)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219935 --- Comment #14 from Andriy Gapon --- (In reply to Raimo Niskanen from comment #13) Maybe there will be another kind of panic from the debug code... Meanwhile, it seems that my original theory about this panic was wrong. Could you please print *mp->mnt_vnodecovered as well? -- 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 219935] Kernel panic in getnewvnode (possibly ZFS related)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219935 Andriy Gapon changed: What|Removed |Added Version|10.3-STABLE |10.3-RELEASE -- 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 219935] Kernel panic in getnewvnode (possibly ZFS related)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219935
--- Comment #15 from Raimo Niskanen ---
(kgdb) p *mp->mnt_vnodecovered
$2 = {
v_tag = 0x80ea8ace "none",
v_op = 0x8148eb18,
v_data = 0x0,
v_mount = 0x0,
v_nmntvnodes = {
tqe_next = 0xf801d028c588,
tqe_prev = 0xf80250a29d08
},
v_un = {
vu_mount = 0x0,
vu_socket = 0x0,
vu_cdev = 0x0,
vu_fifoinfo = 0x0
},
v_hashlist = {
le_next = 0x0,
le_prev = 0xfeb80be0
},
v_cache_src = {
lh_first = 0x0
},
v_cache_dst = {
tqh_first = 0x0,
tqh_last = 0xf8017144e5d8
},
v_cache_dd = 0x0,
v_lock = {
lock_object = {
lo_name = 0x81af1c7b "zfs",
lo_flags = 117112832,
lo_data = 0,
lo_witness = 0x0
},
lk_lock = 1,
lk_exslpfail = 0,
lk_timo = 51,
lk_pri = 96
},
v_interlock = {
lock_object = {
lo_name = 0x80fe4da3 "vnode interlock",
lo_flags = 16973824,
lo_data = 0,
lo_witness = 0x0
},
mtx_lock = 18446735278365454336
},
v_vnlock = 0xf8017144e5f0,
v_actfreelist = {
tqe_next = 0xf801d028c588,
tqe_prev = 0x81623330
},
v_bufobj = {
bo_lock = {
lock_object = {
lo_name = 0x80fe4db3 "bufobj interlock",
lo_flags = 86179840,
lo_data = 0,
lo_witness = 0x0
},
rw_lock = 1
},
bo_ops = 0x814b73e0,
bo_object = 0x0,
bo_synclist = {
le_next = 0x0,
le_prev = 0x0
},
bo_private = 0xf8017144e588,
__bo_vnode = 0xf8017144e588,
bo_clean = {
bv_hd = {
tqh_first = 0x0,
tqh_last = 0xf8017144e6a8
},
bv_root = {
pt_root = 0
},
bv_cnt = 0
},
bo_dirty = {
bv_hd = {
tqh_first = 0x0,
tqh_last = 0xf8017144e6c8
},
bv_root = {
pt_root = 0
},
bv_cnt = 0
},
bo_numoutput = 0,
bo_flag = 0,
bo_bsize = 131072
},
v_pollinfo = 0x0,
v_label = 0x0,
v_lockf = 0x0,
v_rl = {
rl_waiters = {
tqh_first = 0x0,
tqh_last = 0xf8017144e710
},
rl_currdep = 0x0
},
v_cstart = 0,
v_lasta = 0,
v_lastw = 0,
v_clen = 0,
v_holdcnt = 1,
v_usecount = 0,
v_iflag = 0,
v_vflag = 0,
v_writecount = 0,
v_hash = 119749,
v_type = VBAD
}
--
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 191359] [memguard] [panic] Memory modified after free w/MEMGUARD build
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191359 --- Comment #9 from Peter Holm --- (In reply to Siva Mahadevan from comment #8) Hard for me to say it the original panic is still there. With the same scenario I see: panic: MemGuard detected double-free of 0xfe75e000 cpuid = 2 time = 1504166229 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe2ebbde5db0 vpanic() at vpanic+0x19c/frame 0xfe2ebbde5e30 panic() at panic+0x43/frame 0xfe2ebbde5e90 memguard_free() at memguard_free+0x14f/frame 0xfe2ebbde5ed0 bufkva_free() at bufkva_free+0xf8/frame 0xfe2ebbde5ef0 buf_free() at buf_free+0xd5/frame 0xfe2ebbde5f40 brelse() at brelse+0x5c0/frame 0xfe2ebbde5fd0 bufdone_finish() at bufdone_finish+0xd4/frame 0xfe2ebbde5ff0 bufdone() at bufdone+0xe3/frame 0xfe2ebbde6020 biodone() at biodone+0x188/frame 0xfe2ebbde6060 g_io_deliver() at g_io_deliver+0x5e4/frame 0xfe2ebbde6140 biodone() at biodone+0x188/frame 0xfe2ebbde6180 g_io_deliver() at g_io_deliver+0x5e4/frame 0xfe2ebbde6260 biodone() at biodone+0x188/frame 0xfe2ebbde62a0 g_io_deliver() at g_io_deliver+0x5e4/frame 0xfe2ebbde6380 g_disk_done() at g_disk_done+0x1ee/frame 0xfe2ebbde6400 biodone() at biodone+0x188/frame 0xfe2ebbde6440 dadone() at dadone+0x194b/frame 0xfe2ebbde69a0 xpt_done_process() at xpt_done_process+0x35f/frame 0xfe2ebbde69e0 xpt_done_td() at xpt_done_td+0x136/frame 0xfe2ebbde6a30 fork_exit() at fork_exit+0x13b/frame 0xfe2ebbde6ab0 Details @ https://people.freebsd.org/~pho/stress/log/memguard8.txt -- 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 213155] possible kernel regression when running 11.x-RELEASE on KVM on AMD Opterons
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213155 Martin Waschbüsch changed: What|Removed |Added Summary|possible kernel regression |possible kernel regression |when running 11.0-RELEASE |when running 11.x-RELEASE |on KVM on AMD Opterons |on KVM on AMD Opterons -- 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 219935] Kernel panic in getnewvnode (possibly ZFS related)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219935 --- Comment #16 from Andriy Gapon --- (In reply to Raimo Niskanen from comment #15) Okay, I believe that the snapshot problem is already fixed in the newer ZFS code (e.g. in stable/10, 11.1 and FreeBSD 10.4 betas). Let's hope that the other (original) problem can be caught as well. -- 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 219935] Kernel panic in getnewvnode (possibly ZFS related)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219935 --- Comment #17 from Raimo Niskanen --- Does that mean that we now wait for a different panic? Or should I upgrade the server first? -- 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 219935] Kernel panic in getnewvnode (possibly ZFS related)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219935 --- Comment #18 from Andriy Gapon --- (In reply to Raimo Niskanen from comment #17) If you can afford to upgrade the system that would be the best. Please re-apply the debug patch in that case. Otherwise, we would have to wait for a different 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 219935] Kernel panic in getnewvnode (possibly ZFS related)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219935 --- Comment #19 from Raimo Niskanen --- Upgrade to what version? (the shorter the better right now) -- 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 219935] Kernel panic in getnewvnode (possibly ZFS related)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219935 --- Comment #20 from Andriy Gapon --- (In reply to Raimo Niskanen from comment #19) Whichever is more comfortable for you. 11.1 or 10.4 beta aka stable/10. -- 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 219935] Kernel panic in getnewvnode (possibly ZFS related)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219935 --- Comment #21 from Raimo Niskanen --- I do not know how to upgrade to stable/10 or 10.4 beta with freebsd-upgrade... And have locally compiled applications that do not know if I can easily recompile for 11.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 221952] cam iosched: Fix trim statistics
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221952 Bug ID: 221952 Summary: cam iosched: Fix trim statistics Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Keywords: patch Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: f...@fabiankeil.de Flags: mfc-stable11? Created attachment 185944 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=185944&action=edit cam iosched: Fix trim statistics The attached patch fixes the cam iosched trim statistics. When cam_iosched_bio_complete() gets called, all pending BIO_DELETEs are done. Previously only one of them was accounted for, as a result the "pending" counter got higher and higher and the "out" count was off as well. An ElectroBSD release build in a vm resulted in ~60k "leaked" pending trims. cam_iosched_ticker() has a note that seems to refer to this bug but I didn't adjust it. Obtained from: ElectroBSD -- 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 221953] cam iosched: Limit the quanta default to hz if it's below 200
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221953 Bug ID: 221953 Summary: cam iosched: Limit the quanta default to hz if it's below 200 Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Keywords: patch Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: f...@fabiankeil.de Flags: mfc-stable11? Created attachment 185945 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=185945&action=edit cam iosched: Limit the quanta default to hz if it's below 200 The attached patch limits the quanta default to hz if it's below 200 Previously the quanta default was always 200 while hz defaults to 100 when running in a vm. The cam_iosched_ticker() can't be scheduled more than once per tick and some of the limiters depend on quanta matching the number of calls per second to enforce the proper limits. Obtained from: ElectroBSD -- 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 221954] cam iosched: Call cam_iosched_limiter_init() after ios->current is set to the default
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221954 Bug ID: 221954 Summary: cam iosched: Call cam_iosched_limiter_init() after ios->current is set to the default Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Keywords: patch Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: f...@fabiankeil.de Created attachment 185946 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=185946&action=edit cam iosched: Call cam_iosched_limiter_init() after ios->current is set to the default The attached patch lets cam_iosched_iop_stats_init() call cam_iosched_limiter_init() after ios->current is set to the default. Previously ios->current was set to 0 until the first cam_iosched_cl_maybe_steer() call. Obtained from: ElectroBSD -- 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 221956] cam iosched: Schedule cam_iosched_ticker() quanta times per second
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221956 Bug ID: 221956 Summary: cam iosched: Schedule cam_iosched_ticker() quanta times per second Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Keywords: patch Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: f...@fabiankeil.de Flags: mfc-stable11? Created attachment 185947 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=185947&action=edit cam iosched: Schedule cam_iosched_ticker() quanta times per second The attached patch lets cam iosched schedule cam_iosched_ticker() quanta times per second According to callout_reset(9), "[w]hen ticks is used, the callout is scheduled to execute after ticks/hz seconds". It follows that to get quanta calls per second one should specify a tick value of hz / isc->quanta. Previously the value was additionally reduced by one. As a result cam_iosched_ticker() was called more often than requested by the user and expected by some of the limiters. On a system with hz=1000 a quanta value of 200 resulted in 250 calls and a value of 100 in 111 calls. Without the unexplained tick reduction the number of calls matches the quanta value reasonably well. Obtained from: ElectroBSD -- 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 221957] cam iosched: Add a handler for the quanta sysctl to enforce valid values
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221957 Bug ID: 221957 Summary: cam iosched: Add a handler for the quanta sysctl to enforce valid values Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Keywords: patch Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: f...@fabiankeil.de Flags: mfc-stable11? Created attachment 185948 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=185948&action=edit cam iosched: Add a handler for the quanta sysctl to enforce valid values The attached patch adds a handler for the iosched quanta sysctl to enforce valid values Invalid values can result in devision-by-zero panics and other undesirable behaviour. Example panic: Fatal trap 18: integer divide fault while in kernel mode cpuid = 0; apic id = 00 instruction pointer = 0x20:0x802998e5 stack pointer = 0x28:0xfe01ea3bf8d0 frame pointer = 0x28:0xfe01ea3bf900 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 = 12 (swi4: clock (0)) trap number = 18 panic: integer divide fault cpuid = 0 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe01ea3bf510 vpanic() at vpanic+0x186/frame 0xfe01ea3bf590 panic() at panic+0x43/frame 0xfe01ea3bf5f0 trap_fatal() at trap_fatal+0x322/frame 0xfe01ea3bf640 trap() at trap+0x5e/frame 0xfe01ea3bf800 calltrap() at calltrap+0x8/frame 0xfe01ea3bf800 --- trap 0x12, rip = 0x802998e5, rsp = 0xfe01ea3bf8d0, rbp = 0xfe01ea3bf900 --- cam_iosched_ticker() at cam_iosched_ticker+0x25/frame 0xfe01ea3bf900 softclock_call_cc() at softclock_call_cc+0x13e/frame 0xfe01ea3bf9b0 softclock() at softclock+0xb9/frame 0xfe01ea3bf9e0 intr_event_execute_handlers() at intr_event_execute_handlers+0xec/frame 0xfe01ea3bfa20 ithread_loop() at ithread_loop+0xd6/frame 0xfe01ea3bfa70 fork_exit() at fork_exit+0x85/frame 0xfe01ea3bfab0 fork_trampoline() at fork_trampoline+0xe/frame 0xfe01ea3bfab0 --- trap 0, rip = 0, rsp = 0, rbp = 0 --- Uptime: 2h29m20s Dumping 1165 out of 8055 MB:..2%..11%..21%..31%..42%..51%..61%..71%..81%..91% Obtained from: ElectroBSD -- 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 221953] cam iosched: Limit the quanta default to hz if it's below 200
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221953 Conrad Meyer changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org|freebsd-s...@freebsd.org CC||c...@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 221952] cam iosched: Fix trim statistics
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221952 Conrad Meyer changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org|freebsd-s...@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 221954] cam iosched: Call cam_iosched_limiter_init() after ios->current is set to the default
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221954 Conrad Meyer changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org|freebsd-s...@freebsd.org CC||c...@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 221957] cam iosched: Add a handler for the quanta sysctl to enforce valid values
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221957 Conrad Meyer changed: What|Removed |Added CC||c...@freebsd.org Assignee|freebsd-bugs@FreeBSD.org|freebsd-s...@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 221956] cam iosched: Schedule cam_iosched_ticker() quanta times per second
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221956 Conrad Meyer changed: What|Removed |Added CC||c...@freebsd.org Assignee|freebsd-bugs@FreeBSD.org|freebsd-s...@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 221350] Unable to boot/install on HPE Proliant MicroServer Gen10 (AMD Opteron X3000): Hangs/Panics
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350 Thomas Neuber changed: What|Removed |Added CC||th.neu...@gmail.com --- Comment #6 from Thomas Neuber --- At first, I can confirm the behavior as described before. In addition to that: I had a working installation for a HPE Proliant Microserver Gen8 (Intel Xeon E3 v1220L). The old system did not support UEFI. The old installation (SD card copied 1:1 to a USB stick + the 4 hard drives) runs properly on the Gen10 after switching the settings to UEFI with CSM Enabled + Boot Mode Legacy Only - except the console. I expected the console menu after certain amount of time. The console output stops at: pcib0: port 0xcf8-0xcff on acpi0 pcib0: _OSC returned error 0x10 pci0: on pcib0 As I said, everything else works fine. -- 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 221967] ixgbe(4) driver for Intel 82598 chip fails to attach if used 10G-SR SFP+ with message "ix0 attach returned 5"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221967 Bug ID: 221967 Summary: ixgbe(4) driver for Intel 82598 chip fails to attach if used 10G-SR SFP+ with message "ix0 attach returned 5" Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: a...@freebsd.org Created attachment 185963 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=185963&action=edit some debuginfo from ipmi console We have several INTEL-E10G42AFDA cards that worked well with Twinax cable, but driver fails to attach if 10G-SR SFP plugged. The output from patched driver: % pciconf -l | grep 0x0200 ix0@pci0:4:0:0: class=0x02 card=0xa21f8086 chip=0x10f18086 rev=0x01 hdr=0x00 ix1@pci0:4:0:1: class=0x02 card=0xa21f8086 chip=0x10f18086 rev=0x01 hdr=0x00 ix2@pci0:7:0:0: class=0x02 card=0x00038086 chip=0x10fb8086 rev=0x01 hdr=0x00 ix3@pci0:7:0:1: class=0x02 card=0x00038086 chip=0x10fb8086 rev=0x01 hdr=0x00 % grep ^ix /var/run/dmesg.boot ix0: port 0x7020-0x703f mem 0xdf72-0xdf73,0xdf6c-0xdf6f,0xdf744000-0xdf747fff irq 32 at device 0.0 on pci4 ix0: Using MSIX interrupts with 8 vectors ix0: Ethernet address: 00:1b:21:6c:e1:8f ix0: PCI Express Bus: Speed 2.5GT/s Width x8 ix0: netmap queues/slots: TX 7/2048, RX 7/2048 ix1: port 0x7000-0x701f mem 0xdf70-0xdf71,0xdf64-0xdf67,0xdf74-0xdf743fff irq 36 at device 0.1 on pci4 ix1: Using MSIX interrupts with 8 vectors ix1: Ethernet address: 00:1b:21:6c:e1:8e ix1: PCI Express Bus: Speed 2.5GT/s Width x8 ix1: netmap queues/slots: TX 7/2048, RX 7/2048 ix2: port 0x6020-0x603f mem 0xde68-0xde6f,0xde704000-0xde707fff irq 42 at device 0.0 on pci7 ix2: Using MSIX interrupts with 8 vectors ix2: Ethernet address: 90:e2:ba:2b:52:ac ix2: PCI Express Bus: Speed 5.0GT/s Width x8 ix2: netmap queues/slots: TX 7/2048, RX 7/2048 ix3: port 0x6000-0x601f mem 0xde60-0xde67,0xde70-0xde703fff irq 45 at device 0.1 on pci7 ix3: Using MSIX interrupts with 8 vectors ix3: Ethernet address: 90:e2:ba:2b:52:ad ix3: PCI Express Bus: Speed 5.0GT/s Width x8 ix3: netmap queues/slots: TX 7/2048, RX 7/2048 ix0: link state changed to UP ix2: link state changed to UP ix3: link state changed to UP ix1: link state changed to UP All cards use the same SFP modules plugged: SFP/SFP+/SFP28 10G Base-SR (LC) vendor: Upnet PN: SFP+-10G-SR SN: SB3A680013 DATE: 2011-03-14 but 82598 card fails to attach it with message: ix0: Unsupported SFP+ Module device_attach: ix0 attach returned 5 I did some debugging to determine where the driver fails. The fail is in ixgbe_get_sfp_init_sequence_offsets() function. As I understand, there should be some values correspoinding to sfp_type, but in the table only one value, that doesn't match. I modifed the driver that it thinks that SFP module has ixgbe_sfp_type_da_cu type, and after that it successful attached and works, but of course an information about SFP is unavailable: % ifconfig -v ix0 ix0: flags=8843 metric 0 mtu 9000 options=8100bb ether 00:1b:21:6c:e1:8f inet6 fe80::21b:21ff:fe6c:e18f%ix0 prefixlen 64 scopeid 0x3 nd6 options=21 media: Ethernet autoselect (10Gbase-Twinax ) status: active Also there is another version of patch, that seems solves the same issue, but I didn't test it. http://www.grosbein.net/freebsd/patches/patch-if_ix.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 221967] ixgbe(4) driver for Intel 82598 chip fails to attach if used 10G-SR SFP+ with message "ix0 attach returned 5"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221967 Andrey V. Elsukov changed: What|Removed |Added 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 221967] ixgbe(4) driver for Intel 82598 chip fails to attach if used 10G-SR SFP+ with message "ix0 attach returned 5"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221967 --- Comment #1 from Andrey V. Elsukov --- Created attachment 185964 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=185964&action=edit used 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 221967] ixgbe(4) driver for Intel 82598 chip fails to attach if used 10G-SR SFP+ with message "ix0 attach returned 5"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221967 --- Comment #2 from Andrey V. Elsukov --- Forgot to mention, in the loader.conf we have these tunables set, and this doesn't help: hw.ixgbe.unsupported_sfp="1" hw.ix.unsupported_sfp="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 213137] boot2 too large when using gcc-4.6 or later
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213137 Ryan Libby changed: What|Removed |Added Resolution|--- |FIXED CC||rli...@freebsd.org Assignee|freebsd-bugs@FreeBSD.org|rli...@freebsd.org Status|New |Closed --- Comment #4 from Ryan Libby --- I fixed this in r322329 while getting the amd64-gcc (gcc 6.3.0) build working, but didn't know about this PR at the time. The fix was essentially the same as the proposed patch (attachment 175328). https://svnweb.freebsd.org/base?view=revision&revision=322329 -- 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 218206] boot2 fails to compile with xtoolchain-amd64-gcc 6.3.0: negative space left
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218206 Ryan Libby changed: What|Removed |Added CC||rli...@freebsd.org Resolution|--- |DUPLICATE Status|New |Closed --- Comment #8 from Ryan Libby --- *** This bug has been marked as a duplicate of bug 213137 *** -- 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 210413] vidcontrol -c does not work with vt(4)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210413 Ed Maste changed: What|Removed |Added Status|New |In Progress -- 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 210415] vidcontrol -h does not work with vt(4)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210415 Ed Maste changed: What|Removed |Added Status|New |In Progress -- 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 198863] [patch] geli: TRIM passthru
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198863 Ed Maste changed: What|Removed |Added Status|New |In Progress -- 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 201052] capsicum: propagate rights on sctp_peeloff
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201052 Ed Maste changed: What|Removed |Added Summary|capsicum: propagate rights |capsicum: propagate rights |on accept / sctp_peeloff|on sctp_peeloff -- 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 221970] Feature request: Compile -RELEASE with WITH_HESIOD=true
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221970 Bug ID: 221970 Summary: Feature request: Compile -RELEASE with WITH_HESIOD=true Product: Base System Version: 11.1-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: rich...@unixboxen.net I have ~10 FreeBSD 11 servers which I have compiled WITH_HESIOD=true and maintain updated from source. I am shortly planning to installing another 30 or so the same way. I would _greatly_ appreciate it if -RELEASE could be compiled WITH_HESIOD=true so I could avoid doing this for much longer. Additionally, the man pages for nsswitch.conf indicate that it will work out of the box, but doesn't unless you build base with WITH_HESIOD=true. Pretty please :) I'm happy to facilitate this in whatever way possible. -- 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 199075] mtree -F freebsd9 not consistent with fmtree
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199075 Ed Maste changed: What|Removed |Added CC||bro...@freebsd.org, ||ema...@freebsd.org --- Comment #1 from Ed Maste --- Brooks, as someone who's looked at mtree a fair bit, any comment? -- 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 192971] [PATCH]Some utilies might lead to overflow
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192971 Ed Maste changed: What|Removed |Added Status|New |In Progress -- 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"
