/proc not mounted

seems like proc is mounted first. then dies.
restarting it with "/etc/init.d/mountvirtfs".
brings back a working system

A few other people have experienced problems with things being semi-randomly
unmounted. The cause has not yet been found, and it doesn't seem to happen to
most users.

it seems like it is related to network access.

as soon as I try to connect to my local or wireless
network for the first time /proc is gone.

does not seem randomly to me.

Mine's pretty reproduceable. ifdown eth1 (or rmmod ipw2200). Blammo. :-)

It's not just /proc, by the way - if you check /proc/mounts, you'll see that
everything is unmounted (apart from rootfs).

Mine is a touch weird. I think it is related to wifi module as well, but I
haven't found a way to reproduce yet.

I use a custom module for wifi (acx_pci) and a custom script to start and
restart it. I can run that script without this bug occurring, and also can
"rmmod acx_pci" or "modprobe -r acx_pci) without the problem happening.

i notice the problem when I lose my internet connection and then try and get it
back up.

NOTE: my /home directory (separate partition) is also unmounted.

hope this helps, M

Same problem on my machine. After I remove the ipw2100 module, /proc is empty. I
see the following possibly related in /var/log/messsages:

Dec 3 13:28:20 localhost net.agent[5252]: Bad NET invocation: $INTERFACE is not set

Everything's fine again after ``/etc/init.d/mountvirtfs restart''

Of course the ``Bad NET invocation'' stuff doesn't have anything to do with this.

What about marking this thing as critical? I for one think it is.

for me the /proc dies on a

 rmmod ipw2100

I am also tempted to mark this bug as
critical since I am using hoary on a laptop.
which means: since suspend is not yet working
I have to reboot very often ...and everytime
I have to fix the /proc thing. *puke*

Same here, although I'm getting it whenever PPP dies (and it does this fairly
often with my ISP!), so I can concur it's related to a network interface going down.

util-linux (2.12j-3) unstable; urgency=low

  * umount -l "" does bad things. Don't do let the user do that.

This prevents a hal bug (which is also fixed) from causing this behaviour

I'm not so sure this is fixed. I'm running recent util-linux and hal version
(Hoary) and it's still happening for me.

rossg@localhost ~/clients/Prodco/xaltoffshore $ dpkg -l | grep util-linux
ii util-linux 2.12k-2ubuntu1 Miscellaneous system utilities
ii util-linux-loc 2.12k-2ubuntu1 Locales files for util-linux
rossg@localhost ~/clients/Prodco/xaltoffshore $ dpkg -l | grep hal
ii hal 0.4.2-2ubuntu2 Hardware Abstraction Layer
ii hal-device-man 0.4.2-2ubuntu2 Hardware Abstraction Layer user interface
ii libhal-storage 0.4.2-1ubuntu2 Hardware Abstraction Layer - shared library
ii libhal0 0.4.2-2ubuntu2 Hardware Abstraction Layer - shared library

Matt, can you provide some more information on the bug(s)?

The only evidence I've got is the following message in the syslog, and the fact
that it unmounts *everything* whenever the PPP serial link drops.

Dec 19 08:21:35 localhost pppd[4695]: Serial connection established.
Dec 19 08:21:36 localhost pppd[4695]: Using interface ppp0
Dec 19 08:21:36 localhost pppd[4695]: Connect: ppp0 <--> /dev/ttyS5
Dec 19 08:21:59 localhost pppd[4695]: Hangup (SIGHUP)
Dec 19 08:21:59 localhost pppd[4695]: Modem hangup
Dec 19 08:21:59 localhost pppd[4695]: Connection terminated.
Dec 19 08:21:59 localhost net.agent[4804]: Bad NET invocation: $INTERFACE is not set

Hope this helps.

I've since seen a few more util-linux/hald updates go through, and the problem
seems to have stopped happening.