Ubuntu
upstart package

reboot: noisy if /proc/ide doesn't exist

Bug #92685 reported by Colin Watson on 2007-03-15

This bug affects 3 people

Affects		Status	Importance	Assigned to	Milestone
	upstart	Fix Released	Wishlist	Scott James Remnant (Canonical)	upstart 0.6.0 "How appropriate, you fight like a cow"
	upstart (Ubuntu)	Fix Released	Wishlist	Unassigned
Nominated for Jaunty by Martin Plaček

Bug Description

Binary package hint: upstart

On a system with no IDE controller and thus no /proc/ide, I get this on shutdown:

halt: Unable to iterate IDE devices: No such file or directory

/etc/init.d/halt always uses 'halt -h' unless you're using RAID. Maybe it should avoid that if /proc/ide is missing? Or maybe this code should just be removed from upstart:

22:52 <cjwatson> ps3 doesn't seem to have an IDE controller; is upstart's warning message about that too loud maybe?
23:04 <Keybuk> err?
23:04 <Keybuk> upstart shouldn't have a warning about that
23:04 <Keybuk> what warning are you seeing?
23:04 <Keybuk> (why would upstart need an IDE controller?)
23:05 <cjwatson> "halt: Unable to iterate IDE devices: No such file or directory"
23:06 <Keybuk> oh
23:06 <Keybuk> heh
23:06 <Keybuk> interesting question of style that one
23:07 <Keybuk> since you did call halt with -h ("put disks into standby"), it seems potentially wrong to not warn that it didn't work
23:07 <Keybuk> (as apposed to default behaviour)
23:07 <Keybuk> doesn't sysvinit do the same?
23:07 <cjwatson> I have no idea, never run sysvinit on this machine
23:08 <Keybuk> I'm determined that that option is entirely pointless
23:08 <Keybuk> but too scared to find out :p
23:08 <Keybuk> both downing drives and interfaces should be things the kernel does these days
23:09 <Keybuk> file a bug plz :p
23:09 <cjwatson> maybe /etc/init.d/halt should check whether /proc/ide exists before using -h
23:10 <cjwatson> sysvinit's halt man page says that the kernel doesn't flush the write cache itself before poweroff
23:10 <cjwatson> and that that's the side-effectual purpose of putting the drive in standby
23:12 <Keybuk> kernel source disagrees
23:12 <Keybuk> ide_device_shutdown calls ide_cacheflush_p()
23:12 <cjwatson> yeah, could be a more recent change
23:13 <Keybuk> the sysvinit halt manpage is what, 5 years old?
23:13 <cjwatson> dated Nov 6, 2001
23:17 <Keybuk> I'll get Ben to tell me for sure whether that's needed anymore, I'm not 100% sure, or fix the warning on missing /proc/ide

Related branches

lp:~ubuntu-core-dev/upstart/ubuntu

lp:ubuntu/lucid/upstart

Scott James Remnant (Canonical) (canonical-scott) on 2007-03-20

Changed in upstart:
importance:	Undecided → Wishlist
status:	Unconfirmed → Confirmed

Scott James Remnant (Canonical) (canonical-scott) on 2007-03-28

Changed in upstart:
importance:	Undecided → Wishlist
status:	Unconfirmed → Confirmed

Revision history for this message

Scott James Remnant (Canonical) (canonical-scott) wrote on 2007-05-23:

Rejecting Ubuntu task since this is an upstream problem.

Interestingly we've read through the kernel source, and are now convinced that the IDE subsystem does flush the caches and power down the disks on halt.

And we've had a long conversation with the libata maintainers, who have made the same changes to libata so it too flushes caches and powers down the disks.

So reboot needs to do none of this.

Changed in upstart:
status:	Confirmed → Rejected

Scott James Remnant (Canonical) (canonical-scott) on 2007-10-08

Changed in upstart:
status:	Confirmed → Triaged

Scott James Remnant (Canonical) (canonical-scott) on 2008-08-14

