Red Hat Bugzilla – Bug 112801
Immediate power-off during zip or less command
Last modified: 2005-10-31 17:00:50 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3; Linux 2.4.20-27.8;
X11; i686; , en_US, en)
Description of problem:
CPU: Toshiba saltellite 1903 laptop, phoenix bios.
Goto my home dir, /home/lpimmes
dev is a large directory within home.
Now, zip this directory, as in:
zip -r dev.zip dev
Output appears on console, as expected. THEN, after 3-4 min. or so,
immediate power off of computer.
Now, try tracing:
zip -r dev.zip dev > powerOff.txt
Normal termination of zip program.
Examine output, check to check:
Editor comes up normally, and I can scroll to bottom of file.
But, now try less
Output appears, press space bar a few times. Ok, no problem.
But, hold down space bar and continue holding...
after 1-2 min. Immediate powerdown of cpu.
Other large directories will zip without power-off, but
when very large directories are zipped (with console output) then
I get immediate power-off.
Version-Release number of selected component (if applicable):
Many times on certain directories and certain conditions.
Steps to Reproduce:
1. See above.
Actual Results: Immediate powerdown occurs in most cases, after
repeating, the above.
Expected Results: Of course, the computer should not power off,
just terminate whatever program I am running. If an error message is
appropriate, it should give me one.
Other directories zip without incident.
Less works, except in the above case.
By all means contact me!
508 845 5960
508 579 2683 (cell)
1) This sounds like a heat problem in your machine with a thermal shutdow
2) RHL 8 is End of Life since a few days
3) You should have called support not used bugzilla for support ...
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases,
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/