Re: FreeBSD 7.2-STABLE boot freeze
On Fri, 2 Oct 2009, kama wrote: Do you get this message in all cases? That is, every time you tried? Or only with ACPI_DEBUG defined? I cant recall. I have tried so many things lately. But I believe I get it on a verbose boot without ACPI_DEBUG. Im currently rebuilding the system to 8.0. Just upgrading to 8.0 did not help regarding the freezes. I ran into the bge freeze bug too when disabling acpi. I then read the acpi-manpage abit more carefully. With ACPI_DEBUG and debug.acpi.disabled=timer in loader.conf and verbose boot seems to help against the freeze and freezes again if I dont run it in verbose mode. But thats just after 5 starts. Anyhow its better. loader.conf: debug.acpi.disabled=timer debug.acpi.layer=ACPI_ALL_COMPONENTS debug.acpi.level=ACPI_LV_VERBOSE,ACPI_LV_VERBOSITY3,ACPI_LV_VERBOSITY1,ACPI_LV_ALL_EXCEPTIONS I just wanted to bump this. After the checkout yesterday and installation today I still get these freezes. # cat /boot/loader.conf hw.bge.allow_asf=0 hw.acpi.verbose=1 debug.acpi.max_threads=1 debug.acpi.disabled=timer debug.acpi.layer=ACPI_ALL_COMPONENTS debug.acpi.level=ACPI_LV_VERBOSE,ACPI_LV_VERBOSITY3,ACPI_LV_VERBOSITY1,ACPI_LV_ALL_EXCEPTIONS # With this setup and with an GENERIC kernel I am able to boot if I choose a verbose boot. I dont know why it should work with these. If I only use debug.acpi.disabled=timer it will freeze. Is there anyway for me to get more info when it exactly freezes. Like having it print out to the screen when it enters and leaves functions or something. Im not to familiar with where to put these and its quite a large project for me to start to understand where everything goes. If someone wants to give me patches or specify which files to alter and how I print to the screen during boot I might be able to pinpoint where it freezes and mail in the results. /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: FreeBSD 7.2-STABLE boot freeze
On Wed, 30 Sep 2009, Andriy Gapon wrote: on 30/09/2009 16:21 kama said the following: It boot occationally. It does not seem to matter if I include the acpi device into the kernel or not. I get this message in an verbose boot: KLD file acpi.ko - could not finalize loading Do you get this message in all cases? That is, every time you tried? Or only with ACPI_DEBUG defined? I cant recall. I have tried so many things lately. But I believe I get it on a verbose boot without ACPI_DEBUG. Im currently rebuilding the system to 8.0. /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: FreeBSD 7.2-STABLE boot freeze
On Fri, 2 Oct 2009, kama wrote: On Wed, 30 Sep 2009, Andriy Gapon wrote: on 30/09/2009 16:21 kama said the following: It boot occationally. It does not seem to matter if I include the acpi device into the kernel or not. I get this message in an verbose boot: KLD file acpi.ko - could not finalize loading Do you get this message in all cases? That is, every time you tried? Or only with ACPI_DEBUG defined? I cant recall. I have tried so many things lately. But I believe I get it on a verbose boot without ACPI_DEBUG. Im currently rebuilding the system to 8.0. Just upgrading to 8.0 did not help regarding the freezes. I ran into the bge freeze bug too when disabling acpi. I then read the acpi-manpage abit more carefully. With ACPI_DEBUG and debug.acpi.disabled=timer in loader.conf and verbose boot seems to help against the freeze and freezes again if I dont run it in verbose mode. But thats just after 5 starts. Anyhow its better. loader.conf: debug.acpi.disabled=timer debug.acpi.layer=ACPI_ALL_COMPONENTS debug.acpi.level=ACPI_LV_VERBOSE,ACPI_LV_VERBOSITY3,ACPI_LV_VERBOSITY1,ACPI_LV_ALL_EXCEPTIONS I dont know if the output below gives anything. /Bjorn # dmesg | grep -i acpi ACPI set debug layer 'ACPI_ALL_COMPONENTS' level 'ACPI_LV_VERBOSE,ACPI_LV_VERBOSITY3,ACPI_LV_VERBOSITY1,ACPI_LV_ALL_EXCEPTIONS' MADT: Found CPU APIC ID 0 ACPI ID 0: enabled MADT: Found CPU APIC ID 2 ACPI ID 2: enabled MADT: Found CPU APIC ID 4 ACPI ID 4: disabled MADT: Found CPU APIC ID 6 ACPI ID 6: disabled MADT: Found CPU APIC ID 1 ACPI ID 1: enabled MADT: Found CPU APIC ID 3 ACPI ID 3: enabled MADT: Found CPU APIC ID 5 ACPI ID 5: disabled MADT: Found CPU APIC ID 7 ACPI ID 7: disabled ACPI APIC Table: HP 0083 APIC: CPU 0 has ACPI ID 0 APIC: CPU 1 has ACPI ID 1 APIC: CPU 2 has ACPI ID 2 APIC: CPU 3 has ACPI ID 3 ACPI: RSDP 0xf4f20 00024 (v2 HP) ACPI: XSDT 0xbfff83e0 00044 (v1 HP A05 0002 \M-R\^D 162E) ACPI: FACP 0xbfff8460 000F4 (v3 HP A05 0002 \M-R\^D 162E) ACPI Warning: Invalid length for Pm1aControlBlock: 32, using default 16 20090521 tbfadt-707 ACPI Warning: Invalid length for Pm1bControlBlock: 32, using default 16 20090521 tbfadt-707 ACPI: DSDT 0xbfff8560 0422D (v1 HP DSDT 0001 MSFT 0201) ACPI: FACS 0xbfff80c0 00040 ACPI: APIC 0xbfff8100 000B8 (v1 HP 0083 0002 ) ACPI: SPCR 0xbfff81e0 00050 (v1 HP SPCRRBSU 0001 \M-R\^D 162E) ACPI: SRAT 0xbfff8260 00150 (v1 HP A05 0001 ) acpi0: HP A05 on motherboard acpi0: [MPSAFE] acpi0: [ITHREAD] ACPI: SSDT 0xbfffd000 0059D (v1 HPSSDT0 0001 MSFT 0201) ACPI: SSDT 0xbfffd700 0059D (v1 HPSSDT1 0001 MSFT 0201) ACPI: SSDT 0xbfffde00 0059D (v1 HPSSDT2 0001 MSFT 0201) ACPI: SSDT 0xbfffe500 0059D (v1 HPSSDT3 0001 MSFT 0201) acpi0: Power Button (fixed) acpi0: wakeup code va 0xc62cd000 pa 0x1000 AcpiOsDerivePciId: \\_SB_.CFG0.NDE0.NDE0 - bus 0 dev 24 func 0 AcpiOsDerivePciId: \\_SB_.CFG0.MEMC.MEMC - bus 0 dev 24 func 1 AcpiOsDerivePciId: \\_SB_.CFG0.PCI0.PCI0 - bus 0 dev 3 func 0 AcpiOsDerivePciId: \\_SB_.CFG0.IBRG.IBRG - bus 0 dev 4 func 0 AcpiOsDerivePciId: \\_SB_.CFG0.PCI1.PCI1 - bus 0 dev 7 func 0 AcpiOsDerivePciId: \\_SB_.CFG0.PCI2.PCI2 - bus 0 dev 8 func 0 AcpiOsDerivePciId: \\_SB_.CFG1.PCI3.PCI3 - bus 4 dev 9 func 0 AcpiOsDerivePciId: \\_SB_.CFG1.PCI4.PCI4 - bus 4 dev 10 func 0 AcpiOsDerivePciId: \\_SB_.CFG0.TSMM.TSMM - bus 0 dev 4 func 3 pcib0: ACPI Host-PCI bridge on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge at device 3.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge at device 7.0 on pci0 pci2: ACPI PCI bus on pcib2 pcib3: ACPI PCI-PCI bridge at device 8.0 on pci0 pci3: ACPI PCI bus on pcib3 pcib4: ACPI Host-PCI bridge on acpi0 pci4: ACPI PCI bus on pcib4 pcib5: ACPI PCI-PCI bridge at device 9.0 on pci4 pci5: ACPI PCI bus on pcib5 pcib6: ACPI PCI-PCI bridge at device 10.0 on pci4 pci6: ACPI PCI bus on pcib6 atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0 psmcpnp0: PS/2 mouse port irq 12 on acpi0 uart0: 16550 or compatible port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 fdc0: floppy drive controller (FDE) port 0x3f2-0x3f5 irq 6 drq 2 on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 cpu2: ACPI CPU on acpi0 cpu3: ACPI CPU on acpi0 ___ 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
on 29/09/2009 21:50 kama said the following: On Tue, 29 Sep 2009, Andriy Gapon wrote: Serial console and remote debugging perhaps? ILO is serial console or rather console++, since you can even see the whole bootup sequence, change bios. But thats if you connect through their webinterface Just point me what other options I could try to get a proper dump or bt. Perhaps you could still use the following: http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-online-gdb.html Otherwise, no ideas. Anyway, I'll try to see if I can reproduce undefined symbol issue here. Not that it would matter much for resolution of your main problem (freeze). Honestly, I have no clue about it. Ok. Hopefully someone else knows what can produce these freezes. BTW, remembering something you said earlier - does including acpi device into kernel still work for you? I.e. can you boot normally with that? Also, can you try 8 on that machine? Just for the sake of experiment? -- 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
On Wed, 30 Sep 2009, Andriy Gapon wrote: on 29/09/2009 21:50 kama said the following: On Tue, 29 Sep 2009, Andriy Gapon wrote: Serial console and remote debugging perhaps? ILO is serial console or rather console++, since you can even see the whole bootup sequence, change bios. But thats if you connect through their webinterface Just point me what other options I could try to get a proper dump or bt. Perhaps you could still use the following: http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-online-gdb.html Otherwise, no ideas. Anyway, I'll try to see if I can reproduce undefined symbol issue here. Not that it would matter much for resolution of your main problem (freeze). Honestly, I have no clue about it. Ok. Hopefully someone else knows what can produce these freezes. BTW, remembering something you said earlier - does including acpi device into kernel still work for you? I.e. can you boot normally with that? Also, can you try 8 on that machine? Just for the sake of experiment? It boot occationally. It does not seem to matter if I include the acpi device into the kernel or not. I get this message in an verbose boot: KLD file acpi.ko - could not finalize loading I have now included a lot of debuging options. But since the server freezes, Im not able to send a break signal to get into the debugger. I'll try to run FSBD8 on the server later this week. /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: FreeBSD 7.2-STABLE boot freeze
on 30/09/2009 16:21 kama said the following: It boot occationally. It does not seem to matter if I include the acpi device into the kernel or not. I get this message in an verbose boot: KLD file acpi.ko - could not finalize loading Do you get this message in all cases? That is, every time you tried? Or only with ACPI_DEBUG defined? I have now included a lot of debuging options. But since the server freezes, Im not able to send a break signal to get into the debugger. I'll try to run FSBD8 on the server later this week. /Bjorn -- 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
On Mon, 28 Sep 2009, kama wrote: On Mon, 28 Sep 2009, Andriy Gapon wrote: on 28/09/2009 10:21 kama said the following: On Fri, 25 Sep 2009, Andriy Gapon wrote: on 25/09/2009 12:04 kama said the following: On Thu, 24 Sep 2009, kama wrote: I am currently building the source on another machine. Lets see if it will build it any better. Building the the world on another machine and install it on the DL385 machine made it also to freeze. Did you still get the message about unresolved symbol? I did not try with ACPI_DEBUG enabled. Another week, so I can start testing again... I did not ask that :-) I asked - when you got your latest freeze, did you see that 'unresolved' message or not? But that only appears when I enable ACPI_DEBUG. And yes. It stills gets the same undefined symbols. (I presume its these you are referring to...) # dmesg | grep -i acpi Preloaded elf module /boot/kernel/acpi.ko at 0xc0ed31d8. link_elf: symbol AcpiDmDumpMethodInfo undefined KLD file acpi.ko - could not finalize loading # nm -A /boot/kernel/* | fgrep AcpiDmDumpMethodInfo /boot/kernel/acpi.ko: U AcpiDmDumpMethodInfo /boot/kernel/acpi.ko.symbols: U AcpiDmDumpMethodInfo nm: /boot/kernel/linker.hints: File format not recognized # uname -a FreeBSD g24.gs.pvp.se 7.2-STABLE FreeBSD 7.2-STABLE #0: Mon Sep 28 13:39:01 CEST 2009 r...@s11.gs.pvp.se:/usr/obj/usr/src/sys/ddb i386 # diff -ub /usr/src/sys/i386/conf/GENERIC /usr/src/sys/i386/conf/ddb --- /usr/src/sys/i386/conf/GENERIC 2009-07-15 10:32:19.0 +0200 +++ /usr/src/sys/i386/conf/ddb 2009-09-28 13:25:20.0 +0200 @@ -67,6 +67,10 @@ optionsAUDIT # Security event auditing #options KDTRACE_HOOKS # Kernel DTrace hooks +optionsKDB +optionsDDB +options ACPI_DEBUG + # To make an SMP kernel, the next two lines are needed optionsSMP # Symmetric MultiProcessor Kernel device apic# I/O APIC # Its too bad that I cant get into the debugger. The server gets unresponsive when the freeze occurs. Is there any other option that I can add so it goes to the debugger? /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: FreeBSD 7.2-STABLE boot freeze
on 29/09/2009 09:58 Bjorn Hellqvist said the following: On Mon, 28 Sep 2009, kama wrote: On Mon, 28 Sep 2009, Andriy Gapon wrote: on 28/09/2009 10:21 kama said the following: On Fri, 25 Sep 2009, Andriy Gapon wrote: on 25/09/2009 12:04 kama said the following: On Thu, 24 Sep 2009, kama wrote: I am currently building the source on another machine. Lets see if it will build it any better. Building the the world on another machine and install it on the DL385 machine made it also to freeze. Did you still get the message about unresolved symbol? I did not try with ACPI_DEBUG enabled. Another week, so I can start testing again... I did not ask that :-) I asked - when you got your latest freeze, did you see that 'unresolved' message or not? But that only appears when I enable ACPI_DEBUG. OK, then I was thoroughly confused all this time. I thought that the message appeared when didn't have ACPI_DEBUG. And yes. It stills gets the same undefined symbols. (I presume its these you are referring to...) # dmesg | grep -i acpi Preloaded elf module /boot/kernel/acpi.ko at 0xc0ed31d8. link_elf: symbol AcpiDmDumpMethodInfo undefined KLD file acpi.ko - could not finalize loading # nm -A /boot/kernel/* | fgrep AcpiDmDumpMethodInfo /boot/kernel/acpi.ko: U AcpiDmDumpMethodInfo /boot/kernel/acpi.ko.symbols: U AcpiDmDumpMethodInfo nm: /boot/kernel/linker.hints: File format not recognized # uname -a FreeBSD g24.gs.pvp.se 7.2-STABLE FreeBSD 7.2-STABLE #0: Mon Sep 28 13:39:01 CEST 2009 r...@s11.gs.pvp.se:/usr/obj/usr/src/sys/ddb i386 # diff -ub /usr/src/sys/i386/conf/GENERIC /usr/src/sys/i386/conf/ddb --- /usr/src/sys/i386/conf/GENERIC 2009-07-15 10:32:19.0 +0200 +++ /usr/src/sys/i386/conf/ddb 2009-09-28 13:25:20.0 +0200 @@ -67,6 +67,10 @@ optionsAUDIT # Security event auditing #options KDTRACE_HOOKS # Kernel DTrace hooks +optionsKDB +optionsDDB +options ACPI_DEBUG + # To make an SMP kernel, the next two lines are needed optionsSMP # Symmetric MultiProcessor Kernel device apic# I/O APIC # Its too bad that I cant get into the debugger. The server gets unresponsive when the freeze occurs. Is there any other option that I can add so it goes to the debugger? Serial console and remote debugging perhaps? Anyway, I'll try to see if I can reproduce undefined symbol issue here. Not that it would matter much for resolution of your main problem (freeze). Honestly, I have no clue about it. -- 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
On Tue, 29 Sep 2009, Andriy Gapon wrote: Serial console and remote debugging perhaps? ILO is serial console or rather console++, since you can even see the whole bootup sequence, change bios. But thats if you connect through their webinterface Just point me what other options I could try to get a proper dump or bt. Anyway, I'll try to see if I can reproduce undefined symbol issue here. Not that it would matter much for resolution of your main problem (freeze). Honestly, I have no clue about it. Ok. Hopefully someone else knows what can produce these freezes. /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: FreeBSD 7.2-STABLE boot freeze
On Fri, 25 Sep 2009, Andriy Gapon wrote: on 25/09/2009 12:04 kama said the following: On Thu, 24 Sep 2009, kama wrote: I am currently building the source on another machine. Lets see if it will build it any better. Building the the world on another machine and install it on the DL385 machine made it also to freeze. Did you still get the message about unresolved symbol? I did not try with ACPI_DEBUG enabled. Another week, so I can start testing again... /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: FreeBSD 7.2-STABLE boot freeze
on 28/09/2009 10:21 kama said the following: On Fri, 25 Sep 2009, Andriy Gapon wrote: on 25/09/2009 12:04 kama said the following: On Thu, 24 Sep 2009, kama wrote: I am currently building the source on another machine. Lets see if it will build it any better. Building the the world on another machine and install it on the DL385 machine made it also to freeze. Did you still get the message about unresolved symbol? I did not try with ACPI_DEBUG enabled. Another week, so I can start testing again... I did not ask that :-) I asked - when you got your latest freeze, did you see that 'unresolved' message or not? -- 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
On Mon, 28 Sep 2009, Andriy Gapon wrote: on 28/09/2009 10:21 kama said the following: On Fri, 25 Sep 2009, Andriy Gapon wrote: on 25/09/2009 12:04 kama said the following: On Thu, 24 Sep 2009, kama wrote: I am currently building the source on another machine. Lets see if it will build it any better. Building the the world on another machine and install it on the DL385 machine made it also to freeze. Did you still get the message about unresolved symbol? I did not try with ACPI_DEBUG enabled. Another week, so I can start testing again... I did not ask that :-) I asked - when you got your latest freeze, did you see that 'unresolved' message or not? But that only appears when I enable ACPI_DEBUG. /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: FreeBSD 7.2-STABLE boot freeze
on 25/09/2009 12:04 kama said the following: On Thu, 24 Sep 2009, kama wrote: I am currently building the source on another machine. Lets see if it will build it any better. Building the the world on another machine and install it on the DL385 machine made it also to freeze. Did you still get the message about unresolved symbol? -- 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 (was: when calibrating clock.)
On Thu, 24 Sep 2009, kama wrote: I am currently building the source on another machine. Lets see if it will build it any better. Building the the world on another machine and install it on the DL385 machine made it also to freeze. /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: FreeBSD 7.2-STABLE boot freeze (was: when calibrating clock.)
On Wed, 23 Sep 2009, Andriy Gapon wrote: on 23/09/2009 18:19 kama said the following: On Wed, 23 Sep 2009, Andriy Gapon wrote: on 23/09/2009 15:47 kama said the following: g24# nm -A /boot/kernel/* | fgrep AcpiDmDumpMethodInfo /boot/kernel/acpi.ko: U AcpiDmDumpMethodInfo /boot/kernel/acpi.ko.symbols: U AcpiDmDumpMethodInfo So this is what I was talking about - this symbol should not be undefined after normal build. This symbol should not be present and referenced at all unless ACPI_DISASSEMBLER is defined. This is clearly a build problem of some sort. Even though they dont exists on a acpi_debug kernel. It does not really matter since the real problem is that freebsd freezes on a normal generic config. What is acpi_debug kernel? The one with option ACPI_DEBUG in it. And FreeBSD does not freeze on a normal generic config. It freezes because of a mysterious build bug that only you seem to have (so far). Just adding 'device acpi' into the generic kernel made it boot successfully. (without KDB DDB ACPI_DEBUG) I am glad that this worked :) Me too. As a work around. But I would prefer a GENERIC kernel to boot. True GENERIC kernel is the one that you get from FreeBSD.Org :-) The one that you built yourself even using GENERIC config can always get tainted by unspecified problems with your build environment. Can you reproduce this problem if you build world, install it somewhere, chroot to it and then build a GENERIC kernel? (with no tweaking between the steps) Actually I spoke to fast. After an reboot it hanged again. From practical point of view, I don't see why moving acpi from module to kernel could be an issue. Here are the outputfiles suggested from the webpage: http://fbsd-err.pvp.se/acpidump_acpi_compiled.asl http://fbsd-err.pvp.se/dmesg_acpi_compiled.txt http://fbsd-err.pvp.se/sysctl_acpi_compiled.txt This doesn't make it nay clearer why you get that build problem. I dunno. I dont have any insight into kernel programming. Hence trying to get information how to help the people to fix the actual problem. That the server freezes at boot. Im kind of lucky to have HP ILO on my side, to test things. =) But I will upgrade the BIOS. If that does not work, I'll try a clean 7.2-REL install. BIOS upgrade may improve some things for you, but I'd be very surprised if it fixes the build problem in question. Well, it did not improve anything. Apperently the output from ILO is not the correct one. Probably it freezes the output to ILO before it can update the screen. (I run ILO through SSH) I took a photo of the actual output presented on a CRT. http://fbsd-err.pvp.se/fbsd-freeze-dl385.jpg (sorry for the blury image, but I cant get it any better from my cellphone) I did not have time to reinstall the system from scratch. But that can be done remotely if needed. I am currently building the source on another machine. Lets see if it will build it any better. (Remember that this happens on two different servers that are specified the exact same way) /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: FreeBSD 7.2-STABLE boot freeze when calibrating clock.
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? No, this is a clean installed system. Nothing in make.conf or src.conf. And loader.conf is empty. 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 g24# nm -A /boot/kernel/* | fgrep AcpiDmDumpMethodInfo /boot/kernel/acpi.ko: U AcpiDmDumpMethodInfo /boot/kernel/acpi.ko.symbols: U AcpiDmDumpMethodInfo nm: /boot/kernel/linker.hints: File format not recognized g24# Could you please try investigating this? Maybe even include acpi into kernel? Just adding 'device acpi' into the generic kernel made it boot successfully. (without KDB DDB ACPI_DEBUG) Here are the outputfiles suggested from the webpage: http://fbsd-err.pvp.se/acpidump_acpi_compiled.asl http://fbsd-err.pvp.se/dmesg_acpi_compiled.txt http://fbsd-err.pvp.se/sysctl_acpi_compiled.txt Please let me know what else to test or if you want more data... Later today I will head over to the datacenter to swap a failed disk and will then also update the BIOS on these servers. I'll post a message how that goes later tonight. /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: FreeBSD 7.2-STABLE boot freeze when calibrating clock.
on 23/09/2009 15:47 kama said the following: g24# nm -A /boot/kernel/* | fgrep AcpiDmDumpMethodInfo /boot/kernel/acpi.ko: U AcpiDmDumpMethodInfo /boot/kernel/acpi.ko.symbols: U AcpiDmDumpMethodInfo So this is what I was talking about - this symbol should not be undefined after normal build. This symbol should not be present and referenced at all unless ACPI_DISASSEMBLER is defined. This is clearly a build problem of some sort. Just adding 'device acpi' into the generic kernel made it boot successfully. (without KDB DDB ACPI_DEBUG) I am glad that this worked :) Here are the outputfiles suggested from the webpage: http://fbsd-err.pvp.se/acpidump_acpi_compiled.asl http://fbsd-err.pvp.se/dmesg_acpi_compiled.txt http://fbsd-err.pvp.se/sysctl_acpi_compiled.txt This doesn't make it nay clearer why you get that build problem. -- 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 Wed, 23 Sep 2009, Andriy Gapon wrote: on 23/09/2009 15:47 kama said the following: g24# nm -A /boot/kernel/* | fgrep AcpiDmDumpMethodInfo /boot/kernel/acpi.ko: U AcpiDmDumpMethodInfo /boot/kernel/acpi.ko.symbols: U AcpiDmDumpMethodInfo So this is what I was talking about - this symbol should not be undefined after normal build. This symbol should not be present and referenced at all unless ACPI_DISASSEMBLER is defined. This is clearly a build problem of some sort. Even though they dont exists on a acpi_debug kernel. It does not really matter since the real problem is that freebsd freezes on a normal generic config. Just adding 'device acpi' into the generic kernel made it boot successfully. (without KDB DDB ACPI_DEBUG) I am glad that this worked :) Me too. As a work around. But I would prefer a GENERIC kernel to boot. Here are the outputfiles suggested from the webpage: http://fbsd-err.pvp.se/acpidump_acpi_compiled.asl http://fbsd-err.pvp.se/dmesg_acpi_compiled.txt http://fbsd-err.pvp.se/sysctl_acpi_compiled.txt This doesn't make it nay clearer why you get that build problem. I dunno. I dont have any insight into kernel programming. Hence trying to get information how to help the people to fix the actual problem. That the server freezes at boot. Im kind of lucky to have HP ILO on my side, to test things. =) But I will upgrade the BIOS. If that does not work, I'll try a clean 7.2-REL install. /Bjorn PS. Another unrelated issue. I get a bounce everytime I send a mail to you. Final-Recipient: rfc822; a...@icyb.net.ua Action: failed Status: 5.0.0 Diagnostic-Code: X-Postfix; host mt.icyb.net.ua[212.40.38.132] said: 550 (LHP01) Not accepted (in reply to RCPT TO command) DS. ___ 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 23/09/2009 18:19 kama said the following: On Wed, 23 Sep 2009, Andriy Gapon wrote: on 23/09/2009 15:47 kama said the following: g24# nm -A /boot/kernel/* | fgrep AcpiDmDumpMethodInfo /boot/kernel/acpi.ko: U AcpiDmDumpMethodInfo /boot/kernel/acpi.ko.symbols: U AcpiDmDumpMethodInfo So this is what I was talking about - this symbol should not be undefined after normal build. This symbol should not be present and referenced at all unless ACPI_DISASSEMBLER is defined. This is clearly a build problem of some sort. Even though they dont exists on a acpi_debug kernel. It does not really matter since the real problem is that freebsd freezes on a normal generic config. What is acpi_debug kernel? And FreeBSD does not freeze on a normal generic config. It freezes because of a mysterious build bug that only you seem to have (so far). Just adding 'device acpi' into the generic kernel made it boot successfully. (without KDB DDB ACPI_DEBUG) I am glad that this worked :) Me too. As a work around. But I would prefer a GENERIC kernel to boot. True GENERIC kernel is the one that you get from FreeBSD.Org :-) The one that you built yourself even using GENERIC config can always get tainted by unspecified problems with your build environment. Can you reproduce this problem if you build world, install it somewhere, chroot to it and then build a GENERIC kernel? (with no tweaking between the steps) From practical point of view, I don't see why moving acpi from module to kernel could be an issue. Here are the outputfiles suggested from the webpage: http://fbsd-err.pvp.se/acpidump_acpi_compiled.asl http://fbsd-err.pvp.se/dmesg_acpi_compiled.txt http://fbsd-err.pvp.se/sysctl_acpi_compiled.txt This doesn't make it nay clearer why you get that build problem. I dunno. I dont have any insight into kernel programming. Hence trying to get information how to help the people to fix the actual problem. That the server freezes at boot. Im kind of lucky to have HP ILO on my side, to test things. =) But I will upgrade the BIOS. If that does not work, I'll try a clean 7.2-REL install. BIOS upgrade may improve some things for you, but I'd be very surprised if it fixes the build problem in question. PS. Another unrelated issue. I get a bounce everytime I send a mail to you. Final-Recipient: rfc822; a...@icyb.net.ua Action: failed Status: 5.0.0 Diagnostic-Code: X-Postfix; host mt.icyb.net.ua[212.40.38.132] said: 550 (LHP01) Not accepted (in reply to RCPT TO command) I'll investigate this. Meanwhile I will use my freebsd.org address in From. -- 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.
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=0x178bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT Features2=0x1SSE3 AMD Features=0xe2500800SYSCALL,NX,MMX+,FFXSR,LM,3DNow!+,3DNow! AMD Features2=0x2CMP Cores per package: 2 real memory = 3221192704 (3071 MB) avail memory = 3146604544 (3000 MB) MPTable: HP PROLIANT 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 Version 1.1 irqs 0-23 on motherboard ioapic1 Version 1.1 irqs 24-27 on motherboard ioapic2 Version 1.1 irqs 28-31 on motherboard ioapic3 Version 1.1 irqs 32-35 on motherboard ioapic4 Version 1.1 irqs 36-39 on motherboard kbd1 at kbdmux0 pcib0: Host to PCI bridge pcibus 0 on motherboard pci0: PCI bus on pcib0 pcib1: MPTable PCI-PCI bridge at device 3.0 on pci0 pci1: PCI bus on pcib1 ohci0: OHCI (generic) USB controller 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: OHCI (generic) USB controller on ohci0 usb0: USB revision 1.0 uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb0 uhub0: 3 ports with 3 removable, self powered ohci1: OHCI (generic) USB controller 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: OHCI (generic) USB controller on ohci1 usb1: USB revision 1.0 uhub1: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb1 uhub1: 3 ports with 3 removable, self powered pci1: base peripheral at device 2.0 (no driver attached) pci1: base peripheral at device 2.2 (no driver attached) vgapci0: VGA-compatible display port 0x4400-0x44ff mem 0xf600-0xf6ff,0xf5ff-0xf5ff0fff at device 3.0 on pci1 isab0: PCI-ISA bridge at device 4.0 on pci0 isa0: ISA bus on isab0 atapci0: AMD 8111 UDMA133 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x2000-0x200f at device 4.1 on pci0 ata0: ATA channel 0 on atapci0 ata0: [ITHREAD] ata1: ATA channel 1 on atapci0 ata1: [ITHREAD] pci0: bridge at device 4.3 (no driver attached) pcib2: MPTable PCI-PCI bridge at device 7.0 on pci0 pci2: PCI bus on pcib2 ciss0: HP Smart Array 6i port 0x5000-0x50ff mem 0xf7ef-0xf7ef1fff,0xf7e8-0xf7eb irq 24 at device 4.0 on pci2 ciss0:
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=0x178bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT Features2=0x1SSE3 AMD Features=0xe2500800SYSCALL,NX,MMX+,FFXSR,LM,3DNow!+,3DNow! AMD Features2=0x2CMP Cores per package: 2 real memory = 3221192704 (3071 MB) avail memory = 3146604544 (3000 MB) MPTable: HP PROLIANT 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 Version 1.1 irqs 0-23 on motherboard ioapic1 Version 1.1 irqs 24-27 on motherboard ioapic2 Version 1.1 irqs 28-31 on motherboard ioapic3 Version 1.1 irqs 32-35 on motherboard ioapic4 Version 1.1 irqs 36-39 on motherboard kbd1 at kbdmux0 pcib0: Host to PCI bridge pcibus 0 on motherboard pci0: PCI bus on pcib0 pcib1: MPTable PCI-PCI bridge at device 3.0 on pci0 pci1: PCI bus on pcib1 ohci0: OHCI (generic) USB controller 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: OHCI (generic) USB controller on ohci0 usb0: USB revision 1.0 uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb0 uhub0: 3 ports with 3 removable, self powered ohci1: OHCI (generic) USB controller 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: OHCI (generic) USB controller on ohci1 usb1: USB revision 1.0 uhub1: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb1 uhub1: 3 ports with 3 removable, self powered pci1: base peripheral at device 2.0 (no driver attached) pci1: base peripheral at device 2.2 (no driver attached) vgapci0: VGA-compatible display port 0x4400-0x44ff mem 0xf600-0xf6ff,0xf5ff-0xf5ff0fff at device 3.0 on pci1 isab0: PCI-ISA bridge at device 4.0 on pci0 isa0: ISA bus on isab0 atapci0: AMD 8111 UDMA133 controller port
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: 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
