Kernel Trap 9 and freeze
Hello! Just upgraded the world and kernel to the latest 8.1-stable via cvs yesterday. Now, at 6 in the morning got kernel trap 9 (screenshot is attached). The worst part is that it did not reboot. It just froze after stopping other cpus. This is amd64 architecture. Kernel config is attached too. The question is how i can make the reboot in such case more reliable? Any kernel options which would more reliable send the server into reboot? Maybe some other comments on what happened and possible why? Artem cpu HAMMER ident FINIZDAT makeoptions DEBUG=-g# Build kernel with gdb(1) debug symbols options SCHED_ULE # ULE scheduler options PREEMPTION # Enable kernel thread preemption options INET# InterNETworking options INET6 # IPv6 communications protocols options SCTP# Stream Control Transmission Protocol options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options UFS_GJOURNAL# Enable gjournal-based UFS journaling options MD_ROOT # MD is a potential root device options NFSCLIENT # Network Filesystem Client options NFSSERVER # Network Filesystem Server options NFSLOCKD# Network Lock Manager options NFS_ROOT# NFS usable as /, requires NFSCLIENT options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS# Pseudo-filesystem framework options GEOM_PART_GPT # GUID Partition Tables. options GEOM_LABEL # Provides labelization options COMPAT_43TTY# BSD 4.3 TTY compat (sgtty) options COMPAT_FREEBSD32# Compatible with i386 binaries options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options STACK # stack(9) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options P1003_1B_SEMAPHORES # POSIX-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options PRINTF_BUFR_SIZE=128# Prevent printf output being interspersed. options KBD_INSTALL_CDEV# install a CDEV entry in /dev options HWPMC_HOOKS # Necessary kernel hooks for hwpmc(4) options AUDIT # Security event auditing options MAC # TrustedBSD MAC Framework options FLOWTABLE # per-cpu routing cache #optionsKDTRACE_FRAME # Ensure frames are compiled in #optionsKDTRACE_HOOKS # Kernel DTrace hooks options INCLUDE_CONFIG_FILE # Include this file in kernel # Make an SMP-capable kernel by default options SMP # Symmetric MultiProcessor Kernel # CPU frequency control device cpufreq # Bus support. device acpi device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device ataraid # ATA RAID drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives device atapist # ATAPI tape drives options ATA_STATIC_ID # Static device numbering # SCSI Controllers device ahc # AHA2940 and onboard AIC7xxx devices options AHC_REG_PRETTY_PRINT# Print register bitfields in debug # output. Adds ~128k to driver. device ahd # AHA39320/29320 and onboard AIC79xx devices options AHD_REG_PRETTY_PRINT# Print register bitfields in debug # output. Adds ~215k to driver. device amd # AMD 53C974 (Tekram DC-390(T)) device hptiop # Highpoint RocketRaid 3xxx series device isp # Qlogic family #device ispfw # Firmware for QLogic HBAs- normally a module device mpt # LSI-Logic MPT-Fusion #device ncr # NCR/Symbios Logic device sym # NCR/Symbios Logic (newer chipsets + those of `ncr') device trm
Re: Getting kernel trap 12 During Boot Of 8.1-PRERELEASE
Tim Daneliuk tun...@tundraware.com writes: I've seen this twice now - once last Sunday, and once again today when I tried to do a build/installworld/kernel with daily sources from the master tree: http://www.mediafire.com/imageview.php?quickkey=qmhizdtnhyothumb=4 That asked me to jump through too many hoops over multiple domains, so I didn't actually see it. I'll assume it's just more information on the error in your subject line. The system boots fine single-user, so I don't suspect the base kernel functionality. Maybe. What you should do is install the kernel *before* the userland. If you already did that, then make sure youtry with a GENERIC kernel. ___ 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: Getting kernel trap 12 During Boot Of 8.1-PRERELEASE
On 7/4/2010 10:32 AM, Lowell Gilbert wrote: Tim Daneliuk tun...@tundraware.com writes: I've seen this twice now - once last Sunday, and once again today when I tried to do a build/installworld/kernel with daily sources from the master tree: http://www.mediafire.com/imageview.php?quickkey=qmhizdtnhyothumb=4 That asked me to jump through too many hoops over multiple domains, so I didn't actually see it. I'll assume it's just more information on the error in your subject line. I'm not sure what you mean. It should take you to a screenshot of the problem. What does too many hoops mean in this context? The system boots fine single-user, so I don't suspect the base kernel functionality. Maybe. What you should do is install the kernel *before* the userland. If you already did that, then make sure youtry with a GENERIC kernel. I did exactly that, though I did not try the GENERIC kernel. My conf looks like this: include GENERIC ident MACHINENAME options IPFIREWALL options IPDIVERT options VESA # System console options options SC_DISABLE_REBOOT # disable reboot key sequence options SC_HISTORY_SIZE=200 # number of history buffer lines options SC_PIXEL_MODE # add support for the raster text mode # The following options will change the default colors of syscons. options SC_NORM_ATTR=(FG_GREEN|BG_BLACK) options SC_NORM_REV_ATTR=(FG_YELLOW|BG_GREEN) options SC_KERNEL_CONS_ATTR=(FG_RED|BG_BLACK) options SC_KERNEL_CONS_REV_ATTR=(FG_BLACK|BG_RED) Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: Getting kernel trap 12 During Boot Of 8.1-PRERELEASE
Tim Daneliuk tun...@tundraware.com writes: On 7/4/2010 10:32 AM, Lowell Gilbert wrote: Tim Daneliuk tun...@tundraware.com writes: I've seen this twice now - once last Sunday, and once again today when I tried to do a build/installworld/kernel with daily sources from the master tree: http://www.mediafire.com/imageview.php?quickkey=qmhizdtnhyothumb=4 That asked me to jump through too many hoops over multiple domains, so I didn't actually see it. I'll assume it's just more information on the error in your subject line. I'm not sure what you mean. It should take you to a screenshot of the problem. What does too many hoops mean in this context? I had clicked through a couple of click here to download picture screens (each trying to push a pop-up) before I decided it looked too much like malware. The system boots fine single-user, so I don't suspect the base kernel functionality. Maybe. What you should do is install the kernel *before* the userland. If you already did that, then make sure youtry with a GENERIC kernel. I did exactly that, though I did not try the GENERIC kernel. My conf looks like this: include GENERIC ident MACHINENAME options IPFIREWALL options IPDIVERT options VESA # System console options options SC_DISABLE_REBOOT # disable reboot key sequence options SC_HISTORY_SIZE=200 # number of history buffer lines options SC_PIXEL_MODE # add support for the raster text mode # The following options will change the default colors of syscons. options SC_NORM_ATTR=(FG_GREEN|BG_BLACK) options SC_NORM_REV_ATTR=(FG_YELLOW|BG_GREEN) options SC_KERNEL_CONS_ATTR=(FG_RED|BG_BLACK) options SC_KERNEL_CONS_REV_ATTR=(FG_BLACK|BG_RED) None of those look interesting (by which I mean dangerous), but it's still worth trying a GENERIC kernel. Also, minimize the software started at bootup in order to reduce the number of variables. If it's still crashing at that point, go to the Handbook (or maybe it's the Developers' Handbook?) for instructions on diagnosing crashes. If not, then re-enable the userland stuff gradually to find the culprit. It also may be useful to look at the -STABLE mailing list, as at least one crash problem has been solved recently. Good luck. ___ 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
Getting kernel trap 12 During Boot Of 8.1-PRERELEASE
I've seen this twice now - once last Sunday, and once again today when I tried to do a build/installworld/kernel with daily sources from the master tree: http://www.mediafire.com/imageview.php?quickkey=qmhizdtnhyothumb=4 The system boots fine single-user, so I don't suspect the base kernel functionality. Falling back to my 6-18-2010 system image makes everything right again. MOBO is an Intel D946GZIS with a single SATA drive and one additional 3Com 3c905 NIC in addition to the onboard Intel NIC. Anyone else seeing this. Ideas? -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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 trap
sorry for bothering guys, but i have a big problem here, i recently installed freebsd on a box and i was very happy updating ports, when i realized the system suddenly reboot, when i saw the dmesg it says: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x828dee24 fault code = supervisor write, page not present instruction pointer = 0x20:0xc0a27b0b stack pointer = 0x28:0xe4f2fb80 frame pointer = 0x28:0xe4f2fb94 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 = 48 (vnlru) trap number = 12 panic: page fault cpuid = 1 Uptime: 18m45s Physical memory: 1522 MB Dumping 203 MB: 188 172 156 140 124 108 92 76 60 44 28 12 Dump complete Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... I searched in google for something but it seems i need to dump the kernel, i guess if it could be an HD issue. By the way, the current process line has little variations (g_down, fsck_ufs, vnlru Any clue? ___ 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 dying with Kernel Trap 12
My 7.2 FreeBSD server has started to crash with kernel trap 12. I googled around and most of the topics I found were about faulty RAM or other harware problems. This is VMware vitual machine so I see no way of hardware problems as we even tried to move the machine around VMware nodes to see it's RAM. It worked absolutely fine for about two months, but now sometimes the server lives for up to 5 hours, sometimes it panics in 10 minutes. Is there anyone that can help me to resolve the problem? Here are few errors on crash: kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 2; apic id = 02 fault virtual address= 0x10 fault code = supervisor read, page not present instruction pointer = 0x20:0xc07d4a21 stack pointer = 0x28:0xc72dec1c frame pointer = 0x28:0xc72dec30 code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process= 36 (sctp_iterator) trap number = 12 panic: page fault cpuid = 2 - Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address= 0x6e727598 fault code = supervisor read, page not present instruction pointer = 0x20:0xc08bf945 stack pointer = 0x28:0xc72bfaa8 frame pointer = 0x28:0xc72bfacc 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= 30 (em1 taskq) trap number = 12 -- kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address= 0x10 fault code = supervisor read, page not present instruction pointer = 0x20:0xc07d4a21 stack pointer = 0x28:0xc73e29c4 frame pointer = 0x28:0xc73e29d8 code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process= 9020 (libssl.so) trap number = 12 panic: page fault cpuid = 0 Uptime: 25m37s Thank You Zete ___ 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 trap 19/NMI messages
Hi, SMP FreeBSD 6.2-RELEASE (i386), latest version via freebsd-update, on a PentiumD based server with two ide drives running under gmirror. Recently I've been getting the following messages in my daily security run output mails: SNIP +NMI INSAM I IS2A 8, EISA 20 +8, +22NMIN MISI AI SA 38,3 8,E IESAIS A0 +NMI2 NIMSIA ISA 28,2 8EI, SEA I0S +A 0 +NMI ISA N2M8I, ISEIA SA 0 +28, EISA 0 +NMI 2ISAN MI ISA 38, EIS3A8, E0I +S +A 0 +2N2NMMII I SAIS A 38, E3I8S, AEI S0A NMI ISA 38, EISA 0 kernel trap +19 with interrupts disabled NMI ISA 28, EISA 0 NMI 2INSAM I ISA 28, +EISA2 08 /SNIP Sometimes with message like this embedded: SNIP g_vfs_done():mirror/gm0s1f[READ(offset=356486479872, length=16384)]error = 5 /SNIP By now the mail is about 40K. Does anybody have an idea what this means and what's causing it? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel trap 19/NMI messages
On Tue, Apr 24, 2007 at 01:23:00PM +0200, Jan L. Nauta wrote: Hi, SMP FreeBSD 6.2-RELEASE (i386), latest version via freebsd-update, on a PentiumD based server with two ide drives running under gmirror. Recently I've been getting the following messages in my daily security run output mails: SNIP +NMI INSAM I IS2A 8, EISA 20 +8, +22NMIN MISI AI SA 38,3 8,E IESAIS A0 +NMI2 NIMSIA ISA 28,2 8EI, SEA I0S +A 0 +NMI ISA N2M8I, ISEIA SA 0 +28, EISA 0 +NMI 2ISAN MI ISA 38, EIS3A8, E0I +S +A 0 +2N2NMMII I SAIS A 38, E3I8S, AEI S0A NMI ISA 38, EISA 0 kernel trap +19 with interrupts disabled NMI ISA 28, EISA 0 NMI 2INSAM I ISA 28, +EISA2 08 /SNIP Sometimes with message like this embedded: SNIP g_vfs_done():mirror/gm0s1f[READ(offset=356486479872, length=16384)]error = 5 /SNIP By now the mail is about 40K. Does anybody have an idea what this means and what's causing it? NMI errors are caused by hardware failure. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Kernel Trap 22??
Just asking a general curiosity question in regards to this just in case something's starting to go back with my box. Noticed this across two different days of logs and after some digging in google it seems that a kernel trap is a bad thing. Here's what I've been seeing. Warning: pid 25152 used static ldt allocation. See the i386_set_ldt man page for more info That was in my first set of logs. I've seen this like once in a blue moon, usually because one of my programs cops and attitude or something, so I've just generally ignored them. Then I got this today: kernel trap 22 with interrupts disabled Oddly, it appeared in the same number of repetitions as the previous error. Is there any corelation or is this anything to worry about or can I just generally ignore this? Is it caused by a program being naughty? Any info would be welcome. Thanks. :) PS: The bsd box this comes from is being used as a workstation, not a server, fyi if that makes any difference. -- Steven Lake Duct Tape takes over where skill leaves off -Larry the Cucumber from Veggie Tales. I'm not afraid of flying...I'm afraid of being at 35,000 feet and suddenly *not* flying. -Koren ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
strange message -- kernel trap 19
Hi all I have some problems with my machine. After the problem of my hd(many badblocks and consequently bugs in filesystem) a new problem arise. Some time after the login on FBSD is promped this messages: Jan 23 17:16:31 Machina kernel: NMI ISA 20, EISA ff Jan 23 17:16:35 Machina kernel: NMI ISA 20, EISA ff Jan 23 17:16:45 Machina kernel: kernel trap 19 with interrupts disabled Jan 23 17:16:45 Machina kernel: NMI ISA 30, EISA ff Jan 23 17:16:47 Machina kernel: NMI ISA 20, EISA ff Jan 23 17:16:54 Machina kernel: NMI ISA 20, EISA ff Jan 23 17:16:58 Machina kernel: NMI ISA 30, EISA ff Jan 23 17:17:04 Machina kernel: kernel trap 19 with interrupts disabled Jan 23 17:17:04 Machina kernel: NMI ISA 30, EISA ff Jan 23 17:17:06 Machina kernel: kernel trap 19 with interrupts disabled Jan 23 17:17:06 Machina kernel: NMI ISA 30, EISA ff Jan 23 17:17:07 Machina kernel: kernel trap 19 with interrupts disabled Jan 23 17:17:07 Machina kernel: NMI ISA 20, EISA ff Jan 23 17:17:07 Machina kernel: kernel trap 19 with interrupts disabled Jan 23 17:17:07 Machina kernel: NMI ISA 30, EISA ff Jan 23 17:17:12 Machina kernel: kernel trap 19 with interrupts disabled And finally the reboot of system. In my Windows simply arise the blue screen. I'm using the same problematic hd. Could it be the problem? I'm waiting for feedbacks thanks Thiago ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: strange message -- kernel trap 19
On Sun, Mar 05, 2006 at 12:09:32AM -0300, alicornio wrote: Content-Description: Mail message body Hi all I have some problems with my machine. After the problem of my hd(many badblocks and consequently bugs in filesystem) a new problem arise. Some time after the login on FBSD is promped this messages: Jan 23 17:16:31 Machina kernel: NMI ISA 20, EISA ff Jan 23 17:16:35 Machina kernel: NMI ISA 20, EISA ff Jan 23 17:16:45 Machina kernel: kernel trap 19 with interrupts disabled Jan 23 17:16:45 Machina kernel: NMI ISA 30, EISA ff Jan 23 17:16:47 Machina kernel: NMI ISA 20, EISA ff Jan 23 17:16:54 Machina kernel: NMI ISA 20, EISA ff Jan 23 17:16:58 Machina kernel: NMI ISA 30, EISA ff Jan 23 17:17:04 Machina kernel: kernel trap 19 with interrupts disabled Jan 23 17:17:04 Machina kernel: NMI ISA 30, EISA ff Jan 23 17:17:06 Machina kernel: kernel trap 19 with interrupts disabled Jan 23 17:17:06 Machina kernel: NMI ISA 30, EISA ff Jan 23 17:17:07 Machina kernel: kernel trap 19 with interrupts disabled Jan 23 17:17:07 Machina kernel: NMI ISA 20, EISA ff Jan 23 17:17:07 Machina kernel: kernel trap 19 with interrupts disabled Jan 23 17:17:07 Machina kernel: NMI ISA 30, EISA ff Jan 23 17:17:12 Machina kernel: kernel trap 19 with interrupts disabled And finally the reboot of system. In my Windows simply arise the blue screen. I'm using the same problematic hd. Could it be the problem? NMI indicates something is very wrong with your hardware. It's not likely it's your HD, but something else that may have also caused your HD problems. Kris pgpwrffg4XYO9.pgp Description: PGP signature
Getting 'kernel trap 12 with interupts disabled' when i boot new updated system...help
Hello list! I have been successfully been running 5.3 for a couple of weeks when i decided i should upgrade to 5.4 stable. Now the make world went fine except mergemaster complaining it couldn't find usr/src/etc or something similar. I made make buildkernel wich also went fine. But when I booted into my upgraded system I got kernel panic, so I made another restart and this time it went ok. Yestoday I removed SCSI card and DAT tape and NIC so I can have them in my main server. Now i cant get past this: freebsd 5.4-stable kernel trap 12 with interupts disabled Fatal trap 12: page fault while in kernel mode fault virtual address = 0x9 fault code = supervisor write, page not present instruction pointer = 0x8 :0xc077c073 stack pointer = 0x10 :0xc0c20d00 frame pointer = 0x10 :0xc0c20d0c code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = 0 () trap number = 12 panic: page fault Uptime: 1s So my attack-plan is to reinstall system from scratch and never do make buildworld make buildkernel again, BUT, I have a whole lot of information remaining on both disks that are in right now. From what I could see in the installer, fbsd installer wont let me install in a different directory with filesystem still intact like windows doesor does it? UPDATE: I have now done what has been advised, to do boot kernel.old at the boot loader prompt, and I get the same error...running out of options here... :/ Please help! :) // Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
5.4-STABLE panic: kernel trap 12 with interrupts diabled
Hello list, the day before yesterday I experienced my first panic on 5.4-STABLE. Build and cvsup'ed last Friday. My system is a ThinkPad R51 I did nothing spectacular, after boot I: logged in as user cdrecord -scanbus (which didn't work as I hadn't yet set it suid) su chmod +x for cdrecord and readcd (meant was +g ;-) exit cdrecord -scanbus (didn't yet work ;-) su cdrecord -scanbus (did work) readcd dev=2,0,0 -factor meshpoints=100 f=./file exit Then I moved the laptop and plugged in the AC/DC adapter. whoami brought me: Kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode fault virtual address = 0xa94d06c fault code = supervisor read, page not present instruction pointer = 0x8:0xc053cbe5 stack pointer = 0x10:0xe669f98c frame pointer= 0x10:0xe669f990 code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= resume, IOPL = 0 current process = 601 (whoami) trap number = 12 panic: page fault I saved the dump manually with savecore and then tried to follow: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/advanced.html#KERNEL-PANIC-TROUBLESHOOTING [EMAIL PROTECTED] ~ $nm -n /boot/kernel/kernel | grep c053cb c053cb4c T init_turnstiles c053cbc9 t init_turnstile0 c053cbd8 t turnstile_setowner My kernel contains makeoptions DEBUG=-g, however I don't have the file /sys/compile/KERNELCONFIG/kernel.debug and thus wasn't able to do % gdb -k /sys/compile/KERNELCONFIG/kernel.debug /var/crash/vmcore.0 The next best thing seemed to be the -c option, no luck either. [EMAIL PROTECTED] ~ $gdb -c vmcore.0 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. /usr/home/fk/vmcore.0 is not a core dump: File format not recognized (gdb) [EMAIL PROTECTED] ~ $cat info.0 Dump header from device /dev/ad0s3b Architecture: i386 Architecture Version: 16777216 Dump Length: 536215552B (511 MB) Blocksize: 512 Dumptime: Tue May 3 20:18:11 2005 Hostname: r51.local Magic: FreeBSD Kernel Dump Version String: FreeBSD 5.4-STABLE #6: Sat Apr 30 14:57:04 CEST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/THINKPAD Panic String: page fault Dump Parity: 1084811848 Bounds: 0 Dump Status: good The kernel was build the new way. I was not able to reproduce the panic. Is there anything else I can do? Regards Fabian -- http://www.fabiankeil.de/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.4-STABLE panic: kernel trap 12 with interrupts diabled
On 5/5/2005 19:43, Fabian Keil wrote: Hello list, the day before yesterday I experienced my first panic on 5.4-STABLE. Build and cvsup'ed last Friday. My system is a ThinkPad R51 I did nothing spectacular, after boot I: logged in as user cdrecord -scanbus (which didn't work as I hadn't yet set it suid) su chmod +x for cdrecord and readcd (meant was +g ;-) exit cdrecord -scanbus (didn't yet work ;-) su cdrecord -scanbus (did work) readcd dev=2,0,0 -factor meshpoints=100 f=./file exit Then I moved the laptop and plugged in the AC/DC adapter. whoami brought me: Kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode fault virtual address = 0xa94d06c fault code = supervisor read, page not present instruction pointer = 0x8:0xc053cbe5 stack pointer = 0x10:0xe669f98c frame pointer= 0x10:0xe669f990 code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= resume, IOPL = 0 current process = 601 (whoami) trap number = 12 panic: page fault I saved the dump manually with savecore and then tried to follow: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/advanced.html#KERNEL-PANIC-TROUBLESHOOTING [EMAIL PROTECTED] ~ $nm -n /boot/kernel/kernel | grep c053cb c053cb4c T init_turnstiles c053cbc9 t init_turnstile0 c053cbd8 t turnstile_setowner My kernel contains makeoptions DEBUG=-g, however I don't have the file /sys/compile/KERNELCONFIG/kernel.debug and thus wasn't able to do % gdb -k /sys/compile/KERNELCONFIG/kernel.debug /var/crash/vmcore.0 The next best thing seemed to be the -c option, no luck either. [EMAIL PROTECTED] ~ $gdb -c vmcore.0 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. /usr/home/fk/vmcore.0 is not a core dump: File format not recognized (gdb) [EMAIL PROTECTED] ~ $cat info.0 Dump header from device /dev/ad0s3b Architecture: i386 Architecture Version: 16777216 Dump Length: 536215552B (511 MB) Blocksize: 512 Dumptime: Tue May 3 20:18:11 2005 Hostname: r51.local Magic: FreeBSD Kernel Dump Version String: FreeBSD 5.4-STABLE #6: Sat Apr 30 14:57:04 CEST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/THINKPAD Panic String: page fault Dump Parity: 1084811848 Bounds: 0 Dump Status: good The kernel was build the new way. I was not able to reproduce the panic. Is there anything else I can do? Regards Fabian It would be great to have a look at the core. Can you put it up somewhere on the WEB? Also if you are not running a GENERIC kernel then let us have a look at the config file. Regards S. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.4-STABLE panic: kernel trap 12 with interrupts diabled
Subhro [EMAIL PROTECTED] wrote:
On 5/5/2005 19:43, Fabian Keil wrote:
the day before yesterday I experienced my first
panic on 5.4-STABLE. Build and cvsup'ed last
Friday. My system is a ThinkPad R51
I did nothing spectacular, after boot I:
logged in as user
cdrecord -scanbus (which didn't work as I hadn't yet set it suid)
su
chmod +x for cdrecord and readcd (meant was +g ;-)
exit
cdrecord -scanbus (didn't yet work ;-)
su
cdrecord -scanbus (did work)
readcd dev=2,0,0 -factor meshpoints=100 f=./file
exit
Then I moved the laptop and plugged in the AC/DC adapter.
whoami brought me:
Kernel trap 12 with interrupts disabled
Fatal trap 12: page fault while in kernel mode
fault virtual address= 0xa94d06c
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc053cbe5
stack pointer = 0x10:0xe669f98c
frame pointer= 0x10:0xe669f990
code segment = base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= resume, IOPL = 0
current process = 601 (whoami)
trap number = 12
panic: page fault
I saved the dump manually with savecore and then tried
to follow:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/advanced.html#KERNEL-PANIC-TROUBLESHOOTING
[EMAIL PROTECTED] ~ $nm -n /boot/kernel/kernel | grep c053cb
c053cb4c T init_turnstiles
c053cbc9 t init_turnstile0
c053cbd8 t turnstile_setowner
My kernel contains makeoptions DEBUG=-g, however
I don't have the file /sys/compile/KERNELCONFIG/kernel.debug
and thus wasn't able to do
% gdb -k /sys/compile/KERNELCONFIG/kernel.debug /var/crash/vmcore.0
It turned out that I just was looking at the wrong places, kernel.debug
was found at /usr/obj/usr/src/sys/THINKPAD/kernel.debug.
http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-gdb.html
fits better and contains a pointer to kgdb.
[EMAIL PROTECTED] ~ $cat info.0
Dump header from device /dev/ad0s3b
Architecture: i386
Architecture Version: 16777216
Dump Length: 536215552B (511 MB)
Blocksize: 512
Dumptime: Tue May 3 20:18:11 2005
Hostname: r51.local
Magic: FreeBSD Kernel Dump
Version String: FreeBSD 5.4-STABLE #6: Sat Apr 30 14:57:04 CEST 2005
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/THINKPAD
Panic String: page fault
Dump Parity: 1084811848
Bounds: 0
Dump Status: good
The kernel was build the new way.
I was not able to reproduce the panic.
Is there anything else I can do?
It would be great to have a look at the core. Can you put it up
somewhere on the WEB? Also if you are not running a GENERIC kernel then
let us have a look at the config file.
[EMAIL PROTECTED] ~ $ls -lh|grep core
-rw--- 1 fk wheel 511M May 3 20:38 vmcore.0
-rw--- 1 fk wheel 354M May 5 19:11 vmcore.0.gz
I don't have that much web space available.
However the following seems to be interesting:
[EMAIL PROTECTED] ~ $kgdb kernel.debug 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.
#0 doadump () at pcpu.h:160
160 pcpu.h: No such file or directory.
in pcpu.h
(kgdb) where
#0 doadump () at pcpu.h:160
#1 0xc0519e76 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:410
#2 0xc051a1a7 in panic (fmt=0xc06bafe5 %s) at
/usr/src/sys/kern/kern_shutdown.c:566
#3 0xc0693758 in trap_fatal (frame=0xe669f94c, eva=0) at
/usr/src/sys/i386/i386/trap.c:809
#4 0xc0692dca in trap (frame=
{tf_fs = 24, tf_es = 16, tf_ds = 16, tf_edi = -429261692, tf_esi =
-1043159552, tf_ebp = -429262448, tf_isp = -429262472, tf_ebx = -1043640192,
tf_edx = -1043640192, tf_ecx = 177524736, tf_eax = 177524736, tf_trapno = 12,
tf_err = 0, tf_eip = -1068250139, tf_cs = 8, tf_eflags = 65539, tf_esp =
-1043159552, tf_ss = -429262416})
at /usr/src/sys/i386/i386/trap.c:247
#5 0xc0681baa in calltrap () at /usr/src/sys/i386/i386/exception.s:140
#6 0x0018 in ?? ()
#7 0x0010 in ?? ()
#8 0x0010 in ?? ()
#9 0xe669fc84 in ?? ()
#10 0xc1d2a600 in ?? ()
#11 0xe669f990 in ?? ()
#12 0xe669f978 in ?? ()
#13 0xc1cb5080 in ?? ()
#14 0xc1cb5080 in ?? ()
#15 0x0a94d000 in ?? ()
#16 0x0a94d000 in ?? ()
#17 0x000c in ?? ()
#18 0x in ?? ()
#19 0xc053cbe5 in turnstile_setowner (ts=0xc1cb5080, owner=0x0) at
/usr/src/sys/kern/subr_turnstile.c:367
#20 0xc053cecd in turnstile_wait (ts=0xc1cb5080, lock=0xc1cbb000, owner=0x0) at
/usr/src/sys/kern/subr_turnstile.c:504
#21 0xc050fc57
pci_cfgintr_search / Kernel Trap 12
Hi, All the IRQ's on my laptop end up at 11, and was told that if I disable APM and go to ACPI I might be able to remedy this. I took out of my 4.9-STABLE kernel config : device apm0 and put in device acpica options ACPI_DEBUG When I reboot it tells me things like : apci0: DELL CPi R on motherboard [...] Timecounter ACPI-fast frequency 3.579545Hz acpi_cpu0: CPU on apcio (And tz0, acad0, cmbat0, cmbat1, lid0, button0, button1, timer0) After it probes for the miibus0, and I get 2 ukphy0 messages (One about the media interface, the other about the speeds it can go) I get : pci_cfgintr_search: linked (63) to configured irq 11 at 0:29:0 Kernel trap 12 with interrupts disabled Where do I go from here? Can't find anything on this. Thanks, Tuc/TTSG Internet Services, Inc. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
kernel trap 9 with interrupts disabled
Hello! My OS : 4.8-STABLE FreeBSD 4.8-STABLE #0: Thu Sep 4 16:50:44 BST 2003 [EMAIL PROTECTED]:/usr/src/sys/compile/KRL7 i386 My machine is rebooting from time to time. Uptimes are not going more than 1 day. Without reason. After set : dumpdev=/dev/ad0s1b dumpdir=/var/crash I've logs in /var/crash : kernel.0 , vmcore.0 [EMAIL PROTECTED] (17:14) x /var/crash # tail vmcore.0 kernel trap 9 with interrupts disabled kernel trap 9 with interrupts disabled kernel trap 9 with interrupts disabled kernel trap 9 with interrupts disabled kernel trap 9 with interrupts disabled kernel trap 9 with interrupts disabled kernel trap 9 with interrupts disabled kernel trap 9 with interrupts disabled kernel trap 9 with interrupts disabled What can I do? any patch? please help me. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
3ware 7850 kernel trap/NMI problem
Hi All, I have an issue with a 3ware 7850 8 port IDE Raid card on a dual Xeon FreeBSD 4.7 system. Here's the deal: *the system* Dual Xeon 2.4GHz, 2048MB ram, SuperMicro ServerWorks GC-LE chipset PCI-X MB, BIOS 1.1, hyperthreading disabled 3Ware 7850 8 port IDE Raid card, firmware 7.5.2 x8 IBM Deskstar 120GB disk drives, configured as Raid 0 Syskonnect SK-9821 copper gigabit card FreeBSD 4.7, kernel recompiled for single processor only *the problem* - As the machine sits 100% idle, every 60 seconds or so I get the following error message: /kernel: NMI ISA 2c, EISA ff kernel trap 19 with interrupts disabled /kernel: NMI ISA 3c, EISA ff If I do anything with the disk, like recompile a kernel or create a file with dd, the above lines repeat over and over very rapidly until the disk is done being busy. Anyone have any ideas about what the issue might be? TIA, Eff Norwood To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
