4.1-stable crash.

2000-10-03 Thread FengYue


Hi, could someone take a look at this crash.  The box is a
4.1-stable as Sep 6th.  Any hints on what could have caused the crash?
This box crashs almost every 3-5 days.  Thanks!

==cut here=

gdb -k kernel.debug /var/crash/vmcore.0
[GDB messages...]
This GDB was configured as "i386-unknown-freebsd"...
IdlePTD 2863104
initial pcb at 247960
panicstr: page fault
panic messages:
---
dmesg: kvm_read: 
---
#0  0xc0132df8 in boot ()
(kgdb) where
#0  0xc0132df8 in boot ()
Cannot access memory at address 0xce51d9b8.
(kgdb) 

end===

As you can see, I can't seem to be able to do a backtrace.

below is the dmesg output:

--cut here=-
FreeBSD 4.1-STABLE #3: Mon Sep 25 14:28:27 PDT 2000
Timecounter "i8254"  frequency 1193182 Hz
Timecounter "TSC"  frequency 651480181 Hz
CPU: Pentium III/Pentium III Xeon/Celeron (651.48-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x683  Stepping = 3

Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PA
T,PSE36,MMX,FXSR,XMM
real memory  = 201244672 (196528K bytes)
avail memory = 192761856 (188244K bytes)
Preloaded elf kernel "kernel" at 0xc02a9000.
Pentium Pro MTRR support enabled
md0: Malloc disk
npx0: math processor on motherboard
npx0: INT 16 interface
pcib0: Host to PCI bridge on motherboard
pci0: PCI bus on pcib0
pcib2: PCI to PCI bridge (vendor=1106 device=8605) at device 1.0 on pci0
pci1: PCI bus on pcib2
pci1: Trident model 9750 VGA-compatible display device at 0.0 irq 11
isab0: VIA 82C686 PCI-ISA bridge at device 4.0 on pci0
isa0: ISA bus on isab0
atapci0: VIA 82C686 ATA66 controller port 0xd800-0xd80f at device 4.1 on
pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
pci0: VIA 83C572 USB controller at 4.2 irq 10
pci0: VIA 83C572 USB controller at 4.3 irq 10
fxp0: Intel Pro 10/100B/100+ Ethernet port 0xb800-0xb81f mem
0xe080-0xe08f
,0xe300-0xe3000fff irq 10 at device 16.0 on pci0
fxp0: Ethernet address 00:20:35:67:5b:fc
pcib1: Host to PCI bridge on motherboard
pci2: PCI bus on pcib1
fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: 1440-KB 3.5" drive on fdc0 drive 0
atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0
vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0
sc0: System console at flags 0x100 on isa0
sc0: VGA 16 virtual consoles, flags=0x300
IP packet filtering initialized, divert enabled, rule-based forwarding
disabled,
 default to accept, logging limited to 100 packets/entry by default
IP Filter: v3.4.8 initialized.  Default = pass all, Logging = enabled
ad0: 9541MB Maxtor 31024H2 [19386/16/63] at ata0-master using UDMA66
ad1: 6869MB Maxtor 90720D5 [13957/16/63] at ata0-slave using UDMA33
ad2: 14649MB IBM-DTLA-307015 [29765/16/63] at ata1-master using UDMA66
Mounting root from ufs:/dev/ad0s1a
WARNING: / was not properly dismounted




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: 4.1-stable crash.

2000-10-03 Thread Dag-Erling Smorgrav

FengYue [EMAIL PROTECTED] writes:
 gdb -k kernel.debug /var/crash/vmcore.0
 [GDB messages...]
 This GDB was configured as "i386-unknown-freebsd"...
 IdlePTD 2863104
 initial pcb at 247960
 panicstr: page fault
 panic messages:
 ---

Where are the panic messages?

 dmesg: kvm_read: 
 ---
 #0  0xc0132df8 in boot ()
 (kgdb) where
 #0  0xc0132df8 in boot ()
 Cannot access memory at address 0xce51d9b8.
 (kgdb) 

This probably means the panic was in a KLD.

DES
-- 
Dag-Erling Smorgrav - [EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: 4.1-stable crash.

2000-10-03 Thread Dag-Erling Smorgrav

FengYue [EMAIL PROTECTED] writes:
 On 3 Oct 2000, Dag-Erling Smorgrav wrote:
 -  panic messages:
 -  ---
 - Where are the panic messages?
 
 Unfortunately, there is no panic messages. I compiled the kernel with
 -g (without DDB), and set the dumpdev in rc.conf.  Did I do anything
 wrong? 

The only thing I can think of is that the installed kernel is not the
one that paniced, so you are running gdb with the wrong symbol file.

 -  Cannot access memory at address 0xce51d9b8.
 -  (kgdb)
 - This probably means the panic was in a KLD.
 How could I know which KLD was having the problem?  

Hard to tell; usually from context.

DES
-- 
Dag-Erling Smorgrav - [EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: 4.1-stable crash.

2000-10-03 Thread FengYue


On 3 Oct 2000, Dag-Erling Smorgrav wrote:

- panic messages:
- ---
-
-Where are the panic messages?

Unfortunately, there is no panic messages. I compiled the kernel with
-g (without DDB), and set the dumpdev in rc.conf.  Did I do anything
wrong? 

- Cannot access memory at address 0xce51d9b8.
- (kgdb)
-
-This probably means the panic was in a KLD.

How could I know which KLD was having the problem?  

Thanks



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message