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
Kernel Panic - Unix socket communication in kernel module
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? Thanks. * * ___ 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
kernel panic leads to core dump
I was going ahead and attempting to install libreoffice 3.5.7 and it was going along nicely until the kernel panicked. When I rebooted, I tried to start the install again but it aborted so I went to make clean in /usr/ports/editors/libreoffice when the kernel panicked again. I have two of all the core dump files (one set from each). makeoptions DEBUG=-g# Build kernel with gdb(1) debug symbols Is already enabled in the generic (amd64) kernel. $ uname -a FreeBSD alex-laptop 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 -- Yours in Christ, Joseph A Nagy Jr Whoever loves instruction loves knowledge, But he who hates correction is stupid. -- Proverbs 12:1 Emails are not formal business letters, whatever businesses may want. Original content CopyFree (F) under the OWL http://owl.apotheon.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
FreeBSD 8.3 udp_input() kernel panic
Hi All, I posted a blog yesterday with regards to a FreeBSD kernel panic in FreeBSD 8.3 at http://blog.hostileadmin.com/2012/11/05/freebsd-kernel-panic-in-udp_input/ in case anyone has any interest... -- Take care Rick Miller ___ 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
kernel panic
Dear Matthew, 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. looking forward to hear from your side soon. regards shan___ 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
Kernel panic while importing a pool
Hi, I had several kernel panics, and I finally understood that one of memory was bad. I removed it. But now, each time I try to import my pool, I get a kernel panic I'm using freebsd 9.0-release generic Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x468 fault code = supervisor read data, page not present instruction pointer = 0x20:0x81473525 stack pointer = 0x28:0xff811c98e370 frame pointer = 0x28:0xff811c98e390 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 = 1592 (txg_thread_enter) 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 0x8147357e at bp_get_dsize_sync+0x3e #7 0x8145e9b0 at dsl_scan_free_cb+0x120 #8 0x81430c74 at bpobj_iterate_impl+0xd4 #9 0x81430ebb at bpobj_iterate_impl+0x31b #10 0x8145fbc3 at dsl_scan_sync+0x4c3 #11 0x814670e0 at spa_sync+0x390 #12 0x81477739 at txg_sync_thread+0x139 #13 0x8080682f at fork_exit+0x11f #14 0x80b0366e at fork_trampoline+0xe dmesg : http://privatepaste.com/5c8c738627 What else can I add to help solving this bug? I'm not very good with freebsd. Thanks ___ 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 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
Kernel Panic any help?
Hi, as a happy freebsd user since about 2 years I have experienced my first kernel panic and have no idea what to do. My main machine crashed an hour ago and since then I can't get it to boot. The panic message: panic: ffs_clusteralloc: map mismatch cpuid = 0 KDB: stack backtrace #0 0x8063dcbe at kdb_backtrace+0x5e #1 0x8060aed7 at panic+0x187 #2 0x8082c1df at ffs_clusteralloc+0x4cf #3 0x80828448 at ffs_hashalloc+0x28 #4 0x80829a31 at ffs_reallocblks+0x421 #5 0x8068accf at cluster_write+0x4df #6 0x8084a1cf at ffs_write+0x58f #7 0x8097e6a2 at VOP_WRITE_APV+0xb2 #8 0x806a9f23 at vn_write+0x373 #9 0x8064dceb at dofilewrite+0x8b #10 0x8064e000 at kern_writev+0x60 #11 0x8064e085 at write+0x55 #12 0x809000c4 at amd64_syscall+0x1f4 #13 0x808e8a6c at Xfast_syscall+0xfc System setup: FreeBSD 8.3, up to date some file system ufs + soft updates root fs ufs without soft updates home encrypted via geli Regards, Jens -- Jens Jahnke Infos, Projekte, Themes und Downloads (http://www.jan0sch.de) ___ 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 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
kernel: panic: handle_written_inodeblock
Hi guys, I have FreeBSD 9.0-RELEASE installed on VMware vSphere ESXi 5.0 with open-vm-tools-nox11-471268_1. Everything seemed to be working great for a few days until I came into work this morning and it had crashed. I don't have a dump, but this message was in the log when it came back up: Feb 13 08:05:13 snake kernel: panic: handle_written_inodeblock: Invalid link count 65535 for inodedep 0xfe01d557f000 Feb 13 08:05:13 snake kernel: cpuid = 1 Feb 13 08:05:13 snake kernel: KDB: stack backtrace: Feb 13 08:05:13 snake kernel: #0 0x808680fe at kdb_backtrace+0x5e Feb 13 08:05:13 snake kernel: #1 0x80832cb7 at panic+0x187 Feb 13 08:05:13 snake kernel: #2 0x80a5714b at softdep_disk_write_complete+0x1c1b Feb 13 08:05:13 snake kernel: #3 0x808afcac at bufdone_finish+0x2c Feb 13 08:05:13 snake kernel: #4 0x808affe8 at bufdone+0x68 Feb 13 08:05:13 snake kernel: #5 0x807cf666 at g_io_schedule_up+0xa6 Feb 13 08:05:13 snake kernel: #6 0x807cfbec at g_up_procbody+0x5c Feb 13 08:05:13 snake kernel: #7 0x8080682f at fork_exit+0x11f Feb 13 08:05:13 snake kernel: #8 0x80b0366e at fork_trampoline+0xe It wouldn't mount the root filesystem and I had to manually run fsck on it. Ideas? dmesg: Copyright (c) 1992-2012 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 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 CPU: Intel(R) Xeon(R) CPU X5650 @ 2.67GHz (2660.00-MHz K8-class CPU) Origin = GenuineIntel Id = 0x206c2 Family = 6 Model = 2c Stepping = 2 Features=0xfe3fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS Features2=0x82982203SSE3,PCLMULQDQ,SSSE3,CX16,SSE4.1,SSE4.2,POPCNT,AESNI,HV AMD Features=0x28100800SYSCALL,NX,RDTSCP,LM AMD Features2=0x1LAHF TSC: P-state invariant real memory = 8589934592 (8192 MB) avail memory = 8231317504 (7849 MB) Event timer LAPIC quality 600 ACPI APIC Table: PTLTD APIC FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 4 package(s) x 1 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 Version 1.1 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: INTEL 440BX on motherboard acpi0: Power Button (fixed) Timecounter HPET frequency 14318180 Hz quality 950 Timecounter ACPI-fast frequency 3579545 Hz quality 900 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b 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 1.0 on pci0 pci1: ACPI PCI bus on pcib1 isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 UDMA33 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x10c0-0x10cf at device 7.1 on pci0 ata0: ATA channel 0 on atapci0 ata1: ATA channel 1 on atapci0 pci0: bridge at device 7.3 (no driver attached) pci0: base peripheral at device 7.7 (no driver attached) vgapci0: VGA-compatible display port 0x10d0-0x10df mem 0xd800-0xdbff,0xd080-0xd0ff irq 16 at device 15.0 on pci0 mpt0: LSILogic 1030 Ultra4 Adapter port 0x1400-0x14ff mem 0xd004-0xd005,0xd002-0xd003 irq 17 at device 16.0 on pci0 mpt0: MPI Version=1.2.0.0 pcib2: ACPI PCI-PCI bridge at device 17.0 on pci0 pci2: ACPI PCI bus on pcib2 em0: Intel(R) PRO/1000 Legacy Network Connection 1.0.3 port 0x2000-0x203f mem 0xd102-0xd103,0xd100-0xd100 irq 18 at device 0.0 on pci2 em0: Memory Access and/or Bus Master bits were not set! em0: Ethernet address: 00:50:56:b4:73:14 pcib3: ACPI PCI-PCI bridge at device 21.0 on pci0 pci3: ACPI PCI bus on pcib3 pcib4: ACPI PCI-PCI bridge at device 21.1 on pci0 pci4: ACPI PCI bus on pcib4 pcib5: ACPI PCI-PCI bridge at device 21.2 on pci0 pci5: ACPI PCI bus on pcib5 pcib6: ACPI PCI-PCI bridge at device 21.3 on pci0 pci6: ACPI PCI bus on pcib6 pcib7: ACPI PCI-PCI bridge at device 21.4 on pci0 pci7: ACPI PCI bus on pcib7 pcib8: ACPI PCI-PCI bridge at device 21.5 on pci0 pci8: ACPI PCI bus on pcib8 pcib9: ACPI PCI-PCI bridge at device 21.6 on pci0 pci9: ACPI PCI bus on pcib9 pcib10: ACPI PCI-PCI bridge at device 21.7 on pci0 pci10: ACPI PCI bus on pcib10 pcib11: ACPI PCI-PCI bridge at device 22.0 on pci0 pci11: ACPI PCI bus on pcib11 pcib12: ACPI PCI-PCI bridge at device 22.1 on pci0 pci12: ACPI PCI bus on pcib12 pcib13: ACPI PCI-PCI bridge at device 22.2 on pci0 pci13: ACPI PCI bus on pcib13 pcib14: ACPI PCI-PCI bridge at device 22.3 on pci0 pci14: ACPI PCI bus on pcib14 pcib15: ACPI PCI-PCI bridge at device 22.4
Question about kernel panic
Greetings, A server of mine kernel panicked and in the serial console it prints non stop these messages which are repeated again and again.. KDB: stack backtrace: #0 0x802fec5e at kdb_backtrace+0x5e #1 0x80287e57 at hardclock+0x117 #2 0x804610a2 at lapic_handle_timer+0xd2 #3 0x8045b22d at Xtimerint+0x8d #4 0x802e07d5 at softclock+0x305 #5 0x802a4bc4 at intr_event_execute_handlers+0x104 #6 0x802a6255 at ithread_loop+0x95 #7 0x802a1f4f at fork_exit+0x11f #8 0x8045ab9e at fork_trampoline+0xe interrupt total irq1: atkbd0 1 irq4: uart0 7376 irq14: ata01 irq18: atapci2 1237165 irq20: em0 86529 cpu0: timer232803254 cpu1: timer248008646 cpu2: timer248008707 cpu3: timer248008856 Total 978160831 KDB: stack backtrace: The server is: 8.2-STABLE FreeBSD 8.2-STABLE #1: Mon Jan 16 15:54:50 CPU: Intel(R) Xeon(TM) CPU 3.40GHz (3391.52-MHz K8-class CPU) Origin = GenuineIntel Id = 0xf4a Family = f Model = 4 Stepping = 10 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=0x649dSSE3,DTES64,MON,DS_CPL,EST,CNXT-ID,CX16,xTPR AMD Features=0x20100800SYSCALL,NX,LM AMD Features2=0x1LAHF TSC: P-state invariant real memory = 8589934592 (8192 MB) avail memory = 8243830784 (7861 MB) This machine will be rebooted on Monday, so from the time being I can only watch these messages repeated again and again. This server is mainly used for virtualization (virtualbox) and has ZFS, on a Sil 3112 and Intel 6300ESB SATA150 Controllers. I think that either the Sil controller or memory exhaustion due to ZFS and virtualbox has occured. How can I figure out what has really happened? Can I issue any command from the serial console? Thank you ___ 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
Removal Attempt of Directory under ZFS causes Kernel Panic
We have a ZFS file system under FreeBSD9.0 running on a virtual machine which had been running flawlessly for a bit over a month when I discovered that I had copied our home directory into /usr/home such that we had /usr/home/home. As root, I cd'd to /usr/home and then typed rm -r home at which point the kernel panicked after removing most of this bogus home directory. It got to one particular user's subdirectory, worked normally for a bit and then that's when the kernel panicked. What we found were normal symlinks and files that, if you make any attempt to delete them or touch them, provoke the kernel panic and crash. If you mount the file system on a rescue disk, it crashes that. We've tried mounting on a debian rescue disk that supported zfs and it didn't crash, but hung. A coworker ran the debug version of our kernel and it complained about values being out of bounds for the several files in question. Basically, in the roughly 20 years of working with unix systems, I have never once seen anything like this. We don't think it has to do with the virtual machine because you can trigger the disaster only by trying to remove the specific files. everything else appears to be working normally including creating and deleting other files and directories. My gut feeling is that it is related to zfs. The bogus home directory was an attempt by me to rsync from the actual hardware system to the virtual system back in November and every file came out owned by root. I got the rsync working properly and forgot about this home/home directory until yesterday when I realized the mistake and tried to delete it. Does this sound familiar to anybody? This is the first zfs installation I have used and I am not real wild about trying it again if we can't solve this mystery. We can't seem to duplicate the problem. Any ideas are appreciated. Martin McCormick WB5AGZ Stillwater, OK Systems Engineer OSU Information Technology Department Telecommunications Services Group ___ 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: Removal Attempt of Directory under ZFS causes Kernel Panic
On Fri, February 10, 2012 11:43 am, Martin McCormick wrote: Does this sound familiar to anybody? This is the first zfs installation I have used and I am not real wild about trying it again if we can't solve this mystery. We can't seem to duplicate the problem. Any ideas are appreciated. Nothing sounds familiar, but as a first step in debugging most ZFS issues, what does a `zpool scrub`, `zpool status -v` output? (Expect the scrub to take a while; depending on speed/size of your disks and system, it could be several hours, and it will run in the background.) Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. --- ___ 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: Removal Attempt of Directory under ZFS causes Kernel Panic
You will see a message on this group from Ryan Frederick who is a coworker of mine and who also posted a question about this same issue. There was a little confusion about which FreeBSD support group had been asked so my question and his are about the same machine. He submitted the stack trace so hopefully somebody can give us an idea as to how this happened. Thank you again. Martin McCormick ___ 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
Kernel Panic on 9.0-RELEASE When Attempting to Remove Files
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 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: Enter kernel panic
On 31.12.2011 17:05, Bernt Hansson wrote: Hello list! FreeBSD FQDN 8.2-STABLE FreeBSD 8.2-STABLE #0: Wed Sep 21 17:29:38 CEST 2011 root@FQDN:/usr/obj/usr/src/sys/DESKTOP amd64 testbox# If I press enter 4+ times during a cold boot I get a kernel panic. I call hardware problem. Maybe your motherboard has a faulty keyboard controller circuitry. Also, if your keyboard is connected via USB, then maybe the USB-chipset in your mobo is somehow broken/faulty/badly designed or just partially incompatible with freebsd. -- Arto Pekkanen ksym@IRCnet ___ 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
kernel Panic not dumping to swap
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 Sayers Direct: +612 95525510 Corinthian Engineering Office: +612 95525500 Suite 54, Jones Bay Wharf Fax: +612 95525549 26-32 Pirrama Rd email: da...@ci.com.au Pyrmont NSW 2009 Australia www: http://www.ci.com.au ___ 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 8.2-RELEASE generic kernel panic
hey folks, i have a problem related to a fresh-installed freebsd8.2-server, acting as host for 7 jails(mysql, apache, solr, ...). we are using AMD64 / GENERIC at the moment. this kind of kernel-panic occurs from time to time(about once a month, no regular basis) -- Panic String: free: address 0x806274fb0(0x806274000) has not been allocated. -- hardware: we are useing 2 XEON - cpus hw.machine: amd64 hw.model: Intel(R) Xeon(TM) CPU 2.66GHz hw.ncpu: 8 hw.machine_arch: amd64 and 24GB of ram. serverload is low(~3 - 4), swapspace 24GB to, but the OS is hardly ever(lets say never) using swapspace. i can not exclude a hardware fault for sure, because when excessively compiling ports, there was never a problem. on the other hand the address mentioned in the panicstring looks very high to me, so i'm not sure if this can be a valid address at all(memory-fault?) at all. could point me someone here into the right direction? how does freebsd allocate memory, and what address-size(32bit?) does it use? vmcore was written, so i followed the steps described at the freebsd developber-handbook for debugging this issue, but any help would be very appreciated. thx in advance for every piece of information, harri ___ 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
Kernel panic on power button
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? -- Eitan Adler ___ 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
sysinstall with Fixit option and RootOnZFS/GPTZFSBoot caused kernel panic on Vmware machine!
Hi everyone! I followed tut at http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/ to install FreeBSD Root on ZFS using GPT on my VMWARE virtual machine. When I go to step Install FreeBSD to zroot kernel-panic appeared! My virtual machine detail: RAM: 512MB HDD: 10GB vmware workstation: 7.1.0 build-261024 with FreeBSD 8.1-REL! See more detail about panic on image attached file. Please let me know how to solve this problem. Best regards, Mr.Hien -- Mr.Hien E-mail: phanquoch...@gmail.com Website: www.mrhien.info ___ 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: sysinstall with Fixit option and RootOnZFS/GPTZFSBoot caused kernel panic on Vmware machine!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 21/09/2010, at 7:29 PM, Phan Quoc Hien wrote: Hi everyone! I followed tut at http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/ to install FreeBSD Root on ZFS using GPT on my VMWARE virtual machine. When I go to step Install FreeBSD to zroot kernel-panic appeared! It sounds like you are either low on ram, or are using i386. Look at http://wiki.freebsd.org/ZFSTuningGuide and follow the steps here in the loader prompt on the live system, and also add the same options to your loader.conf when you install the system. My virtual machine detail: RAM: 512MB HDD: 10GB vmware workstation: 7.1.0 build-261024 with FreeBSD 8.1-REL! See more detail about panic on image attached file. Please let me know how to solve this problem. Best regards, Mr.Hien Hope this helps you. I think buwping the amount of ram in your VM wouldnt hurt either, ZFS really needs 1GB minimum, 2GB or more is preferred iirc. -- Mr.Hien E-mail: phanquoch...@gmail.com Website: www.mrhien.info ___ 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 William Brown pgp.mit.edu -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) iQIcBAEBAgAGBQJMmN1FAAoJEHF16AnLoz6JYiMP/3xU6a3pd90kEsWIOgaWfQZ5 ff0tCYdMoMTmIZ9zgB7u7/YA7kIEp4o7zM8MbYPRt8OcC+9oWQBjbCvVeKXLEOil 6faRrYR3CxBSa1CIUxTsfPS3OR3rOB8GlTMJObW/UrOPonVgpyD6RMW/J3wMbme9 pN0V2xOSwOv9rgdFWwHgAOT4eBpzmFeOAbLERFMcv3sUm2l1k56IUpgEDQNoHVPY wp8Cxsl8QClP5bTpl2iSXvt0krCvo16HA64G4I1Bm6FSAY/aP45L5zouABHyHyIT RCZjTzCaaWHHXvwErAdQfx6oBFuyAxzwgb1ZRdYMDoFHs1swJd3D0pWIYcjQ9ILz 3AR1YFY5t1SE+kP03Fssoz/HNpq2lO3IgjJsg/T8bsMEbb2/6zJlCKF5wAsMZHdY 1kj+75IsZ+phbzaPrpdL8kjfTWBP1De3WWH7sN85wGAw2c1mQCFLg9bsC2Ahxe1V S/kRWwKDoJPvBaEEdo5LM7CLfoneXOR3taa3mqLvgkWAwyTG0iEtwwxhxMMFSmpp InMWYplq/zu4au27+ujW+f6Mj3GhpSzaMNAfGkGdpsn4D4muBWgrLt04nSxuvjX6 K3ZoGAMlnH9rOLwZLvu2uaxKGZnyf/TYndgPQtpNm3iq7liXoSYnNl3B4NeNjI7j l5wz40a62K6b2J/G/cIa =6/hT -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
FreeBSD 8.0 linux emulator kernel panic
I'm having issues with the Fedora Core6 linux emulator on FreeBSD 8.0 it panics when i run HLDS, the same issue was addressed by Daniel Ballenger in http://lists.freebsd.org/pipermail/freebsd-stable/2010-February/054646.htmlbut i did not get the fix. Giovanni Trematerra gave a response that it was fix in a r200768 now it is clear that i do not know that that code means (in my eyes it's a bsd build or smth) but i'm currently running the latest 8.0-RELEASE-p3 available. Please advise on how to patch the kernel panic. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 8.0 linux emulator kernel panic
On Sunday 06 June 2010 19:31:00 Bogdan Webb wrote: I'm having issues with the Fedora Core6 linux emulator on FreeBSD 8.0 it panics when i run HLDS, the same issue was addressed by Daniel Ballenger in http://lists.freebsd.org/pipermail/freebsd-stable/2010-February/054646.html but i did not get the fix. Giovanni Trematerra gave a response that it was fix in a r200768 now it is clear that i do not know that that code means (in my eyes it's a bsd build or smth) but i'm currently running the latest 8.0-RELEASE-p3 available. Please advise on how to patch the kernel panic. r200768 uniquely identifies a single change to the FreeBSD source code. In this case it identifies a bugfix to linux_signal.c. You need to run 8-STABLE (currently it will show up as 8.1-PRERELEASE) to get the fix. I know it works because I also run multiple HLDS processes on FreeBSD. To get 8-STABLE: cvsup/csup the sources to RELENG_8, then follow these instructions to upgrade: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html Good luck! -- Pieter de Goeje ___ 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
Force reboot after kernel panic.
How can I enforce this? Presently the system just hangs. Thanks. ___ 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: Force reboot after kernel panic.
-Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd- questi...@freebsd.org] On Behalf Of Paul Halliday Sent: Tuesday, April 13, 2010 3:17 PM To: questi...@freebsd.org Subject: Force reboot after kernel panic. How can I enforce this? Presently the system just hangs. Add to kernconf: options KDB_UNATTENDED -- Regards, T. Koeman, MTh/BSc/BPsy; Technical Monk MediaMonks B.V. (www.mediamonks.com) Please quote all replies in correspondence. smime.p7s Description: S/MIME cryptographic signature
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
kernel panic when if_lagg is not loaded.
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. /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 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
7.2-RELEASE-p5 and kernel panic with mpt driver
Hi folks. I updated my server from 7.0 to 7.2 over the Christmas period (sources updated to 26th Dec I think). I have long suspected there was an issue with a hard drive in the server but the hosts told me that the useless messages logged by 7.0 were normal. Well it turns out one of the drives failed today and caused the array to keep changing status. This in turn caused about 20 kernel panics in until the hosts pulled the drive and put a new one. I noted someone else talking about this back in May on the FreeBSD-stable list and the outcome seemed to be that a patch was rolled in but it would appear that whatever this patch is - I don't have it! Can anyone point me in the right direction? Thanks, Colin. ___ 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: 7.2-RELEASE-p5 and kernel panic with mpt driver
It's a little difficult to tell from the lack of info you've provided, but I'd assume you're running a release to which the patch has not been applied. To do this, you'd need to upgrade to 7-STABLE, 8-RELEASE, or 8-STABLE. CURRENT would work too, but that's not really a candidate for production servers and you should think hard about putting STABLE on one. That being said, STABLE is generally quite stable and I don't have a problem with one in production provided they are reasonably tested before deployment. -- Adam Vande More My supfile uses the tag *default release=cvs tag=RELENG_7_2 The docs on stable say to use RELENG_7 for which I assumed was out of date with the docs not always being updated frequently. Is there a different tag for 7.2 Stable or am I not understanding the different versions? Thanks, Colin. ___ 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: 7.2-RELEASE-p5 and kernel panic with mpt driver
On Tue, Jan 5, 2010 at 3:59 PM, Colin Waring free...@southportcomputers.co.uk wrote: My supfile uses the tag *default release=cvs tag=RELENG_7_2 The docs on stable say to use RELENG_7 for which I assumed was out of date with the docs not always being updated frequently. Is there a different tag for 7.2 Stable or am I not understanding the different versions? Thanks, Colin. Your understanding is incorrect. RELENG_7 is stable, RELENG_7_0, RELENG_7_1 and RELENG_7_2 are snapshots of RELENG_7. RELENG_X will always be more current than RELENG_X_Y. Trust the docs unless you explicitly know differently. -- 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 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
kernel panic on SATA drive
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
Kernel panic
Здравствуйте, Freebsd-questions. Fatal trap 18: integer divide fault while in kernel mode cpuid = 0; apic id = 00 instruction pointer = 0x20:0xc0af79b5 stack pointer = 0x28:0xc1b55cb8 frame pointer = 0x28:0xc1b55cb8 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, IOPL = 0 current process = 11 (idle: cpu0) trap number = 18 panic: integer divide fault cpuid = 0 Uptime: 2h56m59s Physical memory: 115 MB Dumping 33 MB: 18 2 Reading symbols from /boot/kernel/ng_socket.ko...Reading symbols from /boot/kernel/ng_socket.ko.symbols...done. done. Loaded symbols for /boot/kernel/ng_socket.ko Reading symbols from /boot/kernel/ng_mppc.ko...Reading symbols from /boot/kernel/ng_mppc.ko.symbols...done. done. Loaded symbols for /boot/kernel/ng_mppc.ko Reading symbols from /boot/kernel/rc4.ko...Reading symbols from /boot/kernel/rc4.ko.symbols...done. done. Loaded symbols for /boot/kernel/rc4.ko Reading symbols from /boot/kernel/ng_iface.ko...Reading symbols from /boot/kernel/ng_iface.ko.symbols...done. done. Loaded symbols for /boot/kernel/ng_iface.ko Reading symbols from /boot/kernel/ng_ppp.ko...Reading symbols from /boot/kernel/ng_ppp.ko.symbols...done. done. Loaded symbols for /boot/kernel/ng_ppp.ko #0 doadump () at pcpu.h:196 196 __asm __volatile(movl %%fs:0,%0 : =r (td)); reboot ~ Wed Sep 2 22:47 kes ttyp110.10.16.18 Wed Sep 2 22:29 - crash (00:17) kes ttyp010.10.16.18 Wed Sep 2 22:29 - crash (00:18) reboot ~ Wed Sep 2 22:27 kes ttyp010.10.16.18 Wed Sep 2 22:19 - crash (00:07) reboot ~ Wed Sep 2 22:19 kes ttyp010.10.16.18 Wed Sep 2 22:17 - crash (00:02) reboot ~ Wed Sep 2 22:09 reboot ~ Wed Sep 2 21:56 reboot ~ Wed Sep 2 21:46 reboot ~ Wed Sep 2 21:39 reboot ~ Wed Sep 2 21:34 reboot ~ Wed Sep 2 21:14 reboot ~ Wed Sep 2 21:05 reboot ~ Wed Sep 2 20:47 reboot ~ Wed Sep 2 20:41 reboot ~ Wed Sep 2 20:18 reboot ~ Wed Sep 2 18:51 reboot ~ Wed Sep 2 17:27 reboot ~ Wed Sep 2 14:29 reboot ~ Wed Sep 2 10:58 I have build latest 7.2 vpn# uname -a FreeBSD vpn.in 7.2-RELEASE-p3 FreeBSD 7.2-RELEASE-p3 #0: Mon Aug 31 23:57:36 EEST 2009 k...@vpn.in:/usr/obj/usr/src/sys/KES_KERN_v72 i386 That version is not stable??? -- С уважением, Коньков mailto:kes-...@yandex.ru ___ 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[2]: Kernel panic
Здравствуйте, Mel. Вы писали 12 августа 2009 г., 19:59:39: MF 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? MF kgdb /boot/kernel/kernel /var/crash/vmcore.4 kes# kgdb /boot/kernel/kernel /var/crash/vmcore.4 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... Cannot access memory at address 0x0 (kgdb) -- С уважением, Коньков mailto:kes-...@yandex.ru ___ 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
Kernel panic
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? -- С уважением, Коньков mailto:kes-...@yandex.ru ___ 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
kernel panic on SATA drive
The FreeBSD Developers' Handbook describes how to get panic information (and dig out further details). http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html#KERNELDEBUG-OBTAIN Was there any output before ad7: FAILURE - device detached? Losing the drive in the bios makes me think hardware, but I'd check for any firmware problems/updates if they exist. I have not tried yet, but FreeBSD8 is supposed to finally handle the anxiety of losing a drive. http://freebsdfoundation.org/press/2008Dec-newsletter.shtml#Project1 I would try smartctl from ports; run a long scan and read the full output to see if it passes or if you get a response like: # 1 Extended offlineCompleted: read failure 20% 32490 308342849 Also look above that output to see if there any metioned 'Error ## occured at disk power-on lifetime' type of messages. to scan, run: smartctl -t long /dev/ad7 after the scan, read output with: smartctl -a long /dev/ad7 What motherboard is it? GeForce 8200 sounds like a graphics chipset to me. For hardware analysis, try to isolate it to a particular drive (sounds like it is only the seagate), cable (data or power), motherboard sata port. When the drive is not recognized, does a coldboot redetect it? Does the drive start any audible clicking? What model of drive is it? Make sure the drive is dusted off, increase the cooling, and try again; I have a drive that flakes out if the three speed antec fan in front of it is only on low but stabilizes when kept cooler; its a great hint to me that the drive is near life's end. ___ 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
mount_smbfs + suspend = kernel panic
Hi guys, I use mount_smbfs on my notebook and I have a little nasty problem.. Sometimes I have kernel panic when resuming after the suspend. The issue seems to happen when I go to suspend with my USB network (WiFi) adapter plugged in (I do use /etc/rc.d/netif stop rum0 before going to suspend), then I resume the notebook without the adapter, then I suspend it again, and finally I resume it with the adapter plugged in. The system panics. Maybe there are any workarounds to avoid the problem.. Should I do umount all smbfs' before I go to suspend?.. Is there any other more elegant way? Here is the kernel buffer and the backtrace: kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x18 fault code = supervisor read, page not present instruction pointer = 0x20:0xc081fa05 stack pointer = 0x28:0xe8cf2adc frame pointer = 0x28:0xe8cf2af8 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= resume, IOPL = 0 current process = 37632 (smbiod4) trap number = 12 panic: page fault cpuid = 0 Uptime: 7d12h57m21s Physical memory: 2022 MB Dumping 275 MB: (CTRL-C to abort) (CTRL-C to abort) (CTRL-C to abort) 260 244 228 (CTRL-C to abort) (CTRL-C to abort) (CTRL-C to abort) 212 196 180 164 148 132 116 100 84 68 52 36 20 4 #0 doadump () at pcpu.h:196 #1 0xc07e8767 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 #2 0xc07e8a39 in panic (fmt=Variable fmt is not available. ) at /usr/src/sys/kern/kern_shutdown.c:574 #3 0xc0aecd3c in trap_fatal (frame=0xe8cf2a9c, eva=24) at /usr/src/sys/i386/i386/trap.c:939 #4 0xc0aed6bf in trap (frame=0xe8cf2a9c) at /usr/src/sys/i386/i386/trap.c:320 #5 0xc0ad207b in calltrap () at /usr/src/sys/i386/i386/exception.s:159 #6 0xc081fa05 in turnstile_broadcast (ts=0x0, queue=0) at /usr/src/sys/kern/subr_turnstile.c:836 #7 0xc07d93f2 in _mtx_unlock_sleep (m=0xc8d82d94, opts=0, file=0xc107c6c3 /usr/src/sys/modules/smbfs/../../netsmb/smb_iod.c, line=97) at /usr/src/sys/kern/kern_mutex.c:619 #8 0xc07d9752 in _mtx_unlock_flags (m=0xc8d82d94, opts=0, file=0xc107c6c3 /usr/src/sys/modules/smbfs/../../netsmb/smb_iod.c, line=97) at /usr/src/sys/kern/kern_mutex.c:210 #9 0xc106fb73 in smb_iod_invrq (iod=Variable iod is not available. ) at /usr/src/sys/modules/smbfs/../../netsmb/smb_iod.c:97 #10 0xc1070d57 in smb_iod_addrq (rqp=0xc8d82d00) at /usr/src/sys/modules/smbfs/../../netsmb/smb_iod.c:424 #11 0xc106d28c in smb_rq_enqueue (rqp=0xc8d82d00) at /usr/src/sys/modules/smbfs/../../netsmb/smb_rq.c:193 #12 0xc106d6d8 in smb_rq_simple (rqp=0xc8d82d00) at /usr/src/sys/modules/smbfs/../../netsmb/smb_rq.c:174 #13 0xc106b9e4 in smb_smb_treeconnect (ssp=0xc778d500, scred=0xc7a6e144) at /usr/src/sys/modules/smbfs/../../netsmb/smb_smb.c:561 #14 0xc10708b8 in smb_iod_thread (arg=0xc7a6e100) at /usr/src/sys/modules/smbfs/../../netsmb/smb_iod.c:212 #15 0xc07c2159 in fork_exit (callout=0xc10705c0 smb_iod_thread, arg=0xc7a6e100, frame=0xe8cf2d38) at /usr/src/sys/kern/kern_fork.c:810 #16 0xc0ad20f0 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:264 Best regards, EforeZZ ___ 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
kernel panic on SATA drive
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. The first time I had the problem, it would regularly happen when I tried to install a particular port (sudo). Then I changed where the SATA cable was plugged in and tried un/re-plugging the USB external drive and rebooting and managed to get it working (so I thought). One weird aspect of that process is that the BIOS would not even list the SATA drive until I switched it to a different plug... freaked me out a bit. Also during POST it would hang for many seconds, when I had the USB drive plugged in, until I went through my random plugging/unplugging/replugging shenanigans. But now it has happened again, this time while copying lots of files from the USB external drive to the SATA one. Both drives are recognized by BIOS (and FreeBSD) on reboot this time, at least. But I'm hesitant to just 'call it good' - I'd like this to be a stable server (: I manually transcribed the bulk of the output - is there a nicer way to get the output of a kernel panic so I can copy/paste? I didn't find an obvious command, though I'm no FreeBSD guru. If someone could tell me how to get that output, I'd be greatful. output below ad7: FAILURE - device detached g_vfs_done():ad7s1d[WRITE(offset=340978335744, length=16384)]error = 6 g_vfs_done():ad7s1d[WRITE(offset=340978352128, length=16384)]error = 6 /dev: got error 6 while accessing filesystem panic: softdep_deallocate_dependencies: unrecovered I/O error cpuid=2 Uptime: 15h23m39s Physical memory: 7923MB Dumping 733MB: 718 702 686 670 654 638twe0:completion event for nonbusy command twe0: completion event for nonbusy command twe0: completion event for nonbusy command twe0: completion event for nonbusy command twe0: completion event for nonbusy command twe0: completion event for nonbusy command twe0: FATAL STATUS BIT(S) 20MCERR twe0: status 13207fd2CQEMPTY,UCREADY,RQEMPTY,MCERR, ### At this point in the log a bunch of output starts getting interleaved, character-by-character even. ### Maybe due to multi-cpus dumping output simultaneously? I don't know... ### eventually... twe0: can't drain AEN queue twe0: controller reset in progress twe0: reset 1 failed ### snip more failing messages twe0: can't reset controller, giving up #Then some more stuff that I haven't written down end log --- So any thoughts? Maybe it's just a mobo / chipset compatibility issue? I should have known with a mobo that says GeForce 8200 for chipset. I thought NVIDIA support was pretty good in FreeBSD though... Do you think recompiling my own kernel would help? Do you think installing a different version of FreeBSD would help? (My main experience is with 6.2) It was quite odd to me that even the BIOS stopped recognizing the SATA drive the first time. Any thoughts on that? Thanks for any feedback -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 - 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
kernel panic - umount xfs partition
Hello, I have a Dabian 5.0 and FreeBSD 7.2-RELEASE-p2 on i386 athlon-xp. I have two partitions under Debian. They are xfs file system. So I mount it from FreeBSD # mount -t xfs -o ro /dev/ad0s1 /mnt # ls /mnt # umount /mnt Everything is OK, but now I do the following # mount -t xfs -o ro /dev/ad0s2 /mnt # ls /mnt # cp /mnt/my_file /home/zbigniew when cp finish the system was frozen and after a while do reboot. After reboot I saw coredump on the swap file. This is only for me or also maybe you have such problem. My system is for desktop usage. I work at school. 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
Kernel Panic
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? Thanks, Shawn ___ 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:Burncd-Kernel Panic
I'm using an Intel DG33BU board with a SATA HD and SATA optical drives. Using FreeBSD 7.1 AMD64 I get a kernel panic and subsequent file system corruption when attempting to burn a cd using the burncd utility. I can avoid this easily enough by using cdrecord and growisofs which work as they should. I wanted to alert others using the same or similar boards. If anyone has any ideas, I'd like to know why this happens. Is there a planned update to the burncd software or how it addresses the system that might remedy this in future releases? --David I'm assuming the reason for the panic is that SATAII is substantially incompatible with the old ATAPI standard that burncd was designed for. In light of the fact that soon, most hardware (even older hardware) will feature SATA drives, it would be nice if there were a compatible base system burn utility. Burncd could linger on for the sake of much older machines, but could be prominently labeled as legacy software. --David yet again ___ 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
BurnCd--Kernel Panic
I'm using an Intel DG33BU board with a SATA HD and SATA optical drives. Using FreeBSD 7.1 AMD64 I get a kernel panic and subsequent file system corruption when attempting to burn a cd using the burncd utility. I can avoid this easily enough by using cdrecord and growisofs which work as they should. I wanted to alert others using the same or similar boards. If anyone has any ideas, I'd like to know why this happens. Is there a planned update to the burncd software or how it addresses the system that might remedy this in future releases? --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
Kernel panic on disk timeout with 3ware controller
Hello, I am using FreeBSD 7.1 RELEASE on a system with a 3Ware RAID controller, the system resides on a RAID volume. I get kernel panics complaining about page faults, swap space and a drive timeout. This is, I think, due to a faulty disk. The 3ware controller detects a timeout, relaunches the disk and retries with success. This is, I suppose, invisible for FreeBSD. I am not experiencing problems with normal disk reads and writes, but when it happens on the swap space FreeBSD does mind, gives a timeout and panics. Can this behavior be changed? I am never on site and I would prefer a simple error message and not a kernel panic, I can change the disk with a hotspare remotely. Impossible when the server is down. Big thanks, Jan ___ 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
Kernel panic. Unsure of cause.
I had just closed Firefox 3 and went to open the Thunar file manager from XFCE and my machine locked up. After ~20 seconds, it rebooted, leaving a 310MB vmcore.0 in /var/crash along with a bounds and info.0 file. I have no idea how to investigate these problems, so please excuse the ignorance that may follow: I followed a section in the FreeBSD Developers Handbook on debugging the kernel, the following means absolutely nothing to me: newton# kgdb /boot/kernel/kernel /var/crash/vmcore.0 [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: kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x18 fault code = supervisor read, page not present instruction pointer = 0x20:0xc0785825 stack pointer = 0x28:0xe929ba58 frame pointer = 0x28:0xe929ba74 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= resume, IOPL = 0 current process = 1072 (Thunar) trap number = 12 panic: page fault cpuid = 1 Uptime: 7h35m34s Physical memory: 3058 MB Dumping 310 MB: 295 279 263 247 231 215 199 183 167 151 135 119 103 87 71 55 39 23 7 #0 doadump () at pcpu.h:195 195 pcpu.h: No such file or directory. in pcpu.h (kgdb) backtrace #0 doadump () at pcpu.h:195 #1 0xc0754457 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409 #2 0xc0754719 in panic (fmt=Variable fmt is not available. ) at /usr/src/sys/kern/kern_shutdown.c:563 #3 0xc0a4905c in trap_fatal (frame=0xe929ba18, eva=24) at /usr/src/sys/i386/i386/trap.c:899 #4 0xc0a499df in trap (frame=0xe929ba18) at /usr/src/sys/i386/i386/trap.c:280 #5 0xc0a2fc0b in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #6 0xc0785825 in turnstile_broadcast (ts=0x0, queue=0) at /usr/src/sys/kern/subr_turnstile.c:835 #7 0xc0747da2 in _mtx_unlock_sleep (m=0xc81c60a0, opts=0, file=0x0, line=0) at /usr/src/sys/kern/kern_mutex.c:605 #8 0xc06fdbd1 in pfs_getextattr (va=0xe929bafc) at pseudofs_internal.h:110 #9 0xc0a5e667 in VOP_GETEXTATTR_APV (vop=0xc0b723e0, a=0xe929bafc) at vnode_if.c:2398 #10 0xc07c047e in extattr_get_vp (vp=0xc8fbdaa0, attrnamespace=1, attrname=0xe929bb71 mime_type, data=0x0, nbytes=0, td=0xccc81c60) at vnode_if.h:1289 #11 0xc07c0916 in extattr_get_fd (td=0xccc81c60, uap=0xe929bcfc) at /usr/src/sys/kern/vfs_extattr.c:408 #12 0xc0a49635 in syscall (frame=0xe929bd38) at /usr/src/sys/i386/i386/trap.c:1035 #13 0xc0a2fc70 in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s:196 #14 0x0033 in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) Contents of bound and info,0 files in /var/crash (vmcore.0 is too big for me to put on the Internet) bounds: newton# cat bounds 1 info.0: newton# cat info.0 Dump header from device /dev/ad6s2b Architecture: i386 Architecture Version: 2 Dump Length: 326086656B (310 MB) Blocksize: 512 Dumptime: Sun Feb 15 18:14:51 2009 Hostname: newton.turnerfrontier.net Magic: FreeBSD Kernel Dump Version String: FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008 r...@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC Panic String: page fault Dump Parity: 3822966285 Bounds: 0 Dump Status: good Some information from the output of dmesg: FreeBSD 7.0-RELEASE #0 CPU: Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz (2999.96-MHz 686-class CPU) Origin = GenuineIntel Id = 0x10676 Stepping = 6 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=0x8e3fdSSE3,RSVD2,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,b19 AMD Features=0x2010NX,LM AMD Features2=0x1LAHF Cores per package: 2 real memory = 3220701184 (3071 MB) avail memory = 3146219520 (3000 MB) I'm also using an nVidia 9500GT with 512MB of on-board memory: vgapci0: VGA-compatible display port 0xac00-0xac7f mem 0xfd00-0xfdff,0xc000-0xdfff,0xfa00-0xfbff irq 16 at device 0.0 on pci1 Thank you for reading this. If there is anything further I can do to investigate this I would appreciate you telling me so. I haven't noticed any problems with the hardware recently, and the computer is fairly new. -- Charlie Turner. ___ freebsd-questions@freebsd.org mailing list
Xorg causes kernel panic (intel g45 chipset)
Hi, 7.1-RELEASE installs fine on the machine, but when I try to start xorg I get kernel page fault. it's Intel G45 GMA-4500HD. I saw a thread back in September 2008 that added support for the G45 chipset, did it make its way into the 7.1 release? Thanks, Howard ___ 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
Very slow boot process (from installation disk), followed by kernel panic
Hi, I'm trying to install FreeBSD on my HP Pavilion (AMD Phenom 8650 Triple Core 2.3 GHz, Hitachi SCSI disk drive, booting from ATAPI DVD ROM). I am booting with verbose logging turned on. When the boot process reaches the line Mounting root from ufs:/dev/md0c a series of messages saying t_delta [long number] too short/too long appear for several minutes. When /stand/sysinstall running as init on vty0 is finally reached, more of the messages appear. Finally, sysinstall is started, but keyboard response is very slow. After, a few minutes a kernel panic occurs spin lock held too long and the computer reboots. I've seen bug reports with this sort of kernel panic, but not during installation. Thanks in advance, Zach ___ 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
kernel panic
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? Kamlesh MS CS, CSUS ___ 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
kernel panic
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 Type InUse MemUse HighUse Requests Size(s) GEOM 22832K - 1206 16,32,64,128,256,512,1024,2048 isadev20 2K - 20 64 CAM dev queue 5 1K -5 64 ata_generic 6 6K -6 1024 ad_driver 5 1K -5 32 ata_dma 4 1K -4 128 cdev21 3K - 21 128 sigio 1 1K -1 32 filedesc9023K - 1606 16,256,512 kenv 113 8K - 115 16,32,64,4096 kqueue 0 0K - 166 128,1024 proc-args39 2K - 7402 16,32,64,128,256 ata_cam 4 4K - 27 64,256,1024 ithread63 6K - 65 16,64,128 acd_driver 1 2K -1 2048 KTRACE 10013K - 100 128 ath_hal 623K -6 128,256,512,1024 linker 106 361K - 520 16,32,64,256,1024,2048,4096 lockf14 1K -12884 64 athdev 337K -3 256 ip6ndp 4 1K -4 64,128 temp20 137K - 6437 16,32,64,128,256,512,1024,2048,4096 devbuf 489 3364K -23810 16,32,64,128,256,512,1024,2048,4096 CAM queue17 1K - 112 16 module 24716K - 273 64,128 mtx_pool 1 4K -1 4096 kbdmux 6 9K -6 16,128,256,2048,4096 subproc 192 371K - 1707 256,4096 proc 2 4K -2 2048 session27 2K - 125 64 pgrp36 3K - 169 64 cred34 9K - 6399 256 uidinfo 4 1K - 101 32,512 plimit20 5K - 1286 256 sysctltmp 0 0K - 284 16,32,64,128 sysctloid 291689K - 3116 16,32,64 sysctl 0 0K - 475 16,32,64 umtx 112 7K - 112 64 p1003.1b 1 1K -1 16 SWAP 2 141K -2 64 bus-sc5828K - 963 16,32,64,128,256,512,1024,2048,4096 bus 80036K - 3148 16,32,64,128,1024 devstat1633K - 16 16,4096 eventhandler65 4K - 65 32,64,128 kobj 148 296K - 225 2048 CAM SIM 5 1K -5 128 rman 16110K - 525 16,32,64 CAM periph 4 1K -9 16,32,128 sbuf 0 0K - 792 16,32,64,128,256,512,1024,2048,4096 CAM XPT4213K - 147 16,32,64,256,512,1024 taskqueue17 2K - 17 16,128 Unitno 7 1K - 13 16,64 iov 0 0K - 561 16,64,128,256 ioctlops 0 0K - 5774 16,32,64,128,256,512,1024 msg 425K -4 1024,4096 sem 4 7K -4 256,1024,4096 shm 112K -1 ttys 1232 175K - 4907 128,1024 ptys 3 1K -3 128 mbuf_tag 5382 169K - 5399 32 scsi_cd 0 0K -5 16 pcb2577K - 195 16,32,64,2048,4096 soname 4 1K - 1753 16,32,128 biobuf1122K - 277 2048 vfscache 1 128K -1 cl_savebuf 0 0K - 1672 32,64 vfs_hash 164K -1 vnodes 1 1K -1 128 vnodemarker 0 0K - 9656 512 mount 139 5K - 325 16,32,64,128,256 BPF 965K - 10 16,64,128,256 ether_multi15 1K - 16 16,32,64 ifaddr 23515K - 235 16,32,64,128,256,512,2048 ifnet 4 4K -4 128,1024 clone 520K -5 4096 arpcom 2 1K -2 16 lo 1 1K -1 16 entropy 102464K - 1024 64 routetbl 15435K - 233 16,32,64,128,256 80211node 8081 21705K - 8081 16,32,512 80211scan 5 3K -5 256,2048 in_multi 2 1K -2 64 IpFw/IpAcct 1
usb port use causes kernel panic on boot. why?
can someone explain to me, please, why i get a kernel panic on boot w/ the latest 7.1 when i have something plugged into a usb port? thx. david coder network engineer emeritus verio/ntt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Kernel Panic on 7.0-REL
Hello all, I keep getting a kernel panic every Saturday night, so I figured I would go through the core dump. # uname -a FreeBSD xx.fsklaw.com 7.0-RELEASE FreeBSD 7.0-RELEASE #1: Wed Apr 23 08:01:10 PDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/TEST amd64 # kgdb kernel.symbols /var/crash/vmcore.2 [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: Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address= 0x250 fault code= supervisor read data, page not present instruction pointer= 0x8:0x80482a5d stack pointer= 0x10:0xb184b570 frame pointer= 0x10:0xff003f9cf6a0 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= 37920 (bsdtar) trap number= 12 panic: page fault cpuid = 1 Uptime: 7d2h23m33s Physical memory: 2034 MB Dumping 415 MB: 400 384 368 352 336 320 304 288 272 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) where #0 doadump () at pcpu.h:194 #1 0x0004 in ?? () #2 0x8048e0d9 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409 #3 0x8048e4dd in panic (fmt=0x104 Address 0x104 out of bounds) at /usr/src/sys/kern/kern_shutdown.c:563 #4 0x80786f44 in trap_fatal (frame=0xff003f9cf6a0, eva=18446742975518566608) at /usr/src/sys/amd64/amd64/trap.c:724 #5 0x80787315 in trap_pfault (frame=0xb184b4c0, usermode=0) at /usr/src/sys/amd64/amd64/trap.c:641 #6 0x80787c58 in trap (frame=0xb184b4c0) at /usr/src/sys/amd64/amd64/trap.c:410 #7 0x8076d88e in calltrap () at /usr/src/sys/amd64/amd64/exception.S:169 #8 0x80482a5d in _mtx_lock_sleep (m=0xff009662c410, tid=18446742975265175200, opts=Variable opts is not available. ) at /usr/src/sys/kern/kern_mutex.c:335 #9 0x804f5978 in vfs_vmio_release (bp=0x9a329220) at /usr/src/sys/kern/vfs_bio.c:1530 #10 0x804f77f4 in getnewbuf (slpflag=0, slptimeo=0, size=Variable size is not available. ) at /usr/src/sys/kern/vfs_bio.c:1847 #11 0x804f8801 in getblk (vp=0xff000b71c5d0, blkno=294994, size=16384, slpflag=0, slptimeo=0, flags=Variable flags is not available. ) at /usr/src/sys/kern/vfs_bio.c:2602 #12 0x806a3d5b in ffs_balloc_ufs2 (vp=0xff000b71c5d0, startoffset=Variable startoffset is not available. ) at /usr/src/sys/ufs/ffs/ffs_balloc.c:844 #13 0x806bf6e5 in ffs_write (ap=0xb184ba10) at /usr/src/sys/ufs/ffs/ffs_vnops.c:720 #14 0x807e04e5 in VOP_WRITE_APV (vop=0x80a6b0e0, a=0xb184ba10) at vnode_if.c:691 #15 0x8051ae41 in vn_write (fp=0xff00284771e0, uio=0xb184bb00, active_cred=Variable active_cred is not available. ) at vnode_if.h:373 #16 0x804c6468 in dofilewrite (td=0xff003f9cf6a0, fd=3, fp=0xff00284771e0, auio=0xb184bb00, offset=Variable offset is not available. ) at file.h:254 #17 0x804c676e in kern_writev (td=0xff003f9cf6a0, fd=3, auio=0xb184bb00) at /usr/src/sys/kern/sys_generic.c:401 #18 0x804c67ec in write (td=0xff009662c410, uap=0xff003f9cf6a0) at /usr/src/sys/kern/sys_generic.c:317 #19 0x80787597 in syscall (frame=0xb184bc70) at /usr/src/sys/amd64/amd64/trap.c:852 #20 0x8076da9b in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:290 #21 0x000800a66d3c in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) up 8 #8 0x80482a5d in _mtx_lock_sleep (m=0xff009662c410, tid=18446742975265175200, opts=Variable opts is not available. ) at /usr/src/sys/kern/kern_mutex.c:335 335owner = (struct thread *)(v ~MTX_FLAGMASK); (kgdb) p owner $1 = (volatile struct thread *) 0xfff8 (kgdb) p v $2 = 18446744073709551615 Note the uptime, this happens every Saturday for the last three weeks. I have a cronjob that tar/bzips a drive and scps it to another box, but that runs nightly at midnight on the cronjob, and this happens weekly but only on Saturday, same cronjob same data. I figured if it happened again, I would hit up the mailing list. Hopefully you all can suggest what to upgrade to or how to further troubleshoot this issue. Thanks a bundle
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]
Kernel panic! 7.0-RELEASE-p4
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?? ___ 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]
Kernel Panic help.
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 ___ 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]
Rev 7.0 kernel panic with USB camera
I get a kernel panic whenever I connect my digital camera (Olympus C-2040Z) on my 7.0 system. It looks like a rev. 7 related problem, everything works fine on the same PC if I boot into rev. 6.3. This might already be covered by PR usb/117313: [umass] [panic] panic on usb camera insertionraised http://www.freebsd.org/cgi/query-pr.cgi?pr=usb/117313 but wading through crash dumps is new uncharted territory for me. Could anyone advise me if the attached kgdb output suggests that it's the same problem or something different? - kestrel:/boot/kernel% uname -a FreeBSD kestrel.lan 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 kestrel:/boot/kernel% sudo kgdb kernel.symbols /usr/crash/vmcore.5 Password: [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: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x20:0x0 stack pointer = 0x28:0xdd6f669c frame pointer = 0x28:0xdd6f66dc 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 = 13 (swi4: clock sio) trap number = 12 panic: page fault cpuid = 0 Uptime: 3m15s Physical memory: 755 MB Dumping 74 MB: 59 43 27 11 #0 doadump () at pcpu.h:195 195 pcpu.h: No such file or directory. in pcpu.h (kgdb) backtrace #0 doadump () at pcpu.h:195 #1 0xc0754457 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409 #2 0xc0754719 in panic (fmt=Variable fmt is not available. ) at /usr/src/sys/kern/kern_shutdown.c:563 #3 0xc0a4905c in trap_fatal (frame=0xdd6f665c, eva=0) at /usr/src/sys/i386/i386/trap.c:899 #4 0xc0a492e0 in trap_pfault (frame=0xdd6f665c, usermode=0, eva=0) at /usr/src/sys/i386/i386/trap.c:812 #5 0xc0a49c8c in trap (frame=0xdd6f665c) at /usr/src/sys/i386/i386/trap.c:490 #6 0xc0a2fc0b in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #7 0x in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) -- Mike Clarke ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Intermittent -- yet regular -- v6.3 kernel panic
Ryan Coleman wrote: Kris Kennaway wrote: Bruce Cran wrote: On Fri, 13 Jun 2008 14:49:29 -0500 Ryan Coleman [EMAIL PROTECTED] wrote: Jun 12 23:02:41 UnixBox2 kernel: Fatal trap 12: page fault while in kernel mode Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1; apic id = 01 Jun 12 23:02:41 UnixBox2 kernel: fault virtual address = 0x0 Jun 12 23:02:41 UnixBox2 kernel: fault code = supervisor read, page not present Jun 12 23:02:41 UnixBox2 kernel: instruction pointer= 0x20:0x0 Jun 12 23:02:41 UnixBox2 kernel: stack pointer = 0x28:0xec0ea8e0 Jun 12 23:02:41 UnixBox2 kernel: frame pointer = 0x28:0xec0ea8e4 Jun 12 23:02:41 UnixBox2 kernel: code segment = base 0x0, limit 0xf, type 0x1b Jun 12 23:02:41 UnixBox2 kernel: = DPL 0, pres 1, def32 1, gran 1 Jun 12 23:02:41 UnixBox2 kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Jun 12 23:02:41 UnixBox2 kernel: current process= 925 (cp) Jun 12 23:02:41 UnixBox2 kernel: trap number= 12 Jun 12 23:02:41 UnixBox2 kernel: panic: page fault Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1 Jun 12 23:02:41 UnixBox2 kernel: Uptime: 1h21m59s Jun 12 23:02:41 UnixBox2 kernel: Cannot dump. No dump device defined. This is a regular occurrence, but varies by source. Brand new fBSD 6.3 machine, what more information do I need to provide? To be of any use we need a backtrace. See http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html for details. First you need to configure a dump device then when the system crashes a crash dump will be written to /var/crash by default. You then run kgdb on the file to get the backtrace. It's quite likely to be due to bad hardware though. Kris It's crashed twice and stalled on the dump. Any thoughts? Anyone? I'm going to have to disable the dump as I need the machine to come back up if possible. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Intermittent -- yet regular -- v6.3 kernel panic
On Sat, 14 Jun 2008 01:24:07 -0500 Ryan Coleman [EMAIL PROTECTED] wrote: Ryan Coleman wrote: Kris Kennaway wrote: Bruce Cran wrote: On Fri, 13 Jun 2008 14:49:29 -0500 Ryan Coleman [EMAIL PROTECTED] wrote: Jun 12 23:02:41 UnixBox2 kernel: Fatal trap 12: page fault while in kernel mode Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1; apic id = 01 Jun 12 23:02:41 UnixBox2 kernel: fault virtual address = 0x0 Jun 12 23:02:41 UnixBox2 kernel: fault code = supervisor read, page not present Jun 12 23:02:41 UnixBox2 kernel: instruction pointer= 0x20:0x0 Jun 12 23:02:41 UnixBox2 kernel: stack pointer = 0x28:0xec0ea8e0 Jun 12 23:02:41 UnixBox2 kernel: frame pointer = 0x28:0xec0ea8e4 Jun 12 23:02:41 UnixBox2 kernel: code segment = base 0x0, limit 0xf, type 0x1b Jun 12 23:02:41 UnixBox2 kernel: = DPL 0, pres 1, def32 1, gran 1 Jun 12 23:02:41 UnixBox2 kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Jun 12 23:02:41 UnixBox2 kernel: current process= 925 (cp) Jun 12 23:02:41 UnixBox2 kernel: trap number= 12 Jun 12 23:02:41 UnixBox2 kernel: panic: page fault Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1 Jun 12 23:02:41 UnixBox2 kernel: Uptime: 1h21m59s Jun 12 23:02:41 UnixBox2 kernel: Cannot dump. No dump device defined. This is a regular occurrence, but varies by source. Brand new fBSD 6.3 machine, what more information do I need to provide? To be of any use we need a backtrace. See http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html for details. First you need to configure a dump device then when the system crashes a crash dump will be written to /var/crash by default. You then run kgdb on the file to get the backtrace. It's quite likely to be due to bad hardware though. Kris It's crashed twice and stalled on the dump. Any thoughts? Anyone? I'm going to have to disable the dump as I need the machine to come back up if possible. Since it sounds like it's bad hardware, the dump isn't going to provide any useful information so you may as well disable it until you can swap out the RAM etc. -- Bruce Cran signature.asc Description: PGP signature
Intermittent -- yet regular -- v6.3 kernel panic
Jun 12 23:02:41 UnixBox2 kernel: Fatal trap 12: page fault while in kernel mode Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1; apic id = 01 Jun 12 23:02:41 UnixBox2 kernel: fault virtual address = 0x0 Jun 12 23:02:41 UnixBox2 kernel: fault code = supervisor read, page not present Jun 12 23:02:41 UnixBox2 kernel: instruction pointer= 0x20:0x0 Jun 12 23:02:41 UnixBox2 kernel: stack pointer = 0x28:0xec0ea8e0 Jun 12 23:02:41 UnixBox2 kernel: frame pointer = 0x28:0xec0ea8e4 Jun 12 23:02:41 UnixBox2 kernel: code segment = base 0x0, limit 0xf, type 0x1b Jun 12 23:02:41 UnixBox2 kernel: = DPL 0, pres 1, def32 1, gran 1 Jun 12 23:02:41 UnixBox2 kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Jun 12 23:02:41 UnixBox2 kernel: current process= 925 (cp) Jun 12 23:02:41 UnixBox2 kernel: trap number= 12 Jun 12 23:02:41 UnixBox2 kernel: panic: page fault Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1 Jun 12 23:02:41 UnixBox2 kernel: Uptime: 1h21m59s Jun 12 23:02:41 UnixBox2 kernel: Cannot dump. No dump device defined. This is a regular occurrence, but varies by source. Brand new fBSD 6.3 machine, what more information do I need to provide? Wednesday it was crashed by *pagedaemon* and about 15 hours earlier by *g_down*. This is the only record - thus far - to hit the syslog. Also it crashed twice today and has not recorded I have an 8x1TB RAID5 on a HighPoint Tech RocketRaid, the primary drive is a 1TB drive partitioned three times. / 30G, 4G swap and the rest is /usr. Please advise -- Ryan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Intermittent -- yet regular -- v6.3 kernel panic
It just happened again: Jun 13 14:32:21 UnixBox2 kernel: Jun 13 14:32:21 UnixBox2 kernel: Jun 13 14:32:21 UnixBox2 kernel: Fatal trap 12: page fault while in kernel mode Jun 13 14:32:21 UnixBox2 kernel: cpuid = 1; apic id = 01 Jun 13 14:32:21 UnixBox2 kernel: fault virtual address = 0x0 Jun 13 14:32:21 UnixBox2 kernel: fault code = supervisor read, page not present Jun 13 14:32:21 UnixBox2 kernel: instruction pointer= 0x20:0x0 Jun 13 14:32:21 UnixBox2 kernel: stack pointer = 0x28:0xec0738e0 Jun 13 14:32:21 UnixBox2 kernel: frame pointer = 0x28:0xec0738e4 Jun 13 14:32:21 UnixBox2 kernel: code segment = base 0x0, limit 0xf, type 0x1b Jun 13 14:32:21 UnixBox2 kernel: = DPL 0, pres 1, def32 1, gran 1 Jun 13 14:32:21 UnixBox2 kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Jun 13 14:32:21 UnixBox2 kernel: current process= 1385 (cp) Jun 13 14:32:21 UnixBox2 kernel: trap number= 12 Jun 13 14:32:21 UnixBox2 kernel: panic: page fault Jun 13 14:32:21 UnixBox2 kernel: cpuid = 1 Jun 13 14:32:21 UnixBox2 kernel: Uptime: 4h54m13s Jun 13 14:32:21 UnixBox2 kernel: Cannot dump. No dump device defined. Ryan Coleman wrote: Jun 12 23:02:41 UnixBox2 kernel: Fatal trap 12: page fault while in kernel mode Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1; apic id = 01 Jun 12 23:02:41 UnixBox2 kernel: fault virtual address = 0x0 Jun 12 23:02:41 UnixBox2 kernel: fault code = supervisor read, page not present Jun 12 23:02:41 UnixBox2 kernel: instruction pointer= 0x20:0x0 Jun 12 23:02:41 UnixBox2 kernel: stack pointer = 0x28:0xec0ea8e0 Jun 12 23:02:41 UnixBox2 kernel: frame pointer = 0x28:0xec0ea8e4 Jun 12 23:02:41 UnixBox2 kernel: code segment = base 0x0, limit 0xf, type 0x1b Jun 12 23:02:41 UnixBox2 kernel: = DPL 0, pres 1, def32 1, gran 1 Jun 12 23:02:41 UnixBox2 kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Jun 12 23:02:41 UnixBox2 kernel: current process= 925 (cp) Jun 12 23:02:41 UnixBox2 kernel: trap number= 12 Jun 12 23:02:41 UnixBox2 kernel: panic: page fault Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1 Jun 12 23:02:41 UnixBox2 kernel: Uptime: 1h21m59s Jun 12 23:02:41 UnixBox2 kernel: Cannot dump. No dump device defined. This is a regular occurrence, but varies by source. Brand new fBSD 6.3 machine, what more information do I need to provide? Wednesday it was crashed by *pagedaemon* and about 15 hours earlier by *g_down*. This is the only record - thus far - to hit the syslog. Also it crashed twice today and has not recorded I have an 8x1TB RAID5 on a HighPoint Tech RocketRaid, the primary drive is a 1TB drive partitioned three times. / 30G, 4G swap and the rest is /usr. Please advise -- Ryan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Intermittent -- yet regular -- v6.3 kernel panic
I will attempt to do this and report back when it happens again. Bruce Cran wrote: On Fri, 13 Jun 2008 14:49:29 -0500 Ryan Coleman [EMAIL PROTECTED] wrote: Jun 12 23:02:41 UnixBox2 kernel: Fatal trap 12: page fault while in kernel mode Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1; apic id = 01 Jun 12 23:02:41 UnixBox2 kernel: fault virtual address = 0x0 Jun 12 23:02:41 UnixBox2 kernel: fault code = supervisor read, page not present Jun 12 23:02:41 UnixBox2 kernel: instruction pointer= 0x20:0x0 Jun 12 23:02:41 UnixBox2 kernel: stack pointer = 0x28:0xec0ea8e0 Jun 12 23:02:41 UnixBox2 kernel: frame pointer = 0x28:0xec0ea8e4 Jun 12 23:02:41 UnixBox2 kernel: code segment = base 0x0, limit 0xf, type 0x1b Jun 12 23:02:41 UnixBox2 kernel: = DPL 0, pres 1, def32 1, gran 1 Jun 12 23:02:41 UnixBox2 kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Jun 12 23:02:41 UnixBox2 kernel: current process= 925 (cp) Jun 12 23:02:41 UnixBox2 kernel: trap number= 12 Jun 12 23:02:41 UnixBox2 kernel: panic: page fault Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1 Jun 12 23:02:41 UnixBox2 kernel: Uptime: 1h21m59s Jun 12 23:02:41 UnixBox2 kernel: Cannot dump. No dump device defined. This is a regular occurrence, but varies by source. Brand new fBSD 6.3 machine, what more information do I need to provide? To be of any use we need a backtrace. See http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html for details. First you need to configure a dump device then when the system crashes a crash dump will be written to /var/crash by default. You then run kgdb on the file to get the backtrace. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Intermittent -- yet regular -- v6.3 kernel panic
On Fri, 13 Jun 2008 14:49:29 -0500 Ryan Coleman [EMAIL PROTECTED] wrote: Jun 12 23:02:41 UnixBox2 kernel: Fatal trap 12: page fault while in kernel mode Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1; apic id = 01 Jun 12 23:02:41 UnixBox2 kernel: fault virtual address = 0x0 Jun 12 23:02:41 UnixBox2 kernel: fault code = supervisor read, page not present Jun 12 23:02:41 UnixBox2 kernel: instruction pointer= 0x20:0x0 Jun 12 23:02:41 UnixBox2 kernel: stack pointer = 0x28:0xec0ea8e0 Jun 12 23:02:41 UnixBox2 kernel: frame pointer = 0x28:0xec0ea8e4 Jun 12 23:02:41 UnixBox2 kernel: code segment = base 0x0, limit 0xf, type 0x1b Jun 12 23:02:41 UnixBox2 kernel: = DPL 0, pres 1, def32 1, gran 1 Jun 12 23:02:41 UnixBox2 kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Jun 12 23:02:41 UnixBox2 kernel: current process= 925 (cp) Jun 12 23:02:41 UnixBox2 kernel: trap number= 12 Jun 12 23:02:41 UnixBox2 kernel: panic: page fault Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1 Jun 12 23:02:41 UnixBox2 kernel: Uptime: 1h21m59s Jun 12 23:02:41 UnixBox2 kernel: Cannot dump. No dump device defined. This is a regular occurrence, but varies by source. Brand new fBSD 6.3 machine, what more information do I need to provide? To be of any use we need a backtrace. See http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html for details. First you need to configure a dump device then when the system crashes a crash dump will be written to /var/crash by default. You then run kgdb on the file to get the backtrace. -- Bruce Cran signature.asc Description: PGP signature
Re: Intermittent -- yet regular -- v6.3 kernel panic
Bruce Cran wrote: On Fri, 13 Jun 2008 14:49:29 -0500 Ryan Coleman [EMAIL PROTECTED] wrote: Jun 12 23:02:41 UnixBox2 kernel: Fatal trap 12: page fault while in kernel mode Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1; apic id = 01 Jun 12 23:02:41 UnixBox2 kernel: fault virtual address = 0x0 Jun 12 23:02:41 UnixBox2 kernel: fault code = supervisor read, page not present Jun 12 23:02:41 UnixBox2 kernel: instruction pointer= 0x20:0x0 Jun 12 23:02:41 UnixBox2 kernel: stack pointer = 0x28:0xec0ea8e0 Jun 12 23:02:41 UnixBox2 kernel: frame pointer = 0x28:0xec0ea8e4 Jun 12 23:02:41 UnixBox2 kernel: code segment = base 0x0, limit 0xf, type 0x1b Jun 12 23:02:41 UnixBox2 kernel: = DPL 0, pres 1, def32 1, gran 1 Jun 12 23:02:41 UnixBox2 kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Jun 12 23:02:41 UnixBox2 kernel: current process= 925 (cp) Jun 12 23:02:41 UnixBox2 kernel: trap number= 12 Jun 12 23:02:41 UnixBox2 kernel: panic: page fault Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1 Jun 12 23:02:41 UnixBox2 kernel: Uptime: 1h21m59s Jun 12 23:02:41 UnixBox2 kernel: Cannot dump. No dump device defined. This is a regular occurrence, but varies by source. Brand new fBSD 6.3 machine, what more information do I need to provide? To be of any use we need a backtrace. See http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html for details. First you need to configure a dump device then when the system crashes a crash dump will be written to /var/crash by default. You then run kgdb on the file to get the backtrace. It's quite likely to be due to bad hardware though. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Intermittent -- yet regular -- v6.3 kernel panic
I'm sure. I could get different RAM this weekend, but that just makes me angry. I bought all the items from recommended lists on NewEgg two weeks ago. This is probably the 11th crash in 12 days. It's quite likely to be due to bad hardware though. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Intermittent -- yet regular -- v6.3 kernel panic
[Don't top-post, please.] It's quite likely to be due to bad hardware though. Ryan Coleman [EMAIL PROTECTED] writes: I'm sure. I could get different RAM this weekend, but that just makes me angry. I bought all the items from recommended lists on NewEgg two weeks ago. This is probably the 11th crash in 12 days. Buying good hardware improves your odds a lot, but failures can still happen. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Intermittent -- yet regular -- v6.3 kernel panic
Kris Kennaway wrote: Bruce Cran wrote: On Fri, 13 Jun 2008 14:49:29 -0500 Ryan Coleman [EMAIL PROTECTED] wrote: Jun 12 23:02:41 UnixBox2 kernel: Fatal trap 12: page fault while in kernel mode Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1; apic id = 01 Jun 12 23:02:41 UnixBox2 kernel: fault virtual address = 0x0 Jun 12 23:02:41 UnixBox2 kernel: fault code = supervisor read, page not present Jun 12 23:02:41 UnixBox2 kernel: instruction pointer= 0x20:0x0 Jun 12 23:02:41 UnixBox2 kernel: stack pointer = 0x28:0xec0ea8e0 Jun 12 23:02:41 UnixBox2 kernel: frame pointer = 0x28:0xec0ea8e4 Jun 12 23:02:41 UnixBox2 kernel: code segment = base 0x0, limit 0xf, type 0x1b Jun 12 23:02:41 UnixBox2 kernel: = DPL 0, pres 1, def32 1, gran 1 Jun 12 23:02:41 UnixBox2 kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Jun 12 23:02:41 UnixBox2 kernel: current process= 925 (cp) Jun 12 23:02:41 UnixBox2 kernel: trap number= 12 Jun 12 23:02:41 UnixBox2 kernel: panic: page fault Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1 Jun 12 23:02:41 UnixBox2 kernel: Uptime: 1h21m59s Jun 12 23:02:41 UnixBox2 kernel: Cannot dump. No dump device defined. This is a regular occurrence, but varies by source. Brand new fBSD 6.3 machine, what more information do I need to provide? To be of any use we need a backtrace. See http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html for details. First you need to configure a dump device then when the system crashes a crash dump will be written to /var/crash by default. You then run kgdb on the file to get the backtrace. It's quite likely to be due to bad hardware though. Kris It's crashed twice and stalled on the dump. Any thoughts? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Kernel Panic: isp - page fault while in kernel mode
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? Listed below is the boot info: /boot/kernel/acpi.ko text=0x44e84 data=0x24e0+0x1b8c syms=[0x4+0x7dc0 +0x4+0xab62] 786428K of memory above 4GB ignored Copyright (c) 1992-2008 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 6.3-STABLE #11: Fri Apr 11 13:25:41 PDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/LAACO WARNING: debug.mpsafenet forced to 0 as ipsec requires Giant WARNING: MPSAFE network stack disabled, expect reduced performance. module_register: module pci/bce already exists! Module pci/bce failed to register: 17 module_register: module bce/miibus already exists! Module bce/miibus failed to register: 17 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(R) CPU5160 @ 3.00GHz (3000.13-MHz 686- class CPU) Origin = GenuineIntel Id = 0x6f6 Stepping = 6 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=0x4e3bdSSE3,RSVD2,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM ,DCA AMD Features=0x2000LM AMD Features2=0x1LAHF Cores per package: 2 real memory = 3487916032 (3326 MB) avail memory = 3408932864 (3251 MB) ACPI APIC Table: HP ProLiant 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 Version 2.0 irqs 0-23 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) hptrr: HPT RocketRAID controller driver v1.1 (Apr 11 2008 13:25:27) acpi0: HP ProLiant on motherboard acpi0: Power Button (fixed) Timecounter ACPI-safe frequency 3579545 Hz quality 850 acpi_timer0: 24-bit timer at 3.579545MHz port 0x908-0x90b on acpi0 acpi_hpet0: High Precision Event Timer iomem 0xfed0-0xfed003ff on acpi0 Timecounter HPET frequency 14318180 Hz quality 900 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 on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge at device 2.0 on pci0 pci4: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge at device 0.0 on pci4 pci5: ACPI PCI bus on pcib2 pcib3: ACPI PCI-PCI bridge at device 0.0 on pci5 pci6: ACPI PCI bus on pcib3 pcib4: ACPI PCI-PCI bridge at device 0.0 on pci6 pci7: ACPI PCI bus on pcib4 bce0: Broadcom NetXtreme II BCM5708 1000Base-SX (B2) mem 0xfa00-0xfbff irq 16 at device 0.0 on pci7 miibus0: MII bus on bce0 brgphy0: BCM5708S 1000/2500BaseSX PHY on miibus0 brgphy0: 1000baseSX-FDX, auto bce0: Ethernet address: 00:17:a4:77:00:0a bce0: [GIANT-LOCKED] bce0: ASIC (0x57081021); Rev (B2); Bus (PCI-X, 64-bit, 133MHz); F/W (0x01090605); Flags( MSI ) pcib5: ACPI PCI-PCI bridge at device 1.0 on pci5 pci8: ACPI PCI bus on pcib5 pcib6: ACPI PCI-PCI bridge at device 0.3 on pci4 pci9: ACPI PCI bus on pcib6 pcib7: ACPI PCI-PCI bridge at device 3.0 on pci0 pci10: ACPI PCI bus on pcib7 pcib8: PCI-PCI bridge at device 0.0 on pci10 pci11: PCI bus on pcib8 pcib9: PCI-PCI bridge at device 4.0 on pci11 pci12: PCI bus on pcib9 ciss0: HP Smart Array E200i port 0x4000-0x40ff mem 0xfdb8-0xfdbf,0xfdb7-0xfdb77fff irq 18 at device 8.0 on pci11 ciss0: [GIANT-LOCKED] pcib10: ACPI PCI-PCI bridge at device 4.0 on pci0 pci13: ACPI PCI bus on pcib10 ciss1: HP Smart Array P400 port 0x5000-0x50ff mem 0xfdd0-0xfddf,0xfdcf-0xfdcf0fff irq 19 at device 0.0 on pci13 ciss1: [GIANT-LOCKED] pcib11: ACPI PCI-PCI bridge at device 5.0 on pci0 pci16: ACPI PCI bus on pcib11 pcib12: ACPI PCI-PCI bridge at device 0.0 on pci16 pci17: ACPI PCI bus on pcib12 bge0: Broadcom BCM5715 A3, ASIC rev. 0x9003 mem 0xfdef-0xfdef,0xfdee-0xfdee irq 18 at device 4.0 on pci17 bge0: Ethernet address: 00:17:a4:77:00:24 bge0: [GIANT-LOCKED] bge1: Broadcom BCM5715 A3, ASIC rev. 0x9003 mem 0xfded-0xfded,0xfdec-0xfdec irq 19 at device 4.1 on pci17 bge1: Ethernet address: 00:17:a4:77:00:26 bge1: [GIANT-LOCKED] pcib13: ACPI PCI-PCI bridge at device 6.0 on pci0 pci19: ACPI PCI bus on pcib13 isp0: Qlogic ISP 2432 PCI FC-AL Adapter port 0x6000-0x60ff mem 0xfdff-0xfdff3fff irq 19 at device 0.0 on pci19 isp0: [GIANT-LOCKED] isp0: Board Type 2422, Chip Revision 0x2, resident F/W
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]
Kernel panic: flush_pagedep_deps: flush failed
Hi, ich have the second core since 3 days, with following info: cat /var/crash/info.1 Dump header from device /dev/da0s1b Architecture: amd64 Architecture Version: 2 Dump Length: 284737536B (271 MB) Blocksize: 512 Dumptime: Mon May 19 09:27:46 2008 Hostname: xxx.yyy.zz Magic: FreeBSD Kernel Dump Version String: FreeBSD 7.0-RELEASE-p1 #4: Wed May 14 10:10:03 CEST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/STORAGE Panic String: flush_pagedep_deps: flush failed Dump Parity: 4068726879 Bounds: 1 Dump Status: good anyone knows whats going on? thanks ___ 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]
kernel panic FreeBSD 7.0 - Xorg
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: Xorg -configure X -config /root/xorg.conf.new and I got black monitor and after few seconds the system reboots. Then I go to single user and do fsck -p (Similar was when I logon as root and typed startx) After that, I boot the system and I saw on the monitor the following (the exactly output is in file messages attached in this e-mail): savecore: reboot after panic: vm_fault: fault on nofault entry, addr: e56e8000 savecore: writing core to vmcore.2 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? After fsck -p i decide to use vesa driver. I could only obtain the resolution 1024x678, but my monitor use 1280x1024. I have the following monitor: Philips 190P Could someone help me, please? If you need more information I send it to you. Thank you in advance. Here are additional information: # uname -a FreeBSD komp1.dom 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 I have the following motherboard: A-7N400SL F5 (from first screen after computer started) and also 3/29/2005-nVidia-nForce-6AG1BG0QC-00. The attached files: 1. messages (from /var/log/messages) 2. xorg.conf.new (from /root/xorg.conf.new) Thank you in advance for any help and I'm sorry for my English. Best wishes, Zbigniew May 12 11:38:29 komp1 syslogd: kernel boot file is /boot/kernel/kernel May 12 11:38:29 komp1 kernel: Copyright (c) 1992-2008 The FreeBSD Project. May 12 11:38:29 komp1 kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 May 12 11:38:29 komp1 kernel: The Regents of the University of California. All rights reserved. May 12 11:38:29 komp1 kernel: FreeBSD is a registered trademark of The FreeBSD Foundation. May 12 11:38:29 komp1 kernel: FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008 May 12 11:38:29 komp1 kernel: [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC May 12 11:38:29 komp1 kernel: Timecounter i8254 frequency 1193182 Hz quality 0 May 12 11:38:29 komp1 kernel: CPU: AMD Athlon(tm) XP 2000+ (1660.38-MHz 686-class CPU) May 12 11:38:29 komp1 kernel: Origin = AuthenticAMD Id = 0x681 Stepping = 1 May 12 11:38:29 komp1 kernel: Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE May 12 11:38:29 komp1 kernel: AMD Features=0xc0400800SYSCALL,MMX+,3DNow!+,3DNow! May 12 11:38:29 komp1 kernel: real memory = 2147418112 (2047 MB) May 12 11:38:29 komp1 kernel: avail memory = 2091872256 (1994 MB) May 12 11:38:29 komp1 kernel: ACPI APIC Table: Nvidia AWRDACPI May 12 11:38:29 komp1 kernel: ioapic0 Version 1.1 irqs 0-23 on motherboard May 12 11:38:29 komp1 kernel: kbd1 at kbdmux0 May 12 11:38:29 komp1 kernel: ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) May 12 11:38:29 komp1 kernel: hptrr: HPT RocketRAID controller driver v1.1 (Feb 24 2008 19:59:27) May 12 11:38:29 komp1 kernel: acpi0: Nvidia AWRDACPI on motherboard May 12 11:38:29 komp1 kernel: acpi0: [ITHREAD] May 12 11:38:29 komp1 kernel: acpi0: Power Button (fixed) May 12 11:38:29 komp1 kernel: acpi0: reservation of 0, a (3) failed May 12 11:38:29 komp1 kernel: acpi0: reservation of 10, 7fef (3) failed May 12 11:38:29 komp1 kernel: Timecounter ACPI-fast frequency 3579545 Hz quality 1000 May 12 11:38:29 komp1 kernel: acpi_timer0: 24-bit timer at 3.579545MHz port 0x4008-0x400b on acpi0 May 12 11:38:29 komp1 kernel: cpu0: ACPI CPU on acpi0 May 12 11:38:29 komp1 kernel: acpi_button0: Power Button on acpi0 May 12 11:38:29 komp1 kernel: pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff,0xcf0-0xcf3 on acpi0 May 12 11:38:29 komp1 kernel: pci0: ACPI PCI bus on pcib0 May 12 11:38:29 komp1 kernel: Correcting nForce2 C1 CPU disconnect hangs May 12 11:38:29 komp1 kernel: agp0: NVIDIA nForce2 AGP Controller on hostb0 May 12 11:38:29 komp1 kernel: pci0: memory, RAM at device 0.1 (no driver attached) May 12 11:38:29 komp1 kernel: pci0: memory, RAM at device 0.2 (no driver attached) May 12 11:38:29 komp1 kernel: pci0: memory, RAM at device 0.3 (no driver attached) May 12 11:38:29 komp1 kernel: pci0: memory, RAM at device 0.4 (no driver attached) May 12 11:38:29 komp1 kernel: pci0: memory, RAM at device 0.5 (no driver attached) May 12 11:38:29 komp1 kernel: isab0: PCI-ISA bridge at device 1.0 on pci0 May 12 11:38:29 komp1 kernel: isa0: ISA bus on isab0 May 12 11:38:29 komp1 kernel: pci0: serial bus, SMBus at device 1.1
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
