Re: still can't resolve these system reboots... help please
So the next question is how do I approach Dell to replace the motherboard/cpu/memory? If I show them FreeBSD they'll laugh. Can you find an intensive program to run under Windows that will reproduce it? Hell ... just install ActivePerl and write a perl script that does lots and lots of number crunching (it need not be anything useful) or install SETI and see if it crashes Windows. Tried SETI and WINTEST, neither would do it. Tuc/TTSG Internet Services, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: still can't resolve these system reboots... help please
--- Bill Moran [EMAIL PROTECTED] wrote: True ... I don't know if memtest is better/worse/equal to burnMMX or not. I've just always used both for testing. One thing about memory glitches, they try very hard not to occur when you're looking for them! murphy's law appears at the worst possible times. now i have another bigger issue. the system is completely unresponsive. something is dead in that unit. the HD light is on and not much else is. :/ let this be a lesson for all... try to avoid no-name hardware that has everything integrated into one board. __ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: still can't resolve these system reboots... help please
On Thu, Mar 06, 2003 at 12:58:32AM +0100, Martin Karlsson wrote: * Bsd Neophyte [EMAIL PROTECTED] [2003-03-05 15.52 -0800]: --- Bill Moran [EMAIL PROTECTED] wrote: [snip] Have you tried running memtest for equal lengths of time? memtest doesn't seem to exist in the ports anymore :/ the file can't be fetched from any of the listed sites. You can fetch it here: URI:ftp://ftp.sunet.se/pub/os/FreeBSD/ports/distfiles/memtester-2.93.1.tar.bz2 I just advised someone that memtest gives spurious error on tests 5 and 7 on Asus motherboards. i think I started ths thread. P am amzed at the reaction. The usual bollocks of course about bad harware. Mmm.. sorry guys, X/Screensaver crashes FreeBSD. -- Regards Cliff [ This mail has been checked as virus-free ] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: still can't resolve these system reboots... help please
On Thursday 06 March 2003 10:49 pm, Cliff Sarginson wrote: I just advised someone that memtest gives spurious error on tests 5 and 7 on Asus motherboards. i think I started ths thread. P am amzed at the reaction. The usual bollocks of course about bad harware. Mmm.. sorry guys, X/Screensaver crashes FreeBSD. Cliff, If you can get it to crash at will, I'm sure there would be interest in fixing that, especially if you're running -stable or -current. Tim To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: still can't resolve these system reboots... help please
On Wednesday 05 March 2003 07:28 pm, Chris Howells wrote: | -BEGIN PGP SIGNED MESSAGE- | Hash: SHA1 | | Hi, | | On Wednesday 05 March 2003 19:35, Tuc wrote: | So the next question is how do I approach Dell to replace | the motherboard/cpu/memory? If I show them FreeBSD they'll laugh. | | Oh dear, that's bad news. | | See http://developer.kde.org/~howells/inspiron for the battle I had | against Dell regarding trying to run Linux on a (brand new) faulty | Dell laptop. That is amazing and disheartening since I actually originally starting using Dell laptops because when I bought my first one they were about the only major manufacturor which *did* promise that their equipment would work with Linux. And shortly thereafter they started selling them with Linux pre-installed. Of course about a year later they stopped selling them with Linux, but I didn't realize that they'd gone completely over to the dark side. Actually, I notice that their website still offers Linux driver downloads for machines as recent as the 8000, so it was claerly still supported when I got my current machine. Hate to think I might have to find another company for my next computer. Do NOT buy a Compaq, whatever you do. Officially Compaq technical support disclaims any responsibility if you've installed *software* on it. The conversation: you mean you don't support it if you've installed another *operating* *system*, right? if you've installed any software that didn't come with it. A . . what? . . I . . . you're kidding . . . ok, never mind. I'd like an RMA number, please. Ok, . . . . Thank heavens it went belly-up in the first two weeks while I could still return it for any reason . . . Before I got the Dell I researched to make sure that wouldn't happen again. But before I got the last one I didn't RE-research to see if they had completely changed their tune. Guess I've been lucky :-) -- Brian, the man from Babble-On . . . . [EMAIL PROTECTED] (personal) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: still can't resolve these system reboots... help please
On Wednesday 05 March 2003 07:30 pm, Chris Howells wrote: | -BEGIN PGP SIGNED MESSAGE- | Hash: SHA1 | | Hi, | | On Wednesday 05 March 2003 19:44, Bill Moran wrote: | Hell ... just install ActivePerl and write a perl script that does | lots and lots of number crunching (it need not be anything useful) | or install SETI and see if it crashes Windows. | | When I had a hardware problem with Dell like this one, they insisted | that there could only be a problem if there was an issue with the | installed software. If it was self-installed, then it had to be | faulty software not hardware. FWIW, when I called Dell with a problem of this nature, they had me use (or perhaps download) a testing utility -- which was self-booting and did not require *any* operating system to run. I ran that, it confirmed that the hardware was indeed faulty, and then they happily replaced it. A lot depends on how clueful a person you get in tech support, but if they are not clueful, either try again and hope for better luck or request a test utility that they would accept. Getting the O/S issue out of the way simplifies things greatly. -- Brian, the man from Babble-On . . . . [EMAIL PROTECTED] (personal) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: still can't resolve these system reboots... help please
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On Wednesday 05 March 2003 19:35, Tuc wrote: So the next question is how do I approach Dell to replace the motherboard/cpu/memory? If I show them FreeBSD they'll laugh. Oh dear, that's bad news. See http://developer.kde.org/~howells/inspiron for the battle I had against Dell regarding trying to run Linux on a (brand new) faulty Dell laptop. - -- Cheers, Chris Howells -- [EMAIL PROTECTED], [EMAIL PROTECTED] Web: http://chrishowells.co.uk, PGP ID: 33795A2C KDE: http://www.koffice.org, http://printing.kde.org, http://usability.kde.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE+ZpZAF8Iu1zN5WiwRAgV4AJ9aRH5VMKSU4z6UTK/F4RGog6lAiACeNAyA lmi2PjKvD+wyUzd/ko5pgs0= =qIEY -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: still can't resolve these system reboots... help please
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On Wednesday 05 March 2003 19:44, Bill Moran wrote: Hell ... just install ActivePerl and write a perl script that does lots and lots of number crunching (it need not be anything useful) or install SETI and see if it crashes Windows. When I had a hardware problem with Dell like this one, they insisted that there could only be a problem if there was an issue with the installed software. If it was self-installed, then it had to be faulty software not hardware. - -- Cheers, Chris Howells -- [EMAIL PROTECTED], [EMAIL PROTECTED] Web: http://chrishowells.co.uk, PGP ID: 33795A2C KDE: http://www.koffice.org, http://printing.kde.org, http://usability.kde.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE+ZpaYF8Iu1zN5WiwRAgumAJ9WvtaPvE0t5ol0qXKGxwnCteFApQCfX6hh cXpI4cS0GEgon5Yst+wZuSI= =TRKO -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: still can't resolve these system reboots... help please
On Wednesday, Mar 5, 2003, at 17:30 US/Mountain, Chris Howells wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On Wednesday 05 March 2003 19:44, Bill Moran wrote: Hell ... just install ActivePerl and write a perl script that does lots and lots of number crunching (it need not be anything useful) or install SETI and see if it crashes Windows. When I had a hardware problem with Dell like this one, they insisted that there could only be a problem if there was an issue with the installed software. If it was self-installed, then it had to be faulty software not hardware. At least in the US, small claims court is your friend if they act like jack *sses... Chad To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: still can't resolve these system reboots... help please
I feel for you. I too am having it. Most of the time it does it while I'm not around, but once I was in elm writing mail, and the screen went black, and the DELL splash screen came on. I ran burnP6 for a few minutes (Boy does it make the system unhappy, but it kept chugging) and BurnMMX too. I'm cvsup'd to Feb 23, RELENG_4. Tuc/TTSG Internet Services, Inc. can faulty hardware be ruled out then? I don't know. burnP6 and burnMX have been running all night 342:16 49.17% 49.17% burnBX 340:52 48.10% 48.10% burnP6 and there are no problems so far. BTW: When I run it, the system actually makes a high pitched squeal. It seems to do that anytime the system is doing something CPU intensive. it's odd though, this thing just started happening on day when i first started creating DSA keyparis. other than that, things were rock solid. Same for me, but mine was upgrading X and it locked up installing. this is starting to leave a sour taste in my mouth. :/ Agreed. Tuc/TTSG Internet Services, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: still can't resolve these system reboots... help please
Your problems certainly sound like failing hardware. The archives are littered with examples of people who swore black and blue that failing hardware could not possibly be the cause of their mysterious reboots, until they found the failing hardware and replaced it :-) Check and swap out/replace RAM, power supply, CPU fan, cabling, CPU etc. Heres the rub... Mine is a Dell 8200 laptop. Not like I can do much hardware stuff to it... And the old It don't happen in Winderz. Tuc/TTSG Internet Services, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: still can't resolve these system reboots... help please
My second suggestion is going to sound really weird. My FreeBSD system disappears into the boonies when I have a screen saver enabled. That is xscreevsaver. Given enough time, and enough core dumps. it crashes my system as sure as eggs is eggs. I kind of proved this by leaving the systen running for days with and without screen saver. It boonied with the screen saver, it did not wihout. Mine seems to always do it in X, haven't gotten it to do it in command line yet What did you do to fix it? (I run xlockmore) Tuc/TTSG Internet Services, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: still can't resolve these system reboots... help please
Tuc wrote: Your problems certainly sound like failing hardware. The archives are littered with examples of people who swore black and blue that failing hardware could not possibly be the cause of their mysterious reboots, until they found the failing hardware and replaced it :-) Check and swap out/replace RAM, power supply, CPU fan, cabling, CPU etc. Heres the rub... Mine is a Dell 8200 laptop. Not like I can do much hardware stuff to it... And the old It don't happen in Winderz. It could be incompatible hardware (i.e. mostly compatible hardware) that works most of the time, but occasionally causes a reboot. Meanwhile, the vender drivers for Windows make it work perfectly there. Also, I've seen flakey hardware that Windows simply didn't exercise enough to cause problems. -- Bill Moran Potential Technologies http://www.potentialtech.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: still can't resolve these system reboots... help please
It could be incompatible hardware (i.e. mostly compatible hardware) that works most of the time, but occasionally causes a reboot. Meanwhile, the vender drivers for Windows make it work perfectly there. Its been working reliably since last May in 4.5/4.6/4.7 Then the hard drive failed, put a fresh install, and then it was reliable until I was portupgrading X. What could the X system do so horrible that would make the screen just go black and then the splash page happen? Also, I've seen flakey hardware that Windows simply didn't exercise enough to cause problems. I know, had to throw it in. :) Winderz is here just for when STAROFFICE doesn't work right. Tuc/TTSG Internet Services, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: still can't resolve these system reboots... help please
On Wed, Mar 05, 2003 at 01:59:05PM -0500, Tuc wrote: It could be incompatible hardware (i.e. mostly compatible hardware) that works most of the time, but occasionally causes a reboot. Meanwhile, the vender drivers for Windows make it work perfectly there. Its been working reliably since last May in 4.5/4.6/4.7 Then the hard drive failed, put a fresh install, and then it was reliable until I was portupgrading X. What could the X system do so horrible that would make the screen just go black and then the splash page happen? It exercises the hardware vigorously (CPU, RAM, disk, I/O controllers, ...). This is exactly the situation under which failing hardware is most likely to fail. Kris pgp0.pgp Description: PGP signature
Re: still can't resolve these system reboots... help please
It exercises the hardware vigorously (CPU, RAM, disk, I/O controllers, =2E..). This is exactly the situation under which failing hardware is most likely to fail. So the next question is how do I approach Dell to replace the motherboard/cpu/memory? If I show them FreeBSD they'll laugh. Tuc/TTSG Internet Services, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: still can't resolve these system reboots... help please
Tuc wrote: It exercises the hardware vigorously (CPU, RAM, disk, I/O controllers, =2E..). This is exactly the situation under which failing hardware is most likely to fail. So the next question is how do I approach Dell to replace the motherboard/cpu/memory? If I show them FreeBSD they'll laugh. Can you find an intensive program to run under Windows that will reproduce it? Hell ... just install ActivePerl and write a perl script that does lots and lots of number crunching (it need not be anything useful) or install SETI and see if it crashes Windows. -- Bill Moran Potential Technologies http://www.potentialtech.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: still can't resolve these system reboots... help please
--- Bill Moran [EMAIL PROTECTED] wrote: burnP6 and burnMX have been running all night 342:16 49.17% 49.17% burnBX 340:52 48.10% 48.10% burnP6 and there are no problems so far. Have you tried running memtest for equal lengths of time? memtest doesn't seem to exist in the ports anymore :/ the file can't be fetched from any of the listed sites. reading the man page stated that burnMX -P tested the memory. so i figured i could use it instead of memtest. __ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: still can't resolve these system reboots... help please
* Bsd Neophyte [EMAIL PROTECTED] [2003-03-05 15.52 -0800]: --- Bill Moran [EMAIL PROTECTED] wrote: [snip] Have you tried running memtest for equal lengths of time? memtest doesn't seem to exist in the ports anymore :/ the file can't be fetched from any of the listed sites. You can fetch it here: URI:ftp://ftp.sunet.se/pub/os/FreeBSD/ports/distfiles/memtester-2.93.1.tar.bz2 HTH -- Martin Karlsson To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: still can't resolve these system reboots... help please
Bsd Neophyte wrote: --- Bill Moran [EMAIL PROTECTED] wrote: burnP6 and burnMX have been running all night 342:16 49.17% 49.17% burnBX 340:52 48.10% 48.10% burnP6 and there are no problems so far. Have you tried running memtest for equal lengths of time? reading the man page stated that burnMX -P tested the memory. so i figured i could use it instead of memtest. True ... I don't know if memtest is better/worse/equal to burnMMX or not. I've just always used both for testing. One thing about memory glitches, they try very hard not to occur when you're looking for them! -- Bill Moran Potential Technologies http://www.potentialtech.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: still can't resolve these system reboots... help please
On Wed, Mar 05, 2003 at 03:52:31PM -0800, Bsd Neophyte wrote: --- Bill Moran [EMAIL PROTECTED] wrote: burnP6 and burnMX have been running all night 342:16 49.17% 49.17% burnBX 340:52 48.10% 48.10% burnP6 and there are no problems so far. Have you tried running memtest for equal lengths of time? memtest doesn't seem to exist in the ports anymore :/ the file can't be fetched from any of the listed sites. Yes it does. ls -l /usr/ports/sysutils/memtest/ total 12 drwxr-xr-x 2 root wheel 512 Feb 24 15:53 CVS/ -rw-r--r-- 1 root wheel 672 Feb 24 15:53 Makefile -rw-r--r-- 1 root wheel 66 Jul 19 2000 distinfo drwxr-xr-x 3 root wheel 512 Jan 13 19:57 files/ -rw-r--r-- 1 root wheel 502 Jul 19 2000 pkg-descr -rw-r--r-- 1 root wheel 12 Jul 19 2000 pkg-plist kris pgp0.pgp Description: PGP signature
still can't resolve these system reboots... help please
i've upgraded the kernel as well as the system from 4.7 to 4.8rc3. however, i'm still getting the same issues. my system will randomly reboot when i'm doing anything from changing a directory to ftp-ing. i cracked the case, cleaned out all the dust thinking that the cooling was an issue. i've run cpuburn (burnP6 for the processor and burnBX for the ram) and the processes seem to run fine. i was also able to rebuild everything without issue about the second time. /var/log/messages isn't helping me much. it simply shows the dmesg output everytime the system reboots. why has my system become so unstable? this started when i tried to make rsa and dsa keypairs... and i was told that the system might have faulty parts or that it might get too hot. but even after i cleaned the dust out (and the system is not being overclocked) i am still getting random reboots. please if anyone can help me resolve this... i can't stand having this extremely unstable server. it's causing all sorts of problems on the network. __ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: still can't resolve these system reboots... help please
please if anyone can help me resolve this... i can't stand having this extremely unstable server. it's causing all sorts of problems on the network. I feel for you. I too am having it. Most of the time it does it while I'm not around, but once I was in elm writing mail, and the screen went black, and the DELL splash screen came on. I ran burnP6 for a few minutes (Boy does it make the system unhappy, but it kept chugging) and BurnMMX too. I'm cvsup'd to Feb 23, RELENG_4. Tuc/TTSG Internet Services, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: still can't resolve these system reboots... help please
--- Tuc [EMAIL PROTECTED] wrote: please if anyone can help me resolve this... i can't stand having this extremely unstable server. it's causing all sorts of problems on the network. I feel for you. I too am having it. Most of the time it does it while I'm not around, but once I was in elm writing mail, and the screen went black, and the DELL splash screen came on. I ran burnP6 for a few minutes (Boy does it make the system unhappy, but it kept chugging) and BurnMMX too. I'm cvsup'd to Feb 23, RELENG_4. Tuc/TTSG Internet Services, Inc. can faulty hardware be ruled out then? burnP6 and burnMX have been running all night 342:16 49.17% 49.17% burnBX 340:52 48.10% 48.10% burnP6 and there are no problems so far. it's odd though, this thing just started happening on day when i first started creating DSA keyparis. other than that, things were rock solid. this is starting to leave a sour taste in my mouth. :/ __ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: still can't resolve these system reboots... help please
On Tue, Mar 04, 2003 at 03:30:08PM -0800, Bsd Neophyte wrote: can faulty hardware be ruled out then? No. You can't exhaustively test the hardware using software. You can only test some things: what you have shown is that none of the things that burn* does cause your system to reboot. The only way you can rule out hardware failure completely is to replace it component by component and see if the problem persists. Your problems certainly sound like failing hardware. The archives are littered with examples of people who swore black and blue that failing hardware could not possibly be the cause of their mysterious reboots, until they found the failing hardware and replaced it :-) Check and swap out/replace RAM, power supply, CPU fan, cabling, CPU etc. Kris pgp0.pgp Description: PGP signature
Re: still can't resolve these system reboots... help please
On Tue, Mar 04, 2003 at 06:55:21PM -0800, Kris Kennaway wrote: On Tue, Mar 04, 2003 at 03:30:08PM -0800, Bsd Neophyte wrote: Think you have been given just about all the advice to give. It is a bunner, and expensive to solve if you replace bits. I will give two suggestions. Is the power supply to your firm/house whatever clean ? Computers don't like dirty power, that is power prone to what I think experts call grey-outs. They don't like spikes either, momentary increases in voltage. Do you live in an area prone to thunderstorms? You can get devices to protect against somne of these things. My second suggestion is going to sound really weird. My FreeBSD system disappears into the boonies when I have a screen saver enabled. That is xscreevsaver. Given enough time, and enough core dumps. it crashes my system as sure as eggs is eggs. I kind of proved this by leaving the systen running for days with and without screen saver. It boonied with the screen saver, it did not wihout. A few questons. Power supply ? Do you have SCSI disks ? They eat electricity like it is going out of fashion. Heat, is the server overheating ? If you have a modern BIOS it can tell you what the temperature is. You need to watch what the CPU temp is, because the reaction to over heating is reboot. Good luck. -- Regards Cliff [ This mail has been checked as virus-free ] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: still can't resolve these system reboots... help please
so you have a 3com nic in that thing ? - Original Message - From: Cliff Sarginson [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, March 04, 2003 10:33 PM Subject: Re: still can't resolve these system reboots... help please On Tue, Mar 04, 2003 at 06:55:21PM -0800, Kris Kennaway wrote: On Tue, Mar 04, 2003 at 03:30:08PM -0800, Bsd Neophyte wrote: Think you have been given just about all the advice to give. It is a bunner, and expensive to solve if you replace bits. I will give two suggestions. Is the power supply to your firm/house whatever clean ? Computers don't like dirty power, that is power prone to what I think experts call grey-outs. They don't like spikes either, momentary increases in voltage. Do you live in an area prone to thunderstorms? You can get devices to protect against somne of these things. My second suggestion is going to sound really weird. My FreeBSD system disappears into the boonies when I have a screen saver enabled. That is xscreevsaver. Given enough time, and enough core dumps. it crashes my system as sure as eggs is eggs. I kind of proved this by leaving the systen running for days with and without screen saver. It boonied with the screen saver, it did not wihout. A few questons. Power supply ? Do you have SCSI disks ? They eat electricity like it is going out of fashion. Heat, is the server overheating ? If you have a modern BIOS it can tell you what the temperature is. You need to watch what the CPU temp is, because the reaction to over heating is reboot. Good luck. -- Regards Cliff [ This mail has been checked as virus-free ] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
