I have two systems with which I am having problems during a shutdown or reboot. Both are x86_64 systems running Fedora-18 (Spherical Cow). In both cases the systems will panic before the shutdown or reboot process is completed and system restarts or powers off. This is a problem because the system that controls the UPS must poweroff to shutdown the UPS during a power failure. If it does not, the UPS powers off after the batteries run down. This is not good for the UPS.
Anyway, this problem will occurs on either of these systems after some time has been spent working on them: running X, Firefox, Liferea, LibreOffice, etc... If you than shutdown apps, close windows and terminate the window manager (FVWM), and than do a shutdown or reboot from the command line. the system will panic before the shutdown/reboot is done with the following sampled lines:
Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100 Pid: 1, comm: shutdown Not tainted 3.7.9-205.fc18.x86_64 #1
I am now running the latest kernel: 3.8.1-201.fc18.x86_64 and application updates, but that has not changed the conditions of this problem. I am looking for hints for where the source of the problem may lie. I have tried the Mate and XFCE desktops, and have not seen the problem with them, but I have not used either of them very extensively. I have searched Bugzilla for similar descriptions with no success. The problem appears to be a user level issue that is causing the kernel panic. Not something that I would expect to happen.
Bill
On 03/06/2013 12:42 PM, William Perkins wrote:
This is a problem because the system that controls the UPS must poweroff to shutdown the UPS during a power failure. If it does not, the UPS powers off after the batteries run down. This is not good for the UPS.
I take it, then, that the UPS is only intended to allow for an orderly shutdown. How do you handle short power drops? (Please understand that I've never worked professionally with this type of thing but I'm always interested in learning new things.)
Am 06.03.2013 21:56, schrieb Joe Zeff:
On 03/06/2013 12:42 PM, William Perkins wrote:
This is a problem because the system that controls the UPS must poweroff to shutdown the UPS during a power failure. If it does not, the UPS powers off after the batteries run down. This is not good for the UPS.
I take it, then, that the UPS is only intended to allow for an orderly shutdown. How do you handle short power drops? (Please understand that I've never worked professionally with this type of thing but I'm always interested in learning new thing.)
short power drops are not the topic
the problem is to runa UPS battery completly empty deep uncharge is very bad for most batteries
besides the problem that i have seen UPSes after power comes back starting and get completly discharged while the machine booted because before the power managment of the OS take scontrol you have 150W on a typical SyndyBrdige machine while after boot in idle state it takes only 45-55W
this may end in a loop where the battery gets deep uncharged many times and possibly damaged as also the filesystems are not thankful for repeated hard power off due FS check at boot
On 03/06/2013 01:04 PM, Reindl Harald wrote:
short power drops are not the topic
the problem is to runa UPS battery completly empty deep uncharge is very bad for most batteries
As I said, I'm trying to learn. I gather, then, that there's a way for the computers to know when they're running off of the UPS only and that they're set to shut themselves down when the main power's been off for a specified length of time so as to avoid completely discharging the UPS, or causing the problems you described? If so, thank you for helping me learn; if not, feel free to correct me.
And, in any event, kernel panics while shutting down or rebooting are a bad thing.
Am 06.03.2013 22:13, schrieb Joe Zeff:
On 03/06/2013 01:04 PM, Reindl Harald wrote:
short power drops are not the topic
the problem is to runa UPS battery completly empty deep uncharge is very bad for most batteries
As I said, I'm trying to learn. I gather, then, that there's a way for the computers to know when they're running off of the UPS only and that they're set to shut themselves down when the main power's been off for a specified length of time so as to avoid completely discharging the UPS
that is what the UPS software does, make the shutdown before the UPS is completly discharged, but if you look at the topic we have undefined behavior due the kernel panic prvent the last event: power off
[harry@srv-rhsoft:~/Desktop]$ apcaccess APC : 001,036,0925 DATE : 2013-03-06 22:47:36 +0100 HOSTNAME : srv-rhsoft.rhsoft.net VERSION : 3.14.10 (13 September 2011) redhat UPSNAME : srv-rhsoft CABLE : USB Cable DRIVER : USB UPS Driver UPSMODE : Stand Alone STARTTIME: 2013-03-05 11:18:19 +0100 MODEL : Back-UPS BR1200GI STATUS : ONLINE LINEV : 236.0 Volts LOADPCT : 10.0 Percent Load Capacity BCHARGE : 100.0 Percent TIMELEFT : 60.5 Minutes MBATTCHG : 10 Percent MINTIMEL : 10 Minutes MAXTIME : 0 Seconds SENSE : High LOTRANS : 176.0 Volts HITRANS : 288.0 Volts ALARMDEL : 30 seconds BATTV : 27.7 Volts LASTXFER : Automatic or explicit self test NUMXFERS : 0 TONBATT : 0 seconds CUMONBATT: 0 seconds XOFFBATT : N/A SELFTEST : NO STATFLAG : 0x07000008 Status Flag SERIALNO : 3B1040X42713 BATTDATE : 2011-01-12 NOMINV : 230 Volts NOMBATTV : 24.0 Volts NOMPOWER : 720 Watts FIRMWARE : 877.L2 .I USB FW:L2 END APC : 2013-03-06 22:47:38 +0100
On 03/06/2013 01:48 PM, Reindl Harald wrote:
that is what the UPS software does, make the shutdown before the UPS is completly discharged, but if you look at the topic we have undefined behavior due the kernel panic prvent the last event: power off
Thank you. It's always good to learn something new. Alas, I can't help with the undefined behavior, so now that my own question's been answered I'll drop out of the thread and let you get out of your way.
On Wed, 2013-03-06 at 15:42 -0500, William Perkins wrote:
I have two systems with which I am having problems during a shutdown or reboot. Both are x86_64 systems running Fedora-18 (Spherical Cow). In both cases the systems will panic before the shutdown or reboot process is completed and system restarts or powers off. This is a problem because the system that controls the UPS must poweroff to shutdown the UPS during a power failure. If it does not, the UPS powers off after the batteries run down. This is not good for the UPS.
Anyway, this problem will occurs on either of these systems after some time has been spent working on them: running X, Firefox, Liferea, LibreOffice, etc... If you than shutdown apps, close windows and terminate the window manager (FVWM), and than do a shutdown or reboot from the command line. the system will panic before the shutdown/reboot is done with the following sampled lines:
Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100 Pid: 1, comm: shutdown Not tainted 3.7.9-205.fc18.x86_64 #1
I have a similar problem (see the recent discussion on this list titled "System doesn't shut down properly under Fedora-18". The disks aren't synced; but there is no panic message in /var/log/messages.
jon
Am 06.03.2013 22:02, schrieb Jonathan Ryshpan:
I have a similar problem (see the recent discussion on this list titled "System doesn't shut down properly under Fedora-18". The disks aren't synced;
i have seen this a few times on virtual machines with F17
but there is no panic message in /var/log/messages
no wonder - nobody will write to /var/log/messages at the very end of shutdown or at least write it back to disk because the kernel panic will make this impossible
On Wed, 2013-03-06 at 22:06 +0100, Reindl Harald wrote:
Am 06.03.2013 22:02, schrieb Jonathan Ryshpan:
I have a similar problem (see the recent discussion on this list titled "System doesn't shut down properly under Fedora-18". The disks aren't synced;
i have seen this a few times on virtual machines with F17
but there is no panic message in /var/log/messages
no wonder - nobody will write to /var/log/messages at the very end of shutdown or at least write it back to disk because the kernel panic will make this impossible
This makes perfect sense, except how does Mr. Perkins see his panic message? (See the first posting in this thread.)
jon
Am 06.03.2013 22:21, schrieb Jonathan Ryshpan:
On Wed, 2013-03-06 at 22:06 +0100, Reindl Harald wrote:
Am 06.03.2013 22:02, schrieb Jonathan Ryshpan:
I have a similar problem (see the recent discussion on this list titled "System doesn't shut down properly under Fedora-18". The disks aren't synced;
i have seen this a few times on virtual machines with F17
but there is no panic message in /var/log/messages
no wonder - nobody will write to /var/log/messages at the very end of shutdown or at least write it back to disk because the kernel panic will make this impossible
This makes perfect sense, except how does Mr. Perkins see his panic message? (See the first posting in this thread.)
a kernel panic at shutdown is a undefind behavior
only god knows if /var/logs/messages gets written or not you will not have in 100 treis the same result, especially aftr systemd tries to stop services parallel and the order differs each time
On 2013.03.06 16:02, Jonathan Ryshpan wrote:
On Wed, 2013-03-06 at 15:42 -0500, William Perkins wrote:
I have two systems with which I am having problems during a
shutdown or
reboot. Both are x86_64 systems running Fedora-18 (Spherical Cow).
In
both cases the systems will panic before the shutdown or reboot
process
is completed and system restarts or powers off. This is a problem
because
the system that controls the UPS must poweroff to shutdown the UPS
during
a power failure. If it does not, the UPS powers off after the
batteries
run down. This is not good for the UPS.
Anyway, this problem will occurs on either of these systems after
some
time has been spent working on them: running X, Firefox, Liferea,
LibreOffice,
etc... If you than shutdown apps, close windows and terminate the
window
manager (FVWM), and than do a shutdown or reboot from the command
line.
the system will panic before the shutdown/reboot is done with the following sampled lines:
Kernel panic - not syncing: Attempted to kill init!
exitcode=0x00000100
Pid: 1, comm: shutdown Not tainted 3.7.9-205.fc18.x86_64 #1
I have a similar problem (see the recent discussion on this list titled "System doesn't shut down properly under Fedora-18". The disks aren't synced; but there is no panic message in /var/log/messages.
jon
The panic message displays on the console before the system freezes. You need to boot your Fedora system without the "rhgb quiet" at the end of the linux boot line in order to see all of the details, or hit the ESC key at the right point in time during boot or shutdown.
This is the panic I get at shutdown on two different systems: ---- Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
Pid: 1, comm: shutdown Not tainted 3.8.1-201.fc18.x86_64 #1 Call Trace: [<ffffffff81645b9e>] panic+0xc1/0x1d0 [<ffffffff810647a8>] do_exit_0x918/0x9e0 [<ffffffff810648ff>] do_group_exit+0x3f/0xa0 [<ffffffff81064977>] sys_exit_group_0x17/0x20 [<ffffffff81657c19>] system_call_fastpath+0x16/0x1b drm_kms_helper: panic occurred, switching back to text console ----
I had to photograph the screen and than type this information into this message.
Bill
On Thu, 2013-03-07 at 15:17 -0500, Bill Perkins wrote:
The panic message displays on the console before the system freezes. You need to boot your Fedora system without the "rhgb quiet" at the end of the linux boot line in order to see all of the details, or hit the ESC key at the right point in time during boot or shutdown.
Removing "rhgb quiet" from the boot line is a very good idea. It's a lot more fun to watch the messages flash by under the 4 penguins than to watch a more or less empty screen. Unfortunately, the system puts the monitor to sleep after system shutdown, and the screen goes blank. I *think* I see messages about unmounting file systems and that I don't see a panic message, but I'm not sure.
I'll try to find a monitor setting to keep the screen from going blank when it receives no signal. Any advice would be welcome: the monitor is an Acer P243W)
Thanks - jon
On 2013.03.07 18:21, Jonathan Ryshpan wrote:
On Thu, 2013-03-07 at 15:17 -0500, Bill Perkins wrote:
The panic message displays on the console before the system
freezes.
You need to boot your Fedora system without the "rhgb quiet" at the
end
of the linux boot line in order to see all of the details, or hit
the
ESC key at the right point in time during boot or shutdown.
Removing "rhgb quiet" from the boot line is a very good idea. It's a lot more fun to watch the messages flash by under the 4 penguins than to watch a more or less empty screen. Unfortunately, the system puts the monitor to sleep after system shutdown, and the screen goes blank. I *think* I see messages about unmounting file systems and that I don't see a panic message, but I'm not sure.
I'll try to find a monitor setting to keep the screen from going blank when it receives no signal. Any advice would be welcome: the monitor is an Acer P243W)
Thanks - jon
Jon,
Try tapping the shift key periodically during the shutdown and the screen should stay lit. Once the system freezes with the panic message, the screen may not go to sleep again until you reset the system.
Bill
On Thu, 2013-03-07 at 18:35 -0500, Bill Perkins wrote:
On 2013.03.07 18:21, Jonathan Ryshpan wrote:
On Thu, 2013-03-07 at 15:17 -0500, Bill Perkins wrote:
The panic message displays on the console before the system freezes.
You need to boot your Fedora system without the "rhgb quiet" at the end of the linux boot line in order to see all of the details, or hit the ESC key at the right point in time during boot or shutdown.
Removing "rhgb quiet" from the boot line is a very good idea. It's a lot more fun to watch the messages flash by under the 4 penguins than to watch a more or less empty screen. Unfortunately, the system puts the monitor to sleep after system shutdown, and the screen goes blank. I *think* I see messages about unmounting file systems and that I don't see a panic message, but I'm not sure.
I'll try to find a monitor setting to keep the screen from going blank when it receives no signal. Any advice would be welcome: the monitor is an Acer P243W)
Try tapping the shift key periodically during the shutdown and the screen should stay lit. Once the system freezes with the panic message, the screen may not go to sleep again until you reset the system.
If only... Tried tapping SHIFT lots of times during a couple of halts without result. Looked at the BIOS setup to see if there's anything relevant, nope. Similarly nothing obvious in the monitor manual.
jon
-
Bill Perkins -
Joe Zeff -
Jonathan Ryshpan -
Reindl Harald -
William Perkins