Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: Restart problems
- To: "Tokyo Linux Abusers' Group" <tlug@example.com>
- Subject: Re: Restart problems
- From: "Stephen J. Turnbull" <turnbull@example.com>
- Date: Wed, 18 Dec 1996 12:37:03 +0900
- In-reply-to: Your message of "Tue, 17 Dec 1996 21:05:14 +0900." <v03010d02aedc3b9b9298@[133.98.20.169]>
- Reply-To: tlug@example.com
- Sender: owner-tlug
>>>>> "Totoro" == Totoro <riley@example.com> writes: Totoro> I've been having a wierd problem lately. Don't know if Totoro> it's due to switching to Redhat 4 or not. Anyhow, whenever Totoro> I shutdown the system, it never completely shuts down and Totoro> cycles back. I had a similar problem for a while once I shifted to a kernel greater than 2.0.0. Actually I still have it, but I have a workaround. What happened was this. I have a very crude statistical analysis program for my HTTP logs. This log is now over 15MB :-P but I have lots of disk space at the moment. For some reason (I think having to do with a memory leak and exhaustion of virtual memory) this program would try to access a nonexistent partition on one of my SCSI drives, causing a file system error. Again for reasons I didn't understand, this results in an inability to sync. Exiting processes would hang as zombies, and programs like `df' would just hang. Totoro> I'm always left with the BIOS screen showing Totoro> memory available and the big blue IBM (I sense thoughts of Totoro> crude remarks about IBM out there...). It won't come back Totoro> and restart from "shutdown -r now" or anything. This doesn't sound like your problem, though. First, I never got to the BIOS screen. Second you don't mention a fsck at every reboot (the inevitable consequence of shutting down without completing a sync). It sounds like you're not getting to the boot loader, but are getting to reboot. So I would guess there's something screwy about your BIOS or the MBR. But one can't rule out problems with the kernel, shutdown(8), and reboot(8). Have you checked your BIOS CMOS settings? -- Stephen J. Turnbull Institute of Policy and Planning Sciences Yaseppochi-Gumi University of Tsukuba http://turnbull.sk.tsukuba.ac.jp/ Tel: +81 (298) 53-5091; Fax: 55-3849 turnbull@example.com ----------------------------------------------------------------- a word from the sponsor will appear below ----------------------------------------------------------------- The TLUG mailing list is proudly sponsored by TWICS - Japan's First Public-Access Internet System. Now offering 20,000 yen/year flat rate Internet access with no time charges. Full line of corporate Internet and intranet products are available. info@example.com Tel: 03-3351-5977 Fax: 03-3353-6096
- References:
- Restart problems
- From: Totoro <riley@example.com>
Home | Main Index | Thread Index
- Prev by Date: Re: Old 386s, Solaris x86, SCO, NT
- Next by Date: Re: Am I unreasonable?
- Prev by thread: Restart problems
- Next by thread: Re: Old 386s, Solaris x86, SCO, NT
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links