Re: Lock order reversal errors during boot
I see this LOR often too. I thought maybe this is happening because of my Virtual Box setting :) (?!?) On 5/21/16, Will Brokenbourgh wrote: > On 05/16/16 00:44, Bjoern A. Zeeb wrote: >>> On 15 May 2016, at 07:44 , Kurt Jaeger wrote: >>> >>> Hi! >>> >>>> I am seeing 'lock order reversal' errors during boot on 11-CURRENT - >>>> r298793. A sample error: >>>> >>>> lock order reversal: >>>> 1st 0xf8011280d068 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2498 >>>> 2nd 0xfe01ca539400 bufwait (bufwait) @ >>>> /usr/src/sys/ufs/ffs/ffs_vnops.c:263 >>>> 3rd 0xf80112a23b78 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2498 >>>> stack backtrace: >>>> #0 0x80a94bf0 at witness_debugger+0x70 >>>> #1 0x80a94ae4 at witness_checkorder+0xe54 >>>> #2 0x80a0fdd6 at __lockmgr_args+0x4d6 >>>> #3 0x80ce9626 at ffs_lock+0xa6 >>>> [...snip...] >>>> >>>> I'm not sure if this is even something I should report, but better safe >>>> than sorry, yes? >>> Yes, and there's even a page to compare your LOR against other ones: >>> >>> http://sources.zabbadoz.net/freebsd/lor.html >>> >>> Can you try if you find your LOR there ? If not, can you add it >>> to that page ? >> No he can’t and I haven’t in years either. Searching bugs might however >> be a good idea; there is a LOR category or tag somewhere. >> >> /bz > Thank you for the replies. > > I'm getting these LORs pretty frequently. Is this a normal occurrence > for 11-CURRENT or is it only me having this problem? > > Thanks > > Will Brokenbourgh > > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Lock order reversal errors during boot
On 05/16/16 00:44, Bjoern A. Zeeb wrote: On 15 May 2016, at 07:44 , Kurt Jaeger wrote: Hi! I am seeing 'lock order reversal' errors during boot on 11-CURRENT - r298793. A sample error: lock order reversal: 1st 0xf8011280d068 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2498 2nd 0xfe01ca539400 bufwait (bufwait) @ /usr/src/sys/ufs/ffs/ffs_vnops.c:263 3rd 0xf80112a23b78 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2498 stack backtrace: #0 0x80a94bf0 at witness_debugger+0x70 #1 0x80a94ae4 at witness_checkorder+0xe54 #2 0x80a0fdd6 at __lockmgr_args+0x4d6 #3 0x80ce9626 at ffs_lock+0xa6 [...snip...] I'm not sure if this is even something I should report, but better safe than sorry, yes? Yes, and there's even a page to compare your LOR against other ones: http://sources.zabbadoz.net/freebsd/lor.html Can you try if you find your LOR there ? If not, can you add it to that page ? No he can’t and I haven’t in years either. Searching bugs might however be a good idea; there is a LOR category or tag somewhere. /bz Thank you for the replies. I'm getting these LORs pretty frequently. Is this a normal occurrence for 11-CURRENT or is it only me having this problem? Thanks Will Brokenbourgh ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Lock order reversal errors during boot
> On 15 May 2016, at 07:44 , Kurt Jaeger wrote: > > Hi! > >> I am seeing 'lock order reversal' errors during boot on 11-CURRENT - >> r298793. A sample error: >> >> lock order reversal: >> 1st 0xf8011280d068 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2498 >> 2nd 0xfe01ca539400 bufwait (bufwait) @ >> /usr/src/sys/ufs/ffs/ffs_vnops.c:263 >> 3rd 0xf80112a23b78 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2498 >> stack backtrace: >> #0 0x80a94bf0 at witness_debugger+0x70 >> #1 0x80a94ae4 at witness_checkorder+0xe54 >> #2 0x80a0fdd6 at __lockmgr_args+0x4d6 >> #3 0x80ce9626 at ffs_lock+0xa6 >> [...snip...] >> >> I'm not sure if this is even something I should report, but better safe >> than sorry, yes? > > Yes, and there's even a page to compare your LOR against other ones: > > http://sources.zabbadoz.net/freebsd/lor.html > > Can you try if you find your LOR there ? If not, can you add it > to that page ? No he can’t and I haven’t in years either. Searching bugs might however be a good idea; there is a LOR category or tag somewhere. /bz ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Lock order reversal errors during boot
Hi! > I am seeing 'lock order reversal' errors during boot on 11-CURRENT - > r298793. A sample error: > > lock order reversal: > 1st 0xf8011280d068 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2498 > 2nd 0xfe01ca539400 bufwait (bufwait) @ > /usr/src/sys/ufs/ffs/ffs_vnops.c:263 > 3rd 0xf80112a23b78 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2498 > stack backtrace: > #0 0x80a94bf0 at witness_debugger+0x70 > #1 0x80a94ae4 at witness_checkorder+0xe54 > #2 0x80a0fdd6 at __lockmgr_args+0x4d6 > #3 0x80ce9626 at ffs_lock+0xa6 > [...snip...] > > I'm not sure if this is even something I should report, but better safe > than sorry, yes? Yes, and there's even a page to compare your LOR against other ones: http://sources.zabbadoz.net/freebsd/lor.html Can you try if you find your LOR there ? If not, can you add it to that page ? -- p...@opsec.eu+49 171 3101372 4 years to go ! ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Lock order reversal errors during boot
Greetings, My first post here so please be gentle. I am seeing 'lock order reversal' errors during boot on 11-CURRENT - r298793. A sample error: lock order reversal: 1st 0xf8011280d068 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2498 2nd 0xfe01ca539400 bufwait (bufwait) @ /usr/src/sys/ufs/ffs/ffs_vnops.c:263 3rd 0xf80112a23b78 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2498 stack backtrace: #0 0x80a94bf0 at witness_debugger+0x70 #1 0x80a94ae4 at witness_checkorder+0xe54 #2 0x80a0fdd6 at __lockmgr_args+0x4d6 #3 0x80ce9626 at ffs_lock+0xa6 [...snip...] I'm not sure if this is even something I should report, but better safe than sorry, yes? I'm attaching the full dmesg for more information. Sincerely, Will Brokenbourgh Copyright (c) 1992-2016 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 #0 r298793: Fri Apr 29 20:48:00 UTC 2016 r...@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 FreeBSD clang version 3.8.0 (tags/RELEASE_380/final 262564) (based on LLVM 3.8.0) WARNING: WITNESS option enabled, expect reduced performance. VT(vga): resolution 640x480 CPU: Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz (3300.06-MHz K8-class CPU) Origin="GenuineIntel" Id=0x306c3 Family=0x6 Model=0x3c Stepping=3 Features=0xbfebfbff Features2=0x7ffafbff AMD Features=0x2c100800 AMD Features2=0x21 Structured Extended Features=0x27ab XSAVE Features=0x1 VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID TSC: P-state invariant, performance statistics real memory = 8589934592 (8192 MB) avail memory = 7625789440 (7272 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) random: unblocking device. ioapic0 irqs 0-23 on motherboard random: entropy device external interface kbd1 at kbdmux0 netmap: loaded module module_register_init: MOD_LOAD (vesa, 0x80f10fb0, 0) error 19 random: registering fast source Intel Secure Key RNG random: fast provider: "Intel Secure Key RNG" vtvga0: on motherboard cryptosoft0: on motherboard acpi0: on motherboard acpi0: Power Button (fixed) cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 hpet0: iomem 0xfed0-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 950 Event timer "HPET" frequency 14318180 Hz quality 550 Event timer "HPET1" frequency 14318180 Hz quality 440 Event timer "HPET2" frequency 14318180 Hz quality 440 Event timer "HPET3" frequency 14318180 Hz quality 440 Event timer "HPET4" frequency 14318180 Hz quality 440 atrtc0: port 0x70-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 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1808-0x180b on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 vgapci0: port 0xf000-0xf03f mem 0xf780-0xf7bf,0xe000-0xefff irq 16 at device 2.0 on pci0 vgapci0: Boot video device hdac0: mem 0xf7d04000-0xf7d07fff irq 16 at device 3.0 on pci0 pci0: at device 22.0 (no driver attached) ehci0: mem 0xf7d0b000-0xf7d0b3ff irq 16 at device 26.0 on pci0 usbus0: EHCI version 1.0 usbus0 on ehci0 hdac1: mem 0xf7d0-0xf7d03fff irq 22 at device 27.0 on pci0 pcib1: irq 16 at device 28.0 on pci0 pci1: on pcib1 pcib2: irq 18 at device 28.2 on pci0 pci2: on pcib2 re0: port 0xe000-0xe0ff mem 0xf7c0-0xf7c00fff,0xf000-0xf0003fff irq 18 at device 0.0 on pci2 re0: Using 1 MSI-X message re0: ASPM disabled re0: Chip rev. 0x4c00 re0: MAC rev. 0x miibus0: on re0 rgephy0: PHY 1 on miibus0 rgephy0: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow re0: Using defaults for TSO: 65518/35/2048 re0: Ethernet address: 40:8d:5c:38:04:9d re0: netmap queues/slots: TX 1/256, RX 1/256 pcib3: irq 19 at device 28.3 on pci0 pci3: on pcib3 pcib4: irq 19 at device 0.0 on pci3 pci4: on pcib4 ehci1: mem 0xf7d0a000-0xf7d0a3ff irq 23 at device 29.0 on pci0 usbus1: EHCI version 1.0 usbus1 on ehci1 isab0: at device 31.0 on pci0 isa0: on isab0 ahci0: port 0xf0b0-0xf0b7,0xf0a0-0xf0a3,0xf090-0xf097,0xf080-0xf083,0xf060-0xf07f mem 0xf7d09000-0xf7d097ff irq 19 at device 31.2 on pci0 ahci0: AHCI v1.30 with 6 6Gbps ports, Port Multiplier not supported ahcich0: at channel 0 on ahci0 ahcich1: at channel 1 on ahci0 ahcich2:
