search for: invariant_support

Hi All, I have what I think is a ZFS related bug. Unfortunately my simplest test case is a bit cumbersome and I haven't definitively proven that the problem is ZFS related. I'm hoping for some feedback on how to move forward. Quick background: I rip my CD's using grip and produce flac files. I tag the music using Musicbrainz' Picard and transcode it to mp3's within Picard

I have patches to add locking to the adv(4), adw(4), aha(4), ahb(4), aic(4), and bt(4) drivers so that they no longer use Giant. I would appreciate any testing folks are able to do. The patches are against HEAD but should apply to 8 or 9. Make sure you have INVARIANTS and INVARIANT_SUPPORT enabled for any initial testing that you do. Thanks! http://www.FreeBSD.org/~jhb/patches/adv_locking.patch http://www.FreeBSD.org/~jhb/patches/adw_locking.patch http://www.FreeBSD.org/~jhb/patches/aha_locking.patch http://www.FreeBSD.org/~jhb/patches/ahb_locking.patch http://www.FreeBSD.org/~jhb...

I've got a HP dv8000 laptop. Setting up the wpi driver for wireless freezes the system on boot with the following error: wpi0 requested unsupported memory range wpi0: could not allocate memory resource It lists a pcbi device (pcbi4 i think) and an actual memory range, but since I have to reboot using kernel.old the /var/run/dmesg.boot is wiped with the info. Is there anyway to grab the

...ftc synchronization from the topology lock to per-device sx lock. I'd like to ask gmirror/graid3 users to test those patches as much as possible, because I want to commit them to the HEAD and RELENG_6 branches. Because of locking changes it will be really good if you can turn on INVARIANTS, INVARIANT_SUPPORT options and eventually DIAGNOSTIC in your kernel. Thanks in advance! -- Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! -------------- next part --------...

Hello List, I know 4.9 is ancient history, but unfortunately we have several thousand sites installed. We are in the process of moving to 6.1 when it is released. Right now I have an immediate problem where we are going to install two system at a HQ site. Each of the 2 systems will have two gre/vpn/ospf tunnels to a 100 remote sites in the field. The broadband will be a T3 with failover to

currently i'm trying to setup diskless client, which netboots 6.1-PRERELEASE kernel with help of etherboot. i've built custom kernel with `sudo make -j4 buildkernel KERNCONF=DISKLESS CPUTYPE=pentium-mmx -DNO_MODULES' and attached config. kernell loads off tftp server fine, detecting devices, but traps, when trying to mount root fs from nfs server. i've managed to get copy of

Some more crashes of 4.8-RELEASE. Lets see what do I have today: # ls -l /var/crash total 1576676 -rw-r--r-- 1 root wheel 2 Jul 30 13:31 bounds -rw-r--r-- 1 root wheel 2193252 Jun 25 17:30 kernel.0 -rw-r--r-- 1 root wheel 2193252 Jul 4 00:08 kernel.1 -rw-r--r-- 1 root wheel 2193252 Jul 15 19:28 kernel.2 -rw-r--r-- 1 root wheel 2193252 Jul 16 17:50 kernel.3

...Enable kernel debugger support. options KDB_TRACE # Enable kernel debugger support. options KDB_UNATTENDED # Enable kernel debugger support. options DDB # Support DDB. options GDB # Support remote GDB. options STACK #options INVARIANTS # Enable calls of extra sanity checking #options INVARIANT_SUPPORT # Extra sanity checks of internal structures, required by INVARIANTS #options WITNESS # Enable checks to detect deadlocks and cycles #options WITNESS_SKIPSPIN # Don't run witness on spinlocks for speed # Make an SMP-capable kernel by default options SMP # Symmetric MultiProcessor Kernel...

Colleagues, one of my servers had to be rebooted uncleanly and then I have backgrounded fsck locked for more than an our in snaplk: 742 root 1 -4 4 1320K 688K snaplk 0:02 0.00% fsck_ufs File system in question is 200G gmirror on SATA. Usually making a snapshot (e.g., for making dumps) consumes 3-4 minutes for that fs, so it seems to me that filesystem is in a deadlock. Any

I was trying to simply test bandwidth that Solaris/ZFS (Nevada b63) can deliver from a drive, and doing this: dd if=(raw disk) of=/dev/null gives me around 80MB/s, while dd if=(file on ZFS) of=/dev/null gives me only 35MB/s!?. I am getting basically the same result whether it is single zfs drive, mirror or a stripe (I am testing with two Seagate 7200.10 320G drives hanging off the same interface

...src/sys/GENERIC-DEBUG i386 --------------------------------------------------------------- 2. Kernel configuration file /sys/i386/conf/GENERIC-DEBUG: include GENERIC ident GENERIC-DEBUG # force isp firmware to fully loaded # device ispfw options KDB options DDB options INVARIANTS options INVARIANT_SUPPORT options WITNESS options DEBUG_LOCKS options DEBUG_VFS_LOCKS options DIAGNOSTIC options CAMDEBUG options CAM_DEBUG_BUS=-1 options CAM_DEBUG_TARGET=-1 options CAM_DEBUG_LUN=-1 options CAM_DEBUG_FLAGS=CAM_DEBUG_INFO --------------------------------------------------------------- 3. dmesg output, a...