Daily lockups on 5.2-BETA (maybe pst driver bug?)

2003-12-02 Thread Attila Nagy
Hello,

I'm seeing daily lockups on an up to date -CURRENT machine.
I've had the debugger already compiled in, but it didn't save a 
crashdump. The machine is mostly idle, it has only some IMAP mailboxes 
under cyrus.

All I could save from the console is the following:
pst: timeout mfa=0x002a5850 cmd=0x02
pst: timeout mfa=0x002a38d0 cmd=0x02
pst: timeout mfa=0x002a5af0 cmd=0x02
interrupt  total
irq1: atkbd0 246
irq8: rtc7800771
irq13: npx01
stray irq131
irq14: ata0   144893
irq15: ata1   30
irq48: pstpci0345956
irq54: em0304160
irq0: clk6093522
Total   14689580
watchdog_fire(e65e4b08,c7dfeb00,e65e4a98,c05df35c) at watchdog_fire+0xab
hardlock(e65e4b08,c3f08a00,e65e4ab8,c05df2e4,c7eb0800) at hardlock+0x147
clkintr(e65e4b08,e65e4ac8,46,0,cad91c80) at clkintr+0xef
intr_execute_handlers(c0645d20,e65e4b08,e65e4b04,c05da5d6,80012) at 
intr_execute_handlers+0x8a
atpic_handle_intr(0) at atpic_handle_intr+0xef
Xatpic_intr0() at Xatpic_intr0+0x1e
--- interrupt, eip = 0xc04bb328, esp = 0xe65e4b4c, ebp = 0xe65e4b70 ---
lockmgr(d464ab34,80012,0,cad91c80,c0650010) at lockmgr+0x5ee
getdirtybuf(e65e4bb4,0,1,d464aa68,1) at getdirtybuf+0xb7
flush_deplist(c8f86d44,1,e65e4bdc,e65e4be0,0) at flush_deplist+0x40
flush_inodedep_deps(c813c800,3219373,246,e65e4c38,c04cfbf7) at 
flush_inodedep_deps+0x83
softdep_sync_metadata(e65e4ca8,ce873000,50,c06176c6,0) at 
softdep_sync_metadata+0x7e
ffs_fsync(e65e4ca8,0,0,0,0) at ffs_fsync+0x44f
fsync(cad91c80,e65e4d14,4,29739000,1) at fsync+0x188
syscall(2f,2f,2f,bfbf6c24,0) at syscall+0x2ed
Xint0x80_syscall() at Xint0x80_syscall+0x1d
-- syscall (95), eip = 0x28385053, esp = 0xbfbf4b9c, ebp = 0xbfbfc68 ---
Debugger(watchdog timeout)
Stopped atDebugger+0x4f:  xchgl  %ebx,in_Debugger.0
db panic
panic: from debugger
cpuid = 0;
boot() called on cpu#0

syncing disks, buffers remaining... panic: softdep_lock: locking against 
myself
cpuid = 0;
boot() called on cpu#0
Uptime: 16h55m37s

dmesg:
Copyright (c) 1992-2003 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.2-BETA #6: Mon Dec  1 11:04:55 CET 2003
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/IMAP
Preloaded elf kernel /boot/kernel/kernel at 0xc06eb000.
ACPI APIC Table: PTLTD  APIC  
Timecounter i8254 frequency 1193182 Hz quality 0
CPU: Intel(R) Xeon(TM) CPU 2.40GHz (2399.33-MHz 686-class CPU)
  Origin = GenuineIntel  Id = 0xf27  Stepping = 7
Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SS
E2,SS,HTT,TM,PBE
real memory  = 2146893824 (2047 MB)
avail memory = 2084335616 (1987 MB)
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  6
ioapic0 Version 2.0 irqs 0-23 on motherboard
ioapic1 Version 2.0 irqs 24-47 on motherboard
ioapic2 Version 2.0 irqs 48-71 on motherboard
Pentium Pro MTRR support enabled
acpi0: PTLTDRSDT   on motherboard
pcibios: BIOS version 2.10
Using $PIR table, 21 entries at 0xc00fde70
acpi0: Power Button (fixed)
Timecounter ACPI-fast frequency 3579545 Hz quality 1000
acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0
acpi_cpu0: CPU on acpi0
acpi_cpu1: CPU on acpi0
acpi_cpu2: CPU on acpi0
device_probe_and_attach: acpi_cpu2 attach returned 6
acpi_cpu2: CPU on acpi0
device_probe_and_attach: acpi_cpu2 attach returned 6
pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0
pci0: ACPI PCI bus on pcib0
pci0: unknown at device 0.1 (no driver attached)
pcib1: ACPI PCI-PCI bridge mem 0xf800-0xfbff at device 1.0 on pci0
pci1: ACPI PCI bus on pcib1
pci1: display, VGA at device 0.0 (no driver attached)
pcib2: ACPI PCI-PCI bridge at device 2.0 on pci0
pcib2: could not get PCI interrupt routing table for \\_SB_.PCI0.HLB_ - 
AE_NOT_FOUND
pci2: ACPI PCI bus on pcib2
pci2: base peripheral, interrupt controller at device 28.0 (no driver 
attached)
pcib3: ACPI PCI-PCI bridge at device 29.0 on pci2
pci3: ACPI PCI bus on pcib3
pcib4: PCI-PCI bridge at device 1.0 on pci3
pci4: PCI bus on pcib4
pstpci0: Promise SuperTrak SX6000 ATA RAID controller mem 
0xf240-0xf27f irq 48 at device 1.1 on pci3
em0: Intel(R) PRO/1000 Network Connection, Version - 1.7.19 port 
0x3000-0x303f mem 0xf210-0xf211 irq 54 at device 3.
0 on pci3
em0:  Speed:N/A  Duplex:N/A
pci2: base peripheral, interrupt controller at device 30.0 (no driver 
attached)
pcib5: ACPI PCI-PCI bridge at device 31.0 on pci2
pci5: ACPI PCI bus on pcib5
pcib6: ACPI PCI-PCI bridge at device 30.0 on pci0
pci6: ACPI PCI bus on pcib6
isab0: PCI-ISA bridge at device 31.0 on pci0
isa0: ISA bus on isab0
atapci0: Intel ICH4 UDMA100 controller port 
0x2440-0x244f,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 mem 
0xf000-0xf
3ff 

Re: Daily lockups on 5.2-BETA (maybe pst driver bug?)

2003-12-02 Thread Doug White
On Tue, 2 Dec 2003, Attila Nagy wrote:

 I'm seeing daily lockups on an up to date -CURRENT machine.
 I've had the debugger already compiled in, but it didn't save a
 crashdump. The machine is mostly idle, it has only some IMAP mailboxes
 under cyrus.

It appears you have the hardware watchdog enabled. Any reason you need
that?  It might be malfunctioning on your system.

Also the pst driver might be grabbing interrupts for too long.  You might
check your RAID status.


 All I could save from the console is the following:
 pst: timeout mfa=0x002a5850 cmd=0x02
 pst: timeout mfa=0x002a38d0 cmd=0x02
 pst: timeout mfa=0x002a5af0 cmd=0x02
 interrupt  total
 irq1: atkbd0 246
 irq8: rtc7800771
 irq13: npx01
 stray irq131
 irq14: ata0   144893
 irq15: ata1   30
 irq48: pstpci0345956
 irq54: em0304160
 irq0: clk6093522
 Total   14689580
 watchdog_fire(e65e4b08,c7dfeb00,e65e4a98,c05df35c) at watchdog_fire+0xab
 hardlock(e65e4b08,c3f08a00,e65e4ab8,c05df2e4,c7eb0800) at hardlock+0x147
 clkintr(e65e4b08,e65e4ac8,46,0,cad91c80) at clkintr+0xef
 intr_execute_handlers(c0645d20,e65e4b08,e65e4b04,c05da5d6,80012) at
 intr_execute_handlers+0x8a
 atpic_handle_intr(0) at atpic_handle_intr+0xef
 Xatpic_intr0() at Xatpic_intr0+0x1e
 --- interrupt, eip = 0xc04bb328, esp = 0xe65e4b4c, ebp = 0xe65e4b70 ---
 lockmgr(d464ab34,80012,0,cad91c80,c0650010) at lockmgr+0x5ee
 getdirtybuf(e65e4bb4,0,1,d464aa68,1) at getdirtybuf+0xb7
 flush_deplist(c8f86d44,1,e65e4bdc,e65e4be0,0) at flush_deplist+0x40
 flush_inodedep_deps(c813c800,3219373,246,e65e4c38,c04cfbf7) at
 flush_inodedep_deps+0x83
 softdep_sync_metadata(e65e4ca8,ce873000,50,c06176c6,0) at
 softdep_sync_metadata+0x7e
 ffs_fsync(e65e4ca8,0,0,0,0) at ffs_fsync+0x44f
 fsync(cad91c80,e65e4d14,4,29739000,1) at fsync+0x188
 syscall(2f,2f,2f,bfbf6c24,0) at syscall+0x2ed
 Xint0x80_syscall() at Xint0x80_syscall+0x1d
 -- syscall (95), eip = 0x28385053, esp = 0xbfbf4b9c, ebp = 0xbfbfc68 ---
 Debugger(watchdog timeout)
 Stopped atDebugger+0x4f:  xchgl  %ebx,in_Debugger.0
 db panic
 panic: from debugger
 cpuid = 0;
 boot() called on cpu#0

 syncing disks, buffers remaining... panic: softdep_lock: locking against
 myself
 cpuid = 0;
 boot() called on cpu#0
 Uptime: 16h55m37s

 dmesg:
 Copyright (c) 1992-2003 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.2-BETA #6: Mon Dec  1 11:04:55 CET 2003
  [EMAIL PROTECTED]:/usr/obj/usr/src/sys/IMAP
 Preloaded elf kernel /boot/kernel/kernel at 0xc06eb000.
 ACPI APIC Table: PTLTD  APIC  
 Timecounter i8254 frequency 1193182 Hz quality 0
 CPU: Intel(R) Xeon(TM) CPU 2.40GHz (2399.33-MHz 686-class CPU)
