Nut will monitor the ups and shutdown Linux when the ups goes to low
battery as it should. But the UPS is not shut down so the system will
restart when the power is restored. If I switch the UPS off , restore
power and switch the UPS on the system will restart. I have not been
able to get nut to switch the UPS off after it brings the system down. I
can get the UPS to switch off with upscmd load.off. So the UPS can be
controlled. Here is my SHUTDOWNCMD:
SHUTDOWNCMD "/sbin/shutdown now -P"
I also tried:
SHUTDOWNCMD "/sbin/shutdown now -h"
I found this script in /etc/init.d/nut and changed the paths to upsd and
upsmon and used it.
#! /bin/sh
#
# nut - Script to start and stop Network UPS Tools daemons
PATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/local/sbin:/usr/local/bin
NAME=nut
DESC="Network UPS Tools"
DEFAULT=/etc/default/nut
[ -f $DEFAULT ] || exit 0
. $DEFAULT
pid_dir=/var/run/nut
upsmon_pid=${pid_dir}/upsmon.pid
upsd_pid=${pid_dir}/upsd.pid
upsd=/usr/local/ups/sbin/upsd
upsmon=/usr/local/ups/sbin/upsmon
upsdrvctl=/usr/local/ups/bin/upsdrvctl
log=">/dev/null 2>/dev/null"
# Check if /var/run/nut exists and has the correct perms
check_var_directory() {
[ ! -d ${pid_dir} ] && mkdir -p ${pid_dir} \
&& chown root:nut ${pid_dir} \
&& chmod 770 ${pid_dir}
}
start_stop_server () {
case "$START_UPSD" in
y|Y|yes|YES|Yes)
case "$1" in
start)
! $upsdrvctl start >/dev/null 2>&1 && \
echo -n " (upsdrvctl failed)"
start-stop-daemon -S -q -p $upsd_pid -x $upsd >/dev/null
2>&1
;;
stop)
start-stop-daemon -K -o -q -p $upsd_pid -n upsd >/dev/null
2>&1
! $upsdrvctl stop >/dev/null 2>&1 && \
echo -n " (upsdrvctl failed)"
;;
esac
;;
n|N|no|NO|No|*)
return 1
;;
esac
}
start_stop_client () {
case "$START_UPSMON" in
y|Y|yes|YES|Yes)
case "$1" in
start)
start-stop-daemon -S -q -p $upsmon_pid -x $upsmon >/dev/null
2>&1
;;
stop)
start-stop-daemon -K -o -q -p $upsmon_pid -n upsmon >/dev/null
2>&1
;;
esac
;;
n|N|no|NO|No|*)
return 1
;;
esac
}
case "$1" in
start)
echo -n "Starting $DESC:"
check_var_directory
start_stop_server start && echo -n " upsd"
start_stop_client start && echo -n " upsmon"
echo "."
;;
stop)
echo -n "Stopping $DESC:"
start_stop_server stop && echo -n " upsd"
start_stop_client stop && echo -n " upsmon"
echo "."
;;
reload)
$upsd -c reload >/dev/null 2>&1
$upsmon -c reload >/dev/null 2>&1
;;
restart|force-reload)
echo -n "Restarting $DESC:"
start_stop_client stop
start_stop_server stop
sleep 5
check_var_directory
start_stop_server start && echo -n " upsd"
start_stop_client start && echo -n " upsmon"
echo "."
;;
poweroff)
flag=`sed -ne 's#^ *POWERDOWNFLAG *\(.*\)$#\1#p'
usr/local/ups/etc/upsmon.conf`
wait_delay=`sed -ne 's#^ *POWEROFF_WAIT= *\(.*\)$#\1#p'
/etc/default/nut`
if [ -f "$flag" ] ; then
if $upsmon -K >/dev/null 2>&1 ; then
echo "Shutting down the UPS ..."
sleep 1
if $upsdrvctl shutdown ; then
sleep 5
echo -n "Waiting for UPS to cut the power"
else
echo "Shutdown failed."
echo -n "Waiting for UPS batteries to run down"
fi
if [ "$wait_delay" ] ; then
echo " (will reboot after $wait_delay) ..."
sleep "$wait_delay"
/etc/init.d/reboot
fi
else
echo "Power down flag is not set (UPS shutdown not needed)"
fi
else
if [ -z "$flag" ] ; then
echo
"##########################################################"
echo "## POWERDOWNFLAG is not defined in /etc/nut/upsmon.conf
##"
echo "##
##"
echo "## Please read the Manual page upsmon.conf(5)
##"
echo
"##########################################################"
fi
fi
;;
*)
N=/etc/init.d/$NAME
echo "Usage: $N {start|stop|reload|restart|force-reload|poweroff}"
>&2
exit 1
;;
esac
exit 0
Since I do not have much knowledge on how the Linux system boots and
shutdown I have spent the last several days searching for how the scrips
/etc/init.d are supposed to work but every thing I have found is a
little different than what I find on my Ubuntu system. Does this script
ever get called with poweroff?
I am using nut 2.0.5 driver newhidups Doug Reynolds wrote:> Gary Redden wrote: >> Nut will monitor the ups and shutdown Linux when the ups goes to low >> battery as it should. But the UPS is not shut down so the system will >> restart when the power is restored. If I switch the UPS off , restore >> power and switch the UPS on the system will restart. I have not been >> able to get nut to switch the UPS off after it brings the system >> down. I can get the UPS to switch off with upscmd load.off. So the >> UPS can be controlled. Here is my SHUTDOWNCMD: >> SHUTDOWNCMD "/sbin/shutdown now -P" >> I also tried: >> SHUTDOWNCMD "/sbin/shutdown now -h" > > Refresh my memory, which driver are you using, and the version? >
Doug Reynolds
2007-Feb-06 18:35 UTC
[Nut-upsuser] Shutdown problem with Geek Squad GS1285U
Gary Redden wrote:> Nut will monitor the ups and shutdown Linux when the ups goes to low > battery as it should. But the UPS is not shut down so the system will > restart when the power is restored. If I switch the UPS off , restore > power and switch the UPS on the system will restart. I have not been > able to get nut to switch the UPS off after it brings the system down. I > can get the UPS to switch off with upscmd load.off. So the UPS can be > controlled. Here is my SHUTDOWNCMD: > SHUTDOWNCMD "/sbin/shutdown now -P" > I also tried: > SHUTDOWNCMD "/sbin/shutdown now -h"Refresh my memory, which driver are you using, and the version?
Peter Selinger
2007-Feb-06 18:51 UTC
[Nut-upsuser] Shutdown problem with Geek Squad GS1285U
For NUT to switch off your UPS at the end of the shutdown sequence, you have to edit your shutdown scripts. See INSTALL, "Configuring shutdowns for low battery events", item 11 "Edit your shutdown scripts: add upsdrvctl shutdown". -- Peter Gary Redden wrote:> > Nut will monitor the ups and shutdown Linux when the ups goes to low > battery as it should. But the UPS is not shut down so the system will > restart when the power is restored. If I switch the UPS off , restore > power and switch the UPS on the system will restart. I have not been > able to get nut to switch the UPS off after it brings the system down. I > can get the UPS to switch off with upscmd load.off. So the UPS can be > controlled. Here is my SHUTDOWNCMD: > SHUTDOWNCMD "/sbin/shutdown now -P" > I also tried: > SHUTDOWNCMD "/sbin/shutdown now -h" > I found this script in /etc/init.d/nut and changed the paths to upsd and > upsmon and used it. > #! /bin/sh > # > # nut - Script to start and stop Network UPS Tools daemons > > PATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/local/sbin:/usr/local/bin > NAME=nut > DESC="Network UPS Tools" > DEFAULT=/etc/default/nut > > [ -f $DEFAULT ] || exit 0 > . $DEFAULT > > pid_dir=/var/run/nut > upsmon_pid=${pid_dir}/upsmon.pid > upsd_pid=${pid_dir}/upsd.pid > upsd=/usr/local/ups/sbin/upsd > upsmon=/usr/local/ups/sbin/upsmon > upsdrvctl=/usr/local/ups/bin/upsdrvctl > log=">/dev/null 2>/dev/null" > > # Check if /var/run/nut exists and has the correct perms > check_var_directory() { > [ ! -d ${pid_dir} ] && mkdir -p ${pid_dir} \ > && chown root:nut ${pid_dir} \ > && chmod 770 ${pid_dir} > } > > start_stop_server () { > case "$START_UPSD" in > y|Y|yes|YES|Yes) > case "$1" in > start) > ! $upsdrvctl start >/dev/null 2>&1 && \ > echo -n " (upsdrvctl failed)" > start-stop-daemon -S -q -p $upsd_pid -x $upsd >/dev/null 2>&1 > ;; > stop) > start-stop-daemon -K -o -q -p $upsd_pid -n upsd >/dev/null 2>&1 > ! $upsdrvctl stop >/dev/null 2>&1 && \ > echo -n " (upsdrvctl failed)" > ;; > esac > ;; > n|N|no|NO|No|*) > return 1 > ;; > esac > } > > start_stop_client () { > case "$START_UPSMON" in > y|Y|yes|YES|Yes) > case "$1" in > start) > start-stop-daemon -S -q -p $upsmon_pid -x $upsmon >/dev/null 2>&1 > ;; > stop) > start-stop-daemon -K -o -q -p $upsmon_pid -n upsmon >/dev/null > 2>&1 > ;; > esac > ;; > n|N|no|NO|No|*) > return 1 > ;; > esac > } > > case "$1" in > > start) > echo -n "Starting $DESC:" > check_var_directory > start_stop_server start && echo -n " upsd" > start_stop_client start && echo -n " upsmon" > echo "." > ;; > > stop) > echo -n "Stopping $DESC:" > start_stop_server stop && echo -n " upsd" > start_stop_client stop && echo -n " upsmon" > echo "." > ;; > > reload) > $upsd -c reload >/dev/null 2>&1 > $upsmon -c reload >/dev/null 2>&1 > ;; > > restart|force-reload) > echo -n "Restarting $DESC:" > start_stop_client stop > start_stop_server stop > sleep 5 > check_var_directory > start_stop_server start && echo -n " upsd" > start_stop_client start && echo -n " upsmon" > echo "." > ;; > > poweroff) > flag=`sed -ne 's#^ *POWERDOWNFLAG *\(.*\)$#\1#p' > usr/local/ups/etc/upsmon.conf` > wait_delay=`sed -ne 's#^ *POWEROFF_WAIT= *\(.*\)$#\1#p' > /etc/default/nut` > if [ -f "$flag" ] ; then > if $upsmon -K >/dev/null 2>&1 ; then > echo "Shutting down the UPS ..." > sleep 1 > if $upsdrvctl shutdown ; then > sleep 5 > echo -n "Waiting for UPS to cut the power" > else > echo "Shutdown failed." > echo -n "Waiting for UPS batteries to run down" > fi > if [ "$wait_delay" ] ; then > echo " (will reboot after $wait_delay) ..." > sleep "$wait_delay" > /etc/init.d/reboot > fi > else > echo "Power down flag is not set (UPS shutdown not needed)" > fi > else > if [ -z "$flag" ] ; then > echo "##########################################################" > echo "## POWERDOWNFLAG is not defined in /etc/nut/upsmon.conf ##" > echo "## ##" > echo "## Please read the Manual page upsmon.conf(5) ##" > echo "##########################################################" > fi > fi > ;; > > *) > N=/etc/init.d/$NAME > echo "Usage: $N {start|stop|reload|restart|force-reload|poweroff}" >&2 > exit 1 > ;; > > esac > > exit 0 > Since I do not have much knowledge on how the Linux system boots and > shutdown I have spent the last several days searching for how the scrips > /etc/init.d are supposed to work but every thing I have found is a > little different than what I find on my Ubuntu system. Does this script > ever get called with poweroff? > > _______________________________________________ > Nut-upsuser mailing list > Nut-upsuser@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser >
Eric Ashley
2007-Feb-06 23:10 UTC
[Nut-upsuser] Re: Shutdown problem with Geek Squad GS1285U
Hi Gary,
You're probably looking for /etc/init.d/halt. You'd want to call
'upsdrvctl shutdown' just before the final halt but after any mounted
filesystems have been remounted read-only. My Fedora Core 3 system has
the following nut shutdown code after the remount and display of
reboot/halt/fsck forced message but before /sbin/halt.local gets
called:
------ sample /etc/init.d/halt NUT shutdown code -----
if [ "$command" = /sbin/halt -a -r /etc/ups/upsmon.conf -a \
-f /etc/killpower -a -f /etc/sysconfig/ups ] ; then
. /etc/sysconfig/ups
if [ "$SERVER" = "yes" -a "$MODEL" =
"upsdrvctl" ] ; then
/sbin/upsdrvctl shutdown
elif [ "$SERVER" = "yes" -a "$MODEL" !=
"NONE" -a \
-n "$MODEL" -a -n "$DEVICE" ] ; then
$MODEL $OPTIONS_HALT -k $DEVICE
fi
fi
----- end sample -----
Either ensure that there are no spaces after the \ characters at the
end of the 2 lines above or remove them and join the lines their on
with the line immediately following. Hope this helps.
Best regards,
Eric
____________________________________________________________________________________
Any questions? Get answers on any topic at www.Answers.yahoo.com. Try it now.
I am still not able to get the UPS to shutdown. Here is a list of rc0.d
and the file I created to shutdown the UPS after umountroot mounts the
filesystem read-only and before halt (halt seems to be a no op here. No
code under the start case).
gary@redden-p700-610:~$ cd /etc/rc0.d
gary@redden-p700-610:/etc/rc0.d$ ls -l
total 4
lrwxrwxrwx 1 root root 13 2007-01-26 11:13 K01gdm -> ../init.d/gdm
lrwxrwxrwx 1 root root 17 2007-01-26 11:13 K01usplash -> ../init.d/usplash
lrwxrwxrwx 1 root root 17 2007-01-26 11:58 K19camserv -> ../init.d/camserv
lrwxrwxrwx 1 root root 15 2007-01-26 11:13 K19hplip -> ../init.d/hplip
lrwxrwxrwx 1 root root 15 2007-01-28 17:43 K19samba -> ../init.d/samba
lrwxrwxrwx 1 root root 14 2007-01-26 11:13 K20dbus -> ../init.d/dbus
lrwxrwxrwx 1 root root 13 2007-01-26 11:57 K20nut -> ../init.d/nut
lrwxrwxrwx 1 root root 21 2007-02-01 13:05 K20ups-monitor ->
../init.d/ups-monitor
lrwxrwxrwx 1 root root 20 2007-01-26 11:13 K25hwclock.sh ->
../init.d/hwclock.sh
lrwxrwxrwx 1 root root 20 2007-01-26 11:13 K50alsa-utils ->
../init.d/alsa-utils
lrwxrwxrwx 1 root root 17 2007-01-26 11:52 K91apache2 -> ../init.d/apache2
-rw-r--r-- 1 root root 355 2006-10-06 07:34 README
lrwxrwxrwx 1 root root 41 2007-01-26 11:13
S01linux-restricted-modules-common ->
../init.d/linux-restricted-modules-common
lrwxrwxrwx 1 root root 22 2007-01-26 11:13 S15wpa-ifupdown ->
../init.d/wpa-ifupdown
lrwxrwxrwx 1 root root 18 2007-01-26 11:13 S20sendsigs ->
../init.d/sendsigs
lrwxrwxrwx 1 root root 17 2007-01-26 11:13 S30urandom -> ../init.d/urandom
lrwxrwxrwx 1 root root 22 2007-01-26 11:13 S31umountnfs.sh ->
../init.d/umountnfs.sh
lrwxrwxrwx 1 root root 18 2007-01-26 11:13 S40umountfs ->
../init.d/umountfs
lrwxrwxrwx 1 root root 20 2007-01-26 11:13 S60umountroot ->
../init.d/umountroot
lrwxrwxrwx 1 root root 22 2007-02-07 15:29 S89ups-shutdown ->
../init.d/ups-shutdown
lrwxrwxrwx 1 root root 14 2007-01-26 11:13 S90halt -> ../init.d/halt
gary@redden-p700-610:/etc/rc0.d$ cd /etc/init.d
gary@redden-p700-610:/etc/init.d$ cat ups-shutdown
#! /bin/sh
#
# nut - Script to Shutdown UPS if line power is lost & low battery
PATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/local/sbin:/usr/local/bin
NAME=ups-shutdown
DESC="UPS Shutdown"
DEFAULT=/etc/default/nut
[ -f $DEFAULT ] || exit 0
. $DEFAULT
upsdrvctl=/usr/local/ups/bin/upsdrvctl
log=">/dev/null 2>/dev/null"
case "$1" in
start)
echo -n "Starting $DESC:"
flag=`sed -ne 's#^ *POWERDOWNFLAG *\(.*\)$#\1#p'
usr/local/ups/etc/upsmon.conf`
wait_delay=`sed -ne 's#^ *POWEROFF_WAIT= *\(.*\)$#\1#p'
/etc/default/nut`
if [ -f "$flag" ] ; then
if [ $upsdrvctl shutdown >/dev/null ] ; then
echo -n "Waiting for UPS to cut the power"
sleep 5
else
echo "Shutdown failed."
echo -n "Waiting for UPS batteries to run down"
sleep 10
fi
if [ "$wait_delay" ] ; then
echo " (will reboot after $wait_delay) ..."
sleep "$wait_delay"
/etc/init.d/reboot
fi
else
echo "Power down flag is not set (UPS shutdown not needed)"
fi
;;
stop)
;;
*)
N=/etc/init.d/$NAME
echo "Usage: $N {start|stop}" >&2
exit 1
;;
esac
exit 0
gary@redden-p700-610:/etc/init.d$
Charles Lepple
2007-Feb-08 03:39 UTC
[Nut-upsuser] Shutdown problem with Geek Squad GS1285U
On 2/7/07, Gary Redden <redden@skybest.com> wrote:> I am still not able to get the UPS to shutdown. Here is a list of rc0.d > and the file I created to shutdown the UPS after umountroot mounts the > filesystem read-only and before halt (halt seems to be a no op here. No > code under the start case).Which Ubuntu release is this, and do you see any error messages logged? -- - Charles Lepple
I have attached a section of my syslog. It seems to say that newhidups had a problem on the shutdown part of a restart. But before that upsd is still running after newhidups has exited. This might be causing the paging error. My script tries to shut down upsd before it runs upsdrvctl stop. Am I reading this correctly? This happens when I test the shutdown also and may bypass some of the code in the scripts because the error. Also, Peter the scripts in rc0.d are handled different than the others. The Knn.. scripts are called with stop and then the Snn.. scripts are called with stop (not start as in the other rcn.d directories). The halt script had code that should shutdown the ups. There is a bug in there somewhere that I have not found. The scripts came from the package for nut-2.0.4 on Ubuntu 6.10. I had to change the paths to the 2.0.5 executiables and conf files. I need to find who created the scripts. -------------- next part -------------- Feb 18 14:57:47 ubuntu-desk-610 gconfd (root-4754): GConf server is not in use, shutting down. Feb 18 14:57:47 ubuntu-desk-610 gconfd (root-4754): Exiting Feb 18 14:57:51 ubuntu-desk-610 gconfd (gary-4596): Exiting Feb 18 14:57:51 ubuntu-desk-610 gdm[3774]: Restarting computer... Feb 18 14:57:53 ubuntu-desk-610 init: tty1 process (3542) killed by signal 15 Feb 18 14:57:53 ubuntu-desk-610 init: tty2 process (3543) killed by signal 15 Feb 18 14:57:53 ubuntu-desk-610 init: tty3 process (3544) killed by signal 15 Feb 18 14:57:53 ubuntu-desk-610 init: tty4 process (3545) killed by signal 15 Feb 18 14:57:53 ubuntu-desk-610 init: tty5 process (3546) killed by signal 15 Feb 18 14:57:53 ubuntu-desk-610 init: tty6 process (3547) killed by signal 15 Feb 18 14:57:57 ubuntu-desk-610 hcid[4403]: Got disconnected from the system message bus Feb 18 14:57:57 ubuntu-desk-610 newhidups[4318]: Signal 15: exiting Feb 18 14:57:57 ubuntu-desk-610 upsd[4320]: UPS [GeekSquad1] disconnected - check driver Feb 18 14:57:57 ubuntu-desk-610 upsd[4320]: Can't connect to UPS [GeekSquad1] (GeekSquad1): Connection refused Feb 18 14:57:57 ubuntu-desk-610 upsd[4320]: Data for UPS [GeekSquad1] is stale - check driver Feb 18 14:57:57 ubuntu-desk-610 kernel: [ 1504.784748] BUG: unable to handle kernel paging request at virtual address 76697264 Feb 18 14:57:57 ubuntu-desk-610 kernel: [ 1504.784767] printing eip: Feb 18 14:57:57 ubuntu-desk-610 kernel: [ 1504.784772] c01abb38 Feb 18 14:57:57 ubuntu-desk-610 kernel: [ 1504.784777] *pde = 00000000 Feb 18 14:57:57 ubuntu-desk-610 kernel: [ 1504.784784] Oops: 0000 [#1] Feb 18 14:57:57 ubuntu-desk-610 kernel: [ 1504.784789] SMP Feb 18 14:57:57 ubuntu-desk-610 kernel: [ 1504.784795] Modules linked in: binfmt_misc rfcomm l2cap bluetooth apm speedstep_lib cpufreq_userspace cpufreq_stats freq_table cpufreq_powersave cpufreq_ondemand cpufreq_conservative af_packet lp stv680 compat_ioctl32 ipv6 videodev usbhid tsdev snd_emu10k1_synth snd_emux_synth snd_seq_virmidi snd_seq_midi_emul snd_seq_dummy snd_seq_oss parport_pc snd_seq_midi snd_seq_midi_event snd_seq parport evdev floppy serio_raw snd_emu10k1 snd_rawmidi snd_ac97_codec snd_ac97_bus psmouse snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_device snd_timer snd_page_alloc snd_util_mem snd_hwdep pcspkr emu10k1_gp gameport snd intel_agp soundcore i2c_piix4 agpgart r8169 shpchp pci_hotplug i2c_core ext3 jbd uhci_hcd usbcore ide_generic ide_cd cdrom ide_disk piix generic processor fbcon tileblit font bitblit softcursor vesafb capability commoncap Feb 18 14:57:57 ubuntu-desk-610 kernel: [ 1504.784919] CPU: 0 Feb 18 14:57:57 ubuntu-desk-610 kernel: [ 1504.784922] EIP: 0060:[sysfs_hash_and_remove+88/256] Not tainted VLI Feb 18 14:57:57 ubuntu-desk-610 kernel: [ 1504.784926] EFLAGS: 00010246 (2.6.17-10-generic #2) Feb 18 14:57:57 ubuntu-desk-610 kernel: [ 1504.784945] EIP is at sysfs_hash_and_remove+0x58/0x100 Feb 18 14:57:57 ubuntu-desk-610 kernel: [ 1504.784955] eax: 76697264 ebx: d2bc34e0 ecx: d3486d40 edx: 00000020 Feb 18 14:57:57 ubuntu-desk-610 kernel: [ 1504.784965] esi: 76697264 edi: d76c0690 ebp: d2bc34dc esp: d2a2bf1c Feb 18 14:57:57 ubuntu-desk-610 kernel: [ 1504.784973] ds: 007b es: 007b ss: 0068 Feb 18 14:57:57 ubuntu-desk-610 kernel: [ 1504.784982] Process newhidups (pid: 4318, threadinfo=d2a2a000 task=d7739050) Feb 18 14:57:57 ubuntu-desk-610 kernel: [ 1504.784988] Stack: d76c0690 c3d55e7c c3d3bf64 d76c068c d76c0614 d88ba108 d88b98dc c0245dff Feb 18 14:57:57 ubuntu-desk-610 kernel: [ 1504.785009] d76c0614 d76c0614 d128fde0 c02460ec d76c0600 d889abc7 d75a4800 00000000 Feb 18 14:57:57 ubuntu-desk-610 kernel: [ 1504.785029] d88a505a d128fde0 00000000 d75a4800 d3bf994c d88a7f5a 00000008 d7673500 Feb 18 14:57:57 ubuntu-desk-610 kernel: [ 1504.785048] Call Trace: Feb 18 14:57:57 ubuntu-desk-610 kernel: [ 1504.785070] <c0245dff> __device_release_driver+0x2f/0xa0 <c02460ec> device_release_driver+0x1c/0x30 Feb 18 14:57:57 ubuntu-desk-610 kernel: [ 1504.785105] <d889abc7> usb_driver_release_interface+0x77/0x80 [usbcore] <d88a505a> releaseintf+0x9a/0xa0 [usbcore] Feb 18 14:57:57 ubuntu-desk-610 kernel: [ 1504.785242] <d88a7f5a> usbdev_release+0x9a/0x9f [usbcore] <c016b95b> __fput+0x9b/0x1a0 Feb 18 14:57:57 ubuntu-desk-610 kernel: [ 1504.785317] <c0168b27> filp_close+0x47/0x80 <c016a216> sys_close+0x56/0xa0 Feb 18 14:57:57 ubuntu-desk-610 kernel: [ 1504.785342] <c0102fbb> sysenter_past_esp+0x54/0x79 Feb 18 14:57:57 ubuntu-desk-610 kernel: [ 1504.785382] Code: 83 ed 04 8b 45 04 0f 18 00 90 83 c6 0c 8d 5d 04 39 de 89 74 24 08 74 3d 8b 4d 14 85 c9 74 20 89 e8 e8 5d ff ff ff 8b 3c 24 89 c6 <ac> ae 75 08 84 c0 75 f8 31 c0 eb 04 19 c0 0c 01 85 c0 74 34 8b Feb 18 14:57:57 ubuntu-desk-610 kernel: [ 1504.785465] EIP: [sysfs_hash_and_remove+88/256] sysfs_hash_and_remove+0x58/0x100 SS:ESP 0068:d2a2bf1c Feb 18 14:57:59 ubuntu-desk-610 exiting on signal 15 Feb 18 14:59:33 ubuntu-desk-610 syslogd 1.4.1#18ubuntu6: restart.
Arjen de Korte
2007-Feb-19 16:57 UTC
[Nut-upsuser] Shutdown problem with Geek Squad GS1285U
> I have attached a section of my syslog. It seems to say that newhidups > had a problem on the shutdown part of a restart. But before that upsd is > still running after newhidups has exited.That is bad. It looks a lot like neither upsd, nor the driver have been properly stopped before receiving SIGTERM. Could it be that they are called too late in the shutdown sequence (if at all?) Best regards, Arjen -- Eindhoven - The Netherlands Key fingerprint - 66 4E 03 2C 9D B5 CB 9B 7A FE 7E C1 EE 88 BC 57
I do not have enough knowledge of Linux to answer those questions. I am running Ubuntu desktop the GUI version so I must be running some nVidia driver. I run the GUI version so I can poke around faster. I have spent most of three weeks getting this far. I will continue to work on this but need to be pointed in the right direction. I have another project that needs most my attention for the next week(spec. for a fire truck for my volunteer fire department) but will work on this in my spare time. Charles Lepple wrote:> On 2/19/07, Gary Redden <redden@skybest.com> wrote: >> >> Feb 18 14:57:57 ubuntu-desk-610 kernel: [ 1504.784748] BUG: unable >> to handle kernel paging request at virtual address 76697264 >> >> Feb 18 14:57:57 ubuntu-desk-610 kernel: [ 1504.784767] printing eip: >> >> Feb 18 14:57:57 ubuntu-desk-610 kernel: [ 1504.784772] c01abb38 >> >> Feb 18 14:57:57 ubuntu-desk-610 kernel: [ 1504.784777] *pde = >> 00000000 >> >> Feb 18 14:57:57 ubuntu-desk-610 kernel: [ 1504.784784] Oops: 0000 >> [#1] >> >> Feb 18 14:57:57 ubuntu-desk-610 kernel: [ 1504.784789] SMP > > Two things: > > 1) Can you reproduce this if you disable SMP? > > 2) Do I read this right that it still happens without the nVidia > binary driver loaded? > > If either of the above is true, then you have a case for a bug in the > Linux USB stack. > > Nothing that we do from userspace should cause a kernel page fault. >