From owner-freebsd-questions Sat Nov 17 18:27:36 2001 Delivered-To: freebsd-questions@freebsd.org Received: from atkielski.com (atkielski.com [161.58.232.69]) by hub.freebsd.org (Postfix) with ESMTP id 08DC337B417 for ; Sat, 17 Nov 2001 18:27:29 -0800 (PST) Received: from contactdish (ASt-Lambert-101-2-1-14.abo.wanadoo.fr [193.251.59.14]) by atkielski.com (8.11.6) id fAI2RPg77717; Sun, 18 Nov 2001 03:27:25 +0100 (CET) Message-ID: <033901c16fd8$8fb18740$0a00000a@atkielski.com> From: "Anthony Atkielski" To: "Andrew C. Hornback" , "FreeBSD Questions" References: <002401c16fb7$abc1fd00$6600000a@ach.domain> Subject: Re: Mysterious boot during the night Date: Sun, 18 Nov 2001 03:27:18 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Andrew writes: > Yup. I call it cutting edge... it's not an > Itanium or a HP Superdome server, but it's still > cutting edge consumer grade hardware. Maybe in terms of processor speed. But machines are so fast these days, does processor speed really matter? The vendor did cut corners in a lot of other ways, although the machine seems to be reasonably well built and equipped for the price. > I may be mistaken, but I believe there are known > problems with that chipset. Known problems that would reboot a system? > However, they're not a manufacturer known for > quality hardware. It looks okay for what I paid for it. > Your best bet here is going to get one of the memory > checking software programs and basically "bang the > hell" out of the machine to force it to error. If the reboots become frequent and worrisome, I'll consider it. Nowadays I tend to put hardware failures at the bottom of the list of possible system problems--so much so that I question the utility of things like clustered servers, especially since they usually have lots of other problems related to clustering that tend to more than negate their alleged value at increasing uptime (often more theoretical than real, anyway). > What controller chipset does it use? I don't know. > Maybe it's just how I go about things, but I > don't install hardware that I'm not ready to use > immediately. I've seen some strange things > like that. If it will work when I use it, it will surely work when I don't use it. I don't like to open and close the case any more than necessary. > You can get rid of this stuff by modifying your > kernel.conf file. Is there a reason why I'd want to get rid of it? > Look this up on the web and see if you can determine > what it is. This may be a piece of unsupported > hardware. Does your machine include onboard sound > or something like that? Yes, it looks like this is some sort of Compu-Media on-board PCI audio gadget. I don't use the audio on the system. When I started KDE, one of the six million processes it launched for my one user was something called artsd, and it was not at all nice, at -36. I trashed it, shortly before trashing all of KDE. It seemed to have something to do with the sound interface, and I saw complaints it was logging, so I just killed it. > Are you sure that the cable for this is 100% spec? Nope. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message