Origin = GenuineIntel  Id = 0xf27  Stepping = 7

 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SS
 E2,SS,HTT,TM,PBE
 real memory  = 2146893824 (2047 MB)
 avail memory = 2084335616 (1987 MB)
 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
   cpu0 (BSP): APIC ID:  0
   cpu1 (AP): APIC ID:  6
 ioapic0 Version 2.0 irqs 0-23 on motherboard
 ioapic1 Version 2.0 irqs 24-47 on motherboard
 ioapic2 Version 2.0 irqs 48-71 on motherboard
 Pentium Pro MTRR support enabled
 acpi0: PTLTDRSDT   on motherboard
 pcibios: BIOS version 2.10
 Using $PIR table, 21 entries at 0xc00fde70
 acpi0: Power Button (fixed)
 Timecounter ACPI-fast frequency 3579545 Hz quality 1000
 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0
 acpi_cpu0: CPU on acpi0
 acpi_cpu1: CPU on acpi0
 acpi_cpu2: CPU on acpi0
 device_probe_and_attach: acpi_cpu2 attach returned 6
 acpi_cpu2: CPU on acpi0
 device_probe_and_attach: acpi_cpu2 attach returned 6
 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0
 pci0: ACPI PCI bus on pcib0
 pci0: unknown at device 0.1 (no driver attached)
 pcib1: ACPI PCI-PCI bridge mem 0xf800-0xfbff at device 1.0 on pci0
 pci1: ACPI PCI bus on pcib1
 pci1: display, VGA at device 0.0 (no driver attached)
 pcib2: ACPI PCI-PCI bridge at device 2.0 on pci0
 pcib2: could not get PCI interrupt routing table for \\_SB_.PCI0.HLB_ -
 AE_NOT_FOUND
 pci2: ACPI PCI bus on pcib2
 pci2: base peripheral, interrupt controller at device 28.0 (no driver
 attached)
 pcib3: ACPI PCI-PCI bridge at device 29.0 on pci2
 pci3: ACPI PCI bus on pcib3
 pcib4: PCI-PCI bridge at device 1.0 on pci3
 pci4: PCI bus on pcib4
 pstpci0: Promise SuperTrak SX6000 ATA RAID controller mem
 0xf240-0xf27f irq 48 at device 1.1 on pci3
 em0: Intel(R) PRO/1000 Network Connection, Version - 1.7.19 port
 0x3000-0x303f mem 0xf210-0xf211 irq 54 at device 3.
 0 on pci3
 em0:  Speed:N/A  Duplex:N/A
 pci2: base peripheral, interrupt controller at device 30.0 (no driver
 attached)
 

Re: Daily lockups on 5.2-BETA (maybe pst driver bug?)

2003-12-02 Thread Attila Nagy
Doug White wrote:
It appears you have the hardware watchdog enabled. Any reason you need
that?  It might be malfunctioning on your system.
It's FreeBSD's WATCHDOG, and all I compiled that in is why I needed the 
machine to go. But it doesn't :-O

It freezes without the watchdog completely.

Also the pst driver might be grabbing interrupts for too long.  You might
check your RAID status.
Is it normal that a RAID driver crashes the kernel when a RAID array is 
down?
BTW, the card's bios doesn't show any problems (it's dumb as the earth), 
but I will check it with its Windows stuff, but first I need to install 
a Windows somewhere...

Thanks.

--
Attila Nagy   e-mail: [EMAIL PROTECTED]
Free Software Network (FSN.HU)   phone @work: +361 210 1415/127
ISOs: http://www.fsn.hu/?f=downloadcell.: +3630 306 6758
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]