Re: FreeBSD 9.0 hang
I have no ATM interfaces so it shouldn't be loading to my way of thinking. so check while this module is loading at all, no matter if it's unsuccessull. FreeBSD is not random place like windows, everything must have a reason. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9.0 hang
On 2 July 2012, at 22:59, Wojciech Puchar wrote: I have no ATM interfaces so it shouldn't be loading to my way of thinking. so check while this module is loading at all, no matter if it's unsuccessull. FreeBSD is not random place like windows, everything must have a reason. True it must, but I have no idea why if_en would try to be loaded or even how to figure that out. There is nothing in the logs. My understanding is that you would have to have an interface that requires the en driver. pciconf doesn't show any. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9.0 hang
On 03-Jul-2012, at 11:45 AM, Doug Hardie wrote: On 2 July 2012, at 22:59, Wojciech Puchar wrote: I have no ATM interfaces so it shouldn't be loading to my way of thinking. so check while this module is loading at all, no matter if it's unsuccessull. FreeBSD is not random place like windows, everything must have a reason. True it must, but I have no idea why if_en would try to be loaded or even how to figure that out. There is nothing in the logs. My understanding is that you would have to have an interface that requires the en driver. pciconf doesn't show any. How about a verbose boot and a list of your boot messages? Also, how about you create a kernel with ATM missing and see what stops working? Thanks -- Subhro Sankha Kar System Administrator Working and Playing with FreeBSD since 2002 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9.0 hang
link_eif symbol atm_event undefined KLD if_en.ko: depends on utopia - not available or version mismatch. I haven't found anything relevant on those through Google. if_en.ko os present as is utopia.ko. I don't understand why the kernel would try to load if_en as I don't have any of those devices. There are em0 and dc0 ethernet interfaces. This is almost a generic kernel. The config file contains: Was that line printed just before hangup? Do you actually tried to load ATM interface driver. If no - check why it loads at all. Check what is last in your logfile. Check if any addon drivers you use (fuse.ko, vboxdrv.ko) was compiled with the same kernel sources that you compiled kernel. If this doesn't help then recompile your kernel with makeoptions DEBUG=-O0 -g optionsINCLUDE_CONFIG_FILE optionsDEADLKRES optionsKDB optionsDDB optionsINVARIANTS optionsINVARIANT_SUPPORT optionsWITNESS optionsWITNESS_SKIPSPIN optionsDIAGNOSTIC make sure that dump device is active dumpon=/dev/dumpdevicename and reboot with that kernel. At next crash you will get full dump with all symbols and all data where it crashes. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9.0 hang
On 2 July 2012, at 08:50, Wojciech Puchar wrote: link_eif symbol atm_event undefined KLD if_en.ko: depends on utopia - not available or version mismatch. Those were the last 2 lines on the console before the hang. There is nothing at all in messages about this. I suspect the system was not totally hung, just the etnernet interfaces (2 different ones) as I could still ping both interfaces successfully. However, no attempt to access any service worked. I haven't found anything relevant on those through Google. if_en.ko os present as is utopia.ko. I don't understand why the kernel would try to load if_en as I don't have any of those devices. There are em0 and dc0 ethernet interfaces. This is almost a generic kernel. The config file contains: Was that line printed just before hangup? Do you actually tried to load ATM interface driver. If no - check why it loads at all. I have no ATM interfaces so it shouldn't be loading to my way of thinking. Check what is last in your logfile. Nothing. Check if any addon drivers you use (fuse.ko, vboxdrv.ko) was compiled with the same kernel sources that you compiled kernel. kldstat -v shows: 21 0xc5b36000 4000 fdescfs.ko (/boot/kernel/fdescfs.ko) Contains modules: Id Name 493 fdescfs 31 0xc5c8f000 3000 pflog.ko (/boot/kernel/pflog.ko) Contains modules: Id Name 495 pflog 41 0xc5c92000 34000pf.ko (/boot/kernel/pf.ko) Contains modules: Id Name 494 pf if_en is not listed as compiled into the kernel. The kernel and userland were built shortly after an install from memstick image using the procedure in UPDATING: To rebuild everything and install it on the current system. --- # Note: sometimes if you are running current you gotta do more than # is listed here if you are upgrading from a really old current. make sure you have good level 0 dumps make buildworld make kernel KERNCONF=YOUR_KERNEL_HERE [1] reboot in single user [3] mergemaster -p [5] make installworld mergemaster -i [4] make delete-old [6] reboot After that the ports and application software were installed. Basically the only services that run on this system are nagios and mrtg. It is used only as a monitoring system for my production server and for testing new software. It has only been used for monitoring since the upgrade. I can't do any development work till I get the production servers upgraded from 8.2 to 9.0. If this doesn't help then recompile your kernel with makeoptions DEBUG=-O0 -g optionsINCLUDE_CONFIG_FILE optionsDEADLKRES optionsKDB optionsDDB optionsINVARIANTS optionsINVARIANT_SUPPORT optionsWITNESS optionsWITNESS_SKIPSPIN optionsDIAGNOSTIC make sure that dump device is active dumpon=/dev/dumpdevicename and reboot with that kernel. At next crash you will get full dump with all symbols and all data where it crashes. When this repeats I will do that. Thanks for the help. -- Doug ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD 9.0 hang
I have a 9.0 p3 system that is in production for about a week and it just plain hung this morning. The console had the last two messages as: link_eif symbol atm_event undefined KLD if_en.ko: depends on utopia - not available or version mismatch. I haven't found anything relevant on those through Google. if_en.ko os present as is utopia.ko. I don't understand why the kernel would try to load if_en as I don't have any of those devices. There are em0 and dc0 ethernet interfaces. This is almost a generic kernel. The config file contains: include GENERIC ident LAFN nocpu i486_CPU nocpu i586_CPU options QUOTA #device atapicam options ALTQ# Enable ALTQ. options ALTQ_CBQ# Build the ``Class Based Queuing'' discipline. options ALTQ_NOPCC # Required for SMP build I couldn't find any relevant log messages that would indicate why this module was trying to be loaded. However, even so, I would think it should load ok. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
