[Bug 224496] mpr and mps drivers seems to have issues with large seagate drives
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224496 Matthias Pfaller changed: What|Removed |Added CC||matthias.pfaller@familie-pf ||aller.de --- Comment #3 from Matthias Pfaller --- Created attachment 205003 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=205003&action=edit /var/log/messages during device resets -- 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 224496] mpr and mps drivers seems to have issues with large seagate drives
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224496 --- Comment #4 from Matthias Pfaller --- We just did configure a backup server with eight seagate ironwulf (ST12000VN0007-2GS116) 12TB disks connected to a SAS2008: Jun 12 08:51:35 nyx kernel: mps0: port 0x8000-0x80ff mem 0xdf70-0xdf703fff,0xdf68-0xdf6b irq 32 at device 0.0 on pci3 Jun 12 08:51:35 nyx kernel: mps0: Firmware: 20.00.07.00, Driver: 21.02.00.00-fbsd Jun 12 08:51:35 nyx kernel: mps0: IOCCapabilities: 185c After writing ~200gb to our pool it started reseting. I did a sysctl dev.mps.0.debug_level=0x$((0x1+0x2+0x4+0x10+0x20)) The resulting trace is attached. -- 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 224496] mpr and mps drivers seems to have issues with large seagate drives
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224496 --- Comment #5 from Matthias Pfaller --- Comment on attachment 205003 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=205003 /var/log/messages during device resets We just did configure a backup server with eight seagate ironwulf (ST12000VN0007-2GS116) 12TB disks connected to a SAS2008: Jun 12 08:51:35 nyx kernel: mps0: port 0x8000-0x80ff mem 0xdf70-0xdf703fff,0xdf68-0xdf6b irq 32 at device 0.0 on pci3 Jun 12 08:51:35 nyx kernel: mps0: Firmware: 20.00.07.00, Driver: 21.02.00.00-fbsd Jun 12 08:51:35 nyx kernel: mps0: IOCCapabilities: 185c After writing ~200gb to our pool it started reseting. I did a sysctl dev.mps.0.debug_level=0x$((0x1+0x2+0x4+0x10+0x20)) The resulting trace is attached. -- 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 224496] mpr and mps drivers seems to have issues with large seagate drives
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224496 --- Comment #6 from Matthias Pfaller --- We are using FreeBSD 12.0-RELEASE: FreeBSD nyx 12.0-RELEASE-p4 FreeBSD 12.0-RELEASE-p4 GENERIC amd64 -- 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 224496] mpr and mps drivers seems to have issues with large seagate drives
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224496 --- Comment #7 from Bane Ivosev --- Just to append my previous post from March, same hardware and same config, we revert back on 11.1-RELEASE and everything working flawlessly for more then two months 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 238514] Adding -flto into compilation/link lines causes the error: /usr/bin/ld: unrecognized option '-plugin'
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238514 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|toolch...@freebsd.org Summary|[toolchain] Adding -flto|Adding -flto into |into compilation/link lines |compilation/link lines |causes the error: |causes the error: |/usr/bin/ld: unrecognized |/usr/bin/ld: unrecognized |option '-plugin'|option '-plugin' --- Comment #1 from Mark Linimon --- Assign to toolchain@, and thus, remove the now-redundant tag. -- 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 238511] [regression] after D18038 usr.bin/strings
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238511 Mariusz Zaborski changed: What|Removed |Added Assignee|b...@freebsd.org|osho...@freebsd.org CC||osho...@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 238517] jail.conf Mount option does not unmount Filesystem on Jail stop anymore
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238517 Bug ID: 238517 Summary: jail.conf Mount option does not unmount Filesystem on Jail stop anymore Product: Base System Version: 12.0-STABLE Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: bin Assignee: b...@freebsd.org Reporter: matthias+freebsd+bugzi...@harz.de I use "Mount" in Jail.conf to Mount the jail root dynamicaly. Up to STABLE 11.2 then mounted filesystem was unmounted on Jail stop. After update to STABLE-12.0 the unmount does not happen anymore. -- 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 224496] mpr and mps drivers seems to have issues with large seagate drives
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224496 --- Comment #8 from Bane Ivosev --- And I don't think the problem is exclusively with Seagate 10TB drives. We have WD Red 4TB drives and have the same problem. We have same situation also with 11.2-RELEASE, and beacuse 11.2 and 12.0 have same mpr/mps driver version we decide to try with 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 224496] mpr and mps drivers seems to have issues with large seagate drives
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224496 --- Comment #9 from Matthias Pfaller --- (In reply to Bane Ivosev from comment #8) We have several other machines with SAS2008 controllers. All of them are running 11.1 and none of them shows these problems... -- 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 238518] make buildkernel fails due to a symlink (and/or zfs)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238518 Bug ID: 238518 Summary: make buildkernel fails due to a symlink (and/or zfs) Product: Base System Version: 12.0-STABLE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: phascolarc...@protonmail.ch Created attachment 205004 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=205004&action=edit log of make buildkernel Here is the setting: - a ZFS filesystem zroot/usr/src-stable is mounted at /usr/src and contains sources for 12-STABLE r348980; - a ZFS filesystem /zroot/usr/obj/usr/src-stable is mounted at /usr/obj/usr/src-stable; - the file /usr/obj/usr/src is a symlink to /usr/obj/usr/src-stable. make buildkernel fails with the error message reported in the attachement. It might be useful to know that this setting is the result of the following old setting: - a ZFS filesystem zroot/usr/src-stable is mounted at /usr/src-stable and contains sources for 12-STABLE, whatever revision; - a ZFS filesystem /zroot/usr/obj/usr/src-stable is mounted at /usr/obj/usr/src-stable. Getting back to the old setting solves the problem, but of course we should try to get the new setting to work too. Moreover, using the old setting, if a softlink /usr/src to /usr/src-stable is created, I can execute make buildkernel successfully both from /usr/src and /usr/src-stable. If I execute it from /usr/src, I can read lines such as "Building /usr/obj/usr/src-stable..." -- 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 231445] [patch] sleepq_catch_signals will still enter sleep after a ptrace attach event
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231445 --- Comment #5 from commit-h...@freebsd.org --- A commit references this bug: Author: kib Date: Wed Jun 12 11:09:34 UTC 2019 New revision: 348988 URL: https://svnweb.freebsd.org/changeset/base/348988 Log: MFC r348360: Do not go into sleep in sleepq_catch_signals() when SIGSTOP from PT_ATTACH was consumed. PR: 231445 Changes: _U stable/12/ stable/12/sys/kern/kern_sig.c stable/12/sys/kern/subr_sleepqueue.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 238517] jail.conf Mount option does not unmount Filesystem on Jail stop anymore
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238517 Mark Linimon changed: What|Removed |Added Keywords||regression Assignee|b...@freebsd.org|j...@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 238520] [sctp] Fatal trap 9: general protection fault while in kernel mode
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238520 Bug ID: 238520 Summary: [sctp] Fatal trap 9: general protection fault while in kernel mode Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Keywords: panic, stress2 Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: p...@freebsd.org CC: n...@freebsd.org 20190612 11:51:26 all (1/1): sctp.sh Fatal trap 9: general protection fault while in kernel mode cpuid = 0; apic id = 00 instruction pointer = 0x20:0x80ba77a8 stack pointer = 0x28:0xfe00ae6275f0 frame pointer = 0x28:0xfe00ae627670 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 = 69451 (server) trap number = 9 panic: general protection fault cpuid = 2 time = 1560333091 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe00ae627300 vpanic() at vpanic+0x19d/frame 0xfe00ae627350 panic() at panic+0x43/frame 0xfe00ae6273b0 trap_fatal() at trap_fatal+0x39c/frame 0xfe00ae627410 trap() at trap+0x6c/frame 0xfe00ae627520 calltrap() at calltrap+0x8/frame 0xfe00ae627520 --- trap 0x9, rip = 0x80ba77a8, rsp = 0xfe00ae6275f0, rbp = 0xfe00ae627670 --- __mtx_lock_sleep() at __mtx_lock_sleep+0xf8/frame 0xfe00ae627670 __mtx_lock_flags() at __mtx_lock_flags+0xee/frame 0xfe00ae6276c0 sctp_accept() at sctp_accept+0xa6e/frame 0xfe00ae627840 soaccept() at soaccept+0x174/frame 0xfe00ae627890 kern_accept4() at kern_accept4+0x26e/frame 0xfe00ae627930 accept1() at accept1+0xe8/frame 0xfe00ae627990 amd64_syscall() at amd64_syscall+0x291/frame 0xfe00ae627ab0 fast_syscall_common() at fast_syscall_common+0x101/frame 0xfe00ae627ab0 Details @ https://people.freebsd.org/~pho/stress/log/sctp.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 238520] [sctp] Fatal trap 9: general protection fault while in kernel mode
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238520 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 237937] Removing path with mpr and geom_multipath causes kernel panic
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237937 harri...@glsan.com changed: What|Removed |Added CC||harri...@glsan.com --- Comment #5 from harri...@glsan.com --- This bug is also found if bad devices are on the bus. Here is message output when then bug is hit. Jun 12 03:33:59 pavo kernel: (da106:mps1:0:120:0): Retrying command, 14 more tries remain Jun 12 03:33:59 pavo kernel: (da106:mps1:0:120:0): WRITE(16). CDB: 8a 00 00 00 00 03 a8 54 56 58 00 00 00 20 00 00 Jun 12 03:33:59 pavo kernel: (da106:mps1:0:120:0): CAM status: CCB request completed with an error Jun 12 03:33:59 pavo kernel: (da106:mps1:0:120:0): Retrying command, 14 more tries remain Jun 12 03:33:59 pavo kernel: (da106:mps1:0:120:0): WRITE(16). CDB: 8a 00 00 00 00 03 a8 54 55 68 00 00 00 18 00 00 Jun 12 03:33:59 pavo kernel: Finished recovery after LUN reset for target 120 Jun 12 03:33:59 pavo kernel: mps1: More commands to abort for target 120 Jun 12 03:33:59 pavo kernel: Jun 12 03:33:59 pavo syslogd: last message repeated 1 times Jun 12 03:33:59 pavo kernel: Fatal trap 12: page fault while in kernel mode Jun 12 03:33:59 pavo kernel: cpuid = 10; apic id = 0a Jun 12 03:33:59 pavo kernel: fault virtual address = 0x0 Jun 12 03:33:59 pavo kernel: fault code = supervisor read data, page not present Jun 12 03:33:59 pavo kernel: instruction pointer= 0x20:0x806f8421 Jun 12 03:33:59 pavo kernel: stack pointer = 0x28:0xfe00bab8f900 Jun 12 03:33:59 pavo kernel: frame pointer = 0x28:0xfe00bab8f940 Jun 12 03:33:59 pavo kernel: code segment = base 0x0, limit 0xf, type 0x1b Jun 12 03:33:59 pavo kernel:= DPL 0, pres 1, long 1, def32 0, gran 1 Jun 12 03:33:59 pavo kernel: (da106:mps1:0:120:0): CAM status: CCB request completed with an error Jun 12 03:33:59 pavo kernel: (da106:mps1:0:120:0): Retrying command, 14 more tries remain Jun 12 03:33:59 pavo kernel: (da106:mps1:0:120:0): WRITE(16). CDB: 8a 00 00 00 00 03 a8 54 56 08 00 00 00 20 00 00 Jun 12 03:33:59 pavo kernel: (da106:mps1:0:120:0): CAM status: CCB request completed with an error Jun 12 03:33:59 pavo kernel: (da106:mps1:0:120:0): Retrying command, 14 more tries remain Jun 12 03:33:59 pavo kernel: (da106:mps1:0:120:0): WRITE(16). CDB: 8a 00 00 00 00 03 a8 54 55 d8 00 00 00 18 00 00 Jun 12 04:09:48 pavo syslogd: kernel boot file is /boot/kernel/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 238526] praudit using lots of swap/memory
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238526 Bug ID: 238526 Summary: praudit using lots of swap/memory Product: Base System Version: 12.0-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: b...@freebsd.org Reporter: in...@incin.me I have some new Dell servers on FreeBSD 12.0-RELEASE that are hungry for swap and memory. It seems like the praudit process just keeps growing in size and doesn't stop. Servers do a similar task but are physically the same. ServerA: uptime 5:15PM up 4 days, 22:29, 2 users, load averages: 0.86, 2.29, 2.84 CPU: 1.4% user, 0.0% nice, 1.2% system, 0.0% interrupt, 97.4% idle Mem: 286M Active, 56G Inact, 6884M Laundry, 27G Wired, 1506M Buf, 2838M Free ARC: 3887M Total, 256M MFU, 3388M MRU, 15M Anon, 37M Header, 191M Other 3120M Compressed, 10G Uncompressed, 3.20:1 Ratio Swap: 16G Total, 1264M Used, 15G Free, 7% Inuse 97831 root 1 200 7547M 6606M audit_ 15 18:43 0.00% praudit 12.0-RELEASE-p3 This server had to be rebooted the other day since it ran out of swap space and crashed. ServerB: uptime 5:18PM up 42 days, 3:19, 2 users, load averages: 2.12, 1.90, 1.85 CPU: 3.7% user, 0.0% nice, 3.0% system, 0.0% interrupt, 93.4% idle Mem: 2829M Active, 37G Inact, 17G Laundry, 34G Wired, 1552M Buf, 2180M Free ARC: 11G Total, 2290M MFU, 8669M MRU, 89M Anon, 66M Header, 248M Other 8299M Compressed, 20G Uncompressed, 2.43:1 Ratio Swap: 16G Total, 16G Used, 4944K Free, 99% Inuse 84360 root 1 20032G16G audit_ 24 58:26 0.07% praudit 12.0-RELEASE-p3 Thank you. -- 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 238526] praudit using lots of swap/memory
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238526 Laszlo Danielisz changed: What|Removed |Added CC||laci...@gmail.com --- Comment #1 from Laszlo Danielisz --- I'm also interested in solving 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 229745] ahcich: CAM status: Command timeout
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229745 --- Comment #25 from d...@jetcafe.org --- (In reply to Allan Jude from comment #24) Did you find a suitable workaround? -- 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 #26 from Alexey --- it works for me since august 2018 with vfs.zfs.cache_flush_disable=1 w/o reboots and disk timeouts. -- 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 #27 from d...@jetcafe.org --- (In reply to Alexey from comment #26) I have another more drastic workaround that works. In /boot/device.hints I placed the following lines: hint.ahcich.0.sata_rev=2 hint.ahcich.1.sata_rev=2 hint.ahcich.2.sata_rev=2 ...etc... This slows down the SATA bus which isn't desirable either, but better than timeouts and controller drops. -- 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"