Changed in upstart:
milestone:	0.5 → none

Scott James Remnant (Canonical) (canonical-scott) on 2008-10-24

Changed in upstart:
status:	Invalid → Triaged

Scott James Remnant (Canonical) (canonical-scott) on 2009-01-29

Changed in upstart:
milestone:	none → 0.5-later

Revision history for this message

Martin Plaček (placek-martin) wrote on 2009-04-16:

/etc/init.d/halt Edit (1.3 KiB, text/plain)

I have this problem too and it helped mi to edit the file called "halt".

Revision history for this message

Renato Candido (renatocan) wrote on 2009-04-27:

I also have this problem. Everytime I shut down Ubuntu I have to press a key in order to turn off the computer.

Revision history for this message

Ralf Jung (ralfjung-e) wrote on 2009-05-01:

I've got the same issue in Kubuntu Jaunty, too. The PC shuts down normally, but that message indicates that something is wrong and I have no clue if that is the case or not.

Revision history for this message

Bo Lundberg (bo-lundberg) wrote on 2009-06-13:

Same problem in Kubuntu 9.04. Same message show up before shutdown. Same problem in Ubuntu 9.04 but there is now message.
In both cases everything seems to shut down ok. except the mouse and KVM switch.
So with the computer turned off the mouse and KVM switch is still active. The only way around this seems to be use of the psu switch.

Scott James Remnant (Canonical) (canonical-scott) on 2009-06-18

Changed in upstart:
milestone:	0.5-later → none
summary:	- noisy halt if /proc/ide doesn't exist + reboot: noisy if /proc/ide doesn't exist

Scott James Remnant (Canonical) (canonical-scott) on 2009-07-08

Changed in upstart:
status:	Triaged → Fix Committed

Revision history for this message

Scott James Remnant (Canonical) (canonical-scott) wrote on 2009-07-09:

Preparing packages of Upstart 0.6.0 for karmic

Changed in upstart (Ubuntu):
status:	Triaged → In Progress

Scott James Remnant (Canonical) (canonical-scott) on 2009-07-09

Changed in upstart:
milestone:	none → 0.6.0

Revision history for this message

Scott James Remnant (Canonical) (canonical-scott) wrote on 2009-07-09:

Download full text (6.7 KiB)

This has been fixed in Upstart 0.6.0.

0.6.0 2009-07-09 "How appropriate, you fight like a cow"

* The licence for Upstart has been changed back to version 2 of the
GNU GPL.

* D-Bus 1.2.15 is now required, this is the current GIT HEAD
pending a 1.2.16 release.

* Configuration paths have changed. Global configuration now
resides in "/etc/init.conf" while jobs are now configured in
"/etc/init"

* Job configuration filenames must now end in ".conf"

* Default configuration files are now supplied in the "conf"
sub-directory of the source, and installed into "/etc/init".

   These match the Debian/Ubuntu sysvinit configuration so may
   require some tweaking for other distributions, but provide an
   excellent base.

The old example-jobs tarballs are deprecated.

* The D-Bus interface remains unstable, to reflect this the current
interface name has changed to "com.ubuntu.Upstart0_6" and the
name of the job and instance interfaces have changed to match.

* The "EmitEvent" D-Bus method gains a wait argument, when given
   as TRUE (the recommended setting) the method call will be blocked
   until all effects of the event have finished. When FALSE the
   method call will return once the event has been queued.

* The "Start", "Stop" and "Restart" D-Bus methods of jobs and
instances gain a similar wait argument.

* The Upstart D-Bus object now has "version" and "log_priority"
properties. The former is to obtain the version of the init daemon,
the latter allows you to obtain and change the logging priority.

* Job D-Bus objects now have "name", "description", "author" and
"version" properties to obtain the job name and the contents of
the equivalent job file fields for the others.

* Instance D-Bus objects now have "name", "goal", "state" and
"processes" properties to obtain the instance name, goal, state
and list of running processes and their pids respectively.

