similar to: repeatable crash on RELENG7

I'm trying to make devd run an stty command whenever a USB serial device is attached. Unfortunately, $device-name is ucom[0-9] and the device names are /dev/cuaU[0-9] - how do I get the correct name in the device action? I haven't found a way to extract the number by itself, so I'm stuck with specifying a separate rule for each number, like so: attach 100 { device-name

Any way to check if another proc has run or been run by a proc that is setuid or seteuid?

Hello! Currently, when a program built without OpenMP (-fopenmp) is trying to dlopen a library, built with the feature, the result is a crash from "bad system call": #0 0x00000008009a223c in ksem_init () from /lib/libc.so.7 #1 0x0000000800998a8f in sem_init () from /lib/libc.so.7 #2 0x00000008011a6537 in omp_get_nested () from /usr/lib/libgomp.so.1 #3

Hello, while reading/writing dvd on 6-STABLE (can't remember on 7-STABLE right now), I'm getting the message buffer filled by errors. This is my dvd-rw $ sysctl dev.acd.0.%desc dev.acd.0.%desc: PIONEER DVD-RW DVR-109/1.58 attached to $ sysctl dev.atapci.1.%desc dev.atapci.1.%desc: VIA 8237A UDMA133 controller And the followings are some examples of the error:

I have a FreeBSD 6.2-based server running a 1.2TB graid3 volume, which consists of 5x 320gb SATA hard drives. I've been getting errors in /var/log/messages from the graid3 volume, which I suspect means an underlying fault with one of the disks, but is there any way to decipher which one of these drives is throwing errors? I've checked smartctl -a /dev/adXX but nothing shows up there..

I'm failing to understand how getrusage() works, which is a bit perplexing, because it doesn't seem like it would be terribly complicated. I've attached the code. My aim is to verify that I can use getrusage() to do (admittedly crude) instrumentation of which functions in my program are allocating lots of memory[1]. So I figure I can call getrusage() at various points and look at

I wouldn't report this if not for one coincidence (which is described below). I have too little facts, so this is more of a mystery problem tale than a real problem report. There are two systems: 1. old, slow, i386, UP, 7-STABLE 2. new, fast, amd64, MP, 6.3-RELEASE Systems are located at different physical locations. What is common between them: 1. they both have the same backup strategy

Hello! My attempt to build openoffice.org-3 seems to be hanging. Pressing Ctrl-T produces: load: 0.11 cmd: tcsh 79759 [sleeping without queue] 0.00u 0.00s 0% 0k (tcsh is used by OOo's build-script). What is this "sleeping without queue" state, and why is process in it for so long? This is an 4-CPU amd64 system with 4Gb of RAM. Only 16% of the swap is currently in use and

We have 10 SuperMicro PDSMi+ 5015M-MTs that are panic'ing every few days. This started shortly after upgrade from 6.2-RELEASE to 6.3-RELEASE with freebsd-update. Other than switching to a debugging kernel, a little sysctl tuning, and patching with freebsd-update, they are stock. The debugging kernel was built from source that is also being patched with freebsd-update. These systems are

On Mon, Nov 13, 2017 at 01:46:32PM -0800, Davide Italiano wrote: > On Mon, Nov 13, 2017 at 11:48 AM, Rafael Avila de Espindola > <rafael.espindola at gmail.com> wrote: > > Davide Italiano <davide.italiano at gmail.com> writes: > > > >>> I couldn't find any support for this on FreeBSD. > >>> > >> > >> AFAIK FreeBSD supports

I've been playing around with snapshots lately but I've got a problem on one of my servers running 7-STABLE amd64: FreeBSD paladin 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #8: Mon Nov 10 20:49:51 GMT 2008 tdb@paladin:/usr/obj/usr/src/sys/PALADIN amd64 I run the mksnap_ffs command to take the snapshot and some time later the system completely freezes up: paladin# cd /u2/.snap/ paladin#

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

Two machines (NFS Server: running ZFS / Client: disk-less), both are running FreeBSD r253506. The NFS client starts to deadlock processes within a few hours. It usually gets worse from there on. The processes stay in "D" state. I haven't been able to reproduce it when I want it to happen. I only have to wait a few hours until the deadlocks occur when traffic to the client machine

I've been trying to get a problem fixed with a Highpoint 1820a crashing out with errors like: kernel: IAL: COMPLETION ERROR, adapter 0, channel 2, flags=104 kernel: ATA regs: error 10, sector count 20, LBA low ff, LBA mid ff, LBA high ff, device 4f, status 51 which results in the disk being dropped from the array. A sharp eyed engineer at Highpoint has just spotted the fact that the read

Hi, my FreeBSD-9/stable machine (FreeBSD freebsd-tower.goebo.site 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #2 r241044M: Sat Sep 29 12:52:01 CEST 2012 lbo@freebsd-tower.goebo.site:/usr/obj/usr/src/sys/GENERIC i386) crashes reproducibly when rsync-ing files to an NFSv4 share on the FreeBSD machine. The crash makes the system reboot. The crash creates files in /var/crash which may be obtained

After several years I replaced desktop and laptop and wait for release to start fresh. On desktop I put nvidia gt520. Forums say nvidia prop driver dislikes agp op- tion in kernel and recommend removing it. Laptop is sandy bridge with hd3000 integrated. Would I trigger something if I delete agp from conf file in both cases? Another issue bothers me also. RC version of amdtemp failed to read

Normally the FreeBSD Project tries very hard to avoid ABI breakage in "Stable Branches". However occasionally the fix for a bug can not be implemented without ABI breakage, and it is decided that the fix warrants the impact of the ABI breakage. We have one of those situations coming along for RELENG_7 (what will become FreeBSD 7.1). The ABI breakage should only impact kernel modules

So I have a system running: FreeBSD walk.dclg.ca 9.2-RC3 FreeBSD 9.2-RC3 # r254952: Wed Aug 28 03:02:55 EDT 2013 root at walk.dclg.ca:/usr/obj/usr/src/sys/STRIKE i386 and it has two 2T SATA disks. To keep this post short, the crash.txt is here. https://uk.eicat.ca/owncloud/public.php?service=files&t=fea9d25579fe0c4afb808859e80e1493 now curiously, while running a "make -j4

Hi, This happened to me repeatedly (but not always), even after updating to the latest RELENG_7 yesterday ... 1. Boot into single user mode 2. fsck / # finishes successful! 3. mount -u / 4. Do a few edits to files in /etc 5. mount -u -o ro / softdep_waitidle: Failed to flush worklist for 0xc1f36b30 mount: /dev/ad0s1a : Device busy I can't remount the root file system read-only, so

Hello, Recently, the FreeBSD base system OpenSSH was upgraded to OpenSSH_5.1p1 FreeBSD-20080901, OpenSSL 0.9.8e 23 Feb 2007 Before the upgrade, with OpenSSH_4.5p1 FreeBSD-20061110, OpenSSL 0.9.7e-p1 25 Oct 2004 I had no troubles connecting to the ssh server built-in into the HP Proliant G5 ILO management board, authenticating by id_dsa, v2 protocol. On that board, ssh server greets with