My computer keeps crashing
cali
calculus at softhome.net
Thu Jan 20 16:06:21 PST 2005
If this is the wrong mailing list, I apologise, suggestions to a more
appropriate mailing list will be appreciated.
Reasonably recently I upgraded my hardware to the following:
Soltek SL-NV400-64 "Purple
Ray" (Socket A) Motherboard
AMD Athlon "Barton" XP3200+
400FSB (Socket A) CPU - OEM
Asus DRW-0402P DVD-R/RW -
Retail
Adata 512MB DDR PC3200 CAS 2.5
Adata 512MB DDR PC3200 CAS 2.5
Zalman Flower CNPS6000-Cu
Silent Socket A CPU Cooler -
Antec Sonata Piano Black
Quiet Case - 380W TruePower
Silent PSU
Hyundai ImageQuest Q995 19''
Perfectly Flat CRT Monitor -
Black/Silver
Geforce FX 5200 graphics card
IBM 60GB HD
Western Digital 160GB HD
Sometimes when I run CPU intensive applications the system will
crash at seemingly unpredictable times, I have to hard reset the machine as
it
is completely unresponsive, I was running an experiment in console mode and
it showed me the kernel panic:
kernel trap 9 with interrupts disabled
kernel trap 9 with interrupts disabled
Fatal trap 9: general protection fault while in kernel mode
instruction pointer = 0xed7c:0x0
stack pointer = 0x10:0xe529ed88
frame pointer = 0x10:0x0
code segment = base 0xcc084, limit 0xaaec, type 0x0
= DPL 0, pres 0, def32 0, gran 0
processor eflags = IOPL = 0
current process = 533 (maximumcut)
trap number = 9
panic: general protection fault
Uptime: 5m27s
and another time:
kernel trap 9 with interrupts disabled
kernel trap 9 with interrupts disabled
Fatal trap 9: general protection fault while in kernel mode
instruction pointer = 0x9d7c:0x0
stack pointer = 0x10:0xe7509d88
frame pointer = 0x10:0x0
code segment = base 0x8c084, limit 0x74ec, type 0x0
= DPL 0, pres 0, def 32 0, gran 0
processor eflags = IOPL = 0
currrentprocess = 593 (maximumcut)
trap number = 9
panic: general protection fault
Uptime: 16m7s
I copied this manually so hopefully I copied it correctly.
I think the problem might be due to my bios settings running the CPU to fast
although I do not think I am overclocking it. This might explain the strange
timing of the problem, maybe the motherboard is unstable.
here is my dmesg:
Copyright (c) 1992-2005 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 5.3-STABLE #5: Thu Jan 13 12:34:13 GMT 2005
XXXXXX:/usr/obj/usr/src/sys/GENERIC
mptable_probe: MP Config Table has bad signature: Mous
ACPI APIC Table: <Nvidia AWRDACPI>
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: AMD Athlon(tm) XP 3200+ (2205.01-MHz 686-class CPU)
Origin = "AuthenticAMD" Id = 0x6a0 Stepping = 0
Features=0x383fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE>
AMD Features=0xc0400000<AMIE,DSP,3DNow!>
real memory = 1073676288 (1023 MB)
avail memory = 1036918784 (988 MB)
ioapic0 <Version 1.1> irqs 0-23 on motherboard
npx0: [FAST]
npx0: <math processor> on motherboard
npx0: INT 16 interface
acpi0: <Nvidia AWRDACPI> on motherboard
acpi0: Power Button (fixed)
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0
cpu0: <ACPI CPU> on acpi0
acpi_tz0: <Thermal Zone> on acpi0
acpi_button0: <Power Button> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pci0: <memory, RAM> at device 0.1 (no driver attached)
pci0: <memory, RAM> at device 0.2 (no driver attached)
pci0: <memory, RAM> at device 0.3 (no driver attached)
pci0: <memory, RAM> at device 0.4 (no driver attached)
pci0: <memory, RAM> at device 0.5 (no driver attached)
isab0: <PCI-ISA bridge> at device 1.0 on pci0
isa0: <ISA bus> on isab0
pci0: <serial bus, SMBus> at device 1.1 (no driver attached)
ohci0: <OHCI (generic) USB controller> mem 0xdb002000-0xdb002fff irq 22 at
device 2.0 on pci0
ohci0: [GIANT-LOCKED]
usb0: OHCI version 1.0, legacy support
usb0: SMM does not respond, resetting
usb0: <OHCI (generic) USB controller> on ohci0
usb0: USB revision 1.0
uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 3 ports with 3 removable, self powered
ohci1: <OHCI (generic) USB controller> mem 0xdb003000-0xdb003fff irq 21 at
device 2.1 on pci0
ohci1: [GIANT-LOCKED]
usb1: OHCI version 1.0, legacy support
usb1: SMM does not respond, resetting
usb1: <OHCI (generic) USB controller> on ohci1
usb1: USB revision 1.0
uhub1: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 3 ports with 3 removable, self powered
pci0: <serial bus, USB> at device 2.2 (no driver attached)
pci0: <multimedia, audio> at device 6.0 (no driver attached)
pcib1: <ACPI PCI-PCI bridge> at device 8.0 on pci0
pci1: <ACPI PCI bus> on pcib1
rl0: <RealTek 8139 10/100BaseTX> port 0xc000-0xc0ff mem
0xda000000-0xda0000ff irq 18 at device 5.0 on pci1
miibus0: <MII bus> on rl0
rlphy0: <RealTek internal media interface> on miibus0
rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
rl0: Ethernet address: 00:40:f4:7b:ac:f4
fwohci0: <VIA Fire II (VT6306)> port 0xc400-0xc47f mem 0xda001000-0xda0017ff
irq 18 at device 7.0 on pci1
fwohci0: OHCI version 1.0 (ROM=1)
fwohci0: No. of Isochronous channels is 8.
fwohci0: EUI64 00:11:06:00:00:00:6b:29
fwohci0: Phy 1394a available S400, 3 ports.
fwohci0: Link S400, max_rec 2048 bytes.
firewire0: <IEEE1394(FireWire) bus> on fwohci0
fwe0: <Ethernet over FireWire> on firewire0
if_fwe0: Fake Ethernet address: 02:11:06:00:6b:29
fwe0: Ethernet address: 02:11:06:00:6b:29
fwe0: if_start running deferred for Giant
sbp0: <SBP-2/SCSI over FireWire> on firewire0
fwohci0: Initiate bus reset
fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode
firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me)
firewire0: bus manager 0 (me)
atapci0: <nVidia nForce2 UDMA133 controller> port
0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 9.0 on pci0
ata0: channel #0 on atapci0
ata1: channel #1 on atapci0
pcib2: <ACPI PCI-PCI bridge> at device 30.0 on pci0
pci2: <ACPI PCI bus> on pcib2
nvidia0: <GeForce FX 5200> mem 0xd0000000-0xd7ffffff,0xd8000000-0xd8ffffff
irq 19 at device 0.0 on pci2
nvidia0: [GIANT-LOCKED]
fdc0: <floppy drive controller> port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0
fdc0: [FAST]
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on
acpi0
sio0: type 16550A
sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0
sio1: type 16550A
ppc0: <Standard parallel printer port> port 0x778-0x77b,0x378-0x37f irq 7 on
acpi0
ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
ppbus0: <Parallel port bus> on ppc0
plip0: <PLIP network interface> on ppbus0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0
atkbdc0: <Keyboard controller (i8042)> port 0x64,0x60 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: model IntelliMouse Explorer, device ID 4
orm0: <ISA Option ROM> at iomem 0xd0000-0xd3fff on isa0
pmtimer0 on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Timecounter "TSC" frequency 2205011080 Hz quality 800
Timecounters tick every 10.000 msec
ad0: 58644MB <IC35L060AVER07-0/ER6OA46A> [119150/16/63] at ata0-master
UDMA100
ad1: 152627MB <WDC WD1600JB-00EVA0/15.05R15> [310101/16/63] at ata0-slave
UDMA100
acd0: DVDR <ASUS DVD-RW DRW-0402P/1.10> at ata1-master UDMA33
Mounting root from ufs:/dev/ad1s1a
WARNING: / was not properly dismounted
WARNING: /home was not properly dismounted
WARNING: /proc was not properly dismounted
WARNING: /tmp was not properly dismounted
WARNING: /usr was not properly dismounted
WARNING: /var was not properly dismounted
Does anyone have any idea why this crashing could be happening? Could it
possibly be the bios settings?
I don't think it has anything to do with the program I am running as it does
nothing out of the ordinary, I could send the program source code if
necessary?
If it is the bios settings or an unstable motherboard, then how on earth
does this manifest as a kernel panic? This really interests me.
regards
cali
More information about the freebsd-questions
mailing list