similar to: FW: module_register

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

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

Hello! After today's update (4.8-stable from cvs "RELENG_4") I can see in messages just after boot: Jul 25 18:34:25 gw /kernel: module_register: module miibus/ukphy already exists! Jul 25 18:34:25 gw /kernel: linker_file_sysinit "miibus.ko" failed to register! 17 Jul 25 18:34:25 gw /kernel: module_register: module pci/ed already exists! Jul 25 18:34:25 gw /kernel:

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

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...

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

Doug, I remove ed config from rc.conf and system boots up without any error messages. When I try to config interface manually (ifconfig ed0 ***) then I saw it again. Is it ifconfig problem? Andris > Hm, well you were right, the ed and miibus drivers are compiled in. > > For giggles you might try removing any ifconfig_* lines in rc.conf, > booting, then running 'ifconfig -l'.

Hi! I have PC running FreeBSD 4.8-STABLE and installed Z-COM XI-626 PCI (Prism 2.5). When I try to directly connect notebook (running WinXP) with acx100 chip based card to FreeBSD I can't connect. I try connect running wi in AP and Ad-Hoc modes. NOP. Cards can see each other but can't connect. :( I is possible to connect these cards? Thanks. Andris

I'm experiencing similar problems with a 3C996-T under 4.8-REL. In particular, connecting a 4.8-REL machine to a 5.1-REL machine leads to some interesting situations: I can do simple pings across the link, but ssh fails, and heavy pings crash the 4.8 machine. Similarly changing the interface configuration with ifconfig tends to crash the 4.8 machine (mtu, link0, up/down, etc). The

Hi! I have a programm with code like this (this is example, the real code is at http://fresh.t-systems-sfr.com/linux/src/.warix/logserial-0.4.2.tar.gz.html): #################### void shutdown(int sig) { switch (sig) { default: fprintf(stderr, "Got signal %d. Exit\n", sig); break; } exit(EXIT_SUCCESS); } int main(void) { chproc = fork(); if

> 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,

Thanks Andris, Michael and Petr for your prompt and kind feedbacks. I will try generating my own biplot from low-level graph commands... I hope it will work. Best regards, Marco -- Marco Manca, MD University of Maastricht Faculty of Health, Medicine and Life Sciences (FHML) Cardiovascular Research Institute (CARIM) PO Box 616 6200 MD Maastricht E-mail: m.manca at path.unimaas.nl Office

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

Hi. I got this on today's RELENG_6 with Broadcom BCM5722 A0, ASIC rev. 0xa200. >From dmesg (bge related): bge0: <Broadcom BCM5722 A0, ASIC rev. 0xa200> mem 0xe8400000-0xe840ffff irq 16 at device 0.0 on pci2 bge0: firmware handshake timed out, found 0x4b657654 bge0: firmware handshake timed out, found 0x4b657654 bge0: EEPROM read timed out bge0: failed to read EEPROM device_attach:

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