Re: Kernel Panic - Unix socket communication in kernel module
On Monday, July 29, 2013 3:31:49 am varanasi sainath wrote: Hello, I am writing a kernel module in which I am trying to connect to a UNIX socket (UNIX domain sockets use the file system as their address name space). Kernel module (loadable) acts as a client and User mode program acts as server, I have loaded the module using kldload and communication between user and kernel module works fine, when I try to load the kernel module from loader.conf - auto load the kernel module at boot up leads to kernel panic as the file system is not ready and kern_connect fails. How to notify kernel module that File system is ready? (any specific event flags) Is there any specific location for Unix domain socket files? (currently created it under /root/soc/socket ) Using MODULE_DEPEND Can I make the module dependent of file system? You can register a hook for the 'mountroot' EVENTHANDLER event which will fire after / is mounted. (You could compare rootvnode against NULL during module startup to determine if you should defer your work to the EVENTHANDLER vs doing it right away.) If you need to wait for all local filesystems to be mounted, then you will need to have some userland utility poke your module via a sysctl/ioctl/etc. after the filesystems are mounted (you could use a custom rc.d script for this). -- John Baldwin ___ 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: Kernel Panic - Unix socket communication in kernel module
On 29/07/2013 08:31, varanasi sainath wrote: Hello, I am writing a kernel module in which I am trying to connect to a UNIX socket (UNIX domain sockets use the file system as their address name space). Kernel module (loadable) acts as a client and User mode program acts as server, I have loaded the module using kldload and communication between user and kernel module works fine, when I try to load the kernel module from loader.conf - auto load the kernel module at boot up leads to kernel panic as the file system is not ready and kern_connect fails. How to notify kernel module that File system is ready? (any specific event flags) Is there any specific location for Unix domain socket files? (currently created it under /root/soc/socket ) Using MODULE_DEPEND Can I make the module dependent of file system? I shall resist the obvious why question. I'm assuming you're talking about a fifo here (aka named pipe, and occasionally called UNIX socket) rather than the BSD network socket interface. IIRC since 4.3BSD fifos have been implemented using sockets internally anyway. Where to put it? I tend to go for /tmp but somewhere in /var might make more sense for something that's always supposed to be there. I don't know how to tell when the FS is ready but it will be when init runs, so you might like to try the sysctl variables. Knowing that init is always PID 1, the value of kern.lastpid should give a hint. There may be an official way of doing this properly. You could always load the module from rc.local instead. Regards, Frank. P.S. You do know that an fd only relates to the kernel thread it's currently running in? ___ 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: kernel panic
On 09/08/2012 15:52, dude golden wrote: hope my email find you well,first of all thank you very much for your grate response always in answering my emails, now i am using freeBSD 8.3 in a Intel corI5 server with 12 G of RAM and 500 G HDD sata .we have a voip soft switch application installed on it and do telecommunication business, yesterday night we experience a strange kernel panic and our server hanged, just contact collocation as asked for physical reboot, in attached, you can find screen shot of rebooting the server . i really thank full if you take a look and advise me any update. The freebsd-questions@ probably won't have seen the screen shot, but it showed me that the problem was in ffs_blkfree, ie. that the system panicked because of filesystem corruption. Unfortunately you haven't enabled a dump device, so no more detailed debugging info will be available. There's not a huge amount that can be determined just from the panic screen unfortunately. However, in terms of general advice: * You need to ensure that there is no lingering filesystem corruption which could trigger a repeat. Reboot the system into single user mode, and then run: fsck -fy /dev/ad7s4a etc. for all the devices listed in /etc/fstab or elsewhere that have active filesystems on them. Run fsck like that repeatedly for each partition until it says 'filesystem clean.' * Enable system dumps, so if this happens again, there is more to go on. Just add: dumpdev=AUTO to /etc/rc.conf and reboot. * The problem could well be due to disk malfunction, or maybe something as trivial as a loose or kinked data cable leading to the drive, or overheating. Powering the machine down, opening the case and checking for any obvious problems would be a good idea. Also, check the system logs to see if there are any kernel messages indicating non-fatal trouble. Install the sysutils/smartmontools port and use that to get a health report on the drive: smartctl -A /dev/ad7 * It seems you don't have any sort of hard drive resilience set up. If this server is important for your business, then using mirrored hard drives is just plain common sense. If there's room in the chassis, simply adding another drive identical to the one you have and setting up gmirror RAID should be fairly simple and will offer adequate levels of protection against such failures. -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: Kernel Panic any help?
Hi, On 25 May 2012 20:01:44 - John Levine jo...@iecc.com wrote: JL panic: ffs_clusteralloc: map mismatch JL JL Something's fairly badly screwed up on your disk. My advice would JL be to boot from a CD or USB key and run fsck to try to repair it. the disk was pretty much f...ed up. I always got an access denied on every operation I tried on the device node for the root partition. I had to delete and re-create the partition. Well I took the oportunity and upgraded to 9.0. ;-) Thanks for the help, Jens -- 29. Wonnemond 2012, 18:18 Homepage : http://www.jan0sch.de Criticism comes easier than craftsmanship. -- Zeuxis pgpm4QhisRQxp.pgp Description: PGP signature
Re: Kernel Panic any help?
panic: ffs_clusteralloc: map mismatch Something's fairly badly screwed up on your disk. My advice would be to boot from a CD or USB key and run fsck to try to repair it. R's, John ___ 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: Kernel Panic on 9.0-RELEASE When Attempting to Remove Files
In response to the related thread started by Martin McCormick we did run a `zpool scrub` on the zpool, and the scrub completed successfully with no repairs performed. I successfully tried importing the zpool in Linux using the native Linux ZFS module. However attempting to remove the files via Linux results in `rm` either being killed or hanging. Ryan On 02/10/2012 10:43 AM, Ryan Frederick wrote: I'm attempting to remove a number of old files within a directory that was rsynced over from another box. However a number of files (old symlinks and regular files in this instance) cause a kernel panic when attempting to remove them using rm or unlink. This is the panic message output: Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x160 fault code = supervisor read data, page not present instruction pointer = 0x20:0x81476306 stack pointer = 0x28:0xff811aacf880 frame pointer = 0x28:0xff811aacf940 code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 4729 (rm) trap number = 12 panic: page fault cpuid = 1 KDB: stack backtrace: #0 0x808680fe at kdb_backtrace+0x5e #1 0x80832cb7 at panic+0x187 #2 0x80b18400 at trap_fatal+0x290 #3 0x80b18749 at trap_pfault+0x1f9 #4 0x80b18c0f at trap+0x3df #5 0x80b0313f at calltrap+0x8 #6 0x80b7d694 at VOP_REMOVE_APV+0x34 #7 0x808cb4fd at kern_unlinkat+0x32d #8 0x80b17cf0 at amd64_syscall+0x450 #9 0x80b03427 at Xfast_syscall+0xf7 And this is the backtrace from kgdb: #0 doadump (textdump=Variable textdump is not available. ) at pcpu.h:224 #1 0x808327f5 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:442 #2 0x80832ca1 in panic (fmt=Variable fmt is not available. ) at /usr/src/sys/kern/kern_shutdown.c:607 #3 0x80b18400 in trap_fatal (frame=0xc, eva=Variable eva is not available. ) at /usr/src/sys/amd64/amd64/trap.c:819 #4 0x80b18749 in trap_pfault (frame=0xff811aacf7d0, usermode=0) at /usr/src/sys/amd64/amd64/trap.c:735 #5 0x80b18c0f in trap (frame=0xff811aacf7d0) at /usr/src/sys/amd64/amd64/trap.c:474 #6 0x80b0313f in calltrap () at /usr/src/sys/amd64/amd64/exception.S:228 #7 0x81476306 in zfs_freebsd_remove (ap=Variable ap is not available. ) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c:1842 #8 0x80b7d694 in VOP_REMOVE_APV (vop=Variable vop is not available. ) at vnode_if.c:1333 #9 0x808cb4fd in kern_unlinkat (td=0xfe00046cb8c0, fd=-100, path=0x7fffdd73 Address 0x7fffdd73 out of bounds, pathseg=UIO_USERSPACE, oldinum=0) at vnode_if.h:575 #10 0x80b17cf0 in amd64_syscall (td=0xfe00046cb8c0, traced=0) at subr_syscall.c:131 #11 0x80b03427 in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:387 #12 0x0008009315fc in ?? () This particular system is a VM running on a VMWare ESXi hypervisor. So far I haven't had any luck in finding a cause. Ryan ___ 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: kernel Panic not dumping to swap
On 8/9/11 10:33 PM, Daryl Sayers wrote: I have a FreeBSD 8.2-STABLE (64bit) system with 4G mem installed. I have had a few kernel panics over the last few weeks and would like to capture a core dump. I have added the following to /etc/rc.conf dumpdev=AUTO dumpdir=/var/crash The /var/crash is a 5G filesystem (with 4.8G free). When the machine panics the last 2 lines on the console are something like: Physical memory: 3057 MB Dumping 204 MB: 189 173 157 141 125 The system then completely hangs and a hardware rest is required. As the dump does not seem to finish I dont get my core dump in /var/cache when the machine reboots. Any ideas?? Daryl, A couple of questions: 1) How big is your swap partition? Is it large enough to hold the crash dump? 2) What type of hardware is this? I know that HP Proliants using the CISS raid control fail to produce a crashdump and just hangup these boxes. Perhaps this occurs for other types of hardware? Thanks Patrick. I have an 8G swap that is plenty big enough for the 4G memory. There is nothing special about the hardware. Its an Asus PB5+ mother board using the onboard IDE port with an old Maxtor 120G drive (6Y120P0). ___ 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: kernel Panic not dumping to swap
On 8/9/11 10:33 PM, Daryl Sayers wrote: I have a FreeBSD 8.2-STABLE (64bit) system with 4G mem installed. I have had a few kernel panics over the last few weeks and would like to capture a core dump. I have added the following to /etc/rc.conf dumpdev=AUTO dumpdir=/var/crash The /var/crash is a 5G filesystem (with 4.8G free). When the machine panics the last 2 lines on the console are something like: Physical memory: 3057 MB Dumping 204 MB: 189 173 157 141 125 The system then completely hangs and a hardware rest is required. As the dump does not seem to finish I dont get my core dump in /var/cache when the machine reboots. Any ideas?? Daryl, A couple of questions: 1) How big is your swap partition? Is it large enough to hold the crash dump? 2) What type of hardware is this? I know that HP Proliants using the CISS raid control fail to produce a crashdump and just hangup these boxes. Perhaps this occurs for other types of hardware? Patrick ___ 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: Kernel panic on power button
On 12/10/10 14:47, Eitan Adler wrote: I just pressed the power button on my desktop computer - it seemed like it was attempting to do an ACPI suspend instead of a power down like I expected - but I'm not sure. Either way: When It got close to the end I got Kernel trap 12: page fault in kernel mode followed by the fault address, instruction pointer, etc. I have the information written it down if it would help. At the end it said unable to dump - device not configured uptime: 11d... The current process was listed as 81250 (tmux) if that matter. I then needed to perform a hard shutdown of the computer. uname -a FreeBSD voodoo 8.1-STABLE FreeBSD 8.1-STABLE #1 r213338: Fri Oct 1 22:11:41 UTC 2010 ei...@voodoo:/usr/obj/usr/src/sys/GENERIC i386 What debugging data should I provide to help fix this issue? I've seen that before just a few days ago. Difference was battmond shut it down, but it hasn't done it since so I was worried. I checked my disks and they were fine. Maybe post dmesg and compare similarities? Did I mention mine's a laptop? Copyright (c) 1992-2009 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.0-RELEASE-p4 #0: Mon Jul 12 20:55:11 UTC 2010 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM)2 Duo CPU T7500 @ 2.20GHz (2194.51-MHz K8-class CPU) Origin = GenuineIntel Id = 0x6fb Stepping = 11 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0xe3bdSSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM AMD Features=0x20100800SYSCALL,NX,LM AMD Features2=0x1LAHF TSC: P-state invariant real memory = 1073741824 (1024 MB) avail memory = 1009704960 (962 MB) ACPI APIC Table: A_M_I_ OEMAPIC FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0 Version 2.0 irqs 0-23 on motherboard Cuse4BSD v0.1.13 @ /dev/cuse kbd1 at kbdmux0 acpi0: _ASUS_ Notebook on motherboard acpi0: [ITHREAD] acpi_ec0: Embedded Controller: GPE 0x1c, ECDT port 0x62,0x66 on acpi0 acpi0: Power Button (fixed) unknown: I/O range not supported unknown: I/O range not supported acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 3f70 (3) failed Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 acpi_hpet0: High Precision Event Timer iomem 0xfed0-0xfed003ff on acpi0 Timecounter HPET frequency 14318180 Hz quality 900 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 vgapci0: VGA-compatible display port 0xec00-0xec07 mem 0xfeb0-0xfebf,0xd000-0xdfff irq 16 at device 2.0 on pci0 agp0: Intel GM965 SVGA controller on vgapci0 agp0: detected 7676k stolen memory agp0: aperture size is 256M acpi_video0: ACPI video extension on vgapci0 vgapci1: VGA-compatible display mem 0xfe90-0xfe9f at device 2.1 on pci0 uhci0: Intel 82801H (ICH8) USB controller USB-D port 0xe000-0xe01f irq 16 at device 26.0 on pci0 uhci0: [ITHREAD] uhci0: LegSup = 0x0f30 usbus0: Intel 82801H (ICH8) USB controller USB-D on uhci0 uhci1: Intel 82801H (ICH8) USB controller USB-E port 0xdc00-0xdc1f irq 21 at device 26.1 on pci0 uhci1: [ITHREAD] uhci1: LegSup = 0x0f30 usbus1: Intel 82801H (ICH8) USB controller USB-E on uhci1 ehci0: Intel 82801H (ICH8) USB 2.0 controller USB2-B mem 0xfeaff400-0xfeaff7ff irq 18 at device 26.7 on pci0 ehci0: [ITHREAD] usbus2: EHCI version 1.0 usbus2: Intel 82801H (ICH8) USB 2.0 controller USB2-B on ehci0 hdac0: Intel 82801H High Definition Audio Controller mem 0xfeaf8000-0xfeafbfff irq 22 at device 27.0 on pci0 hdac0: HDA Driver Revision: 20090624_0136 hdac0: [ITHREAD] pcib1: ACPI PCI-PCI bridge irq 16 at device 28.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge irq 17 at device 28.1 on pci0 pci2: ACPI PCI bus on pcib2 pcib3: ACPI PCI-PCI bridge irq 18 at device 28.2 on pci0 pci3: ACPI PCI bus on pcib3 age0: Attansic Technology Corp, L1 Gigabit Ethernet mem 0xfdcc-0xfdcf irq 18 at device 0.0 on pci3 age0: 1280 Tx FIFO, 2364 Rx FIFO age0: Using 1 MSI messages. miibus0: MII bus on age0 atphy0: Atheros F1 10/100/1000 PHY PHY 0 on miibus0 atphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT-FDX, auto age0: Ethernet address: 00:1f:c6:13:3d:30 age0: [FILTER] pcib4: ACPI PCI-PCI bridge irq 19 at device 28.3 on pci0 pci4: ACPI PCI bus on pcib4 pcib5: ACPI PCI-PCI bridge irq 16 at device 28.4 on pci0 pci5: ACPI PCI bus on pcib5 pcib6: ACPI PCI-PCI bridge irq 17 at device 28.5 on pci0 pci7: ACPI PCI bus on pcib6 iwn0: Intel(R) PRO/Wireless 4965BGN mem
Re: Kernel Panic at loading FreeBSD
2010/12/3 Dmitry Postolov anta...@land.ru: Hi to All! Sorry for my bad English... On my notebook HP ProBook 4510s NX668EA (Bios Compaq F17 (latest)) the problem of times in some weeks is observed at loading FreeBSD 8.1. --- Fatal trap 12: page fault while in kernel mode cpuid=0; apic id=00 fault virtual adress=0x14 fault code=supervisos read, page not present instruction pointer=0x20:0xc0966916 stack pointer=0x28:0xea0b7c50 frame pointer=0x28:0xea0b7c50 code segment=base 0x0, limit 0xf type 0x1b =DPL 0, pres 1, def 32 1, gran 1 processor eflags=interrupt enabled, resume, IOPL=0 current process=15 (acpi_thermal) trap number=12 ppanic:smp_tlp_shutdown: interrapts disabled cpuid=0 Uptime: 25s Cannot dump. Device not defined or unavailable Automatic reboot in 15 seconds - press a key on the console to abort or switch off the system now --- Loading was spent with options by default (ACPI ON) as at ACPI OFF, the system isn't loaded in general on this notebook (into networks there were similar cases on this model laptop). Drops out too kernel panic at loading if it is necessary - then I will write log. Any thoughts to solve this problem? best regards, Dmitry ___ 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 Which version is it? I also have a probook 4510s and I don't have any problem .. cheers -- Demelier David ___ 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: kernel panic when if_lagg is not loaded.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2010/03/17 00:31, Leslie Jensen wrote: I have set upp aggregation of my wlan and and wired NIC following the instructions in the handbook. http://www.freebsd.org/doc/handbook/network-aggregation.html I forgot to add the if_lagg_load=YES in /boot/loader.conf. When I rebooted I got a kernel panic. Should this be considerd normal or is it something I should report? Secondly I see there'a a reference to the lagg(4) man page. I think it would help future readers of the above page if a comment about loading if_lagg_load=YES in /boot/loader.conf would be added. Panics can hardly be considered normal... I was unable to reproduce the issue though, is it possible for you to get a backtrace and tell us what release are you using? Cheers, - -- Xin LI delp...@delphij.nethttp://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (FreeBSD) iQEcBAEBAgAGBQJLqWtUAAoJEATO+BI/yjfBHSkIAJC1Ooov8JiddJk+3cw9uZsK f2LvLoQerHY+NVwG0yjdXjhj67FWht4piXewNngePzOzjcXJQybfbrFUxW2zDc3X LSrOLSLtf8CKDhdVK+octUUjYyT1lbkeoyf1Ci1y2h/DE7QY360rzfXhA1VfHJCr 3PTcaHsony3AD6Fwcg3U+7hGseL+zxLfV0DwUtyNIhVZHIrp5hElPseVXnxVPFTT nKaaw4AldH6JYOhT1IZWQObMNJgVhCs48LdAwSCCg7x9Bjias606yY3C1RNupXPM 5TxjmMpiQUhBc/MIAU7mAb27SQY2Lwx6+S9S+4HJoVgr2/eMwjCCOYvXxIt5hXs= =BGMq -END PGP SIGNATURE- ___ 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: kernel panic when if_lagg is not loaded.
Leslie Jensen wrote: I have set upp aggregation of my wlan and and wired NIC following the instructions in the handbook. http://www.freebsd.org/doc/handbook/network-aggregation.html I forgot to add the if_lagg_load=YES in /boot/loader.conf. When I rebooted I got a kernel panic. Should this be considerd normal or is it something I should report? No, it's not normal. Please, report it in an explicit way, commands given and/or changes to rc.conf, loader.conf etc. Try first here questions@ and then n...@. Nonetheless I see no such behavior on my system. if_lagg loads automatically when needed(ifconfig lagg create etc). Secondly I see there'a a reference to the lagg(4) man page. I think it would help future readers of the above page if a comment about loading if_lagg_load=YES in /boot/loader.conf would be added. On 8.0-STABLE if_lagg loads automatically and I think it always did load automatically, though I am not sure. What's the FreeBSD version you are working on? Nikos ___ 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: kernel panic when if_lagg is not loaded.
On 2010-03-17 09:36, Nikos Vassiliadis wrote: Leslie Jensen wrote: I have set upp aggregation of my wlan and and wired NIC following the instructions in the handbook. http://www.freebsd.org/doc/handbook/network-aggregation.html I forgot to add the if_lagg_load=YES in /boot/loader.conf. When I rebooted I got a kernel panic. Should this be considerd normal or is it something I should report? No, it's not normal. Please, report it in an explicit way, commands given and/or changes to rc.conf, loader.conf etc. Try first here questions@ and then n...@. Nonetheless I see no such behavior on my system. if_lagg loads automatically when needed(ifconfig lagg create etc). Secondly I see there'a a reference to the lagg(4) man page. I think it would help future readers of the above page if a comment about loading if_lagg_load=YES in /boot/loader.conf would be added. On 8.0-STABLE if_lagg loads automatically and I think it always did load automatically, though I am not sure. What's the FreeBSD version you are working on? Nikos ___ 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 I'm on a 8.0-RELEASE-p2 system. Actually after more testing I found out that the line ifconfig_iwn0=ether 00:16:ea:61:01:e8 in my rc.conf is the culprit. If I comment it out the system will start but only with the wired interface working. I have if_lagg_load=YES in /boot/loader.conf and the following in /etc/rc.conf wpa_supplicant_enable=YES ifconfig_em0=up # ifconfig_iwn0=ether 00:16:ea:61:01:e8 wlans_iwn0=wlan0 ifconfig_wlan0=WPA cloned_interfaces=lagg0 ifconfig_lagg0=laggproto failover laggport em0 laggport wlan0 DHCP /Leslie ___ 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: kernel panic when if_lagg is not loaded.
Leslie Jensen wrote: I'm on a 8.0-RELEASE-p2 system. Actually after more testing I found out that the line ifconfig_iwn0=ether 00:16:ea:61:01:e8 in my rc.conf is the culprit. If I comment it out the system will start but only with the wired interface working. If you don't comment the line it causes a kernel panic? If that's the case, you should report it to n...@. If you could include a backtrace of the panic, it would be most helpful. I have if_lagg_load=YES in /boot/loader.conf and the following in /etc/rc.conf wpa_supplicant_enable=YES ifconfig_em0=up # ifconfig_iwn0=ether 00:16:ea:61:01:e8 wlans_iwn0=wlan0 ifconfig_wlan0=WPA cloned_interfaces=lagg0 ifconfig_lagg0=laggproto failover laggport em0 laggport wlan0 DHCP /Leslie hm, what you do really matches the process described in the handbook. It should work, please report it. Nikos ___ 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: kernel panic on SATA drive
You may wish to check and see if your firmware is up-to-date on all of your disk drives, and your controller. On Mon, Dec 21, 2009 at 10:40:10PM +0200, Alex thus spake: Dear John, Any progress for bellow? I have the same problem with PCI SATA Controller ST-Lab A-173 Sil3512 It's not RAID, but when copying to HDD: LOG--- ad6:FAILURE - device detached g_vfs_done():ad6s1f[WRITE(offset=38007275520, length=131072)]error = 6 /usr: got error 6 while accessing filesystem panic: softdep_deallocate_dependencies: unrecovered I/O error cpuid = 0 Uptime: 2m18s Physical memory: 243 MB Dumping 58 MB:unknown: timeout waiting to issue command unknown: error issuing WRITE_DMA command ** DUMP FAILED (ERROR 5) ** Automatic reboot in 15 seconds - press any key on the console to abort ---END LOG- Brgrds, Alex I've been having an intermittent problem, wonder if someone on the list has any ideas. First my setup: FreeBSD 7.2-RELEASE (amd64) quad-core Phenom processor mobo: MSI K9N2G Neo chipset: NVIDIA GeForce 8200, which FreeBSD recognizes as nForce (not sure how that works) I have a 3ware RAID card (RAID 1), which is the boot device. A seagate drive connected via SATA A WD external drive via USB I will have the system running fine, then the seagate will apparently fall off the bus, resulting in a panic. The dump fails as well, presumably due to the 3ware driver not being able to handle the panic? not sure... If anyone knows a way I can get the dump to succeed, I'd appreciate that info, too. See below output for details. ___ 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-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: kernel panic on SATA drive
On Tue, Dec 22, 2009 at 11:52 AM, Jason jhelf...@e-e.com wrote: = Any progress for bellow? I have the same problem with PCI SATA Controller ST-Lab A-173 Sil3512 It's not RAID, but when copying to HDD: LOG--- ad6:FAILURE - device detached g_vfs_done():ad6s1f[WRITE(offset=38007275520, length=131072)]error = 6 /usr: got error 6 while accessing filesystem panic: softdep_deallocate_dependencies: unrecovered I/O error cpuid = 0 Uptime: 2m18s Physical memory: 243 MB Dumping 58 MB:unknown: timeout waiting to issue command unknown: error issuing WRITE_DMA command ** DUMP FAILED (ERROR 5) ** Automatic reboot in 15 seconds - press any key on the console to abort ---END LOG- Brgrds, Alex I just had a drive do the same, it was dying. -- Adam Vande More ___ 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: Kernel panic
On Wednesday 12 August 2009 08:01:07 Коньков Евгений wrote: Aug 12 15:59:08 host savecore: reboot after panic: integer divide fault Aug 12 15:59:08 host savecore: writing core to vmcore.4 How to obtain which process cause system to reboot? kgdb /boot/kernel/kernel /var/crash/vmcore.4 -- Mel ___ 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: kernel panic - umount xfs partition
... # mount -t xfs -o ro /dev/ad0s2 /mnt # ls /mnt # cp /mnt/my_file /home/zbigniew I forgot add here that I do then # umount /mnt and after that was kernel panic. I'm sorry for the mistake. Zbigniew ___ 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: Kernel Panic
On Friday 22 May 2009 05:30:42 Shawn Badger wrote: Hi, I installed FreeBSD 7.2 Release on a mini nettop (Intel Atom/945gc/ICH7 hardware), and everything seemed to go smoothly. However, when I boot the system and the filesystem checks have been going for awhile, it always ends in a panic. Here's the dump: dev = ad4s1f, block = 1, fs = /usr panic: ffs_blkfree: freeing free block cpuid: 1 uptime: 15m47s Physical memory: 2027 MB Dumping 180 MB: Fatal Trap 12: page fault while in kernel mode ... I am using the default filesystem. Does anyone know what might cause this, and how I can fix it? This will likely go away after booting into single user and running fsck -y. See the archives for various discussions about the problems with background_fsck. -- Mel ___ 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: kernel panic
Peter Jeremy peterjer...@optushome.com.au writes: Kamlesh Patel shilp.ka...@yahoo.com writes: How do i recover the system from this error. I can't reload the loader.old If you press any key during the first spinner [...] You can then enter the name of the program you wish to run - eg /boot/loader.old That won't work - he changed the forth code, not the compiled code. (or directly load /boot/kernel/kernel) That will work. DES -- Dag-Erling Smørgrav - d...@des.no ___ 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: kernel panic
On Mon, Jan 12, 2009 at 6:50 AM, Dag-Erling Smørgrav d...@des.no wrote: Peter Jeremy peterjer...@optushome.com.au writes: Kamlesh Patel shilp.ka...@yahoo.com writes: How do i recover the system from this error. I can't reload the loader.old If you press any key during the first spinner [...] You can then enter the name of the program you wish to run - eg /boot/loader.old That won't work - he changed the forth code, not the compiled code. (or directly load /boot/kernel/kernel) That will work. DES Maybe this? - Grab the liveCD (ftp://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-i386/7.0/7.0-RELEASE-i386-livefs.iso, or ftp://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-amd64/7.0/7.0-RELEASE-amd64-livefs.iso). Don't grab the 7.1 ones because they don't boot on all systems (it's in the release notes). - Mount your system. - chroot /wherever/your/install/is/mounted /bin/tcsh - Repeat steps to compile and install kernel Cheers, -Garrett ___ 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: kernel panic
Garrett Cooper yanef...@gmail.com writes: Dag-Erling Smørgrav d...@des.no writes: Peter Jeremy peterjer...@optushome.com.au writes: If you press any key during the first spinner [...] You can then enter the name of the program you wish to run - eg /boot/loader.old That won't work - he changed the forth code, not the compiled code. [...] - Repeat steps to compile and install kernel which will achieve absolutely nothing, since the bug is in the forth code, not in the kernel or any other compiled code. DES -- Dag-Erling Smørgrav - d...@des.no ___ 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: kernel panic
On 2009-Jan-09 00:05:47 -0800, Kamlesh Patel shilp.ka...@yahoo.com wrote: How do i recover the system from this error. I can't reload the loader.old If you press any key during the first spinner, you should get a prompt similar to the following: FreeBSD/i386 BOOT Default: 0:ad(0,a)/boot/loader boot: You can then enter the name of the program you wish to run - eg /boot/loader.old (or directly load /boot/kernel/kernel) See the following for a more complete description: http://www.freebsd.org/cgi/man.cgi?query=bootapropos=0sektion=0manpath=FreeBSD+7.1-RELEASEformat=html -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. pgpGuVVF4OejW.pgp Description: PGP signature
Re: kernel panic
Kamlesh Patel shilp.ka...@yahoo.com writes: Hi there, I changed the following file of FreeBSD 7.0: sys/boot/forth/beastie.4th variable rebootkey variable mykey (added line) I built and installed kernel, then i reboot the system, it gives me the following error: --- panic: free: guard1 fail @ 0x6e104 from /usr/src/sys/boot/i386/loader/../../common/module.c:959 -- Press a key on the console to reboot -- How do i recover the system from this error. I can't reload the loader.old Could anyone please help me? Can you boot from a CD to fix things up? -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ 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: kernel panic
Update of kernel panic. Rebuilt kernel without 80211node, seems to have cured the panics. Removed all wireless support for now. Thanks to Toni Schmidbauer --- On Thu, 1/1/09, Mark Busby redt...@sbcglobal.net wrote: From: Mark Busby redt...@sbcglobal.net Subject: kernel panic To: help help freebsd-questions@freebsd.org Date: Thursday, January 1, 2009, 2:05 PM I've had a few panics. Attached are the output from vmsat -m then -z. uname -a FreeBSD mars.sbcglobal.net 7.0-RELEASE-p5 FreeBSD 7.0-RELEASE-p5 #0: Mon Nov 24 23:03:01 CST 2008 box...@mars.sbcglobal.net:/usr/src/sys/i386/compile/MARS i386 Jan 1 08:56:39 mars savecore: reboot after panic: kmem_malloc(12288): kmem_map too small: 128778240 total allocated Jan 1 08:56:39 mars savecore: writing core to vmcore.2 ___ 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: kernel panic
At Thu, 1 Jan 2009 12:05:25 -0800 (PST), Mark Busby wrote: Jan 1 08:56:39 mars savecore: reboot after panic: kmem_malloc(12288): kmem_map too small: 128778240 total allocated as you probably already know this means you ran out of kernel memory. 80211node 8081 21705K - 8081 16,32,512 this is the only thing that catches my eye. but i dunno if 21mb for 80211node is an issue or not. but there is definitely something leaking kernel memory. i would try to run vmstat -z on a regular basis (how often depending on when after a boot the crash happens) to find out what is leaking memory. hth, toni -- Don't forget, there is no security | toni at stderror dot at -- Wulfgar | Toni Schmidbauer ___ 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: Kernel panic! 7.0-RELEASE-p4
Thanks, that took care of it. On Wed, Oct 1, 2008 at 4:49 PM, Manolis Kiagias [EMAIL PROTECTED] wrote: Walter Venable wrote: Our box, without readily obvious provocation, started doing this today: Panic: softdep_setup_inomapdep: dependency for new inode already exists. cpuid: 0 physical memory: 1971 MB dumping 78MB: 63 47 31 15 The system then immediately reboots, and hits the panic, reboots, etc. What can I do?? Maybe boot into single user mode and run fsck? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel panic! 7.0-RELEASE-p4
Walter Venable wrote: Our box, without readily obvious provocation, started doing this today: Panic: softdep_setup_inomapdep: dependency for new inode already exists. cpuid: 0 physical memory: 1971 MB dumping 78MB: 63 47 31 15 The system then immediately reboots, and hits the panic, reboots, etc. What can I do?? Maybe boot into single user mode and run fsck? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel Panic help.
Eric Crist wrote: Hey folks, First, please 'reply-all' as I'm not on the list. I've got a backup server that, every night, offloads things to a secondary, USB attached hard disk. We've got two of these disks, which we rotate so as to have a fairly recent off-site version, in the event of a disaster. One of the two drives has start to cause the backup server to core dump and reboot. The other works fine. I tried taking the problematic drive and repartitioning and reformatting it, but the problems persist. Here is what I get from a kgdb: [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC- sudo kgdb kernel.debug /var/crash/vmcore.17 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol ps_pglobal_lookup] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 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 copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-marcel-freebsd. Unread portion of the kernel message buffer: panic: softdep_deallocate_dependencies: dangling deps cpuid = 0 Uptime: 11d20h37m38s Physical memory: 1011 MB Dumping 201 MB: 186 170 154 138 122 106 90 74 58 42 26 10 #0 doadump () at pcpu.h:195 195__asm __volatile(movl %%fs:0,%0 : =r (td)); Any insight is appreciated. uname -a is: FreeBSD hostname 7.0-RELEASE-p3 FreeBSD 7.0-RELEASE-p3 #1: Tue Jul 15 13:53:28 CDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 See the developers handbook for more details on how to report panics (you also need the backtrace, and it may help to catch the problem earlier if you turn on debugging). However, this kind of panic can happen if the drive is marginal. e.g. if it loses or corrupts I/O in transit. Try compiling e.g. the /usr/src/tools/regression/fsx tool and running that against the problem disk for a few days, or even multiple instances on different files at once to really stress it. It will do lots of I/O to a file and verify that the file remains consistent throughout. It won't touch the whole drive though, so if only parts of the disk are bad it won't catch it. For that you could try generating a large random file on another disk, keeping the md5 checksum, then writing lots of copies of it to the bad disk to fill or almost fill it, then read back the md5 checksums of each to compare. A small script could run this in a loop. Yet another option would be to configure the disk as a geli or zfs volume, since that will validate checksums with each read and will catch data corruption anywhere on the disk. I'd validate those things before proceeding with the existing panic. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel Panic: isp - page fault while in kernel mode
Greg Himes wrote: Hello All, Last week, one half of my dual port Qlogic fibre channel interface started causing a page fault panic while probing the second port at boot time. I was able to get the system back up by disabling the BIOS on the second port. The system still sees the 2nd port, but politely displays a few errors, then continues on. This all started after I powered the system down for maintenance. System is running FreeBSD 6.3-RELEASE i386 What is the proper way to help debug this problem? See the developers handbook. Kris P.S. And don't do this, you're crippling your network: WARNING: MPSAFE network stack disabled, expect reduced performance. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel panic: flush_pagedep_deps: flush failed
with backtrace, it looks like: [EMAIL PROTECTED] STORAGE kgdb kernel.debug /var/crash/vmcore.1 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol ps_pglobal_lookup] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 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 copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as amd64-marcel-freebsd. Unread portion of the kernel message buffer: ad8: FAILURE - WRITE_DMA48 timed out LBA=314770767 g_vfs_done():ad8s1a[WRITE(offset=161162592256, length=16384)]error = 5 panic: flush_pagedep_deps: flush failed cpuid = 0 Uptime: 3d15h11m52s Physical memory: 1011 MB Dumping 271 MB: 256 240 224 208 192 176 160 144 128 112 96 80 64 48 32 16 #0 doadump () at pcpu.h:194 194 __asm __volatile(movq %%gs:0,%0 : =r (td)); (kgdb) backtrace #0 doadump () at pcpu.h:194 #1 0x0004 in ?? () #2 0x804abe09 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409 #3 0x804ac20d in panic (fmt=0x104 Address 0x104 out of bounds) at /usr/src/sys/kern/kern_shutdown.c:563 #4 0x8068f122 in softdep_sync_metadata (vp=0xff003c30eba0) at /usr/src/sys/ufs/ffs/ffs_softdep.c:5689 #5 0x806957ae in ffs_syncvnode (vp=0xff003c30eba0, waitfor=Variable waitfor is not available. ) at /usr/src/sys/ufs/ffs/ffs_vnops.c:310 #6 0x8067c6bc in ffs_truncate (vp=0xff003c30eba0, length=328192, flags=2176, cred=0xff0001079d00, td=0xff00049b19c0) at /usr/src/sys/ufs/ffs/ffs_inode.c:268 #7 0x8069b3af in ufs_direnter (dvp=0xff003c30eba0, tvp=0xff0033d5a7c0, dirp=0xa4715640, cnp=Variable cnp is not available. ) at /usr/src/sys/ufs/ufs/ufs_lookup.c:950 #8 0x806a13b7 in ufs_makeinode (mode=Variable mode is not available. ) at /usr/src/sys/ufs/ufs/ufs_vnops.c:2422 #9 0x807a0b90 in VOP_CREATE_APV (vop=Variable vop is not available. ) at vnode_if.c:206 #10 0x8053234d in vn_open_cred (ndp=0xa4715a10, flagp=0xa471595c, cmode=Variable cmode is not available. ) at vnode_if.h:112 #11 0x80530022 in kern_open (td=0xff00049b19c0, path=0x7f3f9760 Address 0x7f3f9760 out of bounds, pathseg=Variable pathseg is not available. ) at /usr/src/sys/kern/vfs_syscalls.c:1028 #12 0x8075dc57 in syscall (frame=0xa4715c70) at /usr/src/sys/amd64/amd64/trap.c:852 #13 0x8074418b in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:290 #14 0x0008011ebe7c in ?? () Previous frame inner to this frame (corrupt stack?) Thomas Herzog wrote: hi, [EMAIL PROTECTED] STORAGE kgdb kernel.debug /var/crash/vmcore.1 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol ps_pglobal_lookup] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 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 copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as amd64-marcel-freebsd. Unread portion of the kernel message buffer: ad8: FAILURE - WRITE_DMA48 timed out LBA=314770767 g_vfs_done():ad8s1a[WRITE(offset=161162592256, length=16384)]error = 5 panic: flush_pagedep_deps: flush failed cpuid = 0 Uptime: 3d15h11m52s Physical memory: 1011 MB Dumping 271 MB: 256 240 224 208 192 176 160 144 128 112 96 80 64 48 32 16 #0 doadump () at pcpu.h:194 194__asm __volatile(movq %%gs:0,%0 : =r (td)); both cores says the same. Thomas Toni Schmidbauer wrote: At Tue, 20 May 2008 07:59:19 +0200, Thomas Herzog wrote: cat /var/crash/info.1 follow this guide: http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-gdb.html and post the results. if nobody answers, open a pr (problem report) http://www.freebsd.org/send-pr.html hth, toni ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel panic: flush_pagedep_deps: flush failed
since i activate ataidle i have this errors: ad8: FAILURE - WRITE_DMA48 timed out LBA=314770799 +ad8: TIMEOUT - READ_DMA retrying (1 retry left) LBA=12207 +ad4: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly after disable it, this messages are gone. so i think its a problem with ataidle, but why this panics the kernel? thomas Thomas Herzog wrote: hi, [EMAIL PROTECTED] STORAGE kgdb kernel.debug /var/crash/vmcore.1 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol ps_pglobal_lookup] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 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 copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as amd64-marcel-freebsd. Unread portion of the kernel message buffer: ad8: FAILURE - WRITE_DMA48 timed out LBA=314770767 g_vfs_done():ad8s1a[WRITE(offset=161162592256, length=16384)]error = 5 panic: flush_pagedep_deps: flush failed cpuid = 0 Uptime: 3d15h11m52s Physical memory: 1011 MB Dumping 271 MB: 256 240 224 208 192 176 160 144 128 112 96 80 64 48 32 16 #0 doadump () at pcpu.h:194 194__asm __volatile(movq %%gs:0,%0 : =r (td)); both cores says the same. Thomas Toni Schmidbauer wrote: At Tue, 20 May 2008 07:59:19 +0200, Thomas Herzog wrote: cat /var/crash/info.1 follow this guide: http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-gdb.html and post the results. if nobody answers, open a pr (problem report) http://www.freebsd.org/send-pr.html hth, toni ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel panic: flush_pagedep_deps: flush failed
At Tue, 20 May 2008 07:59:19 +0200, Thomas Herzog wrote: cat /var/crash/info.1 follow this guide: http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-gdb.html and post the results. if nobody answers, open a pr (problem report) http://www.freebsd.org/send-pr.html hth, toni -- If you understand what you're doing, you're | toni at stderror dot at not learning anything. | Toni Schmidbauer -- Anonymous| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel panic: flush_pagedep_deps: flush failed
hi, [EMAIL PROTECTED] STORAGE kgdb kernel.debug /var/crash/vmcore.1 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol ps_pglobal_lookup] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 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 copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as amd64-marcel-freebsd. Unread portion of the kernel message buffer: ad8: FAILURE - WRITE_DMA48 timed out LBA=314770767 g_vfs_done():ad8s1a[WRITE(offset=161162592256, length=16384)]error = 5 panic: flush_pagedep_deps: flush failed cpuid = 0 Uptime: 3d15h11m52s Physical memory: 1011 MB Dumping 271 MB: 256 240 224 208 192 176 160 144 128 112 96 80 64 48 32 16 #0 doadump () at pcpu.h:194 194 __asm __volatile(movq %%gs:0,%0 : =r (td)); both cores says the same. Thomas Toni Schmidbauer wrote: At Tue, 20 May 2008 07:59:19 +0200, Thomas Herzog wrote: cat /var/crash/info.1 follow this guide: http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-gdb.html and post the results. if nobody answers, open a pr (problem report) http://www.freebsd.org/send-pr.html hth, toni ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic FreeBSD 7.0 - Xorg
On Monday 12 of May 2008 22:22:12 Roland Smith wrote: It might also be a hardware problem. Testing the RAM would be a good place to start. I bought new RAM and tested it with 'memtest' and now is OK (no error was found). Hover I still got kernel panic when I do: # Xorg -configure # Xorg -config /root/xorg.conf.new what is going on? What else can cause such behavior. As I mentioned previously Debian works great on this computer. Maybe it is a bug in Xorg? Maybe someone else had or have such problems with Xorg? I want to work on FreeBSD 7.0, but this problem is very strange. When I work on FreeBSD 6.3 I hadn't such problems - it simply work. Thank you in advance for any help. Best wishes, Zbigniew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic FreeBSD 7.0 - Xorg
On Monday 12 of May 2008 22:22:12 Roland Smith wrote: It might also be a hardware problem. Testing the RAM would be a good place to start. Yes. You are right. I tested my memory with 'memtest' and got one error: Tst Pass Failing AddressGood BadErr-Bits Count 50 00022c8af50 - 556.6 MB efff 1000 1 After this error 'memtest' hang, keyboard was frozen and only pressed the restart button help. So, I will buy new memory. Thank you very much for help Roland and Mel. Thank you. Roland Best wishes, Zbigniew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic FreeBSD 7.0 - Xorg
On Mon, May 12, 2008 at 12:51:26PM +0200, Zbigniew Komarnicki wrote: Hello! I decide to go on FreeBSD 7.0-RELEASE. Before I used 6.3-RELEASE. But now I cannot get working Xorg. I almost get the kernel panic. I install fresh 7.0-RELEASE and update ports by portsnam and everything compiled by ports system. After instalign 'xorg' ports I do the following steps as root: How *exactly* did you upgrade your ports? Sometimes old libraries hang around causing trouble. Xorg -configure X -config /root/xorg.conf.new Why would you do that? If you haven't changed the hardware, there is no need to change xorg.conf. and I got black monitor and after few seconds the system reboots. Then I go to single user and do Check the X logfile (/var/log/Xorg.0.log). Any clues in there? savecore: reboot after panic: vm_fault: fault on nofault entry, addr: e56e8000 savecore: writing core to vmcore.2 This can also help you debug. Load it up in the kernel debugger; kgdb /boot/kernel/kernel.symbols vmcore.2 Then inside the debugger, give the 'bt' command. and then I examine the file xorg.conf.org (I attached the file) and I saw that I have there the following line: Driver radeon In FreeBSD 6.3-RELEASE I had there Driver ati so I change it to ati and do X -config /root/xorg.conf.new but with no result - kernel panic again. What going on here? What kind of graphics card do you have? What does 'pciconf -lv' say? Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgp4FWXUz6p3n.pgp Description: PGP signature
Re: kernel panic FreeBSD 7.0 - Xorg
On Monday 12 of May 2008 16:24:44 Roland Smith wrote: How *exactly* did you upgrade your ports? Sometimes old libraries hang around causing trouble. I simply download the iso file for boot only: 7.0-RELEASE-i386-bootonly.iso Then burn on CD and then install fresh 7.0-RELEASE on hard disk - minimal system. Next I used portsnap to download ports: portsnap fetch [...] Then go to /usr/ports/x11/xorg and: make install clean After that, when I log as normal user and typed: startx got the first kernel panic. Then I used: Xorg -configure X -config /root/xorg.conf.new and again I got kernel panic, and also as mention previous, for drivers ati and radeon, too. Xorg -configure X -config /root/xorg.conf.new Why would you do that? If you haven't changed the hardware, there is no need to change xorg.conf. Because I hadn't the old version xorg.conf from 6.3. I simply format these partitions and forgotten make a backup of /etc especially /etc/X11. and I got black monitor and after few seconds the system reboots. Then I go to single user and do Check the X logfile (/var/log/Xorg.0.log). Any clues in there? I do obtain nothing in /var/log/Xorg.0.log. I only obtain result when I use vesa driver and it is about 10 kB text. But there no any errors form the vesa drivers. From the drivers radon or ati nothing was written, because was kernel panic. savecore: reboot after panic: vm_fault: fault on nofault entry, addr: e56e8000 savecore: writing core to vmcore.2 Now I have vmcore.8 This can also help you debug. Load it up in the kernel debugger; kgdb /boot/kernel/kernel.symbols vmcore.2 Then inside the debugger, give the 'bt' command. I coudn't do that because I obtain the following information (I do not remember exactly) Couldn't find file vmcore.2 I went to the /boot/kernel/ and there really no such file. What kind of graphics card do you have? What does 'pciconf -lv' say? I have: Radeon 9200 SE Series'. It is correctly recognized in xorg.conf.new, but if I remember in 6.3 the driver was ati for such card not radeon. Here is the output: [EMAIL PROTECTED]:0:0:0:class=0x06 card=0x chip=0x01e010de rev=0xc1 hdr=0x00 vendor = 'Nvidia Corp' device = 'nForce2 AGP Controller' class = bridge subclass = HOST-PCI [EMAIL PROTECTED]:0:0:1:class=0x05 card=0x0c1710de chip=0x01eb10de rev=0xc1 hdr=0x00 vendor = 'Nvidia Corp' device = 'nForce2 Memory Controller 1' class = memory subclass = RAM [EMAIL PROTECTED]:0:0:2:class=0x05 card=0x0c1710de chip=0x01ee10de rev=0xc1 hdr=0x00 vendor = 'Nvidia Corp' device = 'nForce2 Memory Controller 4' class = memory subclass = RAM [EMAIL PROTECTED]:0:0:3:class=0x05 card=0x0c1710de chip=0x01ed10de rev=0xc1 hdr=0x00 vendor = 'Nvidia Corp' device = 'nForce2 Memory Controller 3' class = memory subclass = RAM [EMAIL PROTECTED]:0:0:4:class=0x05 card=0x0c1710de chip=0x01ec10de rev=0xc1 hdr=0x00 vendor = 'Nvidia Corp' device = 'nForce2 Memory Controller 2' class = memory subclass = RAM [EMAIL PROTECTED]:0:0:5:class=0x05 card=0x0c1710de chip=0x01ef10de rev=0xc1 hdr=0x00 vendor = 'Nvidia Corp' device = 'nForce2 Memory Controller 5' class = memory subclass = RAM [EMAIL PROTECTED]:0:1:0:class=0x060100 card=0x0c111458 chip=0x008010de rev=0xa3 hdr=0x00 vendor = 'Nvidia Corp' device = 'nForce MCP2S PCI to ISA Bridge' class = bridge subclass = PCI-ISA [EMAIL PROTECTED]:0:1:1:class=0x0c0500 card=0x0c111458 chip=0x008410de rev=0xa1 hdr=0x00 vendor = 'Nvidia Corp' device = 'nForce MCP2S PCI System Management' class = serial bus subclass = SMBus [EMAIL PROTECTED]:0:2:0:class=0x0c0310 card=0x50041458 chip=0x008710de rev=0xa1 hdr=0x00 vendor = 'Nvidia Corp' device = 'nForce MCP2A USB Controller' class = serial bus subclass = USB [EMAIL PROTECTED]:0:2:1:class=0x0c0310 card=0x50041458 chip=0x008710de rev=0xa1 hdr=0x00 vendor = 'Nvidia Corp' device = 'nForce MCP2A USB Controller' class = serial bus subclass = USB [EMAIL PROTECTED]:0:2:2:class=0x0c0320 card=0x50041458 chip=0x008810de rev=0xa2 hdr=0x00 vendor = 'Nvidia Corp' device = 'nForce MCP2A USB Controller' class = serial bus subclass = USB [EMAIL PROTECTED]:0:6:0:class=0x040100 card=0xa0021458 chip=0x008a10de rev=0xa1 hdr=0x00 vendor = 'Nvidia Corp' device = 'nForce AC'97 Audio Codec Interface' class = multimedia subclass = audio [EMAIL PROTECTED]:0:8:0:class=0x060400 card=0x chip=0x008b10de rev=0xa3 hdr=0x01 vendor = 'Nvidia Corp' device = 'nforce MCP2A PCI Bridge' class
Re: kernel panic FreeBSD 7.0 - Xorg
On Mon, May 12, 2008 at 08:34:17PM +0200, Zbigniew Komarnicki wrote: On Monday 12 of May 2008 16:24:44 Roland Smith wrote: How *exactly* did you upgrade your ports? Sometimes old libraries hang around causing trouble. I simply download the iso file for boot only: 7.0-RELEASE-i386-bootonly.iso Then burn on CD and then install fresh 7.0-RELEASE on hard disk - minimal system. Next I used portsnap to download ports: portsnap fetch [...] Did you do a 'portsnap extract' as well? Fetching alone isn't enough. got the first kernel panic. Then I used: Xorg -configure X -config /root/xorg.conf.new and again I got kernel panic, and also as mention previous, for drivers ati and radeon, too. You should definitely use the radeon driver for this hardware. savecore: reboot after panic: vm_fault: fault on nofault entry, addr: e56e8000 savecore: writing core to vmcore.2 Now I have vmcore.8 This can also help you debug. Load it up in the kernel debugger; kgdb /boot/kernel/kernel.symbols vmcore.2 Then inside the debugger, give the 'bt' command. I coudn't do that because I obtain the following information (I do not remember exactly) Couldn't find file vmcore.2 I went to the /boot/kernel/ and there really no such file. Saved cores are kept in /var/crash by default. See dumpdir in /etc/defaults/rc.conf. Try kgdb /boot/kernel/kernel.symbols /var/crash/vmcore.8 What kind of graphics card do you have? What does 'pciconf -lv' say? I have: Radeon 9200 SE Series'. It is correctly recognized in xorg.conf.new, but if I remember in 6.3 the driver was ati for such card not radeon. [EMAIL PROTECTED]:2:0:0: class=0x03 card=0x596412ab chip=0x59641002 rev=0x01 hdr=0x00 vendor = 'ATI Technologies Inc' device = 'Radeon 9200 Radeon 9200 SE Series' class = display subclass = VGA In file: /var/log/dmesg.today I found at the end of file the following entries: pid 23201 (conftest), uid 0: exited on signal 11 (core dumped) pid 34580 (conftest), uid 0: exited on signal 12 (core dumped) Hmm. Signal 12 is non-existant system call invoked. That's one I've never seen before. This was when I run startx as normal user without file xorg.conf in /etc/X11/xorg.conf. So the Xorg server must such file generated on the fly - and the result of course was kernel panic. Why Xorg do kernel panic? It has access to system internals via /dev/mem and /dev/io. So it can potentially screw things up pretty badly. It might also be a hardware problem. Testing the RAM would be a good place to start. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgp09RV72KXgN.pgp Description: PGP signature
Re: kernel panic FreeBSD 7.0 - Xorg
On Monday 12 May 2008 22:22:12 Roland Smith wrote: On Mon, May 12, 2008 at 08:34:17PM +0200, Zbigniew Komarnicki wrote: On Monday 12 of May 2008 16:24:44 Roland Smith wrote: In file: /var/log/dmesg.today I found at the end of file the following entries: pid 23201 (conftest), uid 0: exited on signal 11 (core dumped) pid 34580 (conftest), uid 0: exited on signal 12 (core dumped) Hmm. Signal 12 is non-existant system call invoked. That's one I've never seen before. It's generated by some configure script (conftest), normally nothing to worry about. It's easy to get if you have a jail 'running' 6.x and you haven't set OSREL and/or UNAME_R correctly. Also, some configure scripts just try to invoke linux/posix/apple_syscall_foo to see if it's there. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic FreeBSD 7.0 - Xorg
On Monday 12 of May 2008 22:22:12 Roland Smith wrote: How *exactly* did you upgrade your ports? Sometimes old libraries hang around causing trouble. I used portsnap to download ports: portsnap fetch [...] Did you do a 'portsnap extract' as well? Fetching alone isn't enough. Yes of course. I first use 'portsnap update', but the portsnap told me that the ports was not created by portsnap and gave me what to do next. So I do it and everythings go on succesfull after that. You should definitely use the radeon driver for this hardware. I use on this computer also Debian lenny and everythings works well also Xorg. But in xorg.conf on Debian I have ati driver not radeon. The Xorg have the following version on Debian: X.Org X Server 1.4.0.90 Release Date: 5 September 2007 X Protocol Version 11, Revision 0 Build Operating System: Linux Debian (xorg-server 2:1.4.1~git20080131-4) Current Operating System: Linux komp1 2.6.24-1-686 #1 SMP Sat Apr 19 00:37:55 UTC 2008 i686 Build Date: 29 April 2008 08:24:00PM Saved cores are kept in /var/crash by default. See dumpdir in /etc/defaults/rc.conf. Try kgdb /boot/kernel/kernel.symbols /var/crash/vmcore.8 I will try it. Thank you. Why Xorg do kernel panic? It has access to system internals via /dev/mem and /dev/io. So it can potentially screw things up pretty badly. I understand. It might also be a hardware problem. Testing the RAM would be a good place to start. I check it. I run memtest today. It is strange why on Debian it works but here not? Thank you very much Roland. Roland Best wishes, Zbigniew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel Panic with heavy disk i/o while running on battery
Nathan Alan Souer wrote: Nathan Alan Souer wrote: In advance, I appreciate any help that anyone has to offer. When my laptop is running on battery and there is heavy i/o on the disk The machine kernel panics and reboots. I have updated my base system to current (7_releng) just a couple days ago in an effort to resolve this issue, to no change. I would start with a memory test program. I have seen similar things happen with broken memory. the machine passes a full pass of memtest86+ Just checking - you did the test in the same conditions (on battery power) as the crash? I have a suggestion that's a bit silly but it might help - can you boot of a live/fixit CD and calculate a hash of the drive's content, on and off AC power, to see if it's a hardware problem with the controller or the drive? (dd if=/dev/drive bs=1m | md5) signature.asc Description: OpenPGP digital signature
Re: Kernel Panic with heavy disk i/o while running on battery
Nathan Alan Souer [EMAIL PROTECTED] writes: In advance, I appreciate any help that anyone has to offer. When my laptop is running on battery and there is heavy i/o on the disk The machine kernel panics and reboots. I have updated my base system to current (7_releng) just a couple days ago in an effort to resolve this issue, to no change. Here are the last few lines of the kernel panic (as read through strings): panic: initiate_write_filepage: dir inum 1576702754 != new 0 cpuid = 0 Uptime: 1h42m24s Physical memory: 1003 MB Dumping 147 MB: 132 116 100 84 68 52 36 20 4 Should I just look into disabling acpi? Do a test with ACPI disabled and see if you can reproduce the problem. It probably will make no difference, but it's worth checking. If it doesn't affect the outcome, then looking at more of the panic message would be the next step. Then doing kernel debugging (instructions in the Handbook, I think; or maybe the developers handbook). Good luck. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel Panic with heavy disk i/o while running on battery
The machine passed the memory test while on battery fine. however, while on battery the checksum failed with i/o errors, it did complete the checksum normally while on AC. I think my next step will be to try and disable acpi, and to try and reproduce the error again. i suppose it could be an issue with a flakey controller, but I havent seen any related issues while I was running windows or ubuntu on the machine. if it isn't an issue with power management, I guess I'll learn some kernel debugging. Nathan Alan Souer wrote: Nathan Alan Souer wrote: In advance, I appreciate any help that anyone has to offer. When my laptop is running on battery and there is heavy i/o on the disk The machine kernel panics and reboots. I have updated my base system to current (7_releng) just a couple days ago in an effort to resolve this issue, to no change. I would start with a memory test program. I have seen similar things happen with broken memory. the machine passes a full pass of memtest86+ Just checking - you did the test in the same conditions (on battery power) as the crash? I have a suggestion that's a bit silly but it might help - can you boot of a live/fixit CD and calculate a hash of the drive's content, on and off AC power, to see if it's a hardware problem with the controller or the drive? (dd if=/dev/drive bs=1m | md5) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel Panic with heavy disk i/o while running on battery
Nathan Alan Souer wrote: In advance, I appreciate any help that anyone has to offer. When my laptop is running on battery and there is heavy i/o on the disk The machine kernel panics and reboots. I have updated my base system to current (7_releng 2/9/08) just a couple days ago in an effort to resolve this issue, to no change. I would start with a memory test program. I have seen similar things happen with broken memory. The machine just made it throug a whole pass of memtest86+. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel Panic with heavy disk i/o while running on battery
Nathan Alan Souer wrote: In advance, I appreciate any help that anyone has to offer. When my laptop is running on battery and there is heavy i/o on the disk The machine kernel panics and reboots. I have updated my base system to current (7_releng) just a couple days ago in an effort to resolve this issue, to no change. I would start with a memory test program. I have seen similar things happen with broken memory. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel Panic with heavy disk i/o while running on battery
Nathan Alan Souer wrote: In advance, I appreciate any help that anyone has to offer. When my laptop is running on battery and there is heavy i/o on the disk The machine kernel panics and reboots. I have updated my base system to current (7_releng) just a couple days ago in an effort to resolve this issue, to no change. I would start with a memory test program. I have seen similar things happen with broken memory. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] the machine passes a full pass of memtest86+ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic 6.2-RELEASE SMP dual quad core
Iain Dooley wrote: hi all, uname -a FreeBSD HOSTNAME 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan 12 11:05:30 UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP i386 running on dual quad core intel xeons with 4gb ram. my server has been rebooting quite a bit and stopped responding today. i found this on the console: Fatal trap: 12 page fault while in kernel mode cpuid = 5; apic id = 05 fault virtual address = 0x0 fault code = supervisor write, page not present instruction pointer = 0x20:0xc0880472 stack pointer = 0x28:0xe6ea9c8c code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = 12 (idle: cpu5) trap number = 12 panic: page fault cpuid = 5 uptime 24m41s cannot dump. no dump device specified i've configured the dump device and will follow the kernel debugging details in the handbook if it happens again but i thought i'd write in now in case the cause of the problem jumped out at anyone. i've run mprime for 24 hours, and memtest for 3 passes, and a script i wrote which just exhausts ram and CPU, then backs off and does it again which have been running for 24 hours. i've also just started running this: http://www.holm.cc/stress/ i noticed that the same fatal trap 12 appeared during stress tests as listed here: http://people.freebsd.org/~pho/stress/log/cons224.html any help, guidance or information would be much appreciated. What you have so far is close to meaningless. The fault virtual address = 0x0 means little more than somewhere in the kernel there was a null pointer dereference. The fact that it was the idle process is suspicious though, it suggests that hardware failure is a high probability. Please follow up with the backtrace if you want to pursue this further. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic 6.2-RELEASE SMP dual quad core
uname -a FreeBSD HOSTNAME 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan 12 11:05:30 UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP i386 running on dual quad core intel xeons with 4gb ram. my server has been rebooting quite a bit and stopped responding today. i found this on the console: Fatal trap: 12 page fault while in kernel mode cpuid = 5; apic id = 05 fault virtual address = 0x0 fault code = supervisor write, page not present instruction pointer = 0x20:0xc0880472 stack pointer = 0x28:0xe6ea9c8c code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = 12 (idle: cpu5) trap number = 12 panic: page fault cpuid = 5 uptime 24m41s cannot dump. no dump device specified i've configured the dump device and will follow the kernel debugging details in the handbook if it happens again but i thought i'd write in now in case the cause of the problem jumped out at anyone. i've run mprime for 24 hours, and memtest for 3 passes, and a script i wrote which just exhausts ram and CPU, then backs off and does it again which have been running for 24 hours. i've also just started running this: http://www.holm.cc/stress/ i noticed that the same fatal trap 12 appeared during stress tests as listed here: http://people.freebsd.org/~pho/stress/log/cons224.html any help, guidance or information would be much appreciated. What you have so far is close to meaningless. The fault virtual address = 0x0 means little more than somewhere in the kernel there was a null pointer dereference. The fact that it was the idle process is suspicious though, it suggests that hardware failure is a high probability. Please follow up with the backtrace if you want to pursue this further. I thought that dodgy ram was the culprit. I've run memtest86 on three passes with no errrors reported although I've also read numerous reports on the net of memtest86 not being very effective. can you suggest a good method of stress testing ram? this is a new machine and still under warranty so if it's a ram issue I can easily just get it replaced. Cheers, Iain ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic 6.2-RELEASE SMP dual quad core
Iain Dooley wrote: hi all, uname -a FreeBSD HOSTNAME 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan 12 11:05:30 UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP i386 running on dual quad core intel xeons with 4gb ram. Are you using PAE? (probably not if this is the generic SMP configuration). Fatal trap: 12 page fault while in kernel mode This only means an equivalent of segmentation fault for user-mode programs. The actual problem can be anything. current process = 12 (idle: cpu5) This is important. The idle process does literary nothing and is highly unlikely to contain a bug. Does this mean that the problem only appears when the system is idle? i've run mprime for 24 hours, and memtest for 3 passes, and a script i wrote which just exhausts ram and CPU, then backs off and does it again which have been running for 24 hours. Do your tests stress multiple CPUs? If not, this may be something to try. Also try disabling CPUs to see if it makes any difference. By the way, you are likely not to get any performance benefits (and some performance regressions are likely) with this number of CPUs on FreeBSD 6.2, except if you intend to do CPU-intensive tasks (like scientific caluclations). If you can, try the latest release candidate of 7.0. signature.asc Description: OpenPGP digital signature
Re: kernel panic 6.2-RELEASE SMP dual quad core
hi ivan, uname -a FreeBSD HOSTNAME 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan 12 11:05:30 UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP i386 running on dual quad core intel xeons with 4gb ram. Are you using PAE? (probably not if this is the generic SMP configuration). no, i checked and i'm not using PAE. current process = 12 (idle: cpu5) This is important. The idle process does literary nothing and is highly unlikely to contain a bug. Does this mean that the problem only appears when the system is idle? hmm maybe i should leave the system idle and see if it crashes again :) i've been running an application which just loads up RAM with lots of processes keeping at least 32 processes running at all times. each script is killed when it uses too much space. the machine hasn't crashed again for like 2 days. i'm going away so i might leave it idle for that time and see if it crashes again. i've got a dump device setup this time which will give me more information to send into the list. By the way, you are likely not to get any performance benefits (and some performance regressions are likely) with this number of CPUs on FreeBSD 6.2, except if you intend to do CPU-intensive tasks (like scientific caluclations). If you can, try the latest release candidate of 7.0. i'm just running a web application on it. it's a total pain though. i should have just bought a late model second hand p4 or something rather than a state of the art machine. i'm too out of touch with modern hardware to have known what i was getting myself into. live and learn i guess. cheers iain ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic 6.2-RELEASE SMP dual quad core
Iain Dooley wrote: i'm just running a web application on it. it's a total pain though. i should have just bought a late model second hand p4 or something rather than a state of the art machine. i'm too out of touch with modern hardware to have known what i was getting myself into. live and learn i guess. Quad core Xeons are not exactly unusual or significantly different nowadays. I and many other people have been running them with FreeBSD without problems almost since they were made. signature.asc Description: OpenPGP digital signature
Re: Kernel panic; fatal trap 12; on task 22, USB0: was Re: Moused issues?
On Saturday 06 October 2007, Joe Altman wrote: chthonic.com/crash-crash-crash Hi, Do you have options KDB in your kernel config file ? http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-options.html You should get a prompt when it panics. Then you type in bt for backtrace. Maybe you could take a picture of that. Probably someone is accessing a NULL pointer. --HPS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel panic; fatal trap 12; on task 22, USB0: was Re: Moused issues?
On Sun, Oct 07, 2007 at 11:01:41AM +0200, Hans Petter Selasky wrote: On Saturday 06 October 2007, Joe Altman wrote: chthonic.com/crash-crash-crash Hi, Do you have options KDB in your kernel config file ? Following your suggestion, I did try this; and there was no change from kernel panic and reboot. http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-options.html You should get a prompt when it panics. There was no prompt. Then you type in bt for backtrace. Maybe you could take a picture of that. Personally, it's a bit embarassing to be so helpless that I am forced to take a picture. I suppose if I could be certain about how to compile bootblocks, I might be able to do something on the serial console with a laptop. But the one time I attempted that was a disaster. Is my speculation about the ...no dump device found... correct? Is it that swapon and multiuser has not occurred, and so there can occur no dump to the swap space? Probably someone is accessing a NULL pointer. If any more damage occurs, ISTM that my entire installation will be accessing a NULL pointer; the following message is from the most recent dmesg, and is new: warning: KLD '/boot/kernel.old.bootable/drm.ko' is newer than the linker.hints file Since my hardware appears to not work with the available source, who knows how that will go? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic installing 5.4-release (2'nd attempt)
On Wed, Apr 04, 2007 at 05:51:55PM -0400, m yelle wrote: I tried posting this earlier, but it appears my message didn't post. Please pardon if it did post without my noticing It did, and I already replied to you. Please read your email. Kris pgpMcBpZurU26.pgp Description: PGP signature
Re: kernel panic installing 5.4-release
Because it's an *old* server, and because 5.4-r should be a mature enough distribution by now that any bugs which were going to be fixed would already be fixed. I could only find one reference to a problem like this one, and in that case it was happening in 6.x, which indicates that whatever the problem is, it hasn't been fixed. Which implies that it's either considered to be not a problem by way of an easy workaround, or that it's not an important problem due to not happening very often. Either way, an answer to the question at hand would be much appreciated. --- Kris Kennaway [EMAIL PROTECTED] wrote: On Wed, Apr 04, 2007 at 03:00:34PM -0400, m yelle wrote: I'm attempting to install 5.4-r on an old server which has been running 4.9-stable for the last few years without any problems, with longest uptime of just over 6 months. I'm installing to a tested clean/blank scsi hdd. Why are you installing a version of FreeBSD that is nearly 2 years old? How about trying modern versions before writing off FreeBSD on your hardware:) Kris __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic installing 5.4-release
On Wed, Apr 04, 2007 at 08:28:56PM -0400, m yelle wrote: Because it's an *old* server, and because 5.4-r should be a mature enough distribution by now that any bugs which were going to be fixed would already be fixed. Sorry, that's just not how it works :) FreeBSD 6.2 supports the same hardware, and has 2 years of further bug fixes. In addition 5.4 is no longer supported (it is not even the most recent 5.x release!) I could only find one reference to a problem like this one, and in that case it was happening in 6.x, which indicates that whatever the problem is, it hasn't been fixed. No, it indicates that there was another problem which: * may or may not be the same as yours. Similar panic string is no indication of cause. * may or may not be fixed, because 6.x encompasses several years of releases and bugfixes. Which implies that it's either considered to be not a problem by way of an easy workaround, or that it's not an important problem due to not happening very often. Either way, an answer to the question at hand would be much appreciated. Please update to 6.2 and file a bug report if the problem persists. Kris pgpXD7OoWJrAl.pgp Description: PGP signature
Re: kernel panic installing 5.4-release
On Wed, Apr 04, 2007 at 03:00:34PM -0400, m yelle wrote: I'm attempting to install 5.4-r on an old server which has been running 4.9-stable for the last few years without any problems, with longest uptime of just over 6 months. I'm installing to a tested clean/blank scsi hdd. Why are you installing a version of FreeBSD that is nearly 2 years old? How about trying modern versions before writing off FreeBSD on your hardware:) Kris pgpY3NnWWsygB.pgp Description: PGP signature
Re: kernel panic at boot on any 6.x OS
- Original Message - From: Mike Meyer [EMAIL PROTECTED] To: Ted Mittelstaedt [EMAIL PROTECTED] Cc: Joe Auty [EMAIL PROTECTED]; Daan Vreeken [PA4DAN] [EMAIL PROTECTED]; Kip Macy [EMAIL PROTECTED]; freebsd-questions@freebsd.org; freebsd-hackers@freebsd.org Sent: Monday, February 26, 2007 8:36 AM Subject: Re: kernel panic at boot on any 6.x OS and do a make deinstall followed by downloading and compiling the program the old fashioned way I shoot for a min of 3 years on the OS before even thinking about updating, and when it's time to update the hardware has generally reached the old rag stage anyway. This works great for servers, that don't have any real users on them, and is pretty much how I do things. I'll try updating the ports tree and installing from that rather than building the old fashioned way, because that works a surprising percentage of the time. On desktop and development systems, the users tend to get pissed if I let things get that old. So I do upgrade them more often. That depends on who's paying for it. If your in-house support your screwed of course, since all of them think your labor hours are inexhaustable. But if the users are in a small business or whatever that has to actually pay real money to have their systems updated, then they are usually a lot less enthusiastic about new updates (at least, their owners are) There are a couple of things you can do to make reinstalling to a clean disk a bit less painfull. 1) Intelligent file system layout. I put all the things that aren't installed from the FreeBSD disks on their own partitions (/home and /local). I can then wipe and reinstall /, /var and /usr without clobbering the non-system data. 2) Mirrored disks. Disks for consumer systems are cheap. Throwing a second one in a system and mirroring the system disk is a cheap way to improve the reliability of the system. When it's time to upgrade, take a drive out of the mirror, and install to that drive. You can reboot to the old system if you need to interrupt the process and run the old system for some reason. With a file system layout as per #1, you can even mount the users files under both versions of the OS. When you're happy with the new system, mirror the new system drive to the old one. I do the mirroring thing too but the one thing you have to watch is inadequate cooling in some of these minitowers. Stacking the disks on top of each other with no cooling fan blowing air on them is not a good idea. Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic at boot on any 6.x OS *SOLVED!*
Joe Auty [EMAIL PROTECTED] writes: I guess the trick here was not considering that user space apps would be trying to do a kldload, and that calling upon a module that is either missing in /boot/kernel or /boot/modules or resides outside of /boot can trigger these panics. That is because they are *not* user-space applications. They are kernel-space code. There is a PORTS_MODULES variable documented for make.conf(5) which is intended for just this problem. I haven't used it, though, and offhand I can't find the macro definition for it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic at boot on any 6.x OS
- Original Message - From: Joe Auty [EMAIL PROTECTED] To: Ted Mittelstaedt [EMAIL PROTECTED] Cc: Daan Vreeken [PA4DAN] [EMAIL PROTECTED]; Kip Macy [EMAIL PROTECTED]; freebsd-questions@freebsd.org; freebsd-hackers@freebsd.org Sent: Sunday, February 25, 2007 10:39 PM Subject: Re: kernel panic at boot on any 6.x OS -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Feb 25, 2007, at 7:56 PM, Ted Mittelstaedt wrote: - Original Message - From: Joe Auty [EMAIL PROTECTED] To: Daan Vreeken [PA4DAN] [EMAIL PROTECTED] Cc: Kip Macy [EMAIL PROTECTED]; freebsd-questions@freebsd.org; freebsd-hackers@freebsd.org Sent: Sunday, February 25, 2007 8:14 AM Subject: Re: kernel panic at boot on any 6.x OS Any idea how this could have happened after disabling everything in my /etc/loader.conf, and simply running a: make buildworld make buildkernel KERNCONF=myconfig make installkernel KERNCONF=myconfig well your supposed to do this single-user, run mergemaster and a few other things. I also don't see a make installworld. I usually perform those steps after I've rebooted to ensure that my system will boot off the new kernel, as per the instructions in the FreeBSD handbook. Joe, please try booting from a 6.2-release install ISO. If it works without panicing, then you did something wrong during the upgrade. Downloading the image now, I'll let you know if I'm able to boot from it... Since by your own admission your not an expert, you would be well advised to simply back up your files the old fashioned way, reformat your hard disk, install from a 6.2 boot ISO, then restore your files. Leave the fancy in-place updating to someone else. It's a big PIA and doesen't work half the time anyway. How well does simply upgrading with the CD work (as opposed to wiping clean)? I've upgraded several times to new releases simply by rebuilding world, it has never failed me in the past. I don't doubt what you are saying here, but since I will have to change how I work, assuming that I can boot off of the 6.2 CD, I'd appreciate any general upgrade tips that don't involve wiping the disk clean (which is not really an option). If wiping the disk really isn't an option then you have one or more of the following problems: 1) Production system with a lack of hardware spares 2) inadequate backup plan and execution. People who state that wiping the disk isn't an option are screaming at the top of their lungs for the hardware gremlins to explain what MTBF is all about. The gremlins will visit you, I guarentee. And they always pick the very best times for it too. I just hope (if this is your workplace) that your job survives. For instance, is rebuilding world between point releases (e.g. 5.4 to 5.5) an okay idea, compared to across major releases (e.g. 5.5 to 6.2)? I'll do my own homework regarding this too, but I appreciate any nuggets of wisdom you might have! As far as me being an expert, I guess I'd categorize me somewhere in between complete newb and FreeBSD developer =) The problem is that all of the ports and packages that you put on a server change from release to release. The developers of openssl, for example, don't give a tinkers damn about how FreeBSD's upgrade process works, when they are making changes in their code. I run a number of FreeBSD servers and what I do is simply keep them patched with security updates. Every once in a while a security hole will be discovered in a non-core program and if it's serious enough I'll go into the port and do a make deinstall followed by downloading and compiling the program the old fashioned way I shoot for a min of 3 years on the OS before even thinking about updating, and when it's time to update the hardware has generally reached the old rag stage anyway. Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic at boot on any 6.x OS
On Feb 26, 2007, at 8:01 AM, Ted Mittelstaedt wrote: - Original Message - From: Joe Auty [EMAIL PROTECTED] To: Ted Mittelstaedt [EMAIL PROTECTED] Cc: Daan Vreeken [PA4DAN] [EMAIL PROTECTED]; Kip Macy [EMAIL PROTECTED]; freebsd-questions@freebsd.org; freebsd-hackers@freebsd.org Sent: Sunday, February 25, 2007 10:39 PM Subject: Re: kernel panic at boot on any 6.x OS -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Feb 25, 2007, at 7:56 PM, Ted Mittelstaedt wrote: - Original Message - From: Joe Auty [EMAIL PROTECTED] To: Daan Vreeken [PA4DAN] [EMAIL PROTECTED] Cc: Kip Macy [EMAIL PROTECTED]; freebsd- [EMAIL PROTECTED]; freebsd-hackers@freebsd.org Sent: Sunday, February 25, 2007 8:14 AM Subject: Re: kernel panic at boot on any 6.x OS Any idea how this could have happened after disabling everything in my /etc/loader.conf, and simply running a: make buildworld make buildkernel KERNCONF=myconfig make installkernel KERNCONF=myconfig well your supposed to do this single-user, run mergemaster and a few other things. I also don't see a make installworld. I usually perform those steps after I've rebooted to ensure that my system will boot off the new kernel, as per the instructions in the FreeBSD handbook. Joe, please try booting from a 6.2-release install ISO. If it works without panicing, then you did something wrong during the upgrade. Downloading the image now, I'll let you know if I'm able to boot from it... Since by your own admission your not an expert, you would be well advised to simply back up your files the old fashioned way, reformat your hard disk, install from a 6.2 boot ISO, then restore your files. Leave the fancy in-place updating to someone else. It's a big PIA and doesen't work half the time anyway. How well does simply upgrading with the CD work (as opposed to wiping clean)? I've upgraded several times to new releases simply by rebuilding world, it has never failed me in the past. I don't doubt what you are saying here, but since I will have to change how I work, assuming that I can boot off of the 6.2 CD, I'd appreciate any general upgrade tips that don't involve wiping the disk clean (which is not really an option). If wiping the disk really isn't an option then you have one or more of the following problems: 1) Production system with a lack of hardware spares 2) inadequate backup plan and execution. People who state that wiping the disk isn't an option are screaming at the top of their lungs for the hardware gremlins to explain what MTBF is all about. The gremlins will visit you, I guarentee. And they always pick the very best times for it too. I just hope (if this is your workplace) that your job survives. My production system is backed up daily to two different sites, that's not an issue. The system I'm thinking of upgrading to 6.2 is my test server I run out of my house that stores movie files and other non-essential files. Technically, wiping it clean *would* be an option if it came down to it, just an inconvenience. Perhaps I should invest in another HD to use for instances such as this. For instance, is rebuilding world between point releases (e.g. 5.4 to 5.5) an okay idea, compared to across major releases (e.g. 5.5 to 6.2)? I'll do my own homework regarding this too, but I appreciate any nuggets of wisdom you might have! As far as me being an expert, I guess I'd categorize me somewhere in between complete newb and FreeBSD developer =) The problem is that all of the ports and packages that you put on a server change from release to release. The developers of openssl, for example, don't give a tinkers damn about how FreeBSD's upgrade process works, when they are making changes in their code. I run a number of FreeBSD servers and what I do is simply keep them patched with security updates. Every once in a while a security hole will be discovered in a non-core program and if it's serious enough I'll go into the port and do a make deinstall followed by downloading and compiling the program the old fashioned way I shoot for a min of 3 years on the OS before even thinking about updating, and when it's time to update the hardware has generally reached the old rag stage anyway. Do you run any non-production machines where you test running newer OSes and test software updates and such? --- Joe Auty NetMusician: web publishing software for musicians http://www.netmusician.org [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic at boot on any 6.x OS
In [EMAIL PROTECTED], Ted Mittelstaedt [EMAIL PROTECTED] typed: For instance, is rebuilding world between point releases (e.g. 5.4 to 5.5) an okay idea, compared to across major releases (e.g. 5.5 to 6.2)? For the record, I do a rebuild between point releases - actually, I track -stable on those systems, but do the wipe reinstall across major releases. I run a number of FreeBSD servers and what I do is simply keep them patched with security updates. Every once in a while a security hole will be discovered in a non-core program and if it's serious enough I'll go into the port and do a make deinstall followed by downloading and compiling the program the old fashioned way I shoot for a min of 3 years on the OS before even thinking about updating, and when it's time to update the hardware has generally reached the old rag stage anyway. This works great for servers, that don't have any real users on them, and is pretty much how I do things. I'll try updating the ports tree and installing from that rather than building the old fashioned way, because that works a surprising percentage of the time. On desktop and development systems, the users tend to get pissed if I let things get that old. So I do upgrade them more often. There are a couple of things you can do to make reinstalling to a clean disk a bit less painfull. 1) Intelligent file system layout. I put all the things that aren't installed from the FreeBSD disks on their own partitions (/home and /local). I can then wipe and reinstall /, /var and /usr without clobbering the non-system data. 2) Mirrored disks. Disks for consumer systems are cheap. Throwing a second one in a system and mirroring the system disk is a cheap way to improve the reliability of the system. When it's time to upgrade, take a drive out of the mirror, and install to that drive. You can reboot to the old system if you need to interrupt the process and run the old system for some reason. With a file system layout as per #1, you can even mount the users files under both versions of the OS. When you're happy with the new system, mirror the new system drive to the old one. Neither of these is an excuse for not backing up your data before you start the process. Given the above, the backups are for disaster recovery, so you don't need full level 0 dumps, just up-to-date incrementals. So if you're running daily backups, this should be easy: drop into single user, and run an incremental since the last daily, which typically takes me a few minutes. mike -- Mike Meyer [EMAIL PROTECTED] http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic at boot on any 6.x OS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Well, My system does boot off of disc 1 of the FreeBSD 6.2 CD. However, even when copying the /boot directory from the CD to my machine, it still produces the same kernel panic, even when starting in safe mode. I've run a memtest, and it checked out fine. There must be something in my user space or world that it barfs on. I guess I will try a clean install and rebuild at some point... If you have any other ideas, I'm all ears! Here is my error message again (with verbose logging enabled, although that has no effect on this output): WARNING: Device driver Fatal trap 12: page fault while in kernel mode fault virtual address = 0x40 fault code = supervisor read, page not present instruction pointer = 0x20:0xc06d4614 stack pointer = 0x28:0xf015491c frame pointer = 0x28:0xf015491c code segment = base 0x0, limit 0xff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interupt enabled, resume, IOPL = 0 current process = 898 (kldload) trap number = 12 panic: page fault uptime: 36s cannot dump. No dump device defined automatic reboot in 15 seconds Thanks again for your time! - --- Joe Auty NetMusician: web publishing software for musicians http://www.netmusician.org [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (Darwin) iD4DBQFF42FSCgdfeCwsL5ERArNQAJ9pEyu3ZT3BXe4YhEsgRsid6fB+SwCXeGjO fO0GeeBUPKKYq4N5rRHDTw== =PgI8 -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic at boot on any 6.x OS
It looks like it may be loading an out of sync kernel module. Cleaning out /boot/modules might help. -Kip On 2/26/07, Joe Auty [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Well, My system does boot off of disc 1 of the FreeBSD 6.2 CD. However, even when copying the /boot directory from the CD to my machine, it still produces the same kernel panic, even when starting in safe mode. I've run a memtest, and it checked out fine. There must be something in my user space or world that it barfs on. I guess I will try a clean install and rebuild at some point... If you have any other ideas, I'm all ears! Here is my error message again (with verbose logging enabled, although that has no effect on this output): WARNING: Device driver Fatal trap 12: page fault while in kernel mode fault virtual address = 0x40 fault code = supervisor read, page not present instruction pointer = 0x20:0xc06d4614 stack pointer = 0x28:0xf015491c frame pointer = 0x28:0xf015491c code segment = base 0x0, limit 0xff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interupt enabled, resume, IOPL = 0 current process = 898 (kldload) trap number = 12 panic: page fault uptime: 36s cannot dump. No dump device defined automatic reboot in 15 seconds Thanks again for your time! - --- Joe Auty NetMusician: web publishing software for musicians http://www.netmusician.org [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (Darwin) iD4DBQFF42FSCgdfeCwsL5ERArNQAJ9pEyu3ZT3BXe4YhEsgRsid6fB+SwCXeGjO fO0GeeBUPKKYq4N5rRHDTw== =PgI8 -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic at boot on any 6.x OS
On 2007-Feb-26 17:38:10 -0500, Joe Auty [EMAIL PROTECTED] wrote: My system does boot off of disc 1 of the FreeBSD 6.2 CD. That's a good start. Together with your memtest results, it suggests that your hardware is OK. However, even when copying the /boot directory from the CD to my machine, it still produces the same kernel panic, even when starting in safe mode. Can you confirm that you have either deleted or renamed /boot before replacing it with files from the CD. An out-of-sync module does sound the most likely problem. If that doesn't help, please start DDB and get a backtrace. I've run a memtest, and it checked out fine. Note that memtest cannot prove that your system doesn't have a problem. There are far too many states that your system could potentially be in. DRAM is especially susceptable to pattern- dependent and temporal glitches. There must be something in my user space or world that it barfs on. I guess I will try a clean install and rebuild at some point... If you're not sure where this is being triggered, you could try adding 'rc_debug=YES' to your rc.conf (or even a 'set -x' if you are getting really desperate). This will make the boot sequence far more verbose. -- Peter Jeremy pgp5OsUZbqlxs.pgp Description: PGP signature
Re: kernel panic at boot on any 6.x OS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Unfortunately, my /boot/modules is already empty =( On Feb 26, 2007, at 9:51 PM, Kip Macy wrote: It looks like it may be loading an out of sync kernel module. Cleaning out /boot/modules might help. -Kip On 2/26/07, Joe Auty [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Well, My system does boot off of disc 1 of the FreeBSD 6.2 CD. However, even when copying the /boot directory from the CD to my machine, it still produces the same kernel panic, even when starting in safe mode. I've run a memtest, and it checked out fine. There must be something in my user space or world that it barfs on. I guess I will try a clean install and rebuild at some point... If you have any other ideas, I'm all ears! Here is my error message again (with verbose logging enabled, although that has no effect on this output): WARNING: Device driver Fatal trap 12: page fault while in kernel mode fault virtual address = 0x40 fault code = supervisor read, page not present instruction pointer = 0x20:0xc06d4614 stack pointer = 0x28:0xf015491c frame pointer = 0x28:0xf015491c code segment = base 0x0, limit 0xff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interupt enabled, resume, IOPL = 0 current process = 898 (kldload) trap number = 12 panic: page fault uptime: 36s cannot dump. No dump device defined automatic reboot in 15 seconds Thanks again for your time! - --- Joe Auty NetMusician: web publishing software for musicians http://www.netmusician.org [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (Darwin) iD4DBQFF42FSCgdfeCwsL5ERArNQAJ9pEyu3ZT3BXe4YhEsgRsid6fB+SwCXeGjO fO0GeeBUPKKYq4N5rRHDTw== =PgI8 -END PGP SIGNATURE- ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers- [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (Darwin) iD8DBQFF47d2CgdfeCwsL5ERAg/iAKCLVp7f+SB/f2xbT43lu4IeQWJxuACfa+L1 tpwQkQetPAVf53uCTA3hr6A= =ej7q -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic at boot on any 6.x OS *SOLVED!*
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sort of... Thanks for everybody that has helped me! It turns out I had a couple of rc.d scripts in /usr/local/etc/rc.d that were doing kldloads: rtc.sh and kqemu.sh - one of these was causing the panic. It might be worthwhile adding to the world rebuild doc a suggestion to grep kldload /usr/local/etc/rc.d and disable/ remove these services... Or, simply moving /usr/local/etc/rc.d might also be worthwhile test. I guess the trick here was not considering that user space apps would be trying to do a kldload, and that calling upon a module that is either missing in /boot/kernel or /boot/modules or resides outside of /boot can trigger these panics. Always the most simple of solutions that kicks you in the ass, isn't it? =) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (Darwin) iD8DBQFF4894CgdfeCwsL5ERAlvfAKCiLEGZMTsGonn0OrdlTTMCp9GeZACePQ2V WCwXuHBFh/FOVsDJLa84Yks= =85PR -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic at boot on any 6.x OS
- Original Message - From: Joe Auty [EMAIL PROTECTED] To: Ted Mittelstaedt [EMAIL PROTECTED] Cc: Daan Vreeken [PA4DAN] [EMAIL PROTECTED]; Kip Macy [EMAIL PROTECTED]; freebsd-questions@freebsd.org; freebsd-hackers@freebsd.org Sent: Monday, February 26, 2007 10:01 AM Subject: Re: kernel panic at boot on any 6.x OS On Feb 26, 2007, at 8:01 AM, Ted Mittelstaedt wrote: - Original Message - From: Joe Auty [EMAIL PROTECTED] To: Ted Mittelstaedt [EMAIL PROTECTED] Cc: Daan Vreeken [PA4DAN] [EMAIL PROTECTED]; Kip Macy [EMAIL PROTECTED]; freebsd-questions@freebsd.org; freebsd-hackers@freebsd.org Sent: Sunday, February 25, 2007 10:39 PM Subject: Re: kernel panic at boot on any 6.x OS -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Feb 25, 2007, at 7:56 PM, Ted Mittelstaedt wrote: - Original Message - From: Joe Auty [EMAIL PROTECTED] To: Daan Vreeken [PA4DAN] [EMAIL PROTECTED] Cc: Kip Macy [EMAIL PROTECTED]; freebsd- [EMAIL PROTECTED]; freebsd-hackers@freebsd.org Sent: Sunday, February 25, 2007 8:14 AM Subject: Re: kernel panic at boot on any 6.x OS Any idea how this could have happened after disabling everything in my /etc/loader.conf, and simply running a: make buildworld make buildkernel KERNCONF=myconfig make installkernel KERNCONF=myconfig well your supposed to do this single-user, run mergemaster and a few other things. I also don't see a make installworld. I usually perform those steps after I've rebooted to ensure that my system will boot off the new kernel, as per the instructions in the FreeBSD handbook. Joe, please try booting from a 6.2-release install ISO. If it works without panicing, then you did something wrong during the upgrade. Downloading the image now, I'll let you know if I'm able to boot from it... Since by your own admission your not an expert, you would be well advised to simply back up your files the old fashioned way, reformat your hard disk, install from a 6.2 boot ISO, then restore your files. Leave the fancy in-place updating to someone else. It's a big PIA and doesen't work half the time anyway. How well does simply upgrading with the CD work (as opposed to wiping clean)? I've upgraded several times to new releases simply by rebuilding world, it has never failed me in the past. I don't doubt what you are saying here, but since I will have to change how I work, assuming that I can boot off of the 6.2 CD, I'd appreciate any general upgrade tips that don't involve wiping the disk clean (which is not really an option). If wiping the disk really isn't an option then you have one or more of the following problems: 1) Production system with a lack of hardware spares 2) inadequate backup plan and execution. People who state that wiping the disk isn't an option are screaming at the top of their lungs for the hardware gremlins to explain what MTBF is all about. The gremlins will visit you, I guarentee. And they always pick the very best times for it too. I just hope (if this is your workplace) that your job survives. My production system is backed up daily to two different sites, that's not an issue. The system I'm thinking of upgrading to 6.2 is my test server I run out of my house that stores movie files and other non-essential files. Technically, wiping it clean *would* be an option if it came down to it, just an inconvenience. Perhaps I should invest in another HD to use for instances such as this. For instance, is rebuilding world between point releases (e.g. 5.4 to 5.5) an okay idea, compared to across major releases (e.g. 5.5 to 6.2)? I'll do my own homework regarding this too, but I appreciate any nuggets of wisdom you might have! As far as me being an expert, I guess I'd categorize me somewhere in between complete newb and FreeBSD developer =) The problem is that all of the ports and packages that you put on a server change from release to release. The developers of openssl, for example, don't give a tinkers damn about how FreeBSD's upgrade process works, when they are making changes in their code. I run a number of FreeBSD servers and what I do is simply keep them patched with security updates. Every once in a while a security hole will be discovered in a non-core program and if it's serious enough I'll go into the port and do a make deinstall followed by downloading and compiling the program the old fashioned way I shoot for a min of 3 years on the OS before even thinking about updating, and when it's time to update the hardware has generally reached the old rag stage anyway. Do you run any non-production machines where you test running newer OSes and test software updates and such? We used to but the problem was that the manufacturers change hardware designs much faster than
Re: kernel panic at boot on any 6.x OS
It looks as if you've hit a device driver that is trying to print out a null string. The message you've given doesn't provide any more information than that. If you install a snapshot kernel it will probably have ddb compiled in which will allow you to at least get a backtrace. I'm sorry you're having trouble. -Kip On 2/24/07, Joe Auty [EMAIL PROTECTED] wrote: Hello, (sorry, don't know whether kernel problems should go to questions or hackers, or both).. This has been a long-standing problem of mine, but I always ignored it hoping it would go away on its own with a future 6.x release, but it remains... No matter whether I boot into safe mode or regular mode, with all kernel extensions disabled in /boot/loader.conf, I get the following panic late at boot of a fresh RELENG_6_2 kernel (with only a few services left to bring up). The 6.x kernels I've tried all build and installed cleanly without any errors... WARNING: Device driver Fatal trap 12: page fault while in kernel mode fault virtual address = 0x40 fault code = supervisor read, page not present instruction pointer = 0x20:0xc06d4614 stack pointer = 0x28:0xf015491c frame pointer = 0x28:0xf015491c code segment = base 0x0, limit 0xff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interupt enabled, resume, IOPL = 0 current process = 898 (kldload) trap number = 12 panic: page fault uptime: 36s cannot dump. No dump device defined automatic reboot in 15 seconds This problem does not occur within any 5.x OS for me. I would certainly like to resolve this issue now, but this sort of debugging is over my head beyond running fsck (which I've tried). Any ideas here? Thanks in advance for your help! --- Joe Auty NetMusician: web publishing software for musicians http://www.netmusician.org [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic at boot on any 6.x OS
Hi, Joe Auty wrote: This problem does not occur within any 5.x OS for me. I would certainly like to resolve this issue now, but this sort of debugging is over my head beyond running fsck (which I've tried). Any ideas here? Which .ko are you trying to load? try removing them and see if things changes? Cheers, -- Xin LI [EMAIL PROTECTED] http://www.delphij.net/ FreeBSD - The Power to Serve! signature.asc Description: OpenPGP digital signature
Re: kernel panic at boot on any 6.x OS
On Sunday 25 February 2007 08:59, Kip Macy wrote:
It looks as if you've hit a device driver that is trying to print out
a null string. The message you've given doesn't provide any more
information than that. If you install a snapshot kernel it will
probably have ddb compiled in which will allow you to at least get a
backtrace. I'm sorry you're having trouble.
Grepping the source tree on 6.2-RELEASE shows this message can only have com
from one place : sys/kern/kern_conf.c in the function prep_cdevsw() :
if (devsw-d_version != D_VERSION_01) {
printf(
WARNING: Device driver \%s\ has wrong version %s\n,
devsw-d_name == NULL ? ??? : devsw-d_name,
and is disabled. Recompile KLD module.);
Looks like the kernel and the modules are out of sync.
On 2/24/07, Joe Auty [EMAIL PROTECTED] wrote:
Hello,
(sorry, don't know whether kernel problems should go to questions or
hackers, or both)..
This has been a long-standing problem of mine, but I always ignored
it hoping it would go away on its own with a future 6.x release, but
it remains...
No matter whether I boot into safe mode or regular mode, with all
kernel extensions disabled in /boot/loader.conf, I get the following
panic late at boot of a fresh RELENG_6_2 kernel (with only a few
services left to bring up). The 6.x kernels I've tried all build and
installed cleanly without any errors...
WARNING: Device driver
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x40
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc06d4614
stack pointer = 0x28:0xf015491c
frame pointer = 0x28:0xf015491c
code segment = base 0x0, limit 0xff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = interupt enabled, resume, IOPL = 0
current process = 898 (kldload)
trap number = 12
panic: page fault
uptime: 36s
cannot dump. No dump device defined
automatic reboot in 15 seconds
This problem does not occur within any 5.x OS for me. I would
certainly like to resolve this issue now, but this sort of debugging
is over my head beyond running fsck (which I've tried). Any ideas here?
Thanks in advance for your help!
---
Joe Auty
NetMusician: web publishing software for musicians
http://www.netmusician.org
[EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
--
Daan
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic at boot on any 6.x OS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Feb 25, 2007, at 3:01 AM, LI Xin wrote: Hi, Joe Auty wrote: This problem does not occur within any 5.x OS for me. I would certainly like to resolve this issue now, but this sort of debugging is over my head beyond running fsck (which I've tried). Any ideas here? Which .ko are you trying to load? try removing them and see if things changes? I've disabled all third party modules (this happens when I boot in safe mode too). The modules that are being loaded are whatever modules are installed after a: make buildworld make buildkernel KERNCONF=myconfig make installkernel KERNCONF=myconfig Does this reveal anything useful? - --- Joe Auty NetMusician: web publishing software for musicians http://www.netmusician.org [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (Darwin) iD8DBQFF4bSSCgdfeCwsL5ERAmi0AKCKu0DwEP1JtUuAkhj5O85sKDYlqwCeOWbz NQvULu8I/0B/EBesXo+mtjQ= =S3Mo -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic at boot on any 6.x OS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hey Kip, I'd gladly try a snapshot kernel, but I'm not sure which one to pick out of this list: ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/6.2-RELEASE/kernels Any suggestions? On Feb 25, 2007, at 2:59 AM, Kip Macy wrote: It looks as if you've hit a device driver that is trying to print out a null string. The message you've given doesn't provide any more information than that. If you install a snapshot kernel it will probably have ddb compiled in which will allow you to at least get a backtrace. I'm sorry you're having trouble. -Kip On 2/24/07, Joe Auty [EMAIL PROTECTED] wrote: Hello, (sorry, don't know whether kernel problems should go to questions or hackers, or both).. This has been a long-standing problem of mine, but I always ignored it hoping it would go away on its own with a future 6.x release, but it remains... No matter whether I boot into safe mode or regular mode, with all kernel extensions disabled in /boot/loader.conf, I get the following panic late at boot of a fresh RELENG_6_2 kernel (with only a few services left to bring up). The 6.x kernels I've tried all build and installed cleanly without any errors... WARNING: Device driver Fatal trap 12: page fault while in kernel mode fault virtual address = 0x40 fault code = supervisor read, page not present instruction pointer = 0x20:0xc06d4614 stack pointer = 0x28:0xf015491c frame pointer = 0x28:0xf015491c code segment = base 0x0, limit 0xff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interupt enabled, resume, IOPL = 0 current process = 898 (kldload) trap number = 12 panic: page fault uptime: 36s cannot dump. No dump device defined automatic reboot in 15 seconds This problem does not occur within any 5.x OS for me. I would certainly like to resolve this issue now, but this sort of debugging is over my head beyond running fsck (which I've tried). Any ideas here? Thanks in advance for your help! --- Joe Auty NetMusician: web publishing software for musicians http://www.netmusician.org [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers- [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (Darwin) iD8DBQFF4bZMCgdfeCwsL5ERAv0zAJ4zRjih+XoXGjF8Bc4hd2Yj7I0WNQCfeEb5 5mLoo1jTuYnJpa2z1EJqbUY= =Jwsg -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic at boot on any 6.x OS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 25, 2007, at 5:46 AM, Daan Vreeken [PA4DAN] wrote:
On Sunday 25 February 2007 08:59, Kip Macy wrote:
It looks as if you've hit a device driver that is trying to print out
a null string. The message you've given doesn't provide any more
information than that. If you install a snapshot kernel it will
probably have ddb compiled in which will allow you to at least get a
backtrace. I'm sorry you're having trouble.
Grepping the source tree on 6.2-RELEASE shows this message can only
have com
from one place : sys/kern/kern_conf.c in the function prep_cdevsw() :
if (devsw-d_version != D_VERSION_01) {
printf(
WARNING: Device driver \%s\ has wrong
version %s\n,
devsw-d_name == NULL ? ??? : devsw-d_name,
and is disabled. Recompile KLD module.);
Looks like the kernel and the modules are out of sync.
Any idea how this could have happened after disabling everything in
my /etc/loader.conf, and simply running a:
make buildworld
make buildkernel KERNCONF=myconfig
make installkernel KERNCONF=myconfig
Shouldn't this have installed a fresh kernel plus only essential
modules?
Here is a diff of my kernel config (which I've called, rather
uncreatively, 6.x) against GENERIC:
nothing unusual, just IPFIREWALL and Linux compat stuff, right?
# diff 6.x GENERIC
19c19
# $FreeBSD: src/sys/i386/conf/GENERIC,v 1.429.2.7.2.2 2006/05/01
00:15:12 scottl Exp $
- ---
# $FreeBSD: src/sys/i386/conf/GENERIC,v 1.429.2.13 2006/10/09
18:41:36 simon Exp $
30,42c30
options IPFIREWALL
options IPFIREWALL_VERBOSE
options IPFIREWALL_VERBOSE_LIMIT=10
options IPFIREWALL_DEFAULT_TO_ACCEPT
options IPDIVERT
#options VFS_AIO
#options HZ=1200
#options SMP # Symmetric MultiProcessor
Kernel
#device pf
#device pflog
#device pfsync
options COMPAT_LINUX
options BRIDGE
- ---
makeoptions DEBUG=-g# Build kernel with gdb(1)
debug symbols
44,49d31
# Enable the linux-like proc filesystem support (requires
COMPAT_LINUX and PSEUDOFS)
options LINPROCFS
#makeoptions DEBUG=-g# Build kernel with gdb(1)
debug symbols
#options SCHED_ULE # ULE scheduler
77,80d58
options AHC_REG_PRETTY_PRINT# Print register bitfields in
debug
# output. Adds ~128k to driver.
options AHD_REG_PRETTY_PRINT# Print register bitfields in
debug
# output. Adds ~215k to driver.
103a82,83
options AHC_REG_PRETTY_PRINT# Print register bitfields
in debug
# output. Adds ~128k to
driver.
104a85,86
options AHD_REG_PRETTY_PRINT# Print register bitfields
in debug
# output. Adds ~215k to
driver.
226a209
devicestge# Sundance/Tamarack TC9021
gigabit Ethernet
248a232,234
devicewlan_wep# 802.11 WEP support
devicewlan_ccmp # 802.11 CCMP support
devicewlan_tkip # 802.11 TKIP support
249a236,238
deviceath # Atheros pci/cardbus NIC's
deviceath_hal # Atheros HAL (Hardware
Access Layer)
deviceath_rate_sample # SampleRate tx rate control
for ath
On 2/24/07, Joe Auty [EMAIL PROTECTED] wrote:
Hello,
(sorry, don't know whether kernel problems should go to questions or
hackers, or both)..
This has been a long-standing problem of mine, but I always ignored
it hoping it would go away on its own with a future 6.x release, but
it remains...
No matter whether I boot into safe mode or regular mode, with all
kernel extensions disabled in /boot/loader.conf, I get the following
panic late at boot of a fresh RELENG_6_2 kernel (with only a few
services left to bring up). The 6.x kernels I've tried all build and
installed cleanly without any errors...
WARNING: Device driver
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x40
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc06d4614
stack pointer = 0x28:0xf015491c
frame pointer = 0x28:0xf015491c
code segment = base 0x0, limit 0xff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = interupt enabled, resume, IOPL = 0
current process = 898 (kldload)
trap number = 12
panic: page fault
uptime: 36s
cannot dump. No dump device defined
automatic reboot in 15 seconds
This problem does not occur within any 5.x OS for me. I would
certainly like to resolve this issue now, but this sort of debugging
is over my head beyond running fsck (which I've tried). Any ideas
here?
Thanks in advance for your help!
---
Joe Auty
Re: kernel panic at boot on any 6.x OS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 25, 2007, at 11:14 AM, Joe Auty wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 25, 2007, at 5:46 AM, Daan Vreeken [PA4DAN] wrote:
On Sunday 25 February 2007 08:59, Kip Macy wrote:
It looks as if you've hit a device driver that is trying to print
out
a null string. The message you've given doesn't provide any more
information than that. If you install a snapshot kernel it will
probably have ddb compiled in which will allow you to at least get a
backtrace. I'm sorry you're having trouble.
Grepping the source tree on 6.2-RELEASE shows this message can
only have com
from one place : sys/kern/kern_conf.c in the function prep_cdevsw() :
if (devsw-d_version != D_VERSION_01) {
printf(
WARNING: Device driver \%s\ has wrong
version %s\n,
devsw-d_name == NULL ? ??? : devsw-d_name,
and is disabled. Recompile KLD module.);
Looks like the kernel and the modules are out of sync.
Any idea how this could have happened after disabling everything in
my /etc/loader.conf, and simply running a:
make buildworld
make buildkernel KERNCONF=myconfig
make installkernel KERNCONF=myconfig
Shouldn't this have installed a fresh kernel plus only essential
modules?
Here is a diff of my kernel config (which I've called, rather
uncreatively, 6.x) against GENERIC:
nothing unusual, just IPFIREWALL and Linux compat stuff, right?
Forgot to add that I believe I've also tried building a GENERIC
kernel and ran into this same problem. It's been a while since I
tried this though, so I'll gladly try this again if you think it
would be a useful test! =)
# diff 6.x GENERIC
19c19
# $FreeBSD: src/sys/i386/conf/GENERIC,v 1.429.2.7.2.2 2006/05/01
00:15:12 scottl Exp $
- ---
# $FreeBSD: src/sys/i386/conf/GENERIC,v 1.429.2.13 2006/10/09
18:41:36 simon Exp $
30,42c30
options IPFIREWALL
options IPFIREWALL_VERBOSE
options IPFIREWALL_VERBOSE_LIMIT=10
options IPFIREWALL_DEFAULT_TO_ACCEPT
options IPDIVERT
#options VFS_AIO
#options HZ=1200
#options SMP # Symmetric
MultiProcessor Kernel
#device pf
#device pflog
#device pfsync
options COMPAT_LINUX
options BRIDGE
- ---
makeoptions DEBUG=-g# Build kernel with gdb(1)
debug symbols
44,49d31
# Enable the linux-like proc filesystem support (requires
COMPAT_LINUX and PSEUDOFS)
options LINPROCFS
#makeoptions DEBUG=-g# Build kernel with gdb(1)
debug symbols
#options SCHED_ULE # ULE scheduler
77,80d58
options AHC_REG_PRETTY_PRINT# Print register bitfields
in debug
# output. Adds ~128k to
driver.
options AHD_REG_PRETTY_PRINT# Print register bitfields
in debug
# output. Adds ~215k to
driver.
103a82,83
options AHC_REG_PRETTY_PRINT# Print register bitfields
in debug
# output. Adds ~128k to
driver.
104a85,86
options AHD_REG_PRETTY_PRINT# Print register bitfields
in debug
# output. Adds ~215k to
driver.
226a209
devicestge# Sundance/Tamarack TC9021
gigabit Ethernet
248a232,234
devicewlan_wep# 802.11 WEP support
devicewlan_ccmp # 802.11 CCMP support
devicewlan_tkip # 802.11 TKIP support
249a236,238
deviceath # Atheros pci/cardbus NIC's
deviceath_hal # Atheros HAL (Hardware
Access Layer)
deviceath_rate_sample # SampleRate tx rate
control for ath
On 2/24/07, Joe Auty [EMAIL PROTECTED] wrote:
Hello,
(sorry, don't know whether kernel problems should go to
questions or
hackers, or both)..
This has been a long-standing problem of mine, but I always ignored
it hoping it would go away on its own with a future 6.x release,
but
it remains...
No matter whether I boot into safe mode or regular mode, with all
kernel extensions disabled in /boot/loader.conf, I get the
following
panic late at boot of a fresh RELENG_6_2 kernel (with only a few
services left to bring up). The 6.x kernels I've tried all build
and
installed cleanly without any errors...
WARNING: Device driver
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x40
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc06d4614
stack pointer = 0x28:0xf015491c
frame pointer = 0x28:0xf015491c
code segment = base 0x0, limit 0xff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = interupt enabled, resume, IOPL = 0
current process = 898 (kldload)
trap number = 12
panic: page fault
uptime:
Re: kernel panic at boot on any 6.x OS
- Original Message - From: Joe Auty [EMAIL PROTECTED] To: Daan Vreeken [PA4DAN] [EMAIL PROTECTED] Cc: Kip Macy [EMAIL PROTECTED]; freebsd-questions@freebsd.org; freebsd-hackers@freebsd.org Sent: Sunday, February 25, 2007 8:14 AM Subject: Re: kernel panic at boot on any 6.x OS Any idea how this could have happened after disabling everything in my /etc/loader.conf, and simply running a: make buildworld make buildkernel KERNCONF=myconfig make installkernel KERNCONF=myconfig well your supposed to do this single-user, run mergemaster and a few other things. I also don't see a make installworld. Joe, please try booting from a 6.2-release install ISO. If it works without panicing, then you did something wrong during the upgrade. Since by your own admission your not an expert, you would be well advised to simply back up your files the old fashioned way, reformat your hard disk, install from a 6.2 boot ISO, then restore your files. Leave the fancy in-place updating to someone else. It's a big PIA and doesen't work half the time anyway. Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic at boot on any 6.x OS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Feb 25, 2007, at 7:56 PM, Ted Mittelstaedt wrote: - Original Message - From: Joe Auty [EMAIL PROTECTED] To: Daan Vreeken [PA4DAN] [EMAIL PROTECTED] Cc: Kip Macy [EMAIL PROTECTED]; freebsd-questions@freebsd.org; freebsd-hackers@freebsd.org Sent: Sunday, February 25, 2007 8:14 AM Subject: Re: kernel panic at boot on any 6.x OS Any idea how this could have happened after disabling everything in my /etc/loader.conf, and simply running a: make buildworld make buildkernel KERNCONF=myconfig make installkernel KERNCONF=myconfig well your supposed to do this single-user, run mergemaster and a few other things. I also don't see a make installworld. I usually perform those steps after I've rebooted to ensure that my system will boot off the new kernel, as per the instructions in the FreeBSD handbook. Joe, please try booting from a 6.2-release install ISO. If it works without panicing, then you did something wrong during the upgrade. Downloading the image now, I'll let you know if I'm able to boot from it... Since by your own admission your not an expert, you would be well advised to simply back up your files the old fashioned way, reformat your hard disk, install from a 6.2 boot ISO, then restore your files. Leave the fancy in-place updating to someone else. It's a big PIA and doesen't work half the time anyway. How well does simply upgrading with the CD work (as opposed to wiping clean)? I've upgraded several times to new releases simply by rebuilding world, it has never failed me in the past. I don't doubt what you are saying here, but since I will have to change how I work, assuming that I can boot off of the 6.2 CD, I'd appreciate any general upgrade tips that don't involve wiping the disk clean (which is not really an option). For instance, is rebuilding world between point releases (e.g. 5.4 to 5.5) an okay idea, compared to across major releases (e.g. 5.5 to 6.2)? I'll do my own homework regarding this too, but I appreciate any nuggets of wisdom you might have! As far as me being an expert, I guess I'd categorize me somewhere in between complete newb and FreeBSD developer =) Thanks again! - --- Joe Auty NetMusician: web publishing software for musicians http://www.netmusician.org [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (Darwin) iD8DBQFF4oC3CgdfeCwsL5ERAj3vAJ9bMYSj33hg/jU5jU6RyIjXqJ/YLwCfVumh FsunyXJGMjXHEHKso7xWzcI= =0p6j -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel Panic on FreeBSD 6.1 with Dell PE1850 / 1750
Mike wrote: Hello, I got a handful of Dell PE1850 and PE1750 boxes running mail scanning that we recently upgraded to FreeBSD 6.1. It started with a new PE1850 (mx4) that we immediately installed 6.1 on, which started having kernel panics- we initially blamed it on hardware. But last week, we rebuild a PE1750 (mx6) we've been running for over a year with FBSD 4.11 without any problems, and it's crashing now as well. Are there any known issues with FreeBSD 6.1 on any of the Dell PE series machines? Any thoughts would be great, Mike Some details: PE1850 --snip-- FreeBSD mx4 6.1-RELEASE FreeBSD 6.1-RELEASE #0: Mon May 15 18:55:30 PDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/U_GENERIC_SMP i386 Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x5c fault code = supervisor read, page not present instruction pointer = 0x20:0xc072dbda stack pointer = 0x28:0xea9b9a98 frame pointer = 0x28:0xea9b9b28 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 20764 (exim-4.60-1) trap number = 12 panic: page fault cpuid = 0 Uptime: 10d13h1m4s Dumping 3071 MB (2 chunks) chunk 0: 1MB (159 pages) ... ok chunk 1: 3071MB (786112 pages) 3055 3039 3823 3007 2991 --snip-- PE1750 --snip-- FreeBSD mx6 6.1-RELEASE FreeBSD 6.1-RELEASE #0: Mon May 15 18:55:30 PDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/U_GENERIC_SMP i386 Fatal trap 12: page fault while in kernel mode cpuid = 2; apic id = 06 fault virtual address = 0x5c fault code = supervisor read, page not present instruction pointer = 0x20:0xc072dbda stack pointer = 0x28:0xf2791a98 frame pointer = 0x28:0xf2791b28 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 60007 (exim-4.60-1) trap number = 12 panic: page fault cpuid = 2 Uptime: 2d16h44m0s Dumping 3071 MB (2 chunks) chunk 0: 1MB (159 pages) ... ok chunk 1: 3071MB (786135 pages) 3055 3039 --snip-- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] I am running 6.1-STABLE on a Dell PE 1850 very smoothly actually. The machine is rock-solid and a constant load of 5-10. Can you give me a dmesg output? Maybe the hardware isn't identical to the setup we have, or maybe something isn't right in your kernel config. Jorn Jorn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel Panic on FreeBSD 6.1 with Dell PE1850 / 1750
Mike wrote: Hello, I got a handful of Dell PE1850 and PE1750 boxes running mail scanning that we recently upgraded to FreeBSD 6.1. It started with a new PE1850 (mx4) that we immediately installed 6.1 on, which started having kernel panics- we initially blamed it on hardware. But last week, we rebuild a PE1750 (mx6) we've been running for over a year with FBSD 4.11 without any problems, and it's crashing now as well. Are there any known issues with FreeBSD 6.1 on any of the Dell PE series machines? Any thoughts would be great, Mike Some details: PE1850 --snip-- FreeBSD mx4 6.1-RELEASE FreeBSD 6.1-RELEASE #0: Mon May 15 18:55:30 PDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/U_GENERIC_SMP i386 Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x5c fault code = supervisor read, page not present instruction pointer = 0x20:0xc072dbda stack pointer = 0x28:0xea9b9a98 frame pointer = 0x28:0xea9b9b28 code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 20764 (exim-4.60-1) trap number = 12 panic: page fault cpuid = 0 Uptime: 10d13h1m4s Dumping 3071 MB (2 chunks) chunk 0: 1MB (159 pages) ... ok chunk 1: 3071MB (786112 pages) 3055 3039 3823 3007 2991 --snip-- PE1750 --snip-- FreeBSD mx6 6.1-RELEASE FreeBSD 6.1-RELEASE #0: Mon May 15 18:55:30 PDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/U_GENERIC_SMP i386 Fatal trap 12: page fault while in kernel mode cpuid = 2; apic id = 06 fault virtual address = 0x5c fault code = supervisor read, page not present instruction pointer = 0x20:0xc072dbda stack pointer = 0x28:0xf2791a98 frame pointer = 0x28:0xf2791b28 code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 60007 (exim-4.60-1) trap number = 12 panic: page fault cpuid = 2 Uptime: 2d16h44m0s Dumping 3071 MB (2 chunks) chunk 0: 1MB (159 pages) ... ok chunk 1: 3071MB (786135 pages) 3055 3039 --snip-- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] I am running 6.1-STABLE on a Dell PE 1850 very smoothly actually. The machine is rock-solid and a constant load of 5-10. Can you give me a dmesg output? Maybe the hardware isn't identical to the setup we have, or maybe something isn't right in your kernel config. Jorn Jorn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Sure- from the PE1850 --snip-- Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.1-RELEASE #0: Mon May 15 18:55:30 PDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/U_GENERIC_SMP Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.60GHz (3591.25-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf43 Stepping = 3 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA ,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x659dSSE3,RSVD2,MON,DS_CPL,EST,TM2,CNTX-ID,CX16,b14 AMD Features=0x2010NX,LM Logical CPUs per core: 2 real memory = 3220963328 (3071 MB) avail memory = 3151040512 (3005 MB) ACPI APIC Table: DELL PE BKC FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 6 cpu3 (AP): APIC ID: 7 ioapic0: Changing APIC ID to 8 ioapic1: Changing APIC ID to 9 ioapic1: WARNING: intbase 32 != expected base 24 ioapic2: Changing APIC ID to 10 ioapic2: WARNING: intbase 64 != expected base 56 ioapic0 Version 2.0 irqs 0-23 on motherboard ioapic1 Version 2.0 irqs 32-55 on motherboard ioapic2 Version 2.0 irqs 64-87 on motherboard kbd1 at kbdmux0 acpi0: DELL PE BKC on motherboard acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 cpu2: ACPI CPU on acpi0 cpu3: ACPI CPU on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge at device 2.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge at device 0.0 on pci1 pci2: ACPI PCI bus on pcib2 amr0: LSILogic MegaRAID 1.53 mem 0xf80f-0xf80f,0xfe9e-0xfe9f irq 46 at device 14.0 on pci2 amr0: delete logical drives supported by controller amr0: LSILogic PERC 4e/Si
Re: Kernel Panic on FreeBSD 6.1 with Dell PE1850 / 1750
Mike wrote: Mike wrote: Hello, I got a handful of Dell PE1850 and PE1750 boxes running mail scanning that we recently upgraded to FreeBSD 6.1. It started with a new PE1850 (mx4) that we immediately installed 6.1 on, which started having kernel panics- we initially blamed it on hardware. But last week, we rebuild a PE1750 (mx6) we've been running for over a year with FBSD 4.11 without any problems, and it's crashing now as well. Are there any known issues with FreeBSD 6.1 on any of the Dell PE series machines? Any thoughts would be great, Mike Some details: PE1850 --snip-- FreeBSD mx4 6.1-RELEASE FreeBSD 6.1-RELEASE #0: Mon May 15 18:55:30 PDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/U_GENERIC_SMP i386 Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x5c fault code = supervisor read, page not present instruction pointer = 0x20:0xc072dbda stack pointer = 0x28:0xea9b9a98 frame pointer = 0x28:0xea9b9b28 code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 20764 (exim-4.60-1) trap number = 12 panic: page fault cpuid = 0 Uptime: 10d13h1m4s Dumping 3071 MB (2 chunks) chunk 0: 1MB (159 pages) ... ok chunk 1: 3071MB (786112 pages) 3055 3039 3823 3007 2991 --snip-- PE1750 --snip-- FreeBSD mx6 6.1-RELEASE FreeBSD 6.1-RELEASE #0: Mon May 15 18:55:30 PDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/U_GENERIC_SMP i386 Fatal trap 12: page fault while in kernel mode cpuid = 2; apic id = 06 fault virtual address = 0x5c fault code = supervisor read, page not present instruction pointer = 0x20:0xc072dbda stack pointer = 0x28:0xf2791a98 frame pointer = 0x28:0xf2791b28 code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 60007 (exim-4.60-1) trap number = 12 panic: page fault cpuid = 2 Uptime: 2d16h44m0s Dumping 3071 MB (2 chunks) chunk 0: 1MB (159 pages) ... ok chunk 1: 3071MB (786135 pages) 3055 3039 --snip-- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] I am running 6.1-STABLE on a Dell PE 1850 very smoothly actually. The machine is rock-solid and a constant load of 5-10. Can you give me a dmesg output? Maybe the hardware isn't identical to the setup we have, or maybe something isn't right in your kernel config. Jorn Jorn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Sure- from the PE1850 --snip-- Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.1-RELEASE #0: Mon May 15 18:55:30 PDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/U_GENERIC_SMP Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.60GHz (3591.25-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf43 Stepping = 3 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA ,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x659dSSE3,RSVD2,MON,DS_CPL,EST,TM2,CNTX-ID,CX16,b14 AMD Features=0x2010NX,LM Logical CPUs per core: 2 real memory = 3220963328 (3071 MB) avail memory = 3151040512 (3005 MB) ACPI APIC Table: DELL PE BKC FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 6 cpu3 (AP): APIC ID: 7 ioapic0: Changing APIC ID to 8 ioapic1: Changing APIC ID to 9 ioapic1: WARNING: intbase 32 != expected base 24 ioapic2: Changing APIC ID to 10 ioapic2: WARNING: intbase 64 != expected base 56 ioapic0 Version 2.0 irqs 0-23 on motherboard ioapic1 Version 2.0 irqs 32-55 on motherboard ioapic2 Version 2.0 irqs 64-87 on motherboard kbd1 at kbdmux0 acpi0: DELL PE BKC on motherboard acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 cpu2: ACPI CPU on acpi0 cpu3: ACPI CPU on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge at device 2.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge at device 0.0 on pci1 pci2: ACPI PCI bus on pcib2 amr0: LSILogic MegaRAID 1.53 mem 0xf80f-0xf80f,0xfe9e-0xfe9f irq 46 at device 14.0 on pci2 amr0: delete logical drives supported by controller amr0: LSILogic PERC 4e/Si Firmware 521X, BIOS H430, 256MB RAM pcib3: ACPI PCI-PCI bridge at device 0.2 on pci1 pci3: ACPI PCI
Re: kernel panic on kldload in 6.1
On Thu, May 18, 2006 at 10:54:19PM -0400, Joe Auty wrote: On May 18, 2006, at 12:36 AM, Kris Kennaway wrote: On Wed, May 17, 2006 at 07:06:59PM -0400, Joe Auty wrote: Hello, A problem I've had since 6.0 remains in 6.1 where my machine kernel panics at boot trying to kldload some module (it doesn't say which one). It also does not log this panic. I suppose this isn't terribly helpful information, but if there is anything you can suggest I do (including pass this on to an interested party), please let me know how I can help =) It sounds like you have an old (6.0) module you're still trying to load. Things like the nvidia driver and other ports are prime candidates. Hi, I tried commenting out all of the kernel modules in /boot/ loader.conf, and I'm still panicing. I wrote down some of the panic message this time. The code is superviser read, page not present the panic output is: panic: page fault Unless you guys have any ideas of things I can try, I'll just file this. Any ideas? So you claimed originally that it was due to kldloading some module, but now you're still getting the same panic when you're not kldloading anything? Can you please clarify exactly what is the situation? I suspect you're still actually kldloading something (modules are loaded on demand for some things): did you boot into single-user mode and confirm that all modules are up-to-date? Kris pgpm1YMEwUxXq.pgp Description: PGP signature
Re: kernel panic on kldload in 6.1
On May 19, 2006, at 2:38 PM, Kris Kennaway wrote: On Thu, May 18, 2006 at 10:54:19PM -0400, Joe Auty wrote: On May 18, 2006, at 12:36 AM, Kris Kennaway wrote: On Wed, May 17, 2006 at 07:06:59PM -0400, Joe Auty wrote: Hello, A problem I've had since 6.0 remains in 6.1 where my machine kernel panics at boot trying to kldload some module (it doesn't say which one). It also does not log this panic. I suppose this isn't terribly helpful information, but if there is anything you can suggest I do (including pass this on to an interested party), please let me know how I can help =) It sounds like you have an old (6.0) module you're still trying to load. Things like the nvidia driver and other ports are prime candidates. Hi, I tried commenting out all of the kernel modules in /boot/ loader.conf, and I'm still panicing. I wrote down some of the panic message this time. The code is superviser read, page not present the panic output is: panic: page fault Unless you guys have any ideas of things I can try, I'll just file this. Any ideas? So you claimed originally that it was due to kldloading some module, but now you're still getting the same panic when you're not kldloading anything? Can you please clarify exactly what is the situation? I suspect you're still actually kldloading something (modules are loaded on demand for some things): did you boot into single-user mode and confirm that all modules are up-to-date? I'm getting this error message during boot time, not during manual loading of modules. I'm getting this error message despite disabling all my third-party modules listed in /boot/loader.conf. I'm assuming that all modules stored in /boot/kernel are system modules, and it would be expected that they would all be able to run without kernel panicing during boot? Sorry for my lack of clarity! Where I became unclear was probably in saying some module. During boot time, once this panic is spewed onto my screen, it doesn't indicate which (system) module it is choking on. This panic occurred in single user mode under 6.0 too, I haven't tried single user mode in 6.1 yet --- Joe Auty NetMusician: web publishing software for musicians http://www.netmusician.org [EMAIL PROTECTED] PGP.sig Description: This is a digitally signed message part
Re: kernel panic on kldload in 6.1
On Fri, May 19, 2006 at 04:59:44PM -0400, Joe Auty wrote: On May 19, 2006, at 2:38 PM, Kris Kennaway wrote: On Thu, May 18, 2006 at 10:54:19PM -0400, Joe Auty wrote: On May 18, 2006, at 12:36 AM, Kris Kennaway wrote: On Wed, May 17, 2006 at 07:06:59PM -0400, Joe Auty wrote: Hello, A problem I've had since 6.0 remains in 6.1 where my machine kernel panics at boot trying to kldload some module (it doesn't say which one). It also does not log this panic. I suppose this isn't terribly helpful information, but if there is anything you can suggest I do (including pass this on to an interested party), please let me know how I can help =) It sounds like you have an old (6.0) module you're still trying to load. Things like the nvidia driver and other ports are prime candidates. Hi, I tried commenting out all of the kernel modules in /boot/ loader.conf, and I'm still panicing. I wrote down some of the panic message this time. The code is superviser read, page not present the panic output is: panic: page fault Unless you guys have any ideas of things I can try, I'll just file this. Any ideas? So you claimed originally that it was due to kldloading some module, but now you're still getting the same panic when you're not kldloading anything? Can you please clarify exactly what is the situation? I suspect you're still actually kldloading something (modules are loaded on demand for some things): did you boot into single-user mode and confirm that all modules are up-to-date? I'm getting this error message during boot time, not during manual loading of modules. As I said, some modules are loaded on demand. Not when booting single-user though. I'm getting this error message despite disabling all my third-party modules listed in /boot/loader.conf. I'm assuming that all modules stored in /boot/kernel are system modules, and it would be expected that they would all be able to run without kernel panicing during boot? Sorry for my lack of clarity! Where I became unclear was probably in saying some module. During boot time, once this panic is spewed onto my screen, it doesn't indicate which (system) module it is choking on. The rest of the panic message would have given more details though. This panic occurred in single user mode under 6.0 too, I haven't tried single user mode in 6.1 yet Kris pgpXjY9PVxWY4.pgp Description: PGP signature
Re: kernel panic on kldload in 6.1
Kris Kennaway wrote: It sounds like you have an old (6.0) module you're still trying to load. Things like the nvidia driver and other ports are prime candidates. Kris Does that mean that all the panic-issues with kld(un)load are fixed in 6.1? I crashed an important 6.0-STABLE box several times by trying to unload procfs for example and I don't want to run in such nightmares again by fiddling with klds unless I'm sure it's safe now. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic on kldload in 6.1
On Thu, May 18, 2006 at 10:57:51AM +0200, Frank Steinborn wrote: Kris Kennaway wrote: It sounds like you have an old (6.0) module you're still trying to load. Things like the nvidia driver and other ports are prime candidates. Kris Does that mean that all the panic-issues with kld(un)load are fixed in 6.1? I crashed an important 6.0-STABLE box several times by trying to unload procfs for example and I don't want to run in such nightmares again by fiddling with klds unless I'm sure it's safe now. No, it means that modules are not cross-compatible between releases. Please retest your problem with 6.1 and file a PR if you encounter it again; it's the only way it will get fixed. Kris pgpZEQzA6e4Uv.pgp Description: PGP signature
Re: kernel panic on kldload in 6.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On May 18, 2006, at 12:36 AM, Kris Kennaway wrote: On Wed, May 17, 2006 at 07:06:59PM -0400, Joe Auty wrote: Hello, A problem I've had since 6.0 remains in 6.1 where my machine kernel panics at boot trying to kldload some module (it doesn't say which one). It also does not log this panic. I suppose this isn't terribly helpful information, but if there is anything you can suggest I do (including pass this on to an interested party), please let me know how I can help =) It sounds like you have an old (6.0) module you're still trying to load. Things like the nvidia driver and other ports are prime candidates. Hi, I tried commenting out all of the kernel modules in /boot/ loader.conf, and I'm still panicing. I wrote down some of the panic message this time. The code is superviser read, page not present the panic output is: panic: page fault Unless you guys have any ideas of things I can try, I'll just file this. Any ideas? - --- Joe Auty NetMusician: web publishing software for musicians http://www.netmusician.org [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (Darwin) iD8DBQFEbTNcCgdfeCwsL5ERAvchAJ4toYHlfKLLcZV6XoedQQi3DDKLqwCeLZsX BHq3DxDtX+cg2gSPNqAaUVo= =XNLD -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic on kldload in 6.1
On Wed, 17 May 2006, Joe Auty wrote: A problem I've had since 6.0 remains in 6.1 where my machine kernel panics at boot trying to kldload some module (it doesn't say which one). It also does not log this panic. I suppose this isn't terribly helpful information, but if there is anything you can suggest I do (including pass this on to an interested party), please let me know how I can help =) If it were me, I would: 1. Boot from a fixit CD 2. Mount my partitions from the afflicted disk(s) 3. Start commenting out lines in /boot/loader.conf I'd probably start by commenting everything in /boot/loader.conf, but you could also use a binary search type procedure. Eventually it should become clear what the culprit is. HTH. -- Chris Hill [EMAIL PROTECTED] ** [ Busy Expunging | ] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic on kldload in 6.1
On Wed, May 17, 2006 at 07:06:59PM -0400, Joe Auty wrote: Hello, A problem I've had since 6.0 remains in 6.1 where my machine kernel panics at boot trying to kldload some module (it doesn't say which one). It also does not log this panic. I suppose this isn't terribly helpful information, but if there is anything you can suggest I do (including pass this on to an interested party), please let me know how I can help =) It sounds like you have an old (6.0) module you're still trying to load. Things like the nvidia driver and other ports are prime candidates. Kris pgpYkbmbQlDEV.pgp Description: PGP signature
Re: Kernel Panic when using mpd VPN Tunnel
On Thursday 04 May 2006 15:52, Shawn Guillemette wrote: Hello all, I have a Digital AlphaPC 164LX 533 MHz, running FreeBSD 4.11-RELEASE I have installed /usr/ports/net/mpd and attempted to make a vpn connection What kind of VPN? mpd does ppp over serial lines, ethernet, udp and pptp. and after authenticating it seems to bring the machine to a panic with the following info in the messages file. May 3 17:20:35 medusa /kernel: May 3 17:20:35 medusa /kernel: fatal kernel trap: May 3 17:20:35 medusa /kernel: May 3 17:20:35 medusa /kernel: trap entry = 0x4 (unaligned access fault) May 3 17:20:35 medusa /kernel: a0 = 0xfe5cb5ce May 3 17:20:35 medusa /kernel: a1 = 0x28 May 3 17:20:35 medusa /kernel: a2 = 0x1 May 3 17:20:35 medusa /kernel: pc = 0xfc4da0a0 May 3 17:20:35 medusa /kernel: ra = 0xfc4dabec May 3 17:20:35 medusa /kernel: curproc= 0xfe00098d6300 May 3 17:20:35 medusa /kernel: pid = 189, comm = mpd May 3 17:20:35 medusa /kernel: May 3 17:20:35 medusa /kernel: panic: trap May 3 17:20:35 medusa /kernel: Now the how to I was following asked that I make sure that the kernel is compiled with the following device option. device tun # Packet tunnel. I don't know how tun(4) is relevant This line was in the kernel config but was listed as follows pseudo-device tun # Packet tunnel. I have tried using both versions and have seen the same kernel panic each time. Any one have any tips for me? Describe what you want to do please. what kind of VPN and what the peers are. I am using mpd for a long time and never had a panic(well, almost) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel Panic
a) You're not using the kernel.debug, and b) it's not a sensible backtrace. Perhaps it's a side-effect of a) (i.e. you're not running kgdb against the same kernel that panicked). I compiled the kernel using config -g, then rebooted using that kernel. At some point, the system crashes, the dump file is written, and when it reboots, savecore saves the dump to the crash directory. The I use kgdb with this: ns11# kgdb /sys/i386/compile/ADKernel/kernel.debug /var/kcrash/vmcore.5 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol ps_pglobal_lookup] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 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 copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-marcel-freebsd. #0 0xc055c5e2 in doadump () (kgdb) where #0 0xc055c5e2 in doadump () #1 0xc055cb82 in boot () #2 0xc055ce18 in panic () #3 0xc068502c in trap_fatal () #4 0xc06847d5 in trap () #5 0xc0674baa in calltrap () #6 0x0018 in ?? () #7 0xc2d90010 in ?? () #8 0xc2d90010 in ?? () #9 0x0002 in ?? () #10 0xc283b000 in ?? () #11 0xef1f09d0 in ?? () #12 0xef1f09b8 in ?? () #13 0xc28f55c0 in ?? () #14 0xc28f55c0 in ?? () #15 0x in ?? () #16 0xc283b020 in ?? () #17 0x000c in ?? () #18 0x in ?? () #19 0xc057a8f9 in turnstile_setowner () #20 0xc057abbb in turnstile_wait () #21 0xc0554565 in _mtx_lock_sleep () #22 0xc05543dc in _mtx_lock_flags () #23 0xc2699c68 in ?? () #24 0xc26a2a60 in ?? () #25 0x in ?? () #26 0xc26a0289 in ?? () #27 0x09ef in ?? () #28 0x0004 in ?? () #29 0xc26a2a60 in ?? () #30 0x in ?? () #31 0x4002 in ?? () #32 0xc23d5400 in ?? () #33 0x0644 in ?? () #34 0x in ?? () #35 0x017f in ?? () #36 0x in ?? () #37 0x in ?? () #38 0x in ?? () #39 0x017f in ?? () #40 0x in ?? () #41 0x in ?? () #42 0x in ?? () #43 0x in ?? () #44 0x0801 in ?? () #45 0x in ?? () #46 0x in ?? () #47 0xd22d0014 in ?? () #48 0x0001 in ?? () #49 0x in ?? () #50 0x00020014 in ?? () #51 0x in ?? () #52 0x in ?? () #53 0x in ?? () #54 0x in ?? () #55 0x in ?? () #56 0xc26a2a60 in ?? () #57 0xc25a8c54 in ?? () #58 0x001c in ?? () #59 0x0030 in ?? () #60 0x in ?? () #61 0x265f in ?? () #62 0x in ?? () #63 0x0033 in ?? () #64 0x in ?? () #65 0x in ?? () #66 0x in ?? () #67 0xc25a8c40 in ?? () #68 0xef1f0b3c in ?? () #69 0xc25a8c00 in ?? () #70 0xef1f0b80 in ?? () #71 0xc23d1200 in ?? () #72 0xc23c17a0 in ?? () #73 0xc0735a80 in ip_rsvpd () #74 0x0002 in ?? () #75 0xef1f0b1c in ?? () #76 0xc2696402 in ?? () #77 0xc25a8c40 in ?? () #78 0x0014 in ?? () #79 0xc23d5400 in ?? () #80 0x0001 in ?? () #81 0xef1f0b3c in ?? () #82 0xef1f0b4c in ?? () #83 0xc05ca963 in pfil_run_hooks () TIA, Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel Panic
On Sat, Apr 29, 2006 at 01:03:12AM -0400, Steve Douville wrote: My server is rebooting frequently throughout the day. No apparent rhyme or reason, different applications can cause it. The following is what I get from one of the backtraces. a) You're not using the kernel.debug, and b) it's not a sensible backtrace. Perhaps it's a side-effect of a) (i.e. you're not running kgdb against the same kernel that panicked). (kgdb) backtrace #0 0xc055c5e2 in doadump () #1 0xc055cb82 in boot () #2 0xc055ce18 in panic () #3 0xc068502c in trap_fatal () #4 0xc06847d5 in trap () #5 0xc0674baa in calltrap () #6 0xc26d0018 in ?? () #7 0xef230010 in ?? () #8 0xef230010 in ?? () #9 0x0002 in ?? () #10 0xc2b7b300 in ?? () #11 0xef23c900 in ?? () #12 0xef23c8e8 in ?? () #13 0xc2837440 in ?? () #14 0xc2837440 in ?? () #15 0x in ?? () #16 0xc2b7b320 in ?? () #17 0x000c in ?? () #18 0x in ?? () #19 0xc057a8f9 in turnstile_setowner () #20 0xc057abbb in turnstile_wait () #21 0xc0554565 in _mtx_lock_sleep () #22 0xc05543dc in _mtx_lock_flags () It seems that pretty much every time I've traced the dump, it's always the turnstile_setowner that causes the panic. Or am I reading this wrong? Any thoughts or further debugging tips would be appreciated. TIA, Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] pgpPnS3mol7wk.pgp Description: PGP signature
Re: kernel panic because I pulled a floppy?
It happens, I've experienced quite some problems with floppy's and FreeBSD 5.4 and 6.0 anyway, if you mount a floppy, pull it out and unmount it the kernel might panic, if the floppy if reading writing and you pull it out the kernel might panic, if you mount a floppy which is damaged or has a damaged filesystem the kernel might panic I think i've only seen FreeBSD crach about six times in the year I'm using it, all of those were with floppy problems... My advice: Save all your work before you do anything with a floppy Don't do anything with a floppy on critical machines Think before you act when working with a floppy It sucks, I know, I always use a windows machine when I need to write or read something on a floppy. Using windows instead of freebsd because it's better at something. . . . . . . scary. . . On 05/12/05, Kris Kennaway [EMAIL PROTECTED] wrote: On Mon, Dec 05, 2005 at 08:37:23AM -0500, Michael P. Soulier wrote: On 12/4/05, Kris Kennaway [EMAIL PROTECTED] wrote: Is this true? If so, it would be the very first Unix that I've seen crash from this kind of user-mistake. Turns out it's pretty hard to fix. Well, all I know is that it does happen on Linux, Solaris... I don't recall seeing it on HP-UX... I've popped floppies on those OSs before without incident when I went back to the directory. Luckily it's avoidable, just a little disappointing given FreeBSD's rock-solid reputation. OK. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic because I pulled a floppy?
Don't top-post, please. Martin Tournoy [EMAIL PROTECTED] writes: My advice: Save all your work before you do anything with a floppy Don't do anything with a floppy on critical machines Think before you act when working with a floppy Using the mtools port is a lot easier. It uses the Windows model of separate devices instead of mounting the floppy into a unified filesystem tree, so it avoids the kernel interaction with the mount point. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic because I pulled a floppy?
mtools, hmm, might want to check that one out Ok, stupid question perhaps, but what is top-posting, I'm new to the whole mailling list stuff, so if you can explain a bit I won't do it anymore On 06 Dec 2005 10:12:40 -0500, Lowell Gilbert [EMAIL PROTECTED] wrote: Don't top-post, please. Martin Tournoy [EMAIL PROTECTED] writes: My advice: Save all your work before you do anything with a floppy Don't do anything with a floppy on critical machines Think before you act when working with a floppy Using the mtools port is a lot easier. It uses the Windows model of separate devices instead of mounting the floppy into a unified filesystem tree, so it avoids the kernel interaction with the mount point. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic because I pulled a floppy?
On 2005-12-06 15:19, Martin Tournoy [EMAIL PROTECTED] wrote: Ok, stupid question perhaps, but what is top-posting, I'm new to the whole mailling list stuff, so if you can explain a bit I won't do it anymore On 06 Dec 2005 10:12:40 -0500, Lowell Gilbert [EMAIL PROTECTED] wrote: Don't top-post, please. Top-posting is what you did just now. Quoting the original message near the bottom of your post and adding your reply on top of it. It tends to create silly 'nested threads' of messages like the one below: Oh, I see. - Because you have to read the 'thread' of messages and their replies in an entirely backwards order. - So why is top-posting bad? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic because I pulled a floppy?
On 12/5/05, Michael P. Soulier [EMAIL PROTECTED] wrote: On 12/4/05, Kris Kennaway [EMAIL PROTECTED] wrote: Is this true? If so, it would be the very first Unix that I've seen crash from this kind of user-mistake. Turns out it's pretty hard to fix. Well, all I know is that it does happen on Linux, Solaris... I don't recall seeing it on HP-UX... I've popped floppies on those OSs before without incident when I went back to the directory. Luckily it's avoidable, just a little disappointing given FreeBSD's rock-solid reputation. My understanding, and it could be completely wrong, is that Linux distributions usually use something like amd(8) (the automount daemon) to manage removable devices. They automount automagically when inserted, and unmount when they haven't been used for a while, so if you forget about them and pull them out they are usually not mounted and don't cause problems. You might try setting up amd(8) to see if that makes things more robust. - Bob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic because I pulled a floppy?
On 12/4/05, Kris Kennaway [EMAIL PROTECTED] wrote: Is this true? If so, it would be the very first Unix that I've seen crash from this kind of user-mistake. Turns out it's pretty hard to fix. Well, all I know is that it does happen on Linux, Solaris... I don't recall seeing it on HP-UX... I've popped floppies on those OSs before without incident when I went back to the directory. Luckily it's avoidable, just a little disappointing given FreeBSD's rock-solid reputation. Mike -- Michael P. Soulier [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic because I pulled a floppy?
On Mon, Dec 05, 2005 at 08:37:23AM -0500, Michael P. Soulier wrote: On 12/4/05, Kris Kennaway [EMAIL PROTECTED] wrote: Is this true? If so, it would be the very first Unix that I've seen crash from this kind of user-mistake. Turns out it's pretty hard to fix. Well, all I know is that it does happen on Linux, Solaris... I don't recall seeing it on HP-UX... I've popped floppies on those OSs before without incident when I went back to the directory. Luckily it's avoidable, just a little disappointing given FreeBSD's rock-solid reputation. OK. Kris pgpV3p6wIwWSR.pgp Description: PGP signature
Re: kernel panic because I pulled a floppy?
Michael P. Soulier wrote: I'm reading BSD Hacks by Dru Lavigne, published by O'Reilly. In the section on managing floppies, it mentions that if you pull a floppy without umounting it first, the next time to try to access the filesystem, you'll get a kernel panic. Is this true? If so, it would be the very first Unix that I've seen crash from this kind of user-mistake. I've crashed 5.x by pulling a USB umass device and then trying to look at the directory where it was mounted. - d. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
