Still have what looks like exactly this issue on a clean 13.10
installation. Looks like it goes away if I disconnect from wired network
at login screen before rebooting or shutting down. Is there a new bug
filed for 13.10 somewhere ?
--
You received this bug notification because you are a member
If I execute sudo service networking restart or sudo service
networking stop all ttyX are inaccessible and it closes all graphical
sessions. Only it shows a black screen with a cross (the mouse pointer)
on it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
The workaround in comment #35 doesn't work to me.
My system takes ~40 seconds in reboot. I don't know that the system does in
that 40 seconds but it shows the messages in attached screenshot.
** Attachment added: screenshot of messages at shutdown
Finally found a workaround, Yotas fix (#21) seemed to work fine for the
time consumed shutting the system down, but i still got the bug.
Eventually I found out that it only happened when I was connected to a
network, so I made a small script which shuts down my network interfaces
when my computer
I'm still seeing mount: / is busy and unclean shutdowns with 3.5.0-23.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1061639
Title:
Upstartification of /etc/init.d/networking has lost
@Gard Speermann
You may have tried this but...
The very first shutdown after the kernel update will not be clean as the
kernel has not been loaded yet. So, first boot in the updated kernel and
then try to restart...good luck!
--
You received this bug notification because you are a member of
I've tried several reboots. The problem persists. It could be that I'm
experiencing a different bug, though. What I see is, however, consistent
with what's described here (except for the update fixing the problem).
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Hello all,
I experienced this bug now for quite a while, since upgrading to Quantal
(64bit) to be exact, and while trying some of the above suggestions, I
observed the following:
Until shortly, I got it fixed by following yota's advice (#21).
Then, after a kernel update to 3.5.0-22 (from
Hello all,
I can also confirm that the kernel update (3.5.0-23) seems to resolve the
issue. Two restarts so far, both clean!
Thanks for the fix, hope we will not be seeing this bug in the future :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This bug STILL occurs in 64 bit 1304 (Raring) with kernel 3.8.0-2-generic.
Downloaded and tested today 2013-01_27
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1061639
Title:
Upstartification of
Hello all,
I would just like to add that this issue also affects my desktop and
laptop, the former with a wired connection and the latter with a
wireless, both running quantal 64-bit.
I just tried the workaround in post #20 for my desktop and it seems to
be working, i.e clean reboot/shutdown.
Bug still occurs
Asus U36JC, 128GB SSD instead of normal 500GB HDD
Xubuntu 12.10 (64bit)
mount: / is busy
# Will now halt
[xxx] Power down.
--Freeze--
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Me too!
On several installations, with or without network-manager (wicd
instead). I have tried workarounds suggested by yota (#16 and #21) and
ernie 07 (#20) without success.
Different filesystems are all affected, with JFS seeming to recover the
fastest (but JFS is not yet suitable for SSDs
This bug STILL occurs in 64 bit 1304 (Raring) with kernel 3.8.0-0-generic.
Downloaded and tested today 2013-01_14
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1061639
Title:
Upstartification of
See bug 879120 for a case in which dbus pauses 60 seconds in shutting
down the network. Jan 11, 2013 I am still seeing / busy messages at
shutdown on a USB ext2 file system (no errors found from external
check).
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I also am concerned about this hidden bug - I only discovered there was an
issue when I noticed that boot times were longer than normal. I have converted
all my main computers to 12.10 64 bit...
They all show this behaviour with messaged like:
[1.111309] EXT4-fs (sdb1): INFO: recovery
In my daily work archives are created to preserve snapshots of work in
progress. In addition, they are extracted and the before/after folder
structures are compared via Beyond Compare. IF Nvidia drivers would stop
randomly hanging and thus forcing power resets, I might be able to
reduce archiving
Ok, I've experienced again the problem on a new machine on which quantal was
installed from scratch.
This is everything I've done to solve all issues and get back to a fast 5
seconds shutdown with no filesystem corruption:
- rm /etc/init/modem-manager.conf (it's started by network manager via
Yes, a fix was released.
NO, the problem has NOT been fixed.
When testing with a fresh 64-bit install via the 12.10 Released LiveDVD (from
iso), this problem is 100% reproducible and occurs 100% of the time. Please see
launchpad bug 1073433.
Also I have attached fsck output.
** Attachment
For my environment (Ethernet DSL to Internet) a temporary workaround
follows:
1. UNCHECK Enable Networking
2. Wait until after the disconnected message goes away
3. Restart and Shutdown
4. Fsck from an alternate installation will NOT throw any errors.
Apparently Unchecking Enable Networking does
Thank you Marius!
Yes, modem-manager was causing a significant part (but not all) of the
shutdown delay, I'll post my findings about it in the relative bug
report.
Still I believe that ifupdown could handle dhclient and/or dnsmasq that
were keeping / busy.
--
You received this bug notification
To detect what is keeping / filesystem busy I put a:
lsof / /openfiles.txt
sync
on top of /etc/init.d/umountroot
In my case it results that dhclient and dnsmasq are most likely to be the root
cause; who is supposed to bring them down?
I disabled dnsmasq commenting dns=dnsmasq in
Could it be bug #1070647 that you are seeing?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1061639
Title:
Upstartification of /etc/init.d/networking has lost deconfiguring-
networking event
Err, hello? This is not fixed. I did an installation twice after relase
day. I have no problem with it, I did sudo apt-get remove --purge
dnsmasq-base resolvconf wpasupplicant isc-dhcp-client isc-dhcp-common
libnm-glib-vpn1 libnm-glib4 libnm-gtk-common libnm-gtk0 libnm-util2
network-manager
Christian, this bug is closed as fixed, so it should not be opened
again, so could you please run ubuntu-bug ifupdown in a terminal. Also
state there if this happens on new installations or only upgraded
installations. Please add a reference here to the new bug report number.
--
You received
Please don't file it against ifupdown as it's not the problem anymore,
if you're still seeing this bug, it's very likely to be something
completely unrelated to ifupdown.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Then I would suggest upstart, dbus or network-manager.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1061639
Title:
Upstartification of /etc/init.d/networking has lost deconfiguring-
networking
Final release images tested. Clean standard install, default options on
400GB HDD. Still / device is busy.
Shutdown standard. Log out. And in lightdm Reboot. Problem remains!
With the Live DVD testing the filesystem after shutdown and booting the
DVD instead, it says:
sudo fsck.ext4 -Ffy
Here the same behaviour is described:
Failure to umount root file system at shutdown
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1044640
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1061639
For me this is NOT FIXED. I did a clean install twice yesterday (October
16th) with the daily images of quantal (amd64).
1.) Clean install onto a flash drive. 2.) Clean install onto SATA HDD.
Both with the ext4 filesystem.
Both *never* shutdown cleanly. This really is problematic and makes the
FINALLY worked! :) (for the first time ever with quantal!)
I tried about 2 hours shutting down manually. Stopping, starting init
scripts, networking etc. I found this only way, and it was to be done
exactly in this order. Contra: I have not yet figured the problem out
exactly. I think many
** Attachment added: cleanshutdown_howto2.txt
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1061639/+attachment/3402054/+files/cleanshutdown_howto2.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I still get a message mount: / is busy at every shutdown in Quantal,
I'm not sure whether this means this bug is still not fixed on some
systems or if this is a different bug that I should report separately.
Kind regards,
Jan
--
You received this bug notification because you are a member of
I can confirm that the unmounting issues are indeed fixed, and no more
fsck warnings are shown in dmesg, but shutting down Quantal still takes
conciderably longer than shutting down Precise.
Before this update, I could run 'sudo service networking stop', which
would speed up the shutdown process
ConsoleKit is a dbus service and the fix for this bug was to emit the
event that'd make dbus go away, so nothing unexpected here.
I'd expect any remaining slowness to be related to another upstart or
sysvinit job taking longer than it used to on precise.
--
You received this bug notification
** Changed in: ifupdown (Ubuntu Quantal)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1061639
Title:
Upstartification of /etc/init.d/networking has lost
This bug was fixed in the package ifupdown - 0.7.2ubuntu2
---
ifupdown (0.7.2ubuntu2) quantal; urgency=low
* Fix regression with the removal of the sysvinit networking job:
- Don't bring 'lo' down (add it to --exclude)
- Emit deconfiguring-networking (LP: #1061639)
--
On last shutdown in verbose mode, i've seen one more issue:
During the last part of the shutdown process, a comment is written and says:
- trying to retrieve the remaining processes
- then, strangely, modemmanager is restarted and load its dozen drivers (got a
modemmanager daily update
Stéphane, this is a regression in the latest upload that needs to be
fixed for release. Thanks!
** Also affects: ifupdown (Ubuntu Quantal)
Importance: High
Status: New
** Changed in: ifupdown (Ubuntu Quantal)
Assignee: (unassigned) = Stéphane Graber (stgraber)
** Changed in:
39 matches
Mail list logo
