SuSE 8.2: Not Shutting Down
The machine just sits, doing absolutely nothing thereafter.
I never experienced this problem with 8.1 but hardly want to downgrade
to it. anyone who knows a workaround/fix I would be grateful to hear
from. (not including leaving the machine on)
--
Olipro
Apologies, the message below was strangely mutilated, here is the understandable (and revised) version: For some strange reason, my system will not shut down: All processes are terminated/killed and the system makes a *noise* one which I hear when it shuts down under windows but after that it hangs, not responding to anything. Original Message: I never experienced this problem with 8.1 but hardly want to downgrade
to it. anyone who knows a workaround/fix I would be grateful to hear from. (not including leaving the machine on) The machine just sits, doing absolutely nothing thereafter. I never experienced this problem with 8.1 but hardly want to downgrade to it. anyone who knows a workaround/fix I would be grateful to hear from. (not including leaving the machine on) -- Olipro
Olipro - GTA Global
On Saturday 02 August 2003 22:20, Olipro wrote:
For some strange reason, my system will not shut down: All processes are terminated/killed and the system makes a *noise* one which I hear when it shuts down under windows but after that it hangs, not responding to anything.
<snip>
The machine just sits, doing absolutely nothing thereafter.
Um... where does it "sit"? Is it still displaying anything? Or is it all "black" and just doesn't turn off the power itself? How did you start the shutdown and how far did it actually proceed? You might wanna watch console 10 while shutting down and see what happens. (Just start the shutdown and switch to console 10 by pressing Ctrl-Alt-F10). BTW: Are those messages from console 10 logged to a file somewhere? Or is it at all possible to log those messages to a file? I could'nt find those messages on my system and googling for "shutdown", "log" and "messages" gave me a wealth of links (I gave up after an hour of surfing the most promising ones) without useful information... Hansen -- Powered by SuSE 8.1pro - KDE 3.0.3 - KMail 1.4.3 At least, try asking smart questions: http://www.catb.org/~esr/faqs/smart-questions.html Netiquette is easy: http://learn.to/edit_messages ...and you'll get flame-free answers in no time.
The 03.08.03 at 13:04, Johannes Liedtke wrote:
BTW: Are those messages from console 10 logged to a file somewhere? Or is it at all possible to log those messages to a file?
Yes... to a point. It is done by the syslog daemon, whose configuration file is "/etc/syslog.conf". See syslogd(8) and syslog.conf(5) Kernel error messages are defined thus: kern.warn;*.err;authpriv.none /dev/tty10 kern.warn;*.err;authpriv.none |/dev/xconsole *.emerg * So, kernel error message of level "warn" and above - that is: warn (same as warning), err, error (same as err), crit, alert, emerg, panic (same as emerg) - logged by the "facility kern" go to tty10, and to the xconsole in x (you may or may not see it on your X session, depends). A few more things go there: every message of level "error" and above, and authorization errors. Notice that any messages of level "emerg" go to any active console. Now, if you want to log kernel messages to a file, you could add this line: kern.* -/var/log/kernel The "-" sign implies that output is buffered, not immediately written to disk. Mind you, this file can some times grow pretty fast, like hundred of megabytes per hour, in case of some repeated error, but not normally. Of course, if you enable it you have to configure logrotate to periodically erase and/or compress those logs. I normally have it enabled. But, in the case at hand, it shows nothing! Reasons? All filesystems are umounted before the system is halted (they would be trashed otherwise). Only console number 10 shows the error (see my other message on this thread). -- Cheers, Carlos Robinson
The 03.08.02 at 21:20, Olipro wrote:
For some strange reason, my system will not shut down: All processes are terminated/killed and the system makes a *noise* one which I hear when it shuts down under windows but after that it hangs, not responding to anything.
Same here. The command "reboot" works, but not "halt". If I switch to console number 10, I can see and error message just after the halt beeps, which I copied by hand: ACPI-1121: *** Error: Method execution failed [\SALD] (node efe3dc0), AE_AML_UNINITIALIZED_LOCAL ACPI-1121: *** Error: Method execution failed [\PTS] (node efed5c0), AE_AML_UNINITIALIZED_LOCAL Then the machine crashes (locks). Even the keyboard stops working (caps lock frozen). I have to power off by the power switch. Needles to say, it worked wit suse 8.1 - but I'm not going to downgrade because of that. It's a bug, of course, but who can solve it, I don't know, nor whom write to - nobody is comenting it here :-( -- Cheers, Carlos Robinson
Carlos E. R. wrote:
The 03.08.02 at 21:20, Olipro wrote:
For some strange reason, my system will not shut down: All processes are terminated/killed and the system makes a *noise* one which I hear when it shuts down under windows but after that it hangs, not responding to anything.
Same here.
The command "reboot" works, but not "halt". If I switch to console number 10, I can see and error message just after the halt beeps, which I copied by hand:
ACPI-1121: *** Error: Method execution failed [\SALD] (node efe3dc0), AE_AML_UNINITIALIZED_LOCAL ACPI-1121: *** Error: Method execution failed [\PTS] (node efed5c0), AE_AML_UNINITIALIZED_LOCAL
Then the machine crashes (locks). Even the keyboard stops working (caps lock frozen). I have to power off by the power switch. Needles to say, it worked wit suse 8.1 - but I'm not going to downgrade because of that.
It's a bug, of course, but who can solve it, I don't know, nor whom write to - nobody is comenting it here :-(
I had the same problem in an earlier version of SuSE (?7.2) but the problem was in the BIOS. I wasn't the only one having this problem, and the solution (it's mentioned in the SuSE database) was to add- append=" apm=real-mode-poweroff" in lilo but one would add this now in the grub menu (if using grub). Try it. -- Understanding only begins with the act of perception.
The 03.08.04 at 01:26, Basil Chupin wrote:
I had the same problem in an earlier version of SuSE (?7.2) but the problem was in the BIOS. I wasn't the only one having this problem, and the solution (it's mentioned in the SuSE database) was to add-
append=" apm=real-mode-poweroff"
(Support knowledgebase (apm_poweroff)) But I'm not using apm, but acpi. I don't think that would work here. I don't think it is a problem with my bios, as the same bios worked with suse 8.1 and acpi and apic. It is a software problem introduced by SuSE in the acpi implementation of suse 8.2. Another thing mentioned on the SDB is that an SMP kernel could be installed: but that is not the case. -- Cheers, Carlos Robinson
Carlos E. R. wrote:
The 03.08.04 at 01:26, Basil Chupin wrote:
I had the same problem in an earlier version of SuSE (?7.2) but the problem was in the BIOS. I wasn't the only one having this problem, and the solution (it's mentioned in the SuSE database) was to add-
append=" apm=real-mode-poweroff"
(Support knowledgebase (apm_poweroff))
THAT'S the name of the database - knowledgebase - I was looking for :-)
But I'm not using apm, but acpi. I don't think that would work here. I don't think it is a problem with my bios, as the same bios worked with suse 8.1 and acpi and apic. It is a software problem introduced by SuSE in the acpi implementation of suse 8.2.
Another thing mentioned on the SDB is that an SMP kernel could be installed: but that is not the case.
Eh, back to the drawingboard then :-(. -- Understanding only begins with the act of perception.
participants (4)
-
Basil Chupin -
Carlos E. R. -
Johannes Liedtke -
Olipro