Re: panic: UMA: Increase vm.boot_pages on Dell R920 r279210
> On Mar 19, 2015, at 07:34, Keith White wrote: >> I tried the suggestion "Increase vm.boot_pages" but am unsure how >> much. I tried doubling to 128, and even excessive(?) values like >> 102400; but got the same panic. > > How are you trying to change the value? Can you build a custom kernel and > confirm the value in uma_startup()? > > -- > Rui Paulo > - I'm using /boot/loader.conf. Is there another place I should be doing this? vfs.mountroot.timeout="10" boot_multicons="YES" boot_serial="YES" comconsole_speed="115200" console="comconsole,vidconsole" vm.boot_pages=1024 hw.mfi.mrsas_enable=1 - With a custom kernel, the value printed is 64 not my expected "1024": ... 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 #0: Tue Mar 24 04:55:47 UTC 2015 root@:/usr/obj/usr/src/sys/GENERIC amd64 FreeBSD clang version 3.5.1 (tags/RELEASE_351/final 225668) 20150115 WARNING: WITNESS option enabled, expect reduced performance. === UMA startup boot_pages: 64 === VT: running with driver "vga". CPU: Intel(R) Xeon(R) CPU E7-4870 v2 @ 2.30GHz (2300.05-MHz K8-class CPU) Origin="GenuineIntel" Id=0x306e7 Family=0x6 Model=0x3e Stepping=7 Features=0xbfebfbff Features2=0x7fbee3ff AMD Features=0x2c100800 AMD Features2=0x1 Structured Extended Features=0x281 XSAVE Features=0x1 VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr TSC: P-state invariant, performance statistics real memory = 1099478073344 (1048544 MB) avail memory = 1069175943168 (1019645 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 80 CPUs FreeBSD/SMP: 4 package(s) x 10 core(s) x 2 SMT threads ... -- After boot, the value is as expected: # sysctl vm.boot_pages vm.boot_pages: 1024 ...keith ___ 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"
Lost HDMI output on Dell XPS M1330
Some time since 10.3, I am no longer able to select HDMI output using xrandr, just VGA. Hints on how to get it back? Noise follows: == 10.3 == # uname -ap FreeBSD m1330 10.3-RELEASE-p18 FreeBSD 10.3-RELEASE-p18 #0: Tue Apr 11 10:31:00 UTC 2017 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 amd64 # kenv smbios.system.product XPS M1330 # xrandr Screen 0: minimum 320 x 200, current 1280 x 800, maximum 8192 x 8192 LVDS1 connected 1280x800+0+0 (normal left inverted right x axis y axis) 290mm x 180mm 1280x800 60.04*+ 1024x768 60.00 800x600 60.32 56.25 640x480 59.94 VGA1 disconnected (normal left inverted right x axis y axis) HDMI1 disconnected (normal left inverted right x axis y axis) # dmesg -a | egrep -i 'vga|drm' vgapci0: port 0xeff8-0xefff mem 0xf6e0-0xf6ef,0xe000-0xefff irq 16 at device 2.0 on pci0 agp0: on vgapci0 vgapci0: Boot video device vgapci1: mem 0xf6f0-0xf6ff at device 2.1 on pci0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 info: [drm] Initialized drm 1.1.0 20060810 drmn0: on vgapci0 info: [drm] MSI enabled 1 message(s) info: [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). info: [drm] Driver supports precise vblank timestamp query. drmn0: taking over the fictitious range 0xe000-0xf000 info: [drm] initialized overlay support info: [drm] Connector LVDS-1: get mode from tunables: info: [drm] - kern.vt.fb.modes.LVDS-1 info: [drm] - kern.vt.fb.default_mode info: [drm] Connector VGA-1: get mode from tunables: info: [drm] - kern.vt.fb.modes.VGA-1 info: [drm] - kern.vt.fb.default_mode info: [drm] Connector HDMI-A-1: get mode from tunables: info: [drm] - kern.vt.fb.modes.HDMI-A-1 info: [drm] - kern.vt.fb.default_mode fbd0 on drmn0 info: [drm] Initialized i915 1.6.0 20080730 for drmn0 on minor 0 == "Current" == # uname -ap FreeBSD lenovo 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r319078M: Sun May 28 20:22:51 EDT 2017 root@lenovo:/usr/obj/usr/src/sys/GENERIC-NODEBUG amd64 amd64 # kenv smbios.system.product XPS M1330 # xrandr Screen 0: minimum 320 x 200, current 1280 x 800, maximum 8192 x 8192 LVDS1 connected 1280x800+0+0 (normal left inverted right x axis y axis) 290mm x 180mm 1280x800 60.04*+ 1024x768 60.00 800x600 60.32 56.25 640x480 59.94 VGA1 disconnected (normal left inverted right x axis y axis) # dmesg -a | egrep -i 'vga|drm' VT(vga): resolution 640x480 info: [drm] Initialized drm 1.1.0 20060810 vtvga0: on motherboard vgapci0: port 0xeff8-0xefff mem 0xf6e0-0xf6ef,0xe000-0xefff irq 16 at device 2.0 on pci0 agp0: on vgapci0 acpi_video0: on vgapci0 drmn0: on vgapci0 intel_iicbb0 on drmn0 intel_iicbb1 on drmn0 intel_iicbb2 on drmn0 intel_iicbb3 on drmn0 intel_iicbb4 on drmn0 intel_iicbb5 on drmn0 info: [drm] MSI enabled 1 message(s) info: [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). info: [drm] Driver supports precise vblank timestamp query. intel_sdvo_ddc_proxy397632 on drmn0 intel_sdvo_ddc_proxy397664 on drmn0 drmn0: taking over the fictitious range 0xe000-0xf000 info: [drm] initialized overlay support info: [drm] Connector LVDS-1: get mode from tunables: info: [drm] - kern.vt.fb.modes.LVDS-1 info: [drm] - kern.vt.fb.default_mode info: [drm] Connector VGA-1: get mode from tunables: info: [drm] - kern.vt.fb.modes.VGA-1 info: [drm] - kern.vt.fb.default_mode fbd0 on drmn0 VT: Replacing driver "vga" with new "fb". info: [drm] Initialized i915 1.6.0 20080730 for drmn0 on minor 0 vgapci0: Boot video device vgapci1: mem 0xf6f0-0xf6ff at device 2.1 on pci0 acpi_video1: on vgapci1 ...keith ___ 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"
(unionfs) panic: excl->share with r230341 and above
Starting with r230341, I get the following panic when trying to run an executable on a unionfs filesystem: exclusive lock of (lockmgr) ufs @ /usr/src/sys/modules/unionfs/../../fs/unionfs/union_vnops.c:1843 while share locked from /usr/src/sys/modules/unionfs/../../fs/unionfs/union_vnops.c:1843 panic: excl->share cpuid = 0 KDB: enter: panic Narrowing down with a binary search: r230340 (no panic), r230341 (panic). How to repeat: # uuname -a FreeBSD 10.0-CURRENT FreeBSD 10.0-CURRENT #5 r233946M: Fri Apr 6 21:09:32 EDT 2012 kwhite@demo:/usr/src/obj/usr/src/sys/GENERIC i386 # mkdir /tmp/local # mount -t unionfs -o noatime /tmp/local /usr/local # cp /bin/ls /usr/local/bin/ls # /usr/local/bin/ls exclusive lock of (lockmgr) ufs @ /usr/src/sys/modules/unionfs/../../fs/unionfs/union_vnops.c:1843 while share locked from /usr/src/sys/modules/unionfs/../../fs/unionfs/union_vnops.c:1843 panic: excl->share cpuid = 0 KDB: enter: panic [ thread pid 68 tid 100054 ] Stopped at kdb_enter+0x3b: movl$0,kdb_why db> show all locks Process 68 (ls) thread 0xc578 (100054) exclusive sleep mutex vnode interlock (vnode interlock) r = 0 (0xc57cec28) locked @ /usr/src/sys/modules/unionfs/../../fs/unionfs/union_vnops.c:1835 shared lockmgr ufs (ufs) r = 0 (0xc57cec08) locked @ /usr/src/sys/modules/unionfs/../../fs/unionfs/union_vnops.c:1843 db> Workaround? After reverting the change from LK_EXCLUSIVE to LK_SHARED in sys/kern/kern_exec.c, executables on union filesystems no longer cause a panic. ...keith ___ 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"
Re: (unionfs) panic: excl->share with r230341 and above
> Hi > > Please try an attached patch that improves handlings of fs locks. > I think that this patch can resolve this issue. If that works well, > I'm going to refine and commit it to head. > Thanks! I tried your patch but get the same panic: FreeBSD 10.0-CURRENT #6 r233856M: Mon Apr 9 09:47:42 EDT 2012 ... exclusive lock of (lockmgr) ufs @ /usr/src/sys/modules/unionfs/../../fs/unionfs/union_vnops.c:1897 while share locked from /usr/src/sys/modules/unionfs/../../fs/unionfs/ union_vnops.c:1897 panic: excl->share cpuid = 0 KDB: enter: panic [ thread pid 38 tid 100050 ] Stopped at kdb_enter+0x3b: movl$0,kdb_why db> show all locks Process 38 (ls) thread 0xc56dd2e0 (100050) exclusive sleep mutex vnode interlock (vnode interlock) r = 0 (0xc5797d38) locked @ /usr/src/sys/modules/unionfs/../../fs/unionfs/union_vnops.c:1889 shared lockmgr ufs (ufs) r = 0 (0xc5797d18) locked @ /usr/src/sys/modules/unionfs/../../fs/unionfs/union_vnops.c:1897 db> > On Fri, 6 Apr 2012 21:36:29 -0400 (EDT) > kwh...@site.uottawa.ca wrote: >> Starting with r230341, I get the following panic when trying to run >> an executable on a unionfs filesystem: >> >> exclusive lock of (lockmgr) ufs @ >> /usr/src/sys/modules/unionfs/../../fs/unionfs/union_vnops.c:1843 >> while share locked from >> /usr/src/sys/modules/unionfs/../../fs/unionfs/union_vnops.c:1843 >> panic: excl->share >> cpuid = 0 >> KDB: enter: panic >> >> Narrowing down with a binary search: r230340 (no panic), r230341 >> (panic). >> >> How to repeat: >> # uuname -a >> FreeBSD 10.0-CURRENT FreeBSD 10.0-CURRENT #5 r233946M: Fri Apr >> 6 >> 21:09:32 EDT 2012 kwhite@demo:/usr/src/obj/usr/src/sys/GENERIC >> i386 >> >> # mkdir /tmp/local >> # mount -t unionfs -o noatime /tmp/local /usr/local >> # cp /bin/ls /usr/local/bin/ls >> # /usr/local/bin/ls >> >> exclusive lock of (lockmgr) ufs @ >> /usr/src/sys/modules/unionfs/../../fs/unionfs/union_vnops.c:1843 >> while share locked from >> /usr/src/sys/modules/unionfs/../../fs/unionfs/union_vnops.c:1843 >> panic: excl->share >> cpuid = 0 >> KDB: enter: panic >> [ thread pid 68 tid 100054 ] >> Stopped at kdb_enter+0x3b: movl$0,kdb_why >> db> show all locks >> Process 68 (ls) thread 0xc578 (100054) >> exclusive sleep mutex vnode interlock (vnode interlock) r = 0 >> (0xc57cec28) locked @ >> /usr/src/sys/modules/unionfs/../../fs/unionfs/union_vnops.c:1835 >> shared lockmgr ufs (ufs) r = 0 (0xc57cec08) locked @ >> /usr/src/sys/modules/unionfs/../../fs/unionfs/union_vnops.c:1843 >> db> >> >> Workaround? >> After reverting the change from LK_EXCLUSIVE to LK_SHARED >> in sys/kern/kern_exec.c, executables on union filesystems no >> longer cause a panic. >> >> ...keith >> >> >> ___ >> 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" > > > -- > Daichi GOTO (daichi) > FreeBSD Committer, http://www.FreeBSD.org The Power To Serve > ___ 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"
r234118 uart kernel module failure: "uart_cpu_eqres undefined"
The change from sys/dev/uart/uart_cpu_{i386,amd64}.c to uart_cpu_x86.c
probably also needs a corresponding change in the module Makefile.
# kldload uart
link_elf: symbol uart_cpu_eqres undefined
Here's one suggestion that works for me:
Index: /sys/modules/uart/Makefile
===
--- /sys/modules/uart/Makefile (revision 234249)
+++ /sys/modules/uart/Makefile (working copy)
@@ -16,6 +16,8 @@
uart_if.c uart_if.h uart_subr.c uart_tty.c
.if exists(${.CURDIR}/../../dev/uart/uart_cpu_${MACHINE}.c)
SRCS+= uart_cpu_${MACHINE}.c
+.elif ${MACHINE} == "i386" || ${MACHINE} == "amd64"
+SRCS+= uart_cpu_x86.c
.endif
SRCS+= bus_if.h card_if.h device_if.h isa_if.h ${ofw_bus_if} pci_if.h \
power_if.h pccarddevs.h serdev_if.h
...keith
___
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"
ZFS panic with r255937
I get the following reproducible panic when doing a zfs send -R | zfs recv of a well churned file system (snapshots of the ports tree before and after libiconv update) running a recent current: panic: solaris assert: dn->dn_maxblkid == 0 && (BP_IS_HOLE(&dn->dn_phys->dn_blkptr[0]) || dnode_block_freed(dn, 0)), file: /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/dnode.c, line: 598 coredump available. # uname -a FreeBSD freebsd10 10.0-ALPHA4 FreeBSD 10.0-ALPHA4 #0 r255937: Sun Sep 29 09:45:21 EDT 2013 kwhite@freebsd10:/usr/obj/usr/src/sys/GENERIC amd64 # zfs list -t snapshot -r tank/ports NAME USED AVAIL REFER MOUNTPOINT tank/ports@20130915 72.5M - 3.64G - tank/ports@20130917 0 - 3.65G - tank/ports@20130918 0 - 3.65G - tank/ports@20130921 88.6M - 3.66G - tank/ports@20130928 352K - 3.66G - # zpool list -v NAME SIZE ALLOC FREECAP DEDUP HEALTH ALTROOT m_tank 1.81T 831G 1.00T44% 1.00x ONLINE - ada4.nop.eli 1.81T 831G 1.00T - tank 928G 831G 96.9G89% 1.00x ONLINE - ada3.nop.eli 928G 831G 96.9G - # zfs send -vR tank/ports@20130928 | zfs recv -vF m_tank/xports ... panic eventually ... # cd /boot/kernel; kgdb kernel /var/crash/vmcore.last ... (kgdb) up #5 0x81d09735 in dnode_reallocate (dn=0xf8006dde3000, ot=DMU_OT_PLAIN_FILE_CONTENTS, blocksize=1024, bonustype=DMU_OT_SA, bonuslen=168, tx=0xf8006d7a2600) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/dnode.c:596 596 ASSERT(dn->dn_maxblkid == 0 && (kgdb) p dn->dn_maxblkid $1 = 2 So, no question about why the ASSERT failed. Sorry, debugging this is *way* beyond me. Any hints, patches to try? ...keith ___ 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"
