Dan Naumov
2010-Feb-28 01:29 UTC
8.0 on new hardware and a few errors, should I be worried?
Hello I've very recently finished installing 8.0-RELEASE on some new hardware and I noticed a few error messages that make me a bit uneasy. This is a snip from my dmesg: -------------------------------------------------- acpi0: <SMCI > on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of fee00000, 1000 (3) failed acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, bf600000 (3) failed -------------------------------------------------- What do these mean and should I worry about it? The full DMESG can be viewed here: http://jago.pp.fi/temp/dmesg.txt Additionally, while building a whole bunch of ports on this new system (about 30 or so, samba, ncftp, portaudit, bash, the usual suspects), I noticed the following in my logs during the build process: -------------------------------------------------- Feb 27 21:24:01 atombsd kernel: pid 38846 (try), uid 0: exited on signal 10 (core dumped) Feb 27 22:17:49 atombsd kernel: pid 89665 (conftest), uid 0: exited on signal 6 (core dumped) -------------------------------------------------- All ports seem to have built and installed succesfully. Again, what do these mean and should I worry about it? :) Thanks! - Sincerely, Dan Naumov
Jeremy Chadwick
2010-Feb-28 01:34 UTC
8.0 on new hardware and a few errors, should I be worried?
On Sun, Feb 28, 2010 at 03:28:48AM +0200, Dan Naumov wrote:> Additionally, while building a whole bunch of ports on this new system > (about 30 or so, samba, ncftp, portaudit, bash, the usual suspects), I > noticed the following in my logs during the build process: > > -------------------------------------------------- > Feb 27 21:24:01 atombsd kernel: pid 38846 (try), uid 0: exited on > signal 10 (core dumped) > Feb 27 22:17:49 atombsd kernel: pid 89665 (conftest), uid 0: exited on > signal 6 (core dumped) > --------------------------------------------------This is intentional/normal, believe it or not. It's by-design as part of some compiler tests that autoconf (or the software that uses autoconf) induces. Thanks, GNU! FreeBSD logs these to the console by default; the sysctl to control this behaviour is kern.logsigexit. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |
John Baldwin
2010-Mar-01 18:47 UTC
8.0 on new hardware and a few errors, should I be worried?
On Saturday 27 February 2010 8:28:48 pm Dan Naumov wrote:> Hello > > I've very recently finished installing 8.0-RELEASE on some new > hardware and I noticed a few error messages that make me a bit uneasy. > This is a snip from my dmesg: > > -------------------------------------------------- > acpi0: <SMCI > on motherboard > acpi0: [ITHREAD] > acpi0: Power Button (fixed) > acpi0: reservation of fee00000, 1000 (3) failed > acpi0: reservation of 0, a0000 (3) failed > acpi0: reservation of 100000, bf600000 (3) failed > -------------------------------------------------- > > What do these mean and should I worry about it? The full DMESG can be > viewed here: http://jago.pp.fi/temp/dmesg.txtYou can ignore them. FreeBSD creates two psuedo-devices on x86 called apic0 and ram0. Their sole job is to reserve the memory ranges used by APIC devices and system RAM to prevent those address ranges being reused by anything else (such as PCI BARs). Many systems also reserve those ranges as a system resource via ACPI (or PnPBIOS for the non-ACPI case). What is happening is that the ACPI system resource driver isn't able to reserve these ranges because they are already claimed by apic0 and ram0. The important point is that some device claims them. It doesn't really matter which one does. -- John Baldwin