Hi all! Ok, I've got a generic machine, PII 400 on an Asus board, it's got an 8G maxtor, a 3com 3c905c, NE2000(isa), 192M ram, and an SIS video card. So, nothing really odd or troublesome in general. I'm running SuSE 7.3 on this machine, and I use it as a test machine for various configurations. I run apache w/PHP, MySQL, djbdns, qmail with Courier IMAP, openssh, a firewall script I wrote, SAMBA, syslogd, and snort. It boots into level 3 (multi-user/net) Here's the problem: I have to manually reboot this machine every once-in-a-while because it locks up completely. I've never seen this before! I mean the monitor, mouse, keyboard, network, disk access light -- nothing is working! On top of that, there's nothing I see reporting any problems in the syslog. I've looked over every configuration I can think of and I've stripped the processes down to just those listed above. I cannot figure out what's going on, other than "dying" hardware. A "df -h" outputs this: Filesystem Size Used Avail Use% Mounted on /dev/hda2 8.0G 3.2G 4.8G 40% / /dev/hda1 15M 6.5M 7.4M 47% /boot shmfs 93M 0 92M 0% /dev/shm So I know the machine isn't full. I've been watching it for a while whenever I've had to restart, and nothing strange is happening. However, I'm have to restart more frequently the past 3 weeks. :( Any advice on the matter would be greatly appreciated! :) -- Travis "Whois awk?" sed Grep. -- Travis. For Laptop issuses, check out: http://www.linux-laptop.net For Wireless LAN issues, check out: http://www.linux-wlan.com Don't forget to document your experiences, tricks, and advice while using Linux. Post it somewhere so we'll all benefit from it. You never know who will be asking the same question next time.
On Thu, 2002-06-13 at 22:38, Travis Owens wrote:
Hi all!
Ok, I've got a generic machine, PII 400 on an Asus board, it's got an 8G maxtor, a 3com 3c905c, NE2000(isa), 192M ram, and an SIS video card. So, nothing really odd or troublesome in general.
I'm running SuSE 7.3 on this machine, and I use it as a test machine for various configurations. I run apache w/PHP, MySQL, djbdns, qmail with Courier IMAP, openssh, a firewall script I wrote, SAMBA, syslogd, and snort.
It boots into level 3 (multi-user/net)
Here's the problem: I have to manually reboot this machine every once-in-a-while because it locks up completely. I've never seen this before! I mean the monitor, mouse, keyboard, network, disk access light -- nothing is working!
On top of that, there's nothing I see reporting any problems in the syslog. I've looked over every configuration I can think of and I've stripped the processes down to just those listed above. I cannot figure out what's going on, other than "dying" hardware.
Hi Travis, I have just been through 2 weeks of contnuous hangups, similar to yours, but my problem was new hardware conflicts. I suggest that you check your hardware by doing the memtest (in the lilo boot). Let it run through a few iterations. I left mine for a night. It ran 10 iterations. You can also do a 'system' test. I found this: http://sdb.suse.de/en/sdb/html/hmeyer_memtest-sig11.html I also let this one run through the night and it ran 50 odd iterations. According to the web pages, this should tell you if you have hardware problems. If your problem is related to mine (it has the same symptoms), then has to do with disk I/O that fails. The problem is that when the disk that has your /var/partition on have problems, then you will not see any error messages, as the kernel cannot write the error to the log file after the error occurred. I picked up on my problem when I saw the kernel's last dying messages written to a terminal. HTH -- Andre Truter Software Engineer Registered Linux user #185282 ICQ #40935899 AIM: trusoftzaf http://www.trusoft.za.net <-------------------------------------------------> < The box said: Requires Windows 95 or better... > < So I installed Linux > <------------------------------------------------->
Also, you might check all the fans in your system. I had an system acting the same and it turned out that the fan in my power supply was slowly dying but it would only slow down every once in a while. Took weeks to finaly find it. Austin Morgan On Thu, Jun 13, 2002 at 10:48:29PM +0200, Andre Truter wrote:
On Thu, 2002-06-13 at 22:38, Travis Owens wrote:
Hi all!
Ok, I've got a generic machine, PII 400 on an Asus board, it's got an 8G maxtor, a 3com 3c905c, NE2000(isa), 192M ram, and an SIS video card. So, nothing really odd or troublesome in general.
I'm running SuSE 7.3 on this machine, and I use it as a test machine for various configurations. I run apache w/PHP, MySQL, djbdns, qmail with Courier IMAP, openssh, a firewall script I wrote, SAMBA, syslogd, and snort.
It boots into level 3 (multi-user/net)
Here's the problem: I have to manually reboot this machine every once-in-a-while because it locks up completely. I've never seen this before! I mean the monitor, mouse, keyboard, network, disk access light -- nothing is working!
On top of that, there's nothing I see reporting any problems in the syslog. I've looked over every configuration I can think of and I've stripped the processes down to just those listed above. I cannot figure out what's going on, other than "dying" hardware.
Hi Travis,
I have just been through 2 weeks of contnuous hangups, similar to yours, but my problem was new hardware conflicts.
I suggest that you check your hardware by doing the memtest (in the lilo boot). Let it run through a few iterations. I left mine for a night. It ran 10 iterations.
You can also do a 'system' test. I found this: http://sdb.suse.de/en/sdb/html/hmeyer_memtest-sig11.html
I also let this one run through the night and it ran 50 odd iterations.
According to the web pages, this should tell you if you have hardware problems.
If your problem is related to mine (it has the same symptoms), then has to do with disk I/O that fails. The problem is that when the disk that has your /var/partition on have problems, then you will not see any error messages, as the kernel cannot write the error to the log file after the error occurred.
I picked up on my problem when I saw the kernel's last dying messages written to a terminal.
HTH
participants (3)
-
Andre Truter -
Austin Morgan -
Travis Owens