On Friday 23 January 2004 07:50 am, Bogdan TARU wrote: > Hi hackers, > > I am experiencing kernel panics on a poweredge 2650 each day around > 3am (usually the machine comes up at 3:04am). The kernel panics are > reproductable by running: /etc/periodic/security/100.chksetuid (in > fact by runnning find on /usr with -perms). The problem lies > somewhere in /usr/ports. Deleting the /usr/ports tree doesn't solve > it, trying a cvs up of /usr/ports results in a crash again. > > I googled around a lil' bit, and found: > http://lists.freebsd.org/pipermail/freebsd-hackers/2003-April/000192.html, > and also Terry's answer, but that addresses freebsd 4.7. But my box > is running 4.9-release, and the systems was cleanly installed with > 4.9 from the very beginning, so not upgraded from 4.7 or any other > previous version. > > The dmesg looks like: > > 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 4.9-RELEASE #1: Mon Nov 17 23:47:49 CET 2003 > root@:/usr/src/sys/compile/saturn > Timecounter "i8254" frequency 1193182 Hz > Timecounter "TSC" frequency 1790761584 Hz > CPU: Intel(R) Xeon(TM) CPU 1.80GHz (1790.76-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0xf27 Stepping = 7 > > Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MC >A,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > Hyperthreading: 2 logical CPUs > real memory = 2147418112 (2097088K bytes) > avail memory = 2088136704 (2039196K bytes) > Preloaded elf kernel "kernel" at 0xc0312000. > Warning: Pentium 4 CPU: PSE disabled > Pentium Pro MTRR support enabled > Using $PIR table, 9 entries at 0xc00fc430 > npx0: <math processor> on motherboard > npx0: INT 16 interface > pcib0: <Host to PCI bridge> on motherboard > pci0: <PCI bus> on pcib0 > pci0: <unknown card> (vendor=0x1028, dev=0x000c) at 4.0 irq 11 > pci0: <unknown card> (vendor=0x1028, dev=0x0008) at 4.1 irq 10 > pci0: <unknown card> (vendor=0x1028, dev=0x000d) at 4.2 irq 7 > pci0: <ATI Mach64-GR graphics accelerator> at 14.0 > atapci0: <ServerWorks CSB5 ATA100 controller> port > 0x8b0-0x8bf,0x8d8-0x8db,0x8d0-0x8d7,0x8c8-0x8cb,0x8c0-0x8c7 at device > 15.1 on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > pci0: <OHCI USB controller> at 15.2 irq 5 > isab0: <PCI to ISA bridge (vendor=1166 device=0225)> at device 15.3 on > pci0 > isa0: <ISA bus> on isab0 > pcib1: <Host to PCI bridge> on motherboard > pci1: <PCI bus> on pcib1 > pcib2: <Host to PCI bridge> on motherboard > pci2: <PCI bus> on pcib2 > pcib3: <Host to PCI bridge> on motherboard > pci3: <PCI bus> on pcib3 > bge0: <Broadcom BCM5701 Gigabit Ethernet, ASIC rev. 0x105> mem > 0xfcf10000-0xfcf1ffff irq 11 at device 6.0 on pci3 > bge0: Ethernet address: 00:06:5b:f6:48:38 > miibus0: <MII bus> on bge0 > brgphy0: <BCM5701 10/100/1000baseTX PHY> on miibus0 > brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, > 1000baseTX-FDX, auto > bge1: <Broadcom BCM5701 Gigabit Ethernet, ASIC rev. 0x105> mem > 0xfcf00000-0xfcf0ffff irq 10 at device 8.0 on pci3 > bge1: Ethernet address: 00:06:5b:f6:48:39 > miibus1: <MII bus> on bge1 > brgphy1: <BCM5701 10/100/1000baseTX PHY> on miibus1 > brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, > 1000baseTX-FDX, auto > bge1: <Broadcom BCM5701 Gigabit Ethernet, ASIC rev. 0x105> mem > 0xfcf00000-0xfcf0ffff irq 10 at device 8.0 on pci3 > bge1: Ethernet address: 00:06:5b:f6:48:39 > miibus1: <MII bus> on bge1 > brgphy1: <BCM5701 10/100/1000baseTX PHY> on miibus1 > brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, > 1000baseTX-FDX, auto > pcib4: <ServerWorks host to PCI bridge(unknown chipset)> on > motherboard > pci4: <PCI bus> on pcib4 > pcib8: <PCI to PCI bridge (vendor=8086 device=0309)> at device 8.0 on > pci4 > pci5: <PCI bus> on pcib8 > pci5: <unknown card> (vendor=0x9005, dev=0x00c5) at 6.0 irq 7 > pci5: <unknown card> (vendor=0x9005, dev=0x00c5) at 6.1 irq 11 > aac0: <Dell PERC 3/Di> mem 0xf0000000-0xf7ffffff irq 7 at device 8.1 > on pci4 > aac0: i960RX 100MHz, 118MB cache memory, optional battery present > aac0: Kernel 2.7-1, Build 3170, S/N 5010d3 > aac0: Supported > Options=75c<WCACHE,DATA64,HOSTTIME,WINDOW4GB,SOFTERR,NORECOND,SGMAP64> > pcib5: <ServerWorks host to PCI bridge(unknown chipset)> on > motherboard > pci6: <PCI bus> on pcib5 > pcib6: <ServerWorks host to PCI bridge(unknown chipset)> on > motherboard > pci7: <PCI bus> on pcib6 > pcib7: <ServerWorks host to PCI bridge(unknown chipset)> on > motherboard > pci8: <PCI bus> on pcib7 > orm0: <Option ROMs> at iomem > 0xc0000-0xc7fff,0xc8000-0xcbfff,0xec000-0xeffff on isa0 > pmtimer0 on isa0 > 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 0xa0000-0xbffff on > isa0 > sc0: <System console> at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > sio1: type 16550A > IP Filter: v3.4.31 initialized. Default = pass all, Logging = > disabled > ata0-slave: ATAPI identify retries exceeded > acd0: CDROM <TEAC CD-ROM CD-224E> at ata0-master PIO4 > aacd0: <RAID 0/1> on aac0 > aacd0: 139997MB (286714368 sectors)
Sorry for being late, but i just saw this. I'm running 4 Poweredge 2650's with 3 of them dual-Xeons and I've never seen the panics you describe. However, I did have the mail server 2650 just one day act like someone had pulled the plug after running flawlessly for about 3 months. No messages, no anything...just rebooted. I've had it back up for 3 weeks and no further problems. I also had my 2650 fileserver do this while copying the whole file tree, about 66 gigabytes over the network to the 2650 when I was first bringing it up. Since then, no problems. So, the only common thread I can see is maybe disk activity? But...I got no 'panic' messages at all...just 'poof' and it was rebooting like you yanked the power plug. Oh yes, they are on a UPS... and they have dual supplies so that pretty well eliminates power stuff, especially since two of them did it. Do you have 'options HTT' in your kernel. I do not. Someone suggested that they had problems of a similar nature until they added the HTT option. Also, I noticed that I had missed the note on removing i386 and i486 support if you enable SMP. I'm going to try that maybe this weekend. -Jim _______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"