Questions about witness reports on sparc64

2010-03-04 Thread Nikolai Fetissov
Folks,

I'm pretty new here, so feel free to use the clue stick :)

Playing with current- on Sun Fire V210 I see more or less
consistent lock reversal reports like the following:

lock order reversal:
 1st 0xc1c85fb8 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:2559
 2nd 0xf80002784600 dirhash (dirhash) @
/usr/src/sys/ufs/ufs/ufs_dirhash.c:285
KDB: stack backtrace:
_witness_debugger() at _witness_debugger+0x38
witness_checkorder() at witness_checkorder+0xcf8
_sx_xlock() at _sx_xlock+0x9c
ufsdirhash_acquire() at ufsdirhash_acquire+0x30
ufsdirhash_add() at ufsdirhash_add+0x4
ufs_direnter() at ufs_direnter+0x75c
ufs_makeinode() at ufs_makeinode+0x4dc
ufs_create() at ufs_create+0x40
VOP_CREATE_APV() at VOP_CREATE_APV+0x108
vn_open_cred() at vn_open_cred+0x1fc
vn_open() at vn_open+0x1c
kern_openat() at kern_openat+0x10c
kern_open() at kern_open+0x18
open() at open+0x14
syscall() at syscall+0x25c
-- syscall (5, FreeBSD ELF64, open) %o7=0x412bfda8 --
userland() at 0x41344808
user trace: trap %o7=0x412bfda8
pc 0x41344808, sp 0x7fd99d1
pc 0x120008, sp 0x7fd9aa1
pc 0x11216c, sp 0x7fd9b61
pc 0x10d32c, sp 0x7fddd11
pc 0x10d9e4, sp 0x7fdde01
pc 0x10cf2c, sp 0x7fdded1
pc 0x10eea4, sp 0x7fddfa1
pc 0x15a0a0, sp 0x7fde061
pc 0x13024c, sp 0x7fde191
pc 0x103c10, sp 0x7fde281
pc 0x4028ef34, sp 0x7fde341
done

That's just on startup, nothing fancy going on.

My questions are - is it worth spamming the list
with these? If so, what other info needed?

Full dmesg bellow.

Thanks,
--
 Nikolai


GDB: no debug ports present
KDB: debugger backends: ddb
KDB: current backend: ddb
Copyright (c) 1992-2010 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 9.0-CURRENT #0: Sun Feb 28 23:19:48 EST 2010
r...@moon.ipv6.fetissov.org:/usr/obj/usr/src/sys/GENERIC sparc64
WARNING: WITNESS option enabled, expect reduced performance.
real memory  = 4294967296 (4096 MB)
avail memory = 4174233600 (3980 MB)
cpu0: Sun Microsystems UltraSparc-IIIi Processor (1002.00 MHz CPU)
cpu1: Sun Microsystems UltraSparc-IIIi Processor (1002.00 MHz CPU)
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
ispfw: registered firmware isp_1000
ispfw: registered firmware isp_1040
ispfw: registered firmware isp_1040_it
ispfw: registered firmware isp_1080
ispfw: registered firmware isp_1080_it
ispfw: registered firmware isp_12160
ispfw: registered firmware isp_12160_it
ispfw: registered firmware isp_2100
ispfw: registered firmware isp_2200
ispfw: registered firmware isp_2300
ispfw: registered firmware isp_2322
ispfw: registered firmware isp_2400
ispfw: registered firmware isp_2400_multi
ispfw: registered firmware isp_2500
ispfw: registered firmware isp_2500_multi
kbd0 at kbdmux0
nexus0: Open Firmware Nexus device
nexus0: memory-controller mem 0x400-0x407 type
memory-controller (no driver attached)
nexus0: memory-controller mem 0x480-0x487 type
memory-controller (no driver attached)
pcib0: Sun Host-PCI bridge mem
0x4000ff0-0x4000ff0afff,0x4000fc1-0x4000fc1701f,0x7f6-0x7f600ff,0x4000ff8-0x4000ff8
irq 2035,2032,2033,2036,2019 on nexus0
pcib0: Tomatillo, version 4, IGN 0x1f, bus B, 66MHz
pcib0: DVMA map: 0xc000 to 0xdfff 65536 entries
pcib0: [FILTER]
pcib0: [FILTER]
pcib0: [FILTER]
pcib0: [FILTER]
pci0: OFW PCI bus on pcib0
bge0: Broadcom BCM5704 A3, ASIC rev. 0x002003 mem
0x20-0x20,0x11-0x11 at device 2.0 on pci0
miibus0: MII bus on bge0
brgphy0: BCM5704 10/100/1000baseTX PHY PHY 1 on miibus0
brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
1000baseT-FDX, auto
bge0: Ethernet address: 00:03:ba:45:87:2d
bge0: [ITHREAD]
bge1: Broadcom BCM5704 A3, ASIC rev. 0x002003 mem
0x40-0x40,0x12-0x12 at device 2.1 on pci0
miibus1: MII bus on bge1
brgphy1: BCM5704 10/100/1000baseTX PHY PHY 1 on miibus1
brgphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
1000baseT-FDX, auto
bge1: Ethernet address: 00:03:ba:45:87:2e
bge1: [ITHREAD]
pcib1: Sun Host-PCI bridge mem
0x4000f60-0x4000f60afff,0x4000f41-0x4000f41701f,0x7fe-0x7fe00ff,0x4000f78-0x4000f78
irq 1970,1968,1969,1972,1953 on nexus0
pcib1: Tomatillo, version 4, IGN 0x1e, bus A, 33MHz
pcib1: DVMA map: 0xc000 to 0xdfff 65536 entries
pcib1: [FILTER]
pci1: OFW PCI bus on pcib1
isab0: PCI-ISA bridge at device 7.0 on pci1
isa0: ISA bus on isab0
pci1: old, non-VGA display device at device 6.0 (no driver attached)
ohci0: AcerLabs M5237 (Aladdin-V) USB controller mem 0x100-0x1000fff
at device 10.0 on pci1
ohci0: [ITHREAD]
usbus0: AcerLabs M5237 (Aladdin-V) USB controller on ohci0
atapci0: AcerLabs M5229 UDMA100 controller port
0x900-0x907,0x918-0x91b,0x910-0x917,0x908-0x90b,0x920-0x92f at device 13.0
on pci1
atapci0: [ITHREAD]
atapci0: using 

Re: Questions about witness reports on sparc64

2010-03-04 Thread Scot Hetzel
On Thu, Mar 4, 2010 at 7:19 PM, Nikolai Fetissov
nikolai-free...@fetissov.org wrote:
 Folks,

 I'm pretty new here, so feel free to use the clue stick :)

 Playing with current- on Sun Fire V210 I see more or less
 consistent lock reversal reports like the following:

:

 My questions are - is it worth spamming the list
 with these? If so, what other info needed?

It is worth sending it to the list and sending a report as outlined here:

http://sources.zabbadoz.net/freebsd/lor.html

Scot
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org