From owner-freebsd-questions Mon Dec 4 1:25:24 2000 From owner-freebsd-questions@FreeBSD.ORG Mon Dec 4 01:25:20 2000 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from guru.mired.org (okc-65-26-235-186.mmcable.com [65.26.235.186]) by hub.freebsd.org (Postfix) with SMTP id E52A237B400 for ; Mon, 4 Dec 2000 01:25:19 -0800 (PST) Received: (qmail 20369 invoked by uid 100); 4 Dec 2000 09:25:19 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14891.25343.457420.274254@guru.mired.org> Date: Mon, 4 Dec 2000 03:25:19 -0600 (CST) To: "Simon" Cc: questions@freebsd.org Subject: Re: /kernel: fxp0: device timeout In-Reply-To: <111845983@toto.iv> X-Mailer: VM 6.75 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ X-Message: You should get a better mailer. Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Simon types: > Hi all: > > I'm trying to find out what's up with my remotely colocated box. I had it running fine for 4 days after RAM upgrade and all of a sudden it stopped responding. After Please put in newlines every 70 or so characters, not every 170 or so. > reboot, which fixed the problem, I noticed /kernel: fxp0: device timeout in the syslog file repeated until the reboot. This has never happened before with this box. I > had it virtually freeze 2 times while swapping (swap can't handle the load), so I added 512MB of RAM and now this.. Any ideas what can be wrong besides bad > cable/NIC? Is there a way I can do something to see if it stops responding again without having to wait for it to do it on its own? remotely that is. Can attacks (flood, My guess would be that the new RAM is bad. Pulling it to check would be a good idea. > etc...) of some sort cause things like this to happen? or is this purely hardware issue? I read almost all the posts I could find regarding the same issue in the archives, > but couldn't find what I was looking for. My plan is to have the ethernet cable changed and then the NIC. Now, what I'm afraid of is what if that doesn't fix the > problem. Then again, maybe it will never happen again, but since it did once, I'm close to sure it will. Any help and or suggestions would be appreacited. Thank you! This is almost certainly hardware - the system isn't getting the interrupts from the device for some reason. I'd pull the new RAM before trying anything else. Simon > > I'm running 4.1-R > > fxp0: flags=8843 mtu 1500 > inet x.x.x.x netmask 0xffffffc0 broadcast x.x.x.x > ether 00:d0:b7:21:ad:59 > media: autoselect (100baseTX ) status: active > supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP > > Dec 3 03:04:23 anaconda /kernel: Timecounter "i8254" frequency 1193182 Hz > Dec 3 03:04:23 anaconda /kernel: CPU: Pentium III/Pentium III Xeon/Celeron (598.40-MHz 686-class CPU) > Dec 3 03:04:23 anaconda /kernel: Origin = "GenuineIntel" Id = 0x681 Stepping = 1 > Dec 3 03:04:24 anaconda /kernel: Features= > 0x387fbff > Dec 3 03:04:24 anaconda /kernel: real memory = 1073676288 (1048512K bytes) > Dec 3 03:04:24 anaconda /kernel: config> di bt0 > Dec 3 03:04:24 anaconda /kernel: config> di aic0 > Dec 3 03:04:24 anaconda /kernel: config> di aha0 > Dec 3 03:04:24 anaconda /kernel: config> di adv0 > Dec 3 03:04:24 anaconda /kernel: config> en ata1 > Dec 3 03:04:24 anaconda /kernel: config> po ata1 0x170 > Dec 3 03:04:24 anaconda /kernel: config> ir ata1 15 > Dec 3 03:04:24 anaconda /kernel: config> f ata1 0 > Dec 3 03:04:24 anaconda /kernel: config> en ata0 > Dec 3 03:04:24 anaconda /kernel: config> po ata0 0x1f0 > Dec 3 03:04:24 anaconda /kernel: config> ir ata0 14 > Dec 3 03:04:24 anaconda /kernel: config> f ata0 0 > Dec 3 03:04:24 anaconda /kernel: config> q > Dec 3 03:04:24 anaconda /kernel: avail memory = 1041330176 (1016924K bytes) > Dec 3 03:04:24 anaconda /kernel: Programming 24 pins in IOAPIC #0 > Dec 3 03:04:24 anaconda /kernel: IOAPIC #0 intpin 2 -> irq 0 > Dec 3 03:04:24 anaconda /kernel: FreeBSD/SMP: Multiprocessor motherboard > Dec 3 03:04:24 anaconda /kernel: cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 > Dec 3 03:04:24 anaconda /kernel: cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 > Dec 3 03:04:24 anaconda /kernel: io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 > Dec 3 03:04:24 anaconda /kernel: Preloaded elf kernel "kernel" at 0xc02b1000. > Dec 3 03:04:24 anaconda /kernel: Preloaded userconfig_script "/boot/kernel.conf" at 0xc02b109c. > Dec 3 03:04:24 anaconda /kernel: Pentium Pro MTRR support enabled > Dec 3 03:04:24 anaconda /kernel: md0: Malloc disk > Dec 3 03:04:24 anaconda /kernel: npx0: on motherboard > Dec 3 03:04:24 anaconda /kernel: npx0: INT 16 interface > Dec 3 03:04:24 anaconda /kernel: pcib0: on motherboard > Dec 3 03:04:24 anaconda /kernel: pci0: on pcib0 > Dec 3 03:04:24 anaconda /kernel: pcib1: at device 1.0 on pci0 > Dec 3 03:04:24 anaconda /kernel: pci1: on pcib1 > Dec 3 03:04:24 anaconda /kernel: pci1: at 0.0 irq 16 > Dec 3 03:04:24 anaconda /kernel: isab0: at device 7.0 on pci0 > Dec 3 03:04:24 anaconda /kernel: isa0: on isab0 > Dec 3 03:04:24 anaconda /kernel: atapci0: port 0xf000-0xf00f at device 7.1 on pci0 > Dec 3 03:04:24 anaconda /kernel: ata0: at 0x1f0 irq 14 on atapci0 > Dec 3 03:04:24 anaconda /kernel: pci0: at 7.2 irq 10 > Dec 3 03:04:24 anaconda /kernel: Timecounter "PIIX" frequency 3579545 Hz > Dec 3 03:04:24 anaconda /kernel: chip1: port 0x5000-0x500f at device 7.3 on pci0 > Dec 3 03:04:25 anaconda /kernel: fxp0: port 0xe400-0xe43f mem 0xe8000000-0xe80fffff,0xe8101000-0xe8101fff irq 17 at > device 9.0 on pci0 > Dec 3 03:04:25 anaconda /kernel: fxp0: Ethernet address 00:d0:b7:21:ad:59 > Dec 3 03:04:25 anaconda /kernel: ahc0: port 0xe800-0xe8ff mem 0xe8100000-0xe8100fff irq 19 at device 11.0 on pci0 > Dec 3 03:04:25 anaconda /kernel: ahc0: aic7892 Wide Channel A, SCSI Id=7, 16/255 SCBs > Dec 3 03:04:25 anaconda /kernel: fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 > Dec 3 03:04:25 anaconda /kernel: fdc0: FIFO enabled, 8 bytes threshold > Dec 3 03:04:25 anaconda /kernel: fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > Dec 3 03:04:25 anaconda /kernel: atkbdc0: at port 0x60,0x64 on isa0 > Dec 3 03:04:25 anaconda /kernel: atkbd0: irq 1 on atkbdc0 > Dec 3 03:04:25 anaconda /kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > Dec 3 03:04:25 anaconda /kernel: sc0: on isa0 > Dec 3 03:04:25 anaconda /kernel: sc0: VGA <16 virtual consoles, flags=0x200> > Dec 3 03:04:25 anaconda /kernel: APIC_IO: Testing 8254 interrupt delivery > Dec 3 03:04:25 anaconda /kernel: APIC_IO: routing 8254 via IOAPIC #0 intpin 2 > Dec 3 03:04:25 anaconda /kernel: IP packet filtering initialized, divert disabled, rule-based forwarding disabled, default to accept, logging limited to 50 > packets/entry by default > Dec 3 03:04:25 anaconda /kernel: SMP: AP CPU #1 Launched! > Dec 3 03:04:25 anaconda /kernel: ad0: 39082MB [79406/16/63] at ata0-master using UDMA33 > Dec 3 03:04:25 anaconda /kernel: Waiting 5 seconds for SCSI devices to settle > Dec 3 03:04:25 anaconda /kernel: Mounting root from ufs:/dev/da0s1a > Dec 3 03:04:25 anaconda /kernel: da0 at ahc0 bus 0 target 0 lun 0 > Dec 3 03:04:25 anaconda /kernel: da0: Fixed Direct Access SCSI-3 device > Dec 3 03:04:25 anaconda /kernel: da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled > Dec 3 03:04:25 anaconda /kernel: da0: 8761MB (17942584 512 byte sectors: 255H 63S/T 1116C) > Dec 3 03:04:25 anaconda /kernel: da1 at ahc0 bus 0 target 1 lun 0 > Dec 3 03:04:25 anaconda /kernel: da1: Fixed Direct Access SCSI-3 device > Dec 3 03:04:25 anaconda /kernel: da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > -- Mike Meyer http://www.mired.org/home/mwm/ Independent WWW/Unix/FreeBSD consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message