* The default D-Bus security policy now permits use of the "Get"
methods by all users, including obtaining values of properties.

* initctl has been rewritten with functionality more along the
   lines of Upstart 0.3.x than before; since many distributions are
   still shipping 0.3.x the summary of changes for the tool reflects
   both changes from 0.3.x and 0.5.x

* The global "-p"/"--pid" argument has been dropped, since
   communication is over D-Bus. New "--system" and "--dest" arguments
   have been added to force communication over the system bus, and
   specify the destination, instead of using the private socket (this
   is the default when run as non-root to permit "list" and "status"
   to work for ordinary users).

* The "-i"/"--id" and "--show-ids" options to commands have been
dropped since jobs no longer have ids.

* Since instances may now have names, these will be displayed in
   brackets after the job name when one is present. The output of
   the goal and state are now expressed as "start/running" instead
   of "(start) running" to disambiguate.

* initctl "start" and "stop" now only output the final state of
the job, not inte...

This has been fixed in Upstart 0.6.0.

0.6.0  2009-07-09  "How appropriate, you fight like a cow"

* The licence for Upstart has been changed back to version 2 of the
	  GNU GPL.

* D-Bus 1.2.15 is now required, this is the current GIT HEAD
	  pending a 1.2.16 release.

* Configuration paths have changed.  Global configuration now
	  resides in "/etc/init.conf" while jobs are now configured in
	  "/etc/init"

* Job configuration filenames must now end in ".conf"

* Default configuration files are now supplied in the "conf"
	  sub-directory of the source, and installed into "/etc/init".

These match the Debian/Ubuntu sysvinit configuration so may
	  require some tweaking for other distributions, but provide an
	  excellent base.

The old example-jobs tarballs are deprecated.

* The D-Bus interface remains unstable, to reflect this the current
	  interface name has changed to "com.ubuntu.Upstart0_6" and the
	  name of the job and instance interfaces have changed to match.

* The "EmitEvent" D-Bus method gains a wait argument, when given
	  as TRUE (the recommended setting) the method call will be blocked
	  until all effects of the event have finished.  When FALSE the
	  method call will return once the event has been queued.

* The "Start", "Stop" and "Restart" D-Bus methods of jobs and
	  instances gain a similar wait argument.

* The Upstart D-Bus object now has "version" and "log_priority"
	  properties.  The former is to obtain the version of the init daemon,
	  the latter allows you to obtain and change the logging priority.

* Job D-Bus objects now have "name", "description", "author" and
	  "version" properties to obtain the job name and the contents of
	  the equivalent job file fields for the others.

* Instance D-Bus objects now have "name", "goal", "state" and
	  "processes" properties to obtain the instance name, goal, state
	  and list of running processes and their pids respectively.

* The default D-Bus security policy now permits use of the "Get"
	  methods by all users, including obtaining values of properties.

* initctl has been rewritten with functionality more along the
	  lines of Upstart 0.3.x than before; since many distributions are
	  still shipping 0.3.x the summary of changes for the tool reflects
	  both changes from 0.3.x and 0.5.x

* The global "-p"/"--pid" argument has been dropped, since
	  communication is over D-Bus.  New "--system" and "--dest" arguments
	  have been added to force communication over the system bus, and
	  specify the destination, instead of using the private socket (this
	  is the default when run as non-root to permit "list" and "status"
	  to work for ordinary users).

* The "-i"/"--id" and "--show-ids" options to commands have been
	  dropped since jobs no longer have ids.

* Since instances may now have names, these will be displayed in
	  brackets after the job name when one is present.  The output of
	  the goal and state are now expressed as "start/running" instead
	  of "(start) running" to disambiguate.

* initctl "start" and "stop" now only output the final state of
	  the job, not intermediate states it passes through.  When called
	  with "--no-wait", the commands now output a status before
	  returning (which may not be the final status).

* initctl "start", "stop" and "status" now only accept a single
	  job name.  Further arguments are taken as KEY=VALUE environment
	  variables to pass to the job, replacing the previous "-e" option.

* There is a new initctl "restart" command, with matching
	  /sbin/restart symlink.  This is the atomic equivalent of calling
	  "stop" and "start" with the exception that a stopped job will
	  not be started again.

* In keeping with the newer instance model, instance jobs are now
	  output on separate lines with their full names rather than
	  indented under a "master" instance.

* initctl "status" will exit non-zero if the job name was not
	  found.  (Bug: #328323)

* initctl "status" now outputs information for multi-instance
	  jobs.  (Bug: #331407)

* initctl "list" no longer accepts a pattern, use grep.  Output
	  is no longer sorted.

* initctl "emit" no longer outputs changes that occur as a result
	  of the event.

* When initctl "emit" is called with "--no-wait", it will return
	  immediately.  (Bug: #324890)

* initctl "emit" now only accepts a single event name.  Further
	  arguments are taken as KEY=VALUE environment for the event,
	  replacing the previous "-e" option.

* initctl "jobs" and "events" have been dropped.

* initctl "log-priority" may be called without arguments, in
	  which case it will output the current priority.  (Bug: #280529)

* initctl "reload" has been renamed to "reload-configuration"
	  to avoid confusion with reloading a job's configuration.

* initctl(8) man page updated.  (Bug: #285753)

* runlevel no longer accepts the --set and --reboot arguments,
	  instead telinit and shutdown write these records into utmp and wtmp.

* runlevel(7) man page added to describe the runlevel event, and
	  the implementation of runlevels and System V compatibility in
	  Upstart.  (Bug: #60429)

* telinit will no longer silently ignore the "a", "b" or "c"
	  runlevels.

* telinit now accepts the previously ignored "-e" argument, passing
	  the environment variables given along with the runlevel event.

* telinit now officially accepts the "q"/"Q" and "u"/"U" arguments,
	  the former will reload the Upstart configuration while the latter
	  will re-execute Upstart.

* telinit q will also attempt to reconnect to the D-Bus system bus
	  if the connection has not been made, or has been lost.
	  (Bug: #323022)

* reboot no longer silently ignores the "-t" option.

* reboot now silently ignores the "-n", "-i" and "-h" options; it
	  will no longer sync your disks, down your network interfaces or
	  spin down your hard drives.  This functionality is all handled
	  by the kernel on a modern system.  (Bug: #92685)

* reboot now writes a "shutdown" record to /var/log/wtmp, this means
	  that the "-w" option is honoured with its original intent.  We
	  still silently ignore the "-d" option.

* shutdown message generation fixed to be more easily translatable.
	  (Bug: #102565)

* The TERM/KILL timeout, and other system timeouts, now use the
	  monotonic clock so are unaffected by system clock changes.
	  (Bug: #389588)

* Respawn detection now uses the monotonic clock so is unaffected
	  by system clock changes.  (Bug: #389586)

* Significant improvement in the amount of manual pages included
	  with Upstart and their content.  (Bug: #60429)

* A manual page refering people from /etc/inittab to /etc/init
	  is also included.  (Bug: #72058)

Changed in upstart:
assignee:	nobody → Scott James Remnant (scott)
status:	Fix Committed → Fix Released

Revision history for this message

Launchpad Janitor (janitor) wrote on 2009-07-09:

This bug was fixed in the package upstart - 0.6.0-1

---------------
upstart (0.6.0-1) karmic; urgency=low

  * New upstream release ("How appropriate, you fight like a cow")
    - my customary changes list since pointless, it's basically a
      complete rewrite.
    - Handles /bin/sh symlink disappearing. LP: #65024.
    - Boot parameters may be passed to init scripts. LP: #74664.
    - reboot implies --force during shutdown. LP: #388738.
    - reboot no longer iterates /proc/ide. LP: #92685.
    - much improved documentation. LP: #60429, #72058, #388715.