Networking issue in 4.9-Stable (was: Diagnosing hardware issue?)
Marius M. Rex MARIUS
marius at mail.communityconnect.com
Thu Apr 22 15:27:52 PDT 2004
Thanks for your suggestions.
Switching the CPUs has made a lot of difference. Now both CPUs show up to
the OS and are usable. If one CPU works is both sockets, and the other
only works in one socket, I think it is safe to say that I have a bad CPU
unit, and the motherboard is likely O.K. I hope that is what it means, as
the CPU is much cheaper/easier to replace.
The Extended table output from 'mptable' is still listed at 'HOSED'. I
imagine you are right that I should not worry about it for now.
But the question still remains as to why my networking is non-functional.
I am using cards I believe to be good. (One that was working on the
machine just before I did a rebuild to STABLE.) I am using cables I know
to be good. I have link lights, and the OS sees the connected cable and
autoselects the correct media type. The source tree it was built under
works on my laptop with networking just fine. But every time I try to
work with networking, I simply get this:
fxp0: device timeout
fxp0: device timeout
fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255
ether 00:90:27:8a:80:53
media: Ethernet autoselect (10baseT/UTP)
status: active
I am using DHCP in this example, but it does not matter if I set the IP by
hand. The device times out just the same. The other Ethernet card (dc0),
with a different cable, but it too just times out. Normally in this
occasion I would just cvsup again and see if a new buildworld made a
difference.
Well, I will replace the bad CPU and try a rebuild I guess. Perhaps that
will bring some resolution. If anyone can suggest something I can check
in the meantime I would appreciate it. I have not had this trouble in the
past.
-Marius M. Rex
marius at mail.communityconnect.com
On Wed, 21 Apr 2004, Randy Rowe wrote:
> On Tue, 2004-04-20 at 11:17, Marius M. Rex MARIUS wrote:
> > I recently inherited a dual processor x86 machine for my personal use. It
> > was supposed to be in fine working condition as a MS-Windows machine, but upon
> > installing FreeBSD, I have encountered a number of problems I have no
> > doubt that the hardware is the issue, and not FreeBSD.
> >
> > I did a minimal install over the network of 4.7-Release which seemed to go
> > smoothly. I then tarred up my a 4.9 stable source tree from another
> > machine and transfered it over to the new box. (from March 30th) Build
> > world seemed to go fine. (make buildworld) I tweaked the GENERIC kernel to add support for
> > the second processor and a sound card. I made and installed the new
> > kernel without any noticeable errors. (make builkernel KERNCONF=STONE ;
> > make installkernel KERNCONF=STONE) The new kernel booted, but the
> > second processor was not recognized. Likewise, my network cards became
> > unresponsive. (the interfaces would just time out) I now have the machine
> > in serial console, and am wondering how I figure out what is wrong with the
> > machine. I assume it is a hardware issue, but as to what is precisely broken,
> > I do not know. For completeness sake I did the installworld and ran
> > mergmaster, but I am still running on only one processor and no
> > networking.
> >
> > Can anyone give me some pointers on how to start troubleshooting this?
> > The source tree I used seems to work fine on my laptop, so I have doubt
> > that it is a terrible problem on the other machine.
> >
> > Here is some basic info to give a little background:
> >
> >
> > ######################################
> > stone# uname -a
> > FreeBSD stone.ny.home 4.9-STABLE FreeBSD 4.9-STABLE #1: Mon Apr 19
> > 21:42:50 EDT6
> >
> > 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-STABLE #1: Mon Apr 19 21:42:50 EDT 2004
> > root at stone.ny.home:/usr/obj/usr/src/sys/STONE
> > Timecounter "i8254" frequency 1193182 Hz
> > CPU: Pentium II/Pentium II Xeon/Celeron (400.91-MHz 686-class CPU)
> > Origin = "GenuineIntel" Id = 0x652 Stepping = 2
> >
> > Features=0x183fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CM
> > OV,PAT,PSE36,MMX,FXSR>
> > real memory = 134152192 (131008K bytes)
> > avail memory = 126550016 (123584K bytes)
> > Programming 24 pins in IOAPIC #0
> > IOAPIC #0 intpin 2 -> irq 0
> > IOAPIC #0 intpin 16 -> irq 10
> > IOAPIC #0 intpin 17 -> irq 11
> > FreeBSD/SMP: Multiprocessor motherboard: 1 CPUs
> > cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000
> > io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000
> > Preloaded elf kernel "kernel" at 0xc03f1000.
> > Pentium Pro MTRR support enabled
> > md0: Malloc disk
> > npx0: <math processor> on motherboard
> > npx0: INT 16 interface
> > pcib0: <Intel 82443BX (440 BX) host to PCI bridge> on motherboard
> > pci0: <PCI bus> on pcib0
> > agp0: <Intel 82443BX (440 BX) host to PCI bridge> mem
> > 0xf8000000-0xfbffffff at d
> > evice 0.0 on pci0
> > pcib1: <Intel 82443BX (440 BX) PCI-PCI (AGP) bridge> at device 1.0 on pci0
> > pci1: <PCI bus> on pcib1
> > pci1: <ATI Mach64-GB graphics accelerator> at 0.0 irq 11
> > isab0: <Intel 82371AB PCI to ISA bridge> at device 7.0 on pci0
> > isa0: <ISA bus> on isab0
> > atapci0: <Intel PIIX4 ATA33 controller> port 0xffa0-0xffaf at device 7.1
> > on pci0
> > ata0: at 0x1f0 irq 14 on atapci0
> > ata1: at 0x170 irq 15 on atapci0
> > uhci0: <Intel 82371AB/EB (PIIX4) USB controller> port 0xef80-0xef9f irq 11
> > at device 7.2 on pci0
> > usb0: <Intel 82371AB/EB (PIIX4) USB controller> on uhci0
> > usb0: USB revision 1.0
> > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
> > uhub0: 2 ports with 2 removable, self powered
> > Timecounter "PIIX" frequency 3579545 Hz
> > chip0: <Intel 82371AB Power management controller> port 0x440-0x44f at
> > device 7.3 on pci0
> > ahc0: <Adaptec 2940 Ultra SCSI adapter> port 0xe800-0xe8ff mem
> > 0xfebff000-0xfebfffff irq 10 at device 15.0 on pci0
> > aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs
> > fxp0: <Intel 82559 Pro/100 Ethernet> port 0xef00-0xef3f mem
> > 0xfea00000-0xfeaffff
> > f,0xfebfe000-0xfebfefff irq 11 at device 18.0 on pci0
> > fxp0: Ethernet address 00:90:27:8a:80:53
> > inphy0: <i82555 10/100 media interface> on miibus0
> > inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> > dc0: <82c169 PNIC 10/100BaseTX> port 0xe400-0xe4ff mem
> > 0xfebfdf00-0xfebfdfff irq
> > 11 at device 20.0 on pci0
> > dc0: Ethernet address: 00:a0:cc:65:b8:e7
> > miibus1: <MII bus> on dc0
> > ukphy0: <Generic IEEE 802.3u media interface> on miibus1
> > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> > orm0: <Option ROMs> at iomem
> > 0xc0000-0xc7fff,0xc8000-0xcc7ff,0xcc800-0xcd7ff 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
> > atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
> > atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
> > kbd0 at atkbd0
> > 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=0x100>
> > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
> > sio0: type 16550A, console
> > sio1 at port 0x2f8-0x2ff irq 3 on isa0
> > sio1: type 16550A
> > ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
> > ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
> > plip0: <PLIP network interface> on ppbus0
> > lpt0: <Printer> on ppbus0
> > lpt0: Interrupt-driven port
> > ppi0: <Parallel I/O> on ppbus0
> > pcm0: <Yamaha OPL-SAx> at port
> > 0x220-0x22f,0x530-0x537,0x388-0x38b,0x330-0x331,0
> > x370-0x371 irq 5 drq 0,1 on isa0
> > APIC_IO: Testing 8254 interrupt delivery
> > APIC_IO: routing 8254 via IOAPIC #0 intpin 2
> > ad0: 8063MB <WDC AC28400R> [16383/16/63] at ata0-master UDMA33
> > Waiting 15 seconds for SCSI devices to settle
> > Mounting root from ufs:/dev/da0s1a
> > da1 at ahc0 bus 0 target 1 lun 0
> > da1: <SEAGATE ST39103LW 0002> Fixed Direct Access SCSI-2 device
> > da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing
> > Enabled
> > da1: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C)
> > da0 at ahc0 bus 0 target 0 lun 0
> > da0: <SEAGATE ST39204LW 0002> Fixed Direct Access SCSI-3 device
> > da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing
> > Enabled
> > da0: 8750MB (17921835 512 byte sectors: 255H 63S/T 1115C)
> > cd0 at ahc0 bus 0 target 6 lun 0
> > cd0: <TOSHIBA CD-ROM XM-6401TA 1009> Removable CD-ROM SCSI-2 device
> > cd0: 20.000MB/s transfers (20.000MHz, offset 15)
> > cd0: Attempt to query device size failed: NOT READY, Medium not present
> >
> > stone# mptable
> > ===============================================================================
> >
> > MPTable, version 2.0.15
> >
> > -------------------------------------------------------------------------------
> >
> > MP Floating Pointer Structure:
> >
> > location: BIOS
> > physical address: 0x000fb4f0
> > signature: '_MP_'
> > length: 16 bytes
> > version: 1.4
> > checksum: 0x0d
> > mode: Virtual Wire
> >
> > -------------------------------------------------------------------------------
> >
> > MP Config Table Header:
> >
> > physical address: 0x000f2460
> > signature: 'PCMP'
> > base table length: 264
> > version: 1.4
> > checksum: 0x48
> > OEM ID: 'INTEL '
> > Product ID: '440BX '
> > OEM table pointer: 0x00000000
> > OEM table size: 0
> > entry count: 26
> > local APIC address: 0xfee00000
> > extended table length: 16
> > extended table checksum: 234
> >
> > -------------------------------------------------------------------------------
> >
> > MP Config Base Table Entries:
> >
> > --
> > Processors: APIC ID Version State Family Model Step
> > Flags
> > 0 0x11 BSP, usable 6 5 2
> > 0x183fb
> > ff
> > --
> > Bus: Bus ID Type
> > 0 PCI
> > 1 PCI
> > 2 ISA
> > --
> > I/O APICs: APIC ID Version State Address
> > 2 0x11 usable 0xfec00000
> > --
> > I/O Ints: Type Polarity Trigger Bus ID IRQ APIC ID
> > PIN#
> > ExtINT conforms conforms 2 0 2
> > 0
> > INT conforms conforms 2 1 2
> > 1
> > INT conforms conforms 2 0 2
> > 2
> > INT conforms conforms 2 3 2
> > 3
> > INT conforms conforms 2 4 2
> > 4
> > INT conforms conforms 2 5 2
> > 5
> > INT conforms conforms 2 6 2
> > 6
> > INT conforms conforms 2 7 2
> > 7
> > INT active-hi edge 2 8 2
> > 8
> > INT conforms conforms 2 9 2
> > 9
> > INT conforms conforms 2 12 2
> > 12
> > INT conforms conforms 2 13 2
> > 13
> > INT conforms conforms 2 14 2
> > 14
> > INT conforms conforms 2 15 2
> > 15
> > INT active-lo level 2 10 2
> > 16
> > INT active-lo level 2 11 2
> > 17
> > INT active-lo level 2 11 2
> > 18
> > INT active-lo level 2 11 2
> > 19
> > SMI conforms conforms 2 0 2
> > 23
> > --
> > Local Ints: Type Polarity Trigger Bus ID IRQ APIC ID
> > PIN#
> > ExtINT conforms conforms 0 0:A 255
> > 0
> > NMI conforms conforms 0 0:A 255
> > 1
> >
> > -------------------------------------------------------------------------------
> >
> > MP Config Extended Table Entries:
> >
> > Extended Table HOSED!
> >
> >
> > ####################################
> >
> > And yes, I imagine that 'Extended Table HOSED!' is NOT a good sign.
> >
> >
> > -Marius M. Rex
> > marius at mail.communityconnect.com
> >
> > _______________________________________________
> > freebsd-stable at freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> > To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"
>
> Try swapping the micros. Then try swapping the VRU (or whatever they're
> calling it for that particular motherboard :-) , the voltage regulator
> unit or power module).
>
> During the initial boot up when you have a few seconds, hit a key and
> then type "boot -v" to get verbose boot information.
>
> If 4.7 worked and you can return to 4.7, write a dmesg of a boot -v to
> disk, update to 4.9 and then do a diff between the 2 dmesg's for a hint
> on what happened to the interface. Installing from a cd is the best bet.
> Or for that matter use the 2nd iso in the set to boot to a cd and get a
> dmesg from fixit mode.
>
> Extended table hosed isn't necessarily a bad thing. From what I've seen
> in the lists (and on my Compaq servers) it's a motherboard issue that
> won't stop it from running multiple processors. You just need to figure
> out why it only recognizes the one micro.
>
> Good luck.
> Randy
>
>
More information about the freebsd-stable
mailing list