panic in propagate_priority w/ postgresql under heavy load

Thu Sep 1 15:31:04 PDT 2005

> -----Original Message-----
> From: owner-freebsd-hackers at freebsd.org 
> [mailto:owner-freebsd-hackers at freebsd.org] On Behalf Of Koen Martens
> Sent: Thursday, September 01, 2005 3:11 PM
> To: Dimitry Andric
> Cc: freebsd-hackers at freebsd.org
> Subject: Re: panic in propagate_priority w/ postgresql under 
> heavy load
> 
> Hi Dim,
> 
> Dimitry Andric wrote:
> > On 2005-09-01 at 19:02:06 Koen Martens wrote: 
> > 
> >>Anyway, it seems the dump should've gone to the swap partition, but 
> >>i'm into multi-user mode again so i guess i'll have to wait for 
> >>another panic to obtain it?
> > 
> > In RELENG_6, the dump device is chosen automagically during boot by 
> > /etc/rc.d/dumpon, but this is (alas) not the case in RELENG_5_x, so 
> > you'll have to manually specify it in /etc/rc.conf, i.e:
> > 
> >   dumpdev=/dev/ad0s1b
> > 
> > Then make sure you have enough space in /var/crash, and try to 
> > reproduce your panic...
> 
> Ok, i get it.. When it reboots it detects a dump on the swap 
> partition and dd's that to /var/crash.. Which has plenty of 
> free space on the particular box, 59 gigs ought to be enough 
> for everyone :)
> 
> > Also, I think I read somewhere that there used to be problems with 
> > dumping and 3Ware RAID cards (you seem to be using one according to 
> > your kernel config, but you apparently didn't post a dmesg).
> 
> You're right, dmesg included below.
> 
> > However,
> > it looks like revision 1.22.2.1 of src/sys/dev/twe/twe.c fixed that:
> > 
> > 
> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/twe/twe.c?rev=1.22.2
> > .1&content-type=text/x-cvsweb-markup
> > 
> > Just to be sure, can you check if you got this version of twe.c, or
> > 1.22.2.2 (which seems to be the RELENG_5_4 version, and 
> thus it should 
> > be fixed).
> 
>  *      $FreeBSD: src/sys/dev/twe/twe.c,v 1.22.2.2 2005/02/18
> 18:42:16 vkashyap
> Exp $
> 
> (nice wrapping, i think you get the idea :)
> 
> 
> 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.4-RELEASE-p6 #1: Thu Sep  1 14:06:03 CEST 2005
>     root at yin.sonologic.nl:/usr/obj/usr/src/sys/yin-yang-5.4
> WARNING: WITNESS option enabled, expect reduced performance.
> Timecounter "i8254" frequency 1193182 Hz quality 0
> CPU: Intel(R) Xeon(TM) CPU 3.06GHz (3056.50-MHz 686-class CPU)
>   Origin = "GenuineIntel"  Id = 0xf29  Stepping = 9
> 
> Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SE
P,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,
TM,PBE>
>   Hyperthreading: 2 logical CPUs
> real memory  = 2146959360 (2047 MB)
> avail memory = 2095415296 (1998 MB)
> ACPI APIC Table: <PTLTD  	 APIC  >
> 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
> npx0: <math processor> on motherboard
> npx0: INT 16 interface
> acpi0: <PTLTD   RSDT> on motherboard
> 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
> cpu0: <ACPI CPU> on acpi0
> cpu1: <ACPI CPU> on acpi0
> 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> at device 2.0 on pci0
> pci1: <ACPI PCI bus> on pcib1
> pci1: <base peripheral, interrupt controller> at device 28.0 
> (no driver attached)
> pcib2: <ACPI PCI-PCI bridge> at device 29.0 on pci1
> pci2: <ACPI PCI bus> on pcib2
> pci1: <base peripheral, interrupt controller> at device 30.0 
> (no driver attached)
> pcib3: <ACPI PCI-PCI bridge> at device 31.0 on pci1
> pci3: <ACPI PCI bus> on pcib3
> 3ware device driver for 9000 series storage controllers, version:
> 2.50.02.012
> twa0: <3ware 9000 series Storage Controller> port 
> 0x7000-0x70ff mem 0xfd800000-0xfdffffff,0xfb200000-0xfb2000ff 
> irq 48 at device 1.0 on pci3
> twa0: 4 ports, Firmware FE9X 2.02.00.008, BIOS BE9X 2.02.01.037
> pci0: <unknown> at device 2.1 (no driver attached)
> pcib4: <ACPI PCI-PCI bridge> at device 30.0 on pci0
> pci4: <ACPI PCI bus> on pcib4
> pci4: <display, VGA> at device 3.0 (no driver attached)
> fxp0: <Intel 82550 Pro/100 Ethernet> port 0x8400-0x843f mem 
> 0xfb300000-0xfb31ffff,0xfb341000-0xfb341fff irq 20 at device 
> 4.0 on pci4
> miibus0: <MII bus> on fxp0
> inphy0: <i82555 10/100 media interface> on miibus0
> inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> fxp0: Ethernet address: 00:02:b3:d8:8a:b5
> em0: <Intel(R) PRO/1000 Network Connection, Version - 1.7.35> 
> port 0x8440-0x847f mem 0xfb320000-0xfb33ffff irq 23 at device 
> 5.0 on pci4
> em0: Ethernet address: 00:02:b3:d8:8b:05
> em0:  Speed:N/A  Duplex:N/A
> isab0: <PCI-ISA bridge> at device 31.0 on pci0
> isa0: <ISA bus> on isab0
> atapci0: <Intel ICH3 UDMA100 controller> port
> 0x6c60-0x6c6f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 
> 31.1 on pci0
> ata0: channel #0 on atapci0
> ata1: channel #1 on atapci0
> pci0: <serial bus, SMBus> at device 31.3 (no driver attached)
> acpi_button0: <Power Button> on acpi0
> atkbdc0: <Keyboard controller (i8042)> port 0x64,0x60 irq 1 on acpi0
> atkbd0: <AT Keyboard> irq 1 on atkbdc0
> kbd0 at atkbd0
> fdc0: <floppy drive controller> port 
> 0x3f7,0x3f4-0x3f5,0x3f0-0x3f3 irq 6 drq 2 on acpi0
> 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, console
> sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0
> sio1: type 16550A
> ppc0: <ECP parallel printer port> port 
> 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0
> ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
> ppc0: FIFO with 16/16/9 bytes threshold
> 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
> pmtimer0 on isa0
> orm0: <ISA Option ROMs> at iomem
> 0xe3000-0xe3fff,0xc8000-0xc97ff,0xc0000-0xc7fff on isa0
> sc0: <System console> at flags 0x100 on isa0
> sc0: VGA <16 virtual consoles, flags=0x100>
> vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 
> 0xa0000-0xbffff on isa0 Timecounters tick every 10.000 msec
> IPv6 packet filtering initialized, default to accept, logging 
> limited to 10 packets/entry IP Filter: v3.4.35 initialized.  
> Default = block all, Logging = enabled
> witness_get: witness exhausted
> ipfw2 initialized, divert disabled, rule-based forwarding 
> enabled, default to accept, logging limited to 10 
> packets/entry by default
> acd0: CDROM <CD-224E/1.9A> at ata0-master PIO4 da0 at twa0 
> bus 0 target 0 lun 0
> da0: <3ware Logical Disk 00 1.00> Fixed Direct Access SCSI-0 device
> da0: 100.000MB/s transfers
> da0: 114430MB (234352640 512 byte sectors: 255H 63S/T 14587C)
> SMP: AP CPU #1 Launched!
> Mounting root from ufs:/dev/da0s1a
> WARNING: / was not properly dismounted
> WARNING: /usr was not properly dismounted
> WARNING: /var was not properly dismounted
> /var: mount pending error: blocks 1024 files 7
> em0: Link is up 100 Mbps Full Duplex
> 
> twa0: INFO: (0x04: 0x000c): Background initialize started: unit=0
> twa0: INFO: (0x04: 0x0007): Background initialize done: unit=0
> 

You seem to be booting off of a 9000 (twa) controller and not 7000/8000
(twe).
It could be because of a 9000 firmware bug that you are not being able
to
get the dump.  The firmware wrongly interprets physical address 0x0 as
invalid
during dumps, and fails the operations.  This bug will be fixed in
future
firmware releases.
--------------------------------------------------------

CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and contains information that is confidential and proprietary to Applied Micro Circuits Corporation or its subsidiaries. It is to be used solely for the purpose of furthering the parties' business relationship. All unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.