search for: kldunload

Hello About every three months, my dad's little Asterisk server that handles his business phone line with an OpenVox PCI card stops taking calls. To check if it's the cause, I'd like to run a CRON job every night to restart Zaptel and Asterisk. Before I go ahead, I'd like to know if I can just send the following commands, or if there are issues I should know about:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-12:08.linux Security Advisory The FreeBSD Project Topic: Linux compatibility layer input validation error Category: core Module: kernel

...00-0xfc8f7ffff irg 28 at device 3.0 on pci1 hifn0: Hifn 7956, rev 0, 32KB dram, pll=0x800<pci clk, 4x mult> Then I ran: Openssl speed des-cbc And got the following result: 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes 43251.97k 44919.41k 45342.43k 45506.13k 45579.98k Then I did kldunload hifn; kldunload cryptodev and ran the same test again, and got 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes 43108.10k 44917.96k 45460.88k 45532.15k 45566.26k Version of FreeBSD is 5.3-RELEASE. I believe both crypto and cryptodev drivers are supported since v5.0. My understanding...

Dear colleagues, I'm planning to debug usb connection with my new SONY CLIE handheld, and found that this process is much complicated by the fact usb.ko module can not be unloaded 'cause some process is referencing it: marck@revamp:~/tmp> kldstat -v -i 11 Id Refs Address Size Name 11 1 0xc0cf7000 1b000 usb.ko Contains modules: Id Name

.... At least for the servers >>I've set up, this works fine. Now, a development or users' box, well... > > > Yes, I am still catching up on email almost a month old. > > I went in and made a very simple kernel-build option which disables > the use of kldload(2) (and kldunload(2)) at all times. This is not as > good as raising securelevel(8) since root can still write to > /dev/mem. However, a lot of people in this thread still seem to want > this ability. Since you can still write to /dev/mem, it is only raises > the bar a bit for an attacker. But it does ra...

hi - this is my first post to this list so go easy on me ! I am trying to find info on using ipfw2 with freebsd 5.2.1 as I have read that it supports MAC address based firewalling. Situation is, I have a small externally managed VPN network, about 12 different subnets all terminating in my office location, and all managed by a tier 1 telco. Problem is, their CPE routers do not have any firewalling

...fs 5M /rescue/fsck_msdosfs 5M /rescue/fsdb 5M /rescue/fsirand 5M /rescue/gbde 5M /rescue/geom 5M /rescue/glabel 5M /rescue/gpart 5M /rescue/ifconfig 5M /rescue/init 5M /rescue/kldconfig 5M /rescue/kldload 5M /rescue/kldstat 5M /rescue/kldunload 5M /rescue/ldconfig 5M /rescue/md5 5M /rescue/mdconfig 5M /rescue/mdmfs 5M /rescue/mknod 5M /rescue/mount 5M /rescue/mount_cd9660 5M /rescue/mount_msdosfs 5M /rescue/mount_nfs 5M /rescue/mount_ntfs 5M /rescue/mount_nullfs 5M /rescue/mount_...

...Build and install the new kernel. Add a line to the boot loader config file (/boot/loader.conf) like so: uhid_load="YES" You now can load/unload uhid at will without rebooting. If you currently have the uhid kernel module loaded, this will let you start talking to the ups via ugen: kldunload uhid.ko unplug/replug usb connection and vice-versa to go back to uhid: kldload uhid.ko unplug/replug usb connection Another snag I ran into is that some configuration of devfs is required to run all the NUT daemons as a non-root user. The FreeBSD port makes a half-hearted attempt to fix this...

...something fails because of it -- and not as the switch is turned off. "iwi0: radio turned on" is never displayed. I guess that is expected. (I think I like the new behavior better.) Something that really got better is that the device sometimes recovers from firmware errors without me kldunloading if_iwi and I have yet to see not enough dma memory for the firmware. (Firmware errors happened regularly with 6.2-RELEASE. I did not test enough to say if that got any better.) BTW: Playing around with iwi, ath, and ural removing and plugging back in the devices (not iwi), I had two crashes...

...ww.freebsd.org/handbook/kernelconfig.html> and reboot the system. If output is produced, then the linux compatibility layer is loaded as a kernel module. If the module is not currently being used (by a process running under linux emulation, for example) then it may be possible to unload it: # kldunload linux # kldstat | grep linux.ko If this does not successfully unload the module, reboot the system. V. Solution Perform one of the following: 1) Upgrade your vulnerable system to 4-STABLE; or to the RELENG_5_2, RELENG_4_10, RELENG_4_9, or RELENG_4_8 security branch dated after the correction...

...ww.freebsd.org/handbook/kernelconfig.html> and reboot the system. If output is produced, then the linux compatibility layer is loaded as a kernel module. If the module is not currently being used (by a process running under linux emulation, for example) then it may be possible to unload it: # kldunload linux # kldstat | grep linux.ko If this does not successfully unload the module, reboot the system. V. Solution Perform one of the following: 1) Upgrade your vulnerable system to 4-STABLE; or to the RELENG_5_2, RELENG_4_10, RELENG_4_9, or RELENG_4_8 security branch dated after the correction...

...er this is the case) and the system securelevel has not been raised, then the system can be patched at run-time without requiring a reboot, by performing the following steps after patching the source as described above: # cd /usr/src/sys/modules/procfs # make all install # umount -f -a -t procfs # kldunload procfs # kldload procfs # mount -f -a -t procfs -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iQCVAwUBOj4uH1UuHi5z0oilAQG4GAP6ArdnOC6dolMGQt4p6yrd+ssEKD62Uh7a y0EGd/7iFi7exxe+jWHQJVQmtyD4o8QYmO6qSJ+lb2iNYJTyKOlPWFWDlUlIhu3e UvsArp9ns/4ERR7...

Hi, Just update my 8.x kernel sources last weekend, and newly built kernel did not boot for me: link_elf: symbol mem_range_softc undefined KLD file acpi.ko - could not finalize loading kernel trap 12 with interrupts disabled This is stripped down kernel with everything possible loaded from modules. Any ideas? Did not see any warnings in UPDATING... ./danfe

Hi. I experimented a bit with collecting entropy from the time it takes for device_attach() to run (in CPU cycles). It seems that those times have enough variation that we can use it for entropy harvesting. It happens even before root is mounted, so pretty early. On the machine I'm testing it, which has minimal kernel plus NIC driver I see 75 device_attach() calls. I'm being very careful

A while back, I submitted a patch for PR kern/124621, which allows the mounting of an ext2(3) filesystem created with an inode size other than 128. The e2fsprogs' default is now 256, so file systems created on newer Linux distributions or with the port will not be mountable. I was hopeful this would get committed in time for 7.1-RELEASE (and 6.4-RELEASE), however the PR remains open. If