similar to: module_register

Hello! I have the same problem, whats up? Andris > -----Original Message----- > From: owner-freebsd-stable@freebsd.org > [mailto:owner-freebsd-stable@freebsd.org] On Behalf Of Dmitry Agafonov > Sent: Friday, July 25, 2003 8:40 PM > To: freebsd-stable@freebsd.org > Subject: module_register > > > Hello! > > After today's update (4.8-stable from cvs

Hi, in the kernel I have these lines: [...] device miibus # MII bus support device rl device ed options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #enable logging to syslogd(8) options IPFIREWALL_VERBOSE_LIMIT=0 #limit verbosity options IPDIVERT #divert sockets options DUMMYNET

With FreeBSD 4.8-20030731-STABLE #0, dmesg messages indicate: module_register: module miibus/ukphy already exists! linker_file_sysinit "miibus.ko" failed to register! 17 module_register: module pccard/ed already exists! linker_file_sysinit "if_ed.ko" failed to register! 17 This doesn't look dangerous but the rl0 ethernet card just stopped recieving packets suddenly and

After compiling the kernel 4.9RC1 dmesg gives the following error lpt0: Interrupt-driven port ppi0: <Parallel I/O> on ppbus0 ed1: <Realtek Plug & Play Ethernet Card> at port 0x220-0x23f irq 5 on isa0 ed1: address 52:54:40:28:83:9a, type NE2000 (16 bit) ad0: 4112MB <WDC AC24300L> [8912/15/63] at ata0-master WDMA2 Mounting root from ufs:/dev/ad0s1a module_register: module

Hi, Maybe this message should go to mobile. Machine: IBM ThinkPad 600 (Model 2645-85U) PII-300, 64 RAM, 4GB HDD Network card: Xircom CE3B-100BTX (pcmcia) I've SUP yesterday (Sept 30) from cvsup12.freebsd.org , make world, mergemaster, MAKEDEV, updated /stand , rebooted, everyting seems to be ok but I'm getting an error related to the pcmcia network card. uname -a : FreeBSD

Hello, I am having a problem with a new server running FreeBSD 4.9-PRERELEASE. Once every two days or so, it reboots itself.. there is no exact time of the day it reboots.. It rebooted itself at 4:25 PM EDT on 9/25, and 3:05 AM EDT on 9/29 (today). I thought it's the bad memory or some sort, so I've been running memtest today and memtest reports no sign of trouble with the memory...

Sorry if this is a known problem... I've been tracking RELENG_4 on my Toshiba laptop for a while now; a couple of months ago (not sure when) my sound stopped working. More specifically, when it gets to the pcm probe, the boot hangs. I dual-boot with WinXP and figured that somehow XP had hosed the hardware, so I wrote it off. Today, I made world with RELENG_4_8, and voila, my sound's

> That makes no sense because we are supposed to have just forked successfully I just realized libguestfs uses fork. Now we know why qemu-img worked - I launched it with popen. > So it must be something to do with collectd and how it runs programs. > Is it using LD_PRELOAD trickery, or replacing libc, or using seccomp? If I understand the question correctly - it's about how

After updating my kernel from a 4.7-stable to 4.8-stable update, my SB PCI128 is no longer recognized by the pcm driver. Here is my dmesg: FreeBSD 4.8-STABLE #0: Thu Jul 17 14:13:52 CDT 2003 root@hautlos.stout.osu-res.okstate.edu:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz CPU: AMD Athlon(tm) Processor (800.03-MHz 686-class CPU) Origin =

On Wed, Nov 07, 2018 at 01:37:03PM +0200, Peter Dimitrov wrote: > > That makes no sense because we are supposed to have just forked > successfully > > I just realized libguestfs uses fork. Now we know why qemu-img worked - I > launched it with popen. > > > So it must be something to do with collectd and how it runs programs. > > Is it using LD_PRELOAD trickery,

Hello, I've been having spurrious crash troubles with this box a while now and I haven't been able to figure out why. I've ran a couple memtest passes on it and it didn't pick up anything. Here's a backtrace I've been able to obtain. The kernel config is at the end. It's the generic kernel with ULE. I'm following chapter 11 of the developers' handbook, so if

Hello, My server is experiencing occasional kernel panics when under moderate load. I'm attaching a crash dump and the dmesg output. I'm not sure how to read the kernel backtrace but it looks like the Intel NIC (em0) caused the problem. Occasionally, I used to get a "em0: watchdog timeout -- resetting" error message, but I never had a kernel panic. The problem started last

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

Hello, I've met some quite strange reboots recently on my home gateway. I'm trying to reduce its power consumption, so I've loaded the cpufreq(4) driver, and enabled powerd. After this the box started to reboot randomly all over the place. I started to think what can cause the trouble, removing the cpufreq(4) support would be too trivial, so I've removed the ALTQ references from

Is anyone else seeing this: perl @/kern/makeops.pl -h @/opencrypto/crypto_if.m rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/../include -I/usr/obj/usr/local/src-STABLE/src/i386/usr/include /usr/local/src-STABLE/src/sys/modules/hifn/../../dev/hifn/hifn7751.c /usr/local/src-STABLE/src/sys/modules/hifn/../../dev/hifn/hifn7751.c:47: opt_hifn.h: No such file or

Hi, After kernel panic I couldn't get gdb work properly. msi$ uname -sr FreeBSD 4.7-RELEASE msi$ gdb -k /usr/src/sys/compile/MSINW/kernel.debug vmcore.0 GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show

TB --- 2003-10-02 04:44:07 - starting RELENG_4 tinderbox run for i386/i386 TB --- 2003-10-02 04:44:07 - checking out the source tree TB --- cd /home/des/tinderbox/RELENG_4/i386/i386 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_4 src TB --- 2003-10-02 04:49:12 - building world TB --- cd /home/des/tinderbox/RELENG_4/i386/i386/src TB --- /usr/bin/make -B buildworld >>>

TB --- 2003-10-02 04:00:01 - starting RELENG_4 tinderbox run for alpha/alpha TB --- 2003-10-02 04:00:01 - checking out the source tree TB --- cd /home/des/tinderbox/RELENG_4/alpha/alpha TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_4 src TB --- 2003-10-02 04:07:38 - building world TB --- cd /home/des/tinderbox/RELENG_4/alpha/alpha/src TB --- /usr/bin/make -B buildworld >>>

TB --- 2003-07-21 05:27:28 - starting RELENG_4 tinderbox run for i386/pc98 TB --- 2003-07-21 05:27:28 - checking out the source tree TB --- cd /home/des/tinderbox/RELENG_4/i386/pc98 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_4 src TB --- 2003-07-21 05:33:30 - building world TB --- cd /home/des/tinderbox/RELENG_4/i386/pc98/src TB --- /usr/bin/make -B buildworld >>>

Hello I have some problems with 3Com nics, after a upgrade from 5.5-STABLE to 6.4-STABLE. This machine has two 3com nics (one is LAN other is WAN) and i see too much "watchdog timeout" on both cards. This on/off up/down on cards, affect the interrupt to clients that are downloading from apache web server, especially on large files. --------------------------------------------