Re: PATA disks/DVD not detected on ATI IXP 700 - cannot boot (dmesg attached)
Jung-uk Kim wrote: This is a known problem and should be fixed in 8.0. Sorry, I haven't had time to back-port the code. Proabably it's good time to consider testing 8.0-RC1. ;-) Hi, Can you look at this? http://butcher.heavennet.ru/patches/kernel/ata/ata-ati-r191568-backport-to-RELENG_7.diff So, it isn't tested (sorry, i don't have any test machines with RELENG_7, only HEAD :) Ted and Dennis can you try it? -- WBR, Andrey V. Elsukov ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Random Network Drops on Realtek Interfaces (re)
> It looks plain RTL8168C PCIe controller. Is there any odd messages > reported by re(4) such as watchdog timeouts? > If you disable MSI feature does it make any difference?(Add > hw.re.msi_disable="1" to /boot/loader.conf to disable MSI.) No watchdog timeouts reported. I'll try the msi_disable option tonight and report back. Thanks, -c ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
em0 watchdog timeouts -- looking for dcgdis.zip
I am having watchdog timeout issues with my Intel 82573 Pro/1000 ... http://lists.freebsd.org/pipermail/freebsd-net/2008-May/018075.html link to dcgdis.zip didn't work. Do you have a copy? Thanks in advance, Rudy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Random Network Drops on Realtek Interfaces (re)
On Tue, Sep 22, 2009 at 05:33:18PM -0600, Cassidy Larson wrote: > Suggestions were: > #1) try "arp -da". This does not fix the issue. I don't see any ARP > for any other IPs other than the local. > #2) speed/duplex settings. I tried forcing 100FD on the box and that > didnt resolve the issue. When I did force 100 full-duplex on the > switch, the box appeared as if it was reporting 100HD. Odd. > Don't do that. It would be normal behavior if link partner's media configuration is autodetect as link partner have to rely on parallel detection. If you have to use forced link, both your NIC and link partner should use the same forced media configuration which is highly discouraged configuration on gigabit links. > > By chace can you find any messages in dmesg reported by re(4)? > > dmesg output related to re(4) would be more helpful as RealTek > > controllers used to show same device ids. > > Here is my dmesg output for the re(4) devices: > re0: PCIe Gigabit Ethernet> port 0xd800-0xd8ff mem > 0xfeaff000-0xfeaf,0xfdef-0xfdef irq 16 at device 0.0 on > pci2 > re0: Using 1 MSI messages > re0: Chip rev. 0x3c00 > re0: MAC rev. 0x0040 > miibus0: on re0 > re0: Ethernet address: 00:30:48:b0:ec:84 > re0: [FILTER] > re1: PCIe Gigabit Ethernet> port 0xe800-0xe8ff mem > 0xfebff000-0xfebf,0xfdff-0xfdff irq 17 at device 0.0 on > pci3 > re1: Using 1 MSI messages > re1: Chip rev. 0x3c00 > re1: MAC rev. 0x0040 > miibus1: on re1 > re1: Ethernet address: 00:30:48:b0:ec:85 > re1: [FILTER] > > Currently, I am not using re1. Only re0 for access. > It looks plain RTL8168C PCIe controller. Is there any odd messages reported by re(4) such as watchdog timeouts? If you disable MSI feature does it make any difference?(Add hw.re.msi_disable="1" to /boot/loader.conf to disable MSI.) > Another side note, I have updated the BIOS to 1.0a from Supermicro as > of yesterday, but that has not fixed this issue. > > Thanks, > > -c ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Random Network Drops on Realtek Interfaces (re)
Suggestions were: #1) try "arp -da". This does not fix the issue. I don't see any ARP for any other IPs other than the local. #2) speed/duplex settings. I tried forcing 100FD on the box and that didnt resolve the issue. When I did force 100 full-duplex on the switch, the box appeared as if it was reporting 100HD. Odd. > By chace can you find any messages in dmesg reported by re(4)? > dmesg output related to re(4) would be more helpful as RealTek > controllers used to show same device ids. Here is my dmesg output for the re(4) devices: re0: port 0xd800-0xd8ff mem 0xfeaff000-0xfeaf,0xfdef-0xfdef irq 16 at device 0.0 on pci2 re0: Using 1 MSI messages re0: Chip rev. 0x3c00 re0: MAC rev. 0x0040 miibus0: on re0 re0: Ethernet address: 00:30:48:b0:ec:84 re0: [FILTER] re1: port 0xe800-0xe8ff mem 0xfebff000-0xfebf,0xfdff-0xfdff irq 17 at device 0.0 on pci3 re1: Using 1 MSI messages re1: Chip rev. 0x3c00 re1: MAC rev. 0x0040 miibus1: on re1 re1: Ethernet address: 00:30:48:b0:ec:85 re1: [FILTER] Currently, I am not using re1. Only re0 for access. Another side note, I have updated the BIOS to 1.0a from Supermicro as of yesterday, but that has not fixed this issue. Thanks, -c ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Random Network Drops on Realtek Interfaces (re)
On Mon, Sep 21, 2009 at 11:25:17PM -0600, Cassidy Larson wrote: > All, > > I've been experiencing an intermittent issue with a drop in networking > connectivity on a couple of boxes. > > At random times I drop connectivity between the servers and their > gateway. I am able to login via the secondary interface and > "/etc/netstart" and everything starts behaving as normal. My switch > shows the link is up, ifconfig shows the link is up, but I am unable > to ping my gateway until running "/etc/netstart". Somedays it'll > happen a few times an hour, some days once every 8-10 hours. It really > is intermittent, and driving me crazy trying to track down the issue. > I've tried different cables, switches, gateways, IPs, and locations. > Memtest for 5 days showed no errors. However, the same problem exists > on two separate installs at different times. I am able to connect to > the one server from the second via their secondary interfaces, so the > problem isn't related to both network interfaces. > > Both servers have the Supermicro X7SLM-L motherboard, same CPU, RAM > and disks. Using the Realtek network driver (re). pciconf shows: > vendor = 'Realtek Semiconductor' > device = 'Gigabit Ethernet NIC(NDIS 6.0) (RTL8168/8111)' > class = network > subclass = ethernet > > I've experienced the problem for some time now on both 7.2-RELEASE and > 7.2-STABLE (09/20/09) using amd64. > > Any help or suggestions would be useful in getting to the bottom of this. > > Thanks, > By chace can you find any messages in dmesg reported by re(4)? dmesg output related to re(4) would be more helpful as RealTek controllers used to show same device ids. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: PATA disks/DVD not detected on ATI IXP 700 - cannot boot (dmesg attached)
On Tue, Sep 22, 2009 at 01:54:42PM +0300, Andriy Gapon wrote: > > Any ideas? I'll be able to run more diagnostics under 8.0 tonight. > > This could be another of GEOM_PART_BSD vs GEOM_BSD issues. > I think this topic has been discussed several times recently on -current. This looks like the problem. Thanks for the pointer. I remembered something like this, but couldn't put my finger on it. Just to make life easier for the next guy the thread with this message (which includes the dd hex that fixes it) seems to cover it. http://docs.freebsd.org/cgi/getmsg.cgi?fetch=774931+0+archive/2009/freebsd-current/20090118.freebsd-current Which looks like the exact right thing for me. I'll follow up when I know for sure, but thanks much for the pointer! -- Ted Faber http://www.isi.edu/~faber PGP: http://www.isi.edu/~faber/pubkeys.asc Unexpected attachment on this mail? See http://www.isi.edu/~faber/FAQ.html#SIG pgptoQEzKQOgc.pgp Description: PGP signature
Re: FreeBSD 7.2-STABLE boot freeze when calibrating clock.
on 22/09/2009 16:48 kama said the following: > > On Tue, 22 Sep 2009, Andriy Gapon wrote: > >> on 22/09/2009 11:35 kama said the following: >>> Ok. >>> >>> I added KDB DDB and ACPI_DEBUG to the kernel and it then boots but with >>> this error: >>> >>> snip >>> Preloaded elf kernel "/boot/kernel/kernel" at 0xc0ed3000. >>> Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0ed31d8. >>> link_elf: symbol AcpiDmDumpMethodInfo undefined >>> KLD file acpi.ko - could not finalize loading >>> Calibrating clock(s) ... i8254 clock: 1193120 Hz >>> CLK_USE_I8254_CALIBRATION not specified - using default frequency >>> Timecounter "i8254" frequency 1193182 Hz quality 0 >>> Calibrating TSC clock ... TSC clock: 2605923359 Hz >>> CPU: AMD Opteron(tm) Processor 285 (2605.92-MHz 686-class CPU) >>> snap >>> >>> What else can I do to help you to figure this out? >> >> This is a very strange error. >> Did you install a binary distribution or did build your kernel from sources? >> >From your demsg I think that it is the latter. >> And I believe that your source tree may be damaged somehow. >> Please try again with a clean checkout from (- this is important -) a known >> good >> place, some cvsup mirrors have been known to serve inconsistent sources. > > I have now changed from cvsup.dk.freebsd.org to cvsup.freebsd.org with no > luck. > > These are the steps I do (and have done for ages): > # cd /usr/src > # make clean cleandir > # cd .. > # rm -rf src/* obj/* > # cd > # csup stable-supfile-7 > # cd /usr/src > # make buildworld > # make buildkernel > # make installkernel > # mergemaster -p > # make installworld > # mergemaster -U -i > # reboot > > I see that there are a newer BIOS on the HP homepage for this DL385. I > will try to update the BIOS later this week. > > The servers are not up to be in production until early november, so there > are some time to test things. > I specifically meant this message: link_elf: symbol AcpiDmDumpMethodInfo undefined $ glimpse AcpiDmDumpMethodInfo /usr/src/sys/contrib/dev/acpica/dmobject.c: * FUNCTION:AcpiDmDumpMethodInfo /usr/src/sys/contrib/dev/acpica/dmobject.c: AcpiDmDumpMethodInfo ( /usr/src/sys/contrib/dev/acpica/dsmethod.c: AcpiDmDumpMethodInfo (Status, WalkState, WalkState->Op); /usr/src/sys/contrib/dev/acpica/acdisasm.h: AcpiDmDumpMethodInfo ( So this function is both defined and used only inside acpi code (vendor part of it). The error you get does not seem to be a run-time condition. It seems to be a system build/install issue (and it looks like the issue is unique to you). I am almost out of guesses, maybe you have stale acpi.ko module in some modules directory. Hmm, one last idea - maybe you have something like "build modules with world" option and also perhaps ACPI_DEBUG is defined somewhere? It could be that something gets out of sync with respect to ACPI_DISASSEMBLER macro. Output of the following command may be useful: $ nm -A /boot/kernel/* | fgrep AcpiDmDumpMethodInfo Could you please try investigating this? Maybe even include acpi into kernel? -- Andriy Gapon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD 7.2-STABLE boot freeze when calibrating clock.
On Tue, 22 Sep 2009, Andriy Gapon wrote: > on 22/09/2009 11:35 kama said the following: > > Ok. > > > > I added KDB DDB and ACPI_DEBUG to the kernel and it then boots but with > > this error: > > > > snip > > Preloaded elf kernel "/boot/kernel/kernel" at 0xc0ed3000. > > Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0ed31d8. > > link_elf: symbol AcpiDmDumpMethodInfo undefined > > KLD file acpi.ko - could not finalize loading > > Calibrating clock(s) ... i8254 clock: 1193120 Hz > > CLK_USE_I8254_CALIBRATION not specified - using default frequency > > Timecounter "i8254" frequency 1193182 Hz quality 0 > > Calibrating TSC clock ... TSC clock: 2605923359 Hz > > CPU: AMD Opteron(tm) Processor 285 (2605.92-MHz 686-class CPU) > > snap > > > > What else can I do to help you to figure this out? > > > This is a very strange error. > Did you install a binary distribution or did build your kernel from sources? > >From your demsg I think that it is the latter. > And I believe that your source tree may be damaged somehow. > Please try again with a clean checkout from (- this is important -) a known > good > place, some cvsup mirrors have been known to serve inconsistent sources. I have now changed from cvsup.dk.freebsd.org to cvsup.freebsd.org with no luck. These are the steps I do (and have done for ages): # cd /usr/src # make clean cleandir # cd .. # rm -rf src/* obj/* # cd # csup stable-supfile-7 # cd /usr/src # make buildworld # make buildkernel # make installkernel # mergemaster -p # make installworld # mergemaster -U -i # reboot I see that there are a newer BIOS on the HP homepage for this DL385. I will try to update the BIOS later this week. The servers are not up to be in production until early november, so there are some time to test things. /Bjorn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Random Network Drops on Realtek Interfaces (re)
On Mon, 2009-09-21 at 23:25 -0600, Cassidy Larson wrote: > All, > > I've been experiencing an intermittent issue with a drop in networking > connectivity on a couple of boxes. > > At random times I drop connectivity between the servers and their > gateway. I am able to login via the secondary interface and > "/etc/netstart" and everything starts behaving as normal. My switch > shows the link is up, ifconfig shows the link is up, but I am unable > to ping my gateway until running "/etc/netstart". Somedays it'll > happen a few times an hour, some days once every 8-10 hours. It really > is intermittent, and driving me crazy trying to track down the issue. > I've tried different cables, switches, gateways, IPs, and locations. > Memtest for 5 days showed no errors. However, the same problem exists > on two separate installs at different times. I am able to connect to > the one server from the second via their secondary interfaces, so the > problem isn't related to both network interfaces. > > Both servers have the Supermicro X7SLM-L motherboard, same CPU, RAM > and disks. Using the Realtek network driver (re). pciconf shows: > vendor = 'Realtek Semiconductor' > device = 'Gigabit Ethernet NIC(NDIS 6.0) (RTL8168/8111)' > class = network > subclass = ethernet > > I've experienced the problem for some time now on both 7.2-RELEASE and > 7.2-STABLE (09/20/09) using amd64. > > Any help or suggestions would be useful in getting to the bottom of this. I do not know how applicable this is in your case, but I have seen such behavior when speed auto-negotiation was allowed on the box connected to the Cisco switch. Condition was usually triggered by the certain volume of traffic (e.g. system could be fine for weeks with SSH/telnet/X11 and lose interface when someone sends large file over FTP or SCP). Restarting the interface, usually fixed it for a while. In my case it was platform-agnostic causing me to have a cheat-sheet on how to disable auto-negotiation on AIX/Solaris/Linux/etc. -- Alexandre Kovalenko (Олександр Коваленко) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: PATA disks/DVD not detected on ATI IXP 700 - cannot boot (dmesg attached)
on 21/09/2009 20:05 Ted Faber said the following: > Thanks for getting back to me. It does seem to be fixed in 8.0-RC1 (and > thanks for that fix, too). That is, 8.0-RC1 finds the drive, but... > > 8.0 (RELENG_8, from last night) doesn't seem to find the FBSD partitions > on the drive. It finds the drive and the BIOS partition (slice). It > fails on my old motherboard (not the one above) that boots 7.2-STABLE > just fine. It drops me into the menu to manually configure the root > partition, but doesn't accept either the native device names for the > root partition (/dev/ad0s1a) or a geom label (/dev/label/root). The > list of GEOM devices only includes ad0 and ad0s1. > > The disk isn't dangerously dedicated, but I only added geom labels to > the partitions last night. The glabels work fine under 7.2-STABLE, but > RELENG_8 seems to ignore them. I've attached output from fdisk, > bsdlabel, and glabel in case I'm misinterpreting them. > > I've been waiting for a free moment to write a more complete report, but > since I've got your attention... > > Any ideas? I'll be able to run more diagnostics under 8.0 tonight. This could be another of GEOM_PART_BSD vs GEOM_BSD issues. I think this topic has been discussed several times recently on -current. -- Andriy Gapon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD 7.2-STABLE boot freeze when calibrating clock.
on 22/09/2009 11:35 kama said the following: > Ok. > > I added KDB DDB and ACPI_DEBUG to the kernel and it then boots but with > this error: > > snip > Preloaded elf kernel "/boot/kernel/kernel" at 0xc0ed3000. > Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0ed31d8. > link_elf: symbol AcpiDmDumpMethodInfo undefined > KLD file acpi.ko - could not finalize loading > Calibrating clock(s) ... i8254 clock: 1193120 Hz > CLK_USE_I8254_CALIBRATION not specified - using default frequency > Timecounter "i8254" frequency 1193182 Hz quality 0 > Calibrating TSC clock ... TSC clock: 2605923359 Hz > CPU: AMD Opteron(tm) Processor 285 (2605.92-MHz 686-class CPU) > snap > > What else can I do to help you to figure this out? This is a very strange error. Did you install a binary distribution or did build your kernel from sources? >From your demsg I think that it is the latter. And I believe that your source tree may be damaged somehow. Please try again with a clean checkout from (- this is important -) a known good place, some cvsup mirrors have been known to serve inconsistent sources. > On Mon, 21 Sep 2009, kama wrote: > >> Hi. >> >> I have recently upgraded the server from 6.X -> Latest 6.X -> 7.2. But >> after the upgrade it boots OK once and after that it freezes. >> >> Verbose boot give me these lines: >> >> snip >> Copyright (c) 1992-2009 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 is a registered trademark of The FreeBSD Foundation. >> FreeBSD 7.2-STABLE #2: Fri Sep 18 13:22:40 CEST 2009 >> r...@gs4:/usr/obj/usr/src/sys/GENERIC >> Preloaded elf kernel "/boot/kernel/kernel" at 0xc0e7e000. >> Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0e7e1d8. >> Calibrating clock(s) ... i8254 clock: 1193116 Hz >> CLK_USE_I8254_CALIBRATION not specified - using default frequency >> Timecounter "i8254" frequency 1193182 Hz quality 0 >> Calibrating TSC clock ... >> snap >> >> I can boot the system without ACPI enabled w/o problem. But once it is >> enabled it will freeze at this point. >> >> This has happend on both servers I have upgraded. Both of them are >> identical. >> >> /Bjorn >> >> Full dmesg w acpi disabled: >> >> %dmesg >> Copyright (c) 1992-2009 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 is a registered trademark of The FreeBSD Foundation. >> FreeBSD 7.2-STABLE #2: Fri Sep 18 13:22:40 CEST 2009 >> r...@gs4:/usr/obj/usr/src/sys/GENERIC >> Timecounter "i8254" frequency 1193182 Hz quality 0 >> CPU: AMD Opteron(tm) Processor 285 (2605.93-MHz 686-class CPU) >> Origin = "AuthenticAMD" Id = 0x20f12 Stepping = 2 >> >> Features=0x178bfbff >> Features2=0x1 >> AMD Features=0xe2500800 >> AMD Features2=0x2 >> Cores per package: 2 >> real memory = 3221192704 (3071 MB) >> avail memory = 3146604544 (3000 MB) >> MPTable: >> FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs >> cpu0 (BSP): APIC ID: 0 >> cpu1 (AP): APIC ID: 1 >> cpu2 (AP): APIC ID: 2 >> cpu3 (AP): APIC ID: 3 >> ioapic0: Assuming intbase of 0 >> ioapic1: Assuming intbase of 24 >> ioapic2: Assuming intbase of 28 >> ioapic3: Assuming intbase of 32 >> ioapic4: Assuming intbase of 36 >> ioapic0 irqs 0-23 on motherboard >> ioapic1 irqs 24-27 on motherboard >> ioapic2 irqs 28-31 on motherboard >> ioapic3 irqs 32-35 on motherboard >> ioapic4 irqs 36-39 on motherboard >> kbd1 at kbdmux0 >> pcib0: pcibus 0 on motherboard >> pci0: on pcib0 >> pcib1: at device 3.0 on pci0 >> pci1: on pcib1 >> ohci0: mem 0xf7df-0xf7df0fff irq 19 at >> device 0.0 on pci1 >> ohci0: [GIANT-LOCKED] >> ohci0: [ITHREAD] >> usb0: OHCI version 1.0, legacy support >> usb0: SMM does not respond, resetting >> usb0: on ohci0 >> usb0: USB revision 1.0 >> uhub0: on usb0 >> uhub0: 3 ports with 3 removable, self powered >> ohci1: mem 0xf7de-0xf7de0fff irq 19 at >> device 0.1 on pci1 >> ohci1: [GIANT-LOCKED] >> ohci1: [ITHREAD] >> usb1: OHCI version 1.0, legacy support >> usb1: SMM does not respond, resetting >> usb1: on ohci1 >> usb1: USB revision 1.0 >> uhub1: on usb1 >> uhub1: 3 ports with 3 removable, self powered >> pci1: at device 2.0 (no driver attached) >> pci1: at device 2.2 (no driver attached) >> vgapci0: port 0x4400-0x44ff mem >> 0xf600-0xf6ff,0xf5ff-0xf5ff0fff at device 3.0 on pci1 >> isab0: at device 4.0 on pci0 >> isa0: on isab0 >> atapci0: port >> 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x2000-0x200f at device 4.1 on pci0 >> ata0: on atapci0 >> ata0: [ITHREAD] >> ata1: on atapci0 >> ata1: [ITHREAD] >> pci0: at device 4.3 (no driver attached) >> pcib2: at device 7.0 on pci0 >> pci2: on pcib2 >> ciss0: port 0x5000-0x50ff mem >> 0xf7ef-0xf7ef1fff,0xf7e8-0xf7eb irq 24 at device 4.0 on pci2 >>
Re: FreeBSD 7.2-STABLE boot freeze when calibrating clock.
Ok. I added KDB DDB and ACPI_DEBUG to the kernel and it then boots but with this error: snip Preloaded elf kernel "/boot/kernel/kernel" at 0xc0ed3000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0ed31d8. link_elf: symbol AcpiDmDumpMethodInfo undefined KLD file acpi.ko - could not finalize loading Calibrating clock(s) ... i8254 clock: 1193120 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 2605923359 Hz CPU: AMD Opteron(tm) Processor 285 (2605.92-MHz 686-class CPU) snap What else can I do to help you to figure this out? /Bjorn On Mon, 21 Sep 2009, kama wrote: > > Hi. > > I have recently upgraded the server from 6.X -> Latest 6.X -> 7.2. But > after the upgrade it boots OK once and after that it freezes. > > Verbose boot give me these lines: > > snip > Copyright (c) 1992-2009 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 is a registered trademark of The FreeBSD Foundation. > FreeBSD 7.2-STABLE #2: Fri Sep 18 13:22:40 CEST 2009 > r...@gs4:/usr/obj/usr/src/sys/GENERIC > Preloaded elf kernel "/boot/kernel/kernel" at 0xc0e7e000. > Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0e7e1d8. > Calibrating clock(s) ... i8254 clock: 1193116 Hz > CLK_USE_I8254_CALIBRATION not specified - using default frequency > Timecounter "i8254" frequency 1193182 Hz quality 0 > Calibrating TSC clock ... > snap > > I can boot the system without ACPI enabled w/o problem. But once it is > enabled it will freeze at this point. > > This has happend on both servers I have upgraded. Both of them are > identical. > > /Bjorn > > Full dmesg w acpi disabled: > > %dmesg > Copyright (c) 1992-2009 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 is a registered trademark of The FreeBSD Foundation. > FreeBSD 7.2-STABLE #2: Fri Sep 18 13:22:40 CEST 2009 > r...@gs4:/usr/obj/usr/src/sys/GENERIC > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: AMD Opteron(tm) Processor 285 (2605.93-MHz 686-class CPU) > Origin = "AuthenticAMD" Id = 0x20f12 Stepping = 2 > > Features=0x178bfbff > Features2=0x1 > AMD Features=0xe2500800 > AMD Features2=0x2 > Cores per package: 2 > real memory = 3221192704 (3071 MB) > avail memory = 3146604544 (3000 MB) > MPTable: > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > cpu2 (AP): APIC ID: 2 > cpu3 (AP): APIC ID: 3 > ioapic0: Assuming intbase of 0 > ioapic1: Assuming intbase of 24 > ioapic2: Assuming intbase of 28 > ioapic3: Assuming intbase of 32 > ioapic4: Assuming intbase of 36 > ioapic0 irqs 0-23 on motherboard > ioapic1 irqs 24-27 on motherboard > ioapic2 irqs 28-31 on motherboard > ioapic3 irqs 32-35 on motherboard > ioapic4 irqs 36-39 on motherboard > kbd1 at kbdmux0 > pcib0: pcibus 0 on motherboard > pci0: on pcib0 > pcib1: at device 3.0 on pci0 > pci1: on pcib1 > ohci0: mem 0xf7df-0xf7df0fff irq 19 at > device 0.0 on pci1 > ohci0: [GIANT-LOCKED] > ohci0: [ITHREAD] > usb0: OHCI version 1.0, legacy support > usb0: SMM does not respond, resetting > usb0: on ohci0 > usb0: USB revision 1.0 > uhub0: on usb0 > uhub0: 3 ports with 3 removable, self powered > ohci1: mem 0xf7de-0xf7de0fff irq 19 at > device 0.1 on pci1 > ohci1: [GIANT-LOCKED] > ohci1: [ITHREAD] > usb1: OHCI version 1.0, legacy support > usb1: SMM does not respond, resetting > usb1: on ohci1 > usb1: USB revision 1.0 > uhub1: on usb1 > uhub1: 3 ports with 3 removable, self powered > pci1: at device 2.0 (no driver attached) > pci1: at device 2.2 (no driver attached) > vgapci0: port 0x4400-0x44ff mem > 0xf600-0xf6ff,0xf5ff-0xf5ff0fff at device 3.0 on pci1 > isab0: at device 4.0 on pci0 > isa0: on isab0 > atapci0: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x2000-0x200f at device 4.1 on pci0 > ata0: on atapci0 > ata0: [ITHREAD] > ata1: on atapci0 > ata1: [ITHREAD] > pci0: at device 4.3 (no driver attached) > pcib2: at device 7.0 on pci0 > pci2: on pcib2 > ciss0: port 0x5000-0x50ff mem > 0xf7ef-0xf7ef1fff,0xf7e8-0xf7eb irq 24 at device 4.0 on pci2 > ciss0: [ITHREAD] > pcib3: at device 8.0 on pci0 > pci3: on pcib3 > bge0: mem > 0xf7ff-0xf7ff irq 28 at device 6.0 on pci3 > miibus0: on bge0 > brgphy0: PHY 1 on miibus0 > brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > 1000baseT-FDX, auto > bge0: Ethernet address: 00:17:a4:8d:f9:2a > bge0: [ITHREAD] > bge1: mem > 0xf7fe-0xf7fe irq 29 at device 6.1 on pci3 > miibus1: on bge1 > brgphy1: PHY 1 on miibus1 > brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > 1000baseT-FDX, auto > bge1: E
Re: Random Network Drops on Realtek Interfaces (re)
On 22 Sep 2009, at 06:25, Cassidy Larson wrote: I've been experiencing an intermittent issue with a drop in networking connectivity on a couple of boxes. At random times I drop connectivity between the servers and their gateway. I am able to login via the secondary interface and "/etc/netstart" and everything starts behaving as normal. My switch shows the link is up, ifconfig shows the link is up, but I am unable to ping my gateway until running "/etc/netstart". Can you see if "arp -da" is sufficient to get the server online? Thanks, Gavin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
