[gentoo-user] Shutting down process hangs - how to proceed?

[gentoo-user] Shutting down process hangs - how to proceed?

[meino.cramer]

Hi,

 I am updateing my Gentoo on a dialy basis.
 Since two days the shutdown process of the systems 
 hangs around "Bringing down net.lo".
 Booting the PC is not a problem -- except the
 "replaying transactions" (resierfs).

 I fear to finally damage the filesystem while trying
 to figure out, why the shutdown process does not
 succeed.

 How can I proceed?
 What is suspicous for hanging the shutdown process?
 Every help is very welcome !  :)

 Thank you very much in advance!
 Keep hacking!
 mcc

-- 
Please don't send me any Word- or Powerpoint-Attachments
unless it's absolutely neccessary. - Send simply Text.
See http://www.gnu.org/philosophy/no-word-attachments.html
In a world without fences and walls nobody needs gates and windows.

Re: [gentoo-user] Shutting down process hangs - how to proceed?

[Dale]

meino.cramer@gmx.de wrote:
> Hi,
>
>  I am updateing my Gentoo on a dialy basis.
>  Since two days the shutdown process of the systems 
>  hangs around "Bringing down net.lo".
>  Booting the PC is not a problem -- except the
>  "replaying transactions" (resierfs).
>
>  I fear to finally damage the filesystem while trying
>  to figure out, why the shutdown process does not
>  succeed.
>
>  How can I proceed?
>  What is suspicous for hanging the shutdown process?
>  Every help is very welcome !  :)
>
>  Thank you very much in advance!
>  Keep hacking!
>  mcc
>
>   

I don't know about the reason it hangs but this may help get you a
cleaner shutdown.  This is taken from a email that was sent to me during
that horrible xorg-server and hal upgrade.

> Hold down Atl, hold down SysRq, press each of the keys in turn. The
> usual full sequence is R-E-I-S-U-B Reboot Even If System Utterly
> Broken By ${DEITY} - this tagline picker is spooky at times :-O
> -- Neil Bothwick

I tried this once when I was unable to get my keyboard to respond to
anything else.  I made it through the first three or four and was
returned to a console with a working keyboard.  Since you are shutting
down, you may want to go through them all to be safe.  I think the last
one does a reboot.

Hope that helps.

Dale

:-) :-) 

Re: [gentoo-user] Shutting down process hangs - how to proceed?

[meino.cramer]

> cleaner shutdown.  This is taken from a email that was sent to me during
> that horrible xorg-server and hal upgrade.
> 
> > Hold down Atl, hold down SysRq, press each of the keys in turn. The
> > usual full sequence is R-E-I-S-U-B Reboot Even If System Utterly
> > Broken By ${DEITY} - this tagline picker is spooky at times :-O
> > -- Neil Bothwick
> 
> I tried this once when I was unable to get my keyboard to respond to
> anything else.  I made it through the first three or four and was
> returned to a console with a working keyboard.  Since you are shutting
> down, you may want to go through them all to be safe.  I think the last
> one does a reboot.
> 
> Hope that helps.
> 
> Dale
> 
> :-) :-) 


Hi Dale,

thanks a lot for your help!!!  :)

This will help to bring donw the machine in an more
cleaner way as simply pressing the power switch ;-)

But:
How can I figure out, what hangs the shutdown process itsself?

Keep hacking!
mcc

---
Please don't send me any Word- or Powerpoint-Attachments
unless it's absolutely neccessary. - Send simply Text.
See http://www.gnu.org/philosophy/no-word-attachments.html
In a world without fences and walls nobody needs gates and windows.

Re: [gentoo-user] Shutting down process hangs - how to proceed?

[Dale]

meino.cramer@gmx.de wrote:
>> cleaner shutdown.  This is taken from a email that was sent to me during
>> that horrible xorg-server and hal upgrade.
>>
>>     
>>> Hold down Atl, hold down SysRq, press each of the keys in turn. The
>>> usual full sequence is R-E-I-S-U-B Reboot Even If System Utterly
>>> Broken By ${DEITY} - this tagline picker is spooky at times :-O
>>> -- Neil Bothwick
>>>       
>> I tried this once when I was unable to get my keyboard to respond to
>> anything else.  I made it through the first three or four and was
>> returned to a console with a working keyboard.  Since you are shutting
>> down, you may want to go through them all to be safe.  I think the last
>> one does a reboot.
>>
>> Hope that helps.
>>
>> Dale
>>
>> :-) :-) 
>>     
>
>
> Hi Dale,
>
> thanks a lot for your help!!!  :)
>
> This will help to bring donw the machine in an more
> cleaner way as simply pressing the power switch ;-)
>
> But:
> How can I figure out, what hangs the shutdown process itsself?
>
> Keep hacking!
> mcc
>
> ---
> Please don't send me any Word- or Powerpoint-Attachments
> unless it's absolutely neccessary. - Send simply Text.
> See http://www.gnu.org/philosophy/no-word-attachments.html
> In a world without fences and walls nobody needs gates and windows.
>
>
>
>   

That will be answered by another guru who knows what to ask.  I have
never had mine to hang like that so I have no idea.  Someone will be
along soon and help that knows how to figure this out or has ran into
this before.

Dale

:-)  :-) 

Re: [gentoo-user] Shutting down process hangs - how to proceed?

[Mick]

[-- Attachment #1: Type: text/plain, Size: 1308 bytes --]

On Saturday 19 September 2009, meino.cramer@gmx.de wrote:
> > cleaner shutdown.  This is taken from a email that was sent to me during
> > that horrible xorg-server and hal upgrade.
> >
> > > Hold down Atl, hold down SysRq, press each of the keys in turn. The
> > > usual full sequence is R-E-I-S-U-B Reboot Even If System Utterly
> > > Broken By ${DEITY} - this tagline picker is spooky at times :-O
> > > -- Neil Bothwick
> >
> > I tried this once when I was unable to get my keyboard to respond to
> > anything else.  I made it through the first three or four and was
> > returned to a console with a working keyboard.  Since you are shutting
> > down, you may want to go through them all to be safe.  I think the last
> > one does a reboot.
> >
> > Hope that helps.
> >
> > Dale
> >
> > :-) :-)
>
> Hi Dale,
>
> thanks a lot for your help!!!  :)
>
> This will help to bring donw the machine in an more
> cleaner way as simply pressing the power switch ;-)
>
> But:
> How can I figure out, what hangs the shutdown process itsself?

Last time I came across a problem like this I had forgotten to select the 
right chipset under Graphics support/AGP Support/ in the kernel.  So I 
suggest you revisit your kernel and xorg drivers setups for your card.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Shutting down process hangs - how to proceed?

[Pupino]

2009/9/19 Mick <michaelkintzios@gmail.com>:
> On Saturday 19 September 2009, meino.cramer@gmx.de wrote:
>> > cleaner shutdown.  This is taken from a email that was sent to me during
>> > that horrible xorg-server and hal upgrade.
>> >
>> > > Hold down Atl, hold down SysRq, press each of the keys in turn. The
>> > > usual full sequence is R-E-I-S-U-B Reboot Even If System Utterly
>> > > Broken By ${DEITY} - this tagline picker is spooky at times :-O
>> > > -- Neil Bothwick
>> >
>> > I tried this once when I was unable to get my keyboard to respond to
>> > anything else.  I made it through the first three or four and was
>> > returned to a console with a working keyboard.  Since you are shutting
>> > down, you may want to go through them all to be safe.  I think the last
>> > one does a reboot.
>> >
>> > Hope that helps.
>> >
>> > Dale
>> >
>> > :-) :-)
>>
>> Hi Dale,
>>
>> thanks a lot for your help!!!  :)
>>
>> This will help to bring donw the machine in an more
>> cleaner way as simply pressing the power switch ;-)
>>
>> But:
>> How can I figure out, what hangs the shutdown process itsself?
>
> Last time I came across a problem like this I had forgotten to select the
> right chipset under Graphics support/AGP Support/ in the kernel.  So I
> suggest you revisit your kernel and xorg drivers setups for your card.
> --
> Regards,
> Mick
>

Hi,
I got a similar problem too once... and what was making the system
hang wasn't the last shutting down thing listed, but the one just
after (so i don't think it's net.lo fault in your case). So i suggest
to have a look at which services are started at boot, but aren't
shutted down. Turning off parallel boot could help you find out the
responsible service.
In my case it was a misconfiguration of the alsa module, which
shouldn't be unloaded at shotdown time...
HTH
Davide

Re: [gentoo-user] Shutting down process hangs - how to proceed?

[meino.cramer]

> Hi,
> I got a similar problem too once... and what was making the system
> hang wasn't the last shutting down thing listed, but the one just
> after (so i don't think it's net.lo fault in your case). So i suggest
> to have a look at which services are started at boot, but aren't
> shutted down. Turning off parallel boot could help you find out the
> responsible service.
> In my case it was a misconfiguration of the alsa module, which
> shouldn't be unloaded at shotdown time...
> HTH
> Davide
 
 Hi Davide,

 Is there any way to figure out, in which sequence what is shut down 
 *without* actually shutting down ther system?

 Have a nice weekend! :)
 Best regards,
 mcc




-- 
Please don't send me any Word- or Powerpoint-Attachments
unless it's absolutely neccessary. - Send simply Text.
See http://www.gnu.org/philosophy/no-word-attachments.html
In a world without fences and walls nobody needs gates and windows.

Re: [gentoo-user] Shutting down process hangs - how to proceed?

[pk]

meino.cramer@gmx.de wrote:

>  Is there any way to figure out, in which sequence what is shut down 
>  *without* actually shutting down ther system?

I'm sure there's a simple way of finding that out but I was wondering if
this might be your problem?:

http://bugs.gentoo.org/253535

MfG

Peter K

Re: [gentoo-user] Shutting down process hangs - how to proceed?

[Frank Steinmetzger]

[-- Attachment #1: Type: text/plain, Size: 725 bytes --]

Am Samstag, 19. September 2009 schrieb meino.cramer@gmx.de:
> Hi,
>
>  I am updateing my Gentoo on a dialy basis.
>  Since two days the shutdown process of the systems
>  hangs around "Bringing down net.lo".
>  Booting the PC is not a problem -- except the
>  "replaying transactions" (resierfs).
> [...]
>  How can I proceed?
>  What is suspicous for hanging the shutdown process?
>  Every help is very welcome !  :)

I also thought of the alsa problem pk mentioned. But it might also be another 
kernel module. Search your /var/log/messages or dmesg for kernel oopses.
-- 
Gruß | Greetings | Qapla'
Contrariwise, if it was so, it might be; and if it were so, it would be;
but as it isn’t, it ain’t.

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Shutting down process hangs - how to proceed?

[meino.cramer]

pk <peterk2@coolmail.se> [09-09-19 13:49]:
> meino.cramer@gmx.de wrote:
> 
> >  Is there any way to figure out, in which sequence what is shut down 
> >  *without* actually shutting down ther system?
> 
> I'm sure there's a simple way of finding that out but I was wondering if
> this might be your problem?:
> 
> http://bugs.gentoo.org/253535
> 
> MfG
> 
> Peter K

Hi Peter,

I scanned the bugzilla entry...as far as I understood unloading of
snd_hda_intel hangs due to an unclear dependency.
I am running my Gentoo on an Asus AV8 board with Via chipset and
AMD CPU, so "no intel". 
My modules are:

Module                  Size  Used by
usb_storage            62088  0 
snd_pcm_oss            37536  0 
snd_usb_audio          81280  0 
snd_usb_lib            15132  1 snd_usb_audio
snd_hwdep               6880  1 snd_usb_audio
gspca_ov534             7740  0 
gspca_main             21916  1 gspca_ov534
dvb_bt8xx              12384  0 
mt352                   5984  1 dvb_bt8xx
dst_ca                 12348  1 dvb_bt8xx
dst                    26020  2 dvb_bt8xx,dst_ca
dvb_core               83108  3 dvb_bt8xx,dst_ca,dst
bt878                   9320  2 dvb_bt8xx,dst
nvidia               9580516  36 
bttv                  119252  2 dvb_bt8xx,bt878
ir_common              42464  1 bttv
i2c_algo_bit            5376  1 bttv
v4l2_common            15132  1 bttv
videodev               37824  3 gspca_main,bttv,v4l2_common
v4l1_compat            13344  1 videodev
videobuf_dma_sg        10976  1 bttv
videobuf_core          15584  2 bttv,videobuf_dma_sg
uhci_hcd               30220  0 
i2c_viapro              7344  0 
k8temp                  4188  0 
hwmon                   2392  1 k8temp
btcx_risc               4132  1 bttv
pcspkr                  2300  0 
ehci_hcd               48496  0 
tveeprom               11744  1 bttv

Nonetheless I added the UNLOAD_ON_STOP="no" to /etc/conf.d/alsasound
and we will see what happens.
All this works for a long long time...and it bits me about three days
ago. I did not update alsa*, since I use the kernels alsa-stuff and
the according lib/utils/etc. of the portage tree.

Fingers crossed...

Thanks for your help !:)

Have a nice weekend!
Best regards,
mcc

-- 
Please don't send me any Word- or Powerpoint-Attachments
unless it's absolutely neccessary. - Send simply Text.
See http://www.gnu.org/philosophy/no-word-attachments.html
In a world without fences and walls nobody needs gates and windows.

Re: [gentoo-user] Shutting down process hangs - how to proceed?

[meino.cramer]

> I also thought of the alsa problem pk mentioned. But it might also be another 
> kernel module. Search your /var/log/messages or dmesg for kernel oopses.
> -- 
> Gruß | Greetings | Qapla'
> Contrariwise, if it was so, it might be; and if it were so, it would be;
> but as it isn’t, it ain’t.

I scanned dmesg output and the log files before and found nothing. May
those parts were victim of the "replay transaction" while rebooting
the system afterwards...





-- 
Please don't send me any Word- or Powerpoint-Attachments
unless it's absolutely neccessary. - Send simply Text.
See http://www.gnu.org/philosophy/no-word-attachments.html
In a world without fences and walls nobody needs gates and windows.

Re: [gentoo-user] Shutting down process hangs - how to proceed?

[covici]

Mick <michaelkintzios@gmail.com> wrote:

> On Saturday 19 September 2009, meino.cramer@gmx.de wrote:
> > > cleaner shutdown.  This is taken from a email that was sent to me during
> > > that horrible xorg-server and hal upgrade.
> > >
> > > > Hold down Atl, hold down SysRq, press each of the keys in turn. The
> > > > usual full sequence is R-E-I-S-U-B Reboot Even If System Utterly
> > > > Broken By ${DEITY} - this tagline picker is spooky at times :-O
> > > > -- Neil Bothwick
> > >
> > > I tried this once when I was unable to get my keyboard to respond to
> > > anything else.  I made it through the first three or four and was
> > > returned to a console with a working keyboard.  Since you are shutting
> > > down, you may want to go through them all to be safe.  I think the last
> > > one does a reboot.
> > >
> > > Hope that helps.
> > >
> > > Dale
> > >
> > > :-) :-)
> >
> > Hi Dale,
> >
> > thanks a lot for your help!!!  :)
> >
> > This will help to bring donw the machine in an more
> > cleaner way as simply pressing the power switch ;-)
> >
> > But:
> > How can I figure out, what hangs the shutdown process itsself?
> 
> Last time I came across a problem like this I had forgotten to select the 
> right chipset under Graphics support/AGP Support/ in the kernel.  So I 
> suggest you revisit your kernel and xorg drivers setups for your card.
> -- 
Hi.  I have a somewhat similar problem, when I shutdown it goes all the
way to the end, but instead of shutting down, it says
init: nomore processes left in this runlevel.  This is fine if I am
here, but from a remote location it would not work, so how can I figure
out why this is happening?  I think this started when I went to
baselayout 2, but not certain of that.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] Shutting down process hangs - how to proceed?

[Pupino]

2009/9/19  <meino.cramer@gmx.de>:
>> Hi,
>> I got a similar problem too once... and what was making the system
>> hang wasn't the last shutting down thing listed, but the one just
>> after (so i don't think it's net.lo fault in your case). So i suggest
>> to have a look at which services are started at boot, but aren't
>> shutted down. Turning off parallel boot could help you find out the
>> responsible service.
>> In my case it was a misconfiguration of the alsa module, which
>> shouldn't be unloaded at shotdown time...
>> HTH
>> Davide
>
>  Hi Davide,
>


>  Is there any way to figure out, in which sequence what is shut down
>  *without* actually shutting down ther system?
I'm not really sure about this but i think it's just the booting
sequence reversed...

Davide

Re: [gentoo-user] Shutting down process hangs - how to proceed?

[Mick]

[-- Attachment #1: Type: text/plain, Size: 722 bytes --]

On Saturday 19 September 2009, meino.cramer@gmx.de wrote:

> Nonetheless I added the UNLOAD_ON_STOP="no" to /etc/conf.d/alsasound
> and we will see what happens.
> All this works for a long long time...and it bits me about three days
> ago. I did not update alsa*, since I use the kernels alsa-stuff and
> the according lib/utils/etc. of the portage tree.
>
> Fingers crossed...

If that doesn't work, then exit your X session and Ctl+Alt+F1 will drop you to 
a console.  Run '/etc/init.d/xdm stop' (or gdm if you are running gnome) and 
then zap.  Then '/sbin/shutdown -h now' from the console.  If it hangs again 
the problem is not related to your video card kernel settings.

HTH.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[gentoo-user] Re: Shutting down process hangs - how to proceed?

[walt]

On 09/19/2009 05:31 AM, meino.cramer@gmx.de wrote:

> Nonetheless I added the UNLOAD_ON_STOP="no" to /etc/conf.d/alsasound
> and we will see what happens.

Did you try stopping the alsa service manually?

#/etc/init.d/alsasound stop

Re: [gentoo-user] Re: Shutting down process hangs - how to proceed?

[meino.cramer]

walt <w41ter@gmail.com> [09-09-20 02:03]:
> On 09/19/2009 05:31 AM, meino.cramer@gmx.de wrote:
> 
> >Nonetheless I added the UNLOAD_ON_STOP="no" to /etc/conf.d/alsasound
> >and we will see what happens.
> 
> Did you try stopping the alsa service manually?
> 
> #/etc/init.d/alsasound stop
> 

This gave me errors, since my Webcam's audio part isn't implemented as
full audio device, but it does not hang:

solfire:/home/mccramer>sudo /etc/init.d/alsasound stop
 * WARNING:  you are stopping a boot service.
 * Storing ALSA Mixer Levels ...
alsactl: get_control:249: Cannot read control '2,0,0,Mic Capture Volume,0': Invalid argument
 * Error saving levels.                                                     [ !! ]
solfire:/home/mccramer>



-- 
Please don't send me any Word- or Powerpoint-Attachments
unless it's absolutely neccessary. - Send simply Text.
See http://www.gnu.org/philosophy/no-word-attachments.html
In a world without fences and walls nobody needs gates and windows.

[gentoo-user] Re: Shutting down process hangs - how to proceed?

[walt]

On 09/19/2009 05:07 PM, meino.cramer@gmx.de wrote:
> walt<w41ter@gmail.com>  [09-09-20 02:03]:
>> On 09/19/2009 05:31 AM, meino.cramer@gmx.de wrote:
>>
>>> Nonetheless I added the UNLOAD_ON_STOP="no" to /etc/conf.d/alsasound
>>> and we will see what happens.
>>
>> Did you try stopping the alsa service manually?
>>
>> #/etc/init.d/alsasound stop
>>
>
> This gave me errors, since my Webcam's audio part isn't implemented as
> full audio device, but it does not hang:
>
> solfire:/home/mccramer>sudo /etc/init.d/alsasound stop
>   * WARNING:  you are stopping a boot service.
>   * Storing ALSA Mixer Levels ...
> alsactl: get_control:249: Cannot read control '2,0,0,Mic Capture Volume,0': Invalid argument
>   * Error saving levels.                                                     [ !! ]
> solfire:/home/mccramer>

Ah! I've seen that same error when I neurotically switch back and forth
between different kernel versions (cf. autoflagellation).

Try (as root) 'alsactl store' and see if that makes any difference.

Re: [gentoo-user] Re: Shutting down process hangs - how to proceed?

[meino.cramer]

walt <w41ter@gmail.com> [09-09-20 04:13]:
> On 09/19/2009 05:07 PM, meino.cramer@gmx.de wrote:
> >walt<w41ter@gmail.com>  [09-09-20 02:03]:
> >>On 09/19/2009 05:31 AM, meino.cramer@gmx.de wrote:
> >>
> >>>Nonetheless I added the UNLOAD_ON_STOP="no" to /etc/conf.d/alsasound
> >>>and we will see what happens.
> >>
> >>Did you try stopping the alsa service manually?
> >>
> >>#/etc/init.d/alsasound stop
> >>
> >
> >This gave me errors, since my Webcam's audio part isn't implemented as
> >full audio device, but it does not hang:
> >
> >solfire:/home/mccramer>sudo /etc/init.d/alsasound stop
> >  * WARNING:  you are stopping a boot service.
> >  * Storing ALSA Mixer Levels ...
> >alsactl: get_control:249: Cannot read control '2,0,0,Mic Capture 
> >Volume,0': Invalid argument
> >  * Error saving levels.                                               
> >      [ !! ]
> >solfire:/home/mccramer>
> 
> Ah! I've seen that same error when I neurotically switch back and forth
> between different kernel versions (cf. autoflagellation).
> 
> Try (as root) 'alsactl store' and see if that makes any difference.
> 
It produces a comparable error, since it does a comparable thing...:

alsactl: get_control:249: Cannot read control '2,0,0,Mic Capture Volume,0': Invalid argument

...but this "problem" was there long before the system cannot be
shutdown anymore and I think it is not clean but the root of all
evil....





-- 
Please don't send me any Word- or Powerpoint-Attachments
unless it's absolutely neccessary. - Send simply Text.
See http://www.gnu.org/philosophy/no-word-attachments.html
In a world without fences and walls nobody needs gates and windows.

[gentoo-user] Re: Shutting down process hangs - how to proceed?

[walt]

On 09/19/2009 07:17 PM, meino.cramer@gmx.de wrote:
> walt<w41ter@gmail.com>  [09-09-20 04:13]:
>> On 09/19/2009 05:07 PM, meino.cramer@gmx.de wrote:
>>> walt<w41ter@gmail.com>   [09-09-20 02:03]:
>>>> On 09/19/2009 05:31 AM, meino.cramer@gmx.de wrote:
>>>>
>>>>> Nonetheless I added the UNLOAD_ON_STOP="no" to /etc/conf.d/alsasound
>>>>> and we will see what happens.
>>>>
>>>> Did you try stopping the alsa service manually?
>>>>
>>>> #/etc/init.d/alsasound stop
>>>>
>>>
>>> This gave me errors, since my Webcam's audio part isn't implemented as
>>> full audio device, but it does not hang:

> ...but this "problem" was there long before the system cannot be
> shutdown anymore and I think it is not clean but the root of all
> evil....

Well, in any case you should be able to eliminate those error messages
if you delete /etc/asound.* and then repeat the alsactl store.

Re: [gentoo-user] Re: Shutting down process hangs - how to proceed?

[meino.cramer]

walt <w41ter@gmail.com> [09-09-20 18:14]:
> On 09/19/2009 07:17 PM, meino.cramer@gmx.de wrote:
> >walt<w41ter@gmail.com>  [09-09-20 04:13]:
> >>On 09/19/2009 05:07 PM, meino.cramer@gmx.de wrote:
> >>>walt<w41ter@gmail.com>   [09-09-20 02:03]:
> >>>>On 09/19/2009 05:31 AM, meino.cramer@gmx.de wrote:
> >>>>
> >>>>>Nonetheless I added the UNLOAD_ON_STOP="no" to 
> >>>>>/etc/conf.d/alsasound
> >>>>>and we will see what happens.
> >>>>
> >>>>Did you try stopping the alsa service manually?
> >>>>
> >>>>#/etc/init.d/alsasound stop
> >>>>
> >>>
> >>>This gave me errors, since my Webcam's audio part isn't implemented 
> >>>as
> >>>full audio device, but it does not hang:
> 
> >...but this "problem" was there long before the system cannot be
> >shutdown anymore and I think it is not clean but the root of all
> >evil....
> 
> Well, in any case you should be able to eliminate those error messages
> if you delete /etc/asound.* and then repeat the alsactl store.
> 

solfire:/home/mccramer>l /etc/asound.state
-rw-r--r-- 1 root root 10122 2009-08-06 18:05 /etc/asound.state
solfire:/home/mccramer>sudo rm -f /etc/asound.state
solfire:/home/mccramer>sudo alsactl store
alsactl: get_control:249: Cannot read control '2,0,0,Mic Capture Volume,0': Invalid argument
solfire:/home/mccramer>


-- 
Please don't send me any Word- or Powerpoint-Attachments
unless it's absolutely neccessary. - Send simply Text.
See http://www.gnu.org/philosophy/no-word-attachments.html
In a world without fences and walls nobody needs gates and windows.

Re: [gentoo-user] Shutting down process hangs - how to proceed?

[meino.cramer]

covici@ccs.covici.com <covici@ccs.covici.com> [09-09-19 15:19]:
> Mick <michaelkintzios@gmail.com> wrote:
> 
> > On Saturday 19 September 2009, meino.cramer@gmx.de wrote:
> > > > cleaner shutdown.  This is taken from a email that was sent to me during
> > > > that horrible xorg-server and hal upgrade.
> > > >
> > > > > Hold down Atl, hold down SysRq, press each of the keys in turn. The
> > > > > usual full sequence is R-E-I-S-U-B Reboot Even If System Utterly
> > > > > Broken By ${DEITY} - this tagline picker is spooky at times :-O
> > > > > -- Neil Bothwick
> > > >
> > > > I tried this once when I was unable to get my keyboard to respond to
> > > > anything else.  I made it through the first three or four and was
> > > > returned to a console with a working keyboard.  Since you are shutting
> > > > down, you may want to go through them all to be safe.  I think the last
> > > > one does a reboot.
> > > >
> > > > Hope that helps.
> > > >
> > > > Dale
> > > >
> > > > :-) :-)
> > >
> > > Hi Dale,
> > >
> > > thanks a lot for your help!!!  :)
> > >
> > > This will help to bring donw the machine in an more
> > > cleaner way as simply pressing the power switch ;-)
> > >
> > > But:
> > > How can I figure out, what hangs the shutdown process itsself?
> > 
> > Last time I came across a problem like this I had forgotten to select the 
> > right chipset under Graphics support/AGP Support/ in the kernel.  So I 
> > suggest you revisit your kernel and xorg drivers setups for your card.
> > -- 
> Hi.  I have a somewhat similar problem, when I shutdown it goes all the
> way to the end, but instead of shutting down, it says
> init: nomore processes left in this runlevel.  This is fine if I am
> here, but from a remote location it would not work, so how can I figure
> out why this is happening?  I think this started when I went to
> baselayout 2, but not certain of that.
> 

I solved the problem:

/etc/slim.conf has the 

    daemon = no

flag, so the boot process seems optically ok but hangs right
after slim hast started.
Shutting down the system tries to stop services/processes/action,
which never has been started...which fails in a hang.

I dont know exactly...but...if that flag is the default configuration
when installing slim I would suggest to change it to

    daemon = yes

to prevent users like me to spend the weekend in searching for a 
problem in the shutdown process.

> -- 
> Your life is like a penny.  You're going to lose it.  The question is:
> How do
> you spend it?
> 
>          John Covici
>          covici@ccs.covici.com

Life is worth more than a penny...

           Meino Christian Cramer
           Meino.Cramer@gmx.de
           ;)


-- 
Please don't send me any Word- or Powerpoint-Attachments
unless it's absolutely neccessary. - Send simply Text.
See http://www.gnu.org/philosophy/no-word-attachments.html
In a world without fences and walls nobody needs gates and windows.

Re: [gentoo-user] Shutting down process hangs - how to proceed?

[covici]

meino.cramer@gmx.de wrote:

> covici@ccs.covici.com <covici@ccs.covici.com> [09-09-19 15:19]:
> > Mick <michaelkintzios@gmail.com> wrote:
> > 
> > > On Saturday 19 September 2009, meino.cramer@gmx.de wrote:
> > > > > cleaner shutdown.  This is taken from a email that was sent to me during
> > > > > that horrible xorg-server and hal upgrade.
> > > > >
> > > > > > Hold down Atl, hold down SysRq, press each of the keys in turn. The
> > > > > > usual full sequence is R-E-I-S-U-B Reboot Even If System Utterly
> > > > > > Broken By ${DEITY} - this tagline picker is spooky at times :-O
> > > > > > -- Neil Bothwick
> > > > >
> > > > > I tried this once when I was unable to get my keyboard to respond to
> > > > > anything else.  I made it through the first three or four and was
> > > > > returned to a console with a working keyboard.  Since you are shutting
> > > > > down, you may want to go through them all to be safe.  I think the last
> > > > > one does a reboot.
> > > > >
> > > > > Hope that helps.
> > > > >
> > > > > Dale
> > > > >
> > > > > :-) :-)
> > > >
> > > > Hi Dale,
> > > >
> > > > thanks a lot for your help!!!  :)
> > > >
> > > > This will help to bring donw the machine in an more
> > > > cleaner way as simply pressing the power switch ;-)
> > > >
> > > > But:
> > > > How can I figure out, what hangs the shutdown process itsself?
> > > 
> > > Last time I came across a problem like this I had forgotten to select the 
> > > right chipset under Graphics support/AGP Support/ in the kernel.  So I 
> > > suggest you revisit your kernel and xorg drivers setups for your card.
> > > -- 
> > Hi.  I have a somewhat similar problem, when I shutdown it goes all the
> > way to the end, but instead of shutting down, it says
> > init: nomore processes left in this runlevel.  This is fine if I am
> > here, but from a remote location it would not work, so how can I figure
> > out why this is happening?  I think this started when I went to
> > baselayout 2, but not certain of that.
> > 
> 
> I solved the problem:
> 
> /etc/slim.conf has the 
> 
>     daemon = no
> 
> flag, so the boot process seems optically ok but hangs right
> after slim hast started.
> Shutting down the system tries to stop services/processes/action,
> which never has been started...which fails in a hang.
> 
> I dont know exactly...but...if that flag is the default configuration
> when installing slim I would suggest to change it to
> 
>     daemon = yes
> 
> to prevent users like me to spend the weekend in searching for a 
> problem in the shutdown process.
> 
I don't have such a file, or as far as I know, such a package.  My
shutdown does not hang, it just says no more processes left at this run
level and sits there forever and will not restart the system.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

[gentoo-user] Re: Shutting down process hangs - how to proceed?

[walt]

On 09/20/2009 09:15 AM, meino.cramer@gmx.de wrote:

> solfire:/home/mccramer>l /etc/asound.state
> -rw-r--r-- 1 root root 10122 2009-08-06 18:05 /etc/asound.state
> solfire:/home/mccramer>sudo rm -f /etc/asound.state
> solfire:/home/mccramer>sudo alsactl store
> alsactl: get_control:249: Cannot read control '2,0,0,Mic Capture Volume,0': Invalid argument
> solfire:/home/mccramer>

I also have /etc/asound.names, which was apparently created a year ago
by "alsactl names" (now deprecated).  If you have that file it should
also be deleted.

Re: [gentoo-user] Shutting down process hangs - how to proceed?

[Dale]

covici@ccs.covici.com wrote:
> meino.cramer@gmx.de wrote:
>
>   
>> covici@ccs.covici.com <covici@ccs.covici.com> [09-09-19 15:19]:
>>     
>> I solved the problem:
>>
>> /etc/slim.conf has the 
>>
>>     daemon = no
>>
>> flag, so the boot process seems optically ok but hangs right
>> after slim hast started.
>> Shutting down the system tries to stop services/processes/action,
>> which never has been started...which fails in a hang.
>>
>> I dont know exactly...but...if that flag is the default configuration
>> when installing slim I would suggest to change it to
>>
>>     daemon = yes
>>
>> to prevent users like me to spend the weekend in searching for a 
>> problem in the shutdown process.
>>
>>     
> I don't have such a file, or as far as I know, such a package.  My
> shutdown does not hang, it just says no more processes left at this run
> level and sits there forever and will not restart the system.
>
>   

Has the OP checked his inittab file?  I ran into something like this
once a long time ago and I had to replace the inittab file since some of
it was gone.  That file belongs to sysvinit so it may be worth
re-emerging that to see if helps. 

I can post mine if you want something to compare to.  Off list of
course.  Then again, it may not be to big.

Dale

:-)  :-) 

Re: [gentoo-user] Shutting down process hangs - how to proceed?

[covici]

Dale <rdalek1967@gmail.com> wrote:

> covici@ccs.covici.com wrote:
> > meino.cramer@gmx.de wrote:
> >
> >   
> >> covici@ccs.covici.com <covici@ccs.covici.com> [09-09-19 15:19]:
> >>     
> >> I solved the problem:
> >>
> >> /etc/slim.conf has the 
> >>
> >>     daemon = no
> >>
> >> flag, so the boot process seems optically ok but hangs right
> >> after slim hast started.
> >> Shutting down the system tries to stop services/processes/action,
> >> which never has been started...which fails in a hang.
> >>
> >> I dont know exactly...but...if that flag is the default configuration
> >> when installing slim I would suggest to change it to
> >>
> >>     daemon = yes
> >>
> >> to prevent users like me to spend the weekend in searching for a 
> >> problem in the shutdown process.
> >>
> >>     
> > I don't have such a file, or as far as I know, such a package.  My
> > shutdown does not hang, it just says no more processes left at this run
> > level and sits there forever and will not restart the system.
> >
> >   
> 
> Has the OP checked his inittab file?  I ran into something like this
> once a long time ago and I had to replace the inittab file since some of
> it was gone.  That file belongs to sysvinit so it may be worth
> re-emerging that to see if helps. 
> 
> I can post mine if you want something to compare to.  Off list of
> course.  Then again, it may not be to big.
> 
> Dale
> 
> :-)  :-) 
Here is my inittab, its pretty short.
#
# /etc/inittab:  This file describes how the INIT process should set up
#                the system in a certain run-level.
#
# Author:  Miquel van Smoorenburg, <miquels@cistron.nl>
# Modified by:  Patrick J. Volkerding, <volkerdi@ftp.cdrom.com>
# Modified by:  Daniel Robbins, <drobbins@gentoo.org>
# Modified by:  Martin Schlemmer, <azarah@gentoo.org>
#
# $Header: /var/cvsroot/gentoo-x86/sys-apps/sysvinit/files/inittab,v 1.5 2005/12/22 02:03:23 vapier Exp $

# Default runlevel.
id:3:initdefault:

# System initialization, mount local filesystems, etc.
si::sysinit:/sbin/rc sysinit

# Further system initialization, brings up the boot runlevel.
rc::bootwait:/sbin/rc boot

l0:0:wait:/sbin/rc shutdown 
l1:S1:wait:/sbin/rc single
l2:2:wait:/sbin/rc nonetwork
l3:3:wait:/sbin/rc default
l4:4:wait:/sbin/rc default
l5:5:wait:/sbin/rc default
l6:6:wait:/sbin/rc reboot
#z6:6:respawn:/sbin/sulogin

# TERMINALS
c1:12345:respawn:/sbin/agetty 38400 tty1 linux
c2:2345:respawn:/sbin/agetty 38400 tty2 linux
c3:2345:respawn:/sbin/agetty 38400 tty3 linux
c4:2345:respawn:/sbin/agetty 38400 tty4 linux
c5:2345:respawn:/sbin/agetty 38400 tty5 linux
c6:2345:respawn:/sbin/agetty 38400 tty6 linux
c7:2345:respawn:/sbin/agetty 38400 tty7 linux
c8:12345:respawn:/sbin/agetty 38400 tty8 linux
c9:2345:respawn:/sbin/agetty 38400 tty9 linux
c10:2345:respawn:/sbin/agetty 38400 tty10 linux
c11:2345:respawn:/sbin/agetty 38400 tty11 linux


# SERIAL CONSOLES
#s0:12345:respawn:/sbin/agetty 9600 ttyS0 vt100
#s1:12345:respawn:/sbin/agetty 9600 ttyS1 vt100

# What to do at the "Three Finger Salute".
ca:12345:ctrlaltdel:/sbin/shutdown -r now

# Used by /etc/init.d/xdm to control DM startup.
# Read the comments in /etc/init.d/xdm for more
# info. Do NOT remove, as this will start nothing
# extra at boot if /etc/init.d/xdm is not added
# to the "default" runlevel.
x:a:once:/etc/X11/startDM.sh



-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] Shutting down process hangs - how to proceed?

[Dale]

covici@ccs.covici.com wrote:
>
> Here is my inittab, its pretty short.
>
>
> # TERMINALS
> c1:12345:respawn:/sbin/agetty 38400 tty1 linux
> c2:2345:respawn:/sbin/agetty 38400 tty2 linux
> c3:2345:respawn:/sbin/agetty 38400 tty3 linux
> c4:2345:respawn:/sbin/agetty 38400 tty4 linux
> c5:2345:respawn:/sbin/agetty 38400 tty5 linux
> c6:2345:respawn:/sbin/agetty 38400 tty6 linux
> c7:2345:respawn:/sbin/agetty 38400 tty7 linux
> c8:12345:respawn:/sbin/agetty 38400 tty8 linux
> c9:2345:respawn:/sbin/agetty 38400 tty9 linux
> c10:2345:respawn:/sbin/agetty 38400 tty10 linux
> c11:2345:respawn:/sbin/agetty 38400 tty11 linux
>
>   

Other than this section, I didn't see any differences.  Surely that
wouldn't cause this type of problem. 

I'm clueless.  emerge -ev system maybe?  It may catch something that is
broken.

Dale

:-)  :-)

Re: [gentoo-user] Re: Shutting down process hangs - how to proceed?

[meino.cramer]

walt <w41ter@gmail.com> [09-09-21 02:32]:
> On 09/20/2009 09:15 AM, meino.cramer@gmx.de wrote:
> 
> >solfire:/home/mccramer>l /etc/asound.state
> >-rw-r--r-- 1 root root 10122 2009-08-06 18:05 /etc/asound.state
> >solfire:/home/mccramer>sudo rm -f /etc/asound.state
> >solfire:/home/mccramer>sudo alsactl store
> >alsactl: get_control:249: Cannot read control '2,0,0,Mic Capture 
> >Volume,0': Invalid argument
> >solfire:/home/mccramer>
> 
> I also have /etc/asound.names, which was apparently created a year ago
> by "alsactl names" (now deprecated).  If you have that file it should
> also be deleted.

If alsactl is deprecated -- what to use instead?


-- 
Please don't send me any Word- or Powerpoint-Attachments
unless it's absolutely neccessary. - Send simply Text.
See http://www.gnu.org/philosophy/no-word-attachments.html
In a world without fences and walls nobody needs gates and windows.

[gentoo-user] Re: Shutting down process hangs - how to proceed?

[walt]

On 09/20/2009 07:40 PM, meino.cramer@gmx.de wrote:
> walt<w41ter@gmail.com>  [09-09-21 02:32]:
>> On 09/20/2009 09:15 AM, meino.cramer@gmx.de wrote:
>>
>>> solfire:/home/mccramer>l /etc/asound.state
>>> -rw-r--r-- 1 root root 10122 2009-08-06 18:05 /etc/asound.state
>>> solfire:/home/mccramer>sudo rm -f /etc/asound.state
>>> solfire:/home/mccramer>sudo alsactl store
>>> alsactl: get_control:249: Cannot read control '2,0,0,Mic Capture
>>> Volume,0': Invalid argument
>>> solfire:/home/mccramer>
>>
>> I also have /etc/asound.names, which was apparently created a year ago
>> by "alsactl names" (now deprecated).  If you have that file it should
>> also be deleted.
>
> If alsactl is deprecated -- what to use instead?

Sorry, only the "names" flag is deprecated, not alsactl.

Re: [gentoo-user] Re: Shutting down process hangs - how to proceed?

[meino.cramer]

walt <w41ter@gmail.com> [09-09-21 19:36]:
> On 09/20/2009 07:40 PM, meino.cramer@gmx.de wrote:
> >walt<w41ter@gmail.com>  [09-09-21 02:32]:
> >>On 09/20/2009 09:15 AM, meino.cramer@gmx.de wrote:
> >>
> >>>solfire:/home/mccramer>l /etc/asound.state
> >>>-rw-r--r-- 1 root root 10122 2009-08-06 18:05 /etc/asound.state
> >>>solfire:/home/mccramer>sudo rm -f /etc/asound.state
> >>>solfire:/home/mccramer>sudo alsactl store
> >>>alsactl: get_control:249: Cannot read control '2,0,0,Mic Capture
> >>>Volume,0': Invalid argument
> >>>solfire:/home/mccramer>
> >>
> >>I also have /etc/asound.names, which was apparently created a year 
> >>ago
> >>by "alsactl names" (now deprecated).  If you have that file it should
> >>also be deleted.
> >
> >If alsactl is deprecated -- what to use instead?
> 
> Sorry, only the "names" flag is deprecated, not alsactl.
> 
No need to feel sorry ! :)
Thanks for the explanation!

Nonetheless...after removing all the stuff I still get the
described error...

Keep hacking!
mcc




-- 
Please don't send me any Word- or Powerpoint-Attachments
unless it's absolutely neccessary. - Send simply Text.
See http://www.gnu.org/philosophy/no-word-attachments.html
In a world without fences and walls nobody needs gates and windows.

Re: [gentoo-user] Re: Shutting down process hangs - how to proceed?

[Pupino]

2009/9/21  <meino.cramer@gmx.de>:
> walt <w41ter@gmail.com> [09-09-21 19:36]:
>> On 09/20/2009 07:40 PM, meino.cramer@gmx.de wrote:
>> >walt<w41ter@gmail.com>  [09-09-21 02:32]:
>> >>On 09/20/2009 09:15 AM, meino.cramer@gmx.de wrote:
>> >>
>> >>>solfire:/home/mccramer>l /etc/asound.state
>> >>>-rw-r--r-- 1 root root 10122 2009-08-06 18:05 /etc/asound.state
>> >>>solfire:/home/mccramer>sudo rm -f /etc/asound.state
>> >>>solfire:/home/mccramer>sudo alsactl store
>> >>>alsactl: get_control:249: Cannot read control '2,0,0,Mic Capture
>> >>>Volume,0': Invalid argument
>> >>>solfire:/home/mccramer>
>> >>
>> >>I also have /etc/asound.names, which was apparently created a year
>> >>ago
>> >>by "alsactl names" (now deprecated).  If you have that file it should
>> >>also be deleted.
>> >
>> >If alsactl is deprecated -- what to use instead?
>>
>> Sorry, only the "names" flag is deprecated, not alsactl.
>>
> No need to feel sorry ! :)
> Thanks for the explanation!
>
> Nonetheless...after removing all the stuff I still get the
> described error...
>
> Keep hacking!
> mcc
>
>
>
>
> --
> Please don't send me any Word- or Powerpoint-Attachments
> unless it's absolutely neccessary. - Send simply Text.
> See http://www.gnu.org/philosophy/no-word-attachments.html
> In a world without fences and walls nobody needs gates and windows.
>
>
>

What about trying to stop every single service by hand and see if one hangs?
you can have a list of services by "rc-update show" (or something like
that, not really sure)
and then "/etc/init.d/<servicename> stop" for every service, leaving
the boot ones for last
HTH

Davide

[gentoo-user] Re: Shutting down process hangs - how to proceed?

[walt]

On 09/19/2009 05:07 PM, meino.cramer@gmx.de wrote:
> walt<w41ter@gmail.com>  [09-09-20 02:03]:
>> On 09/19/2009 05:31 AM, meino.cramer@gmx.de wrote:
>>
>>> Nonetheless I added the UNLOAD_ON_STOP="no" to /etc/conf.d/alsasound
>>> and we will see what happens.
>>
>> Did you try stopping the alsa service manually?
>>
>> #/etc/init.d/alsasound stop
>>
>
> This gave me errors, since my Webcam's audio part isn't implemented as
> full audio device, but it does not hang:
>
> solfire:/home/mccramer>sudo /etc/init.d/alsasound stop
>   * WARNING:  you are stopping a boot service.
>   * Storing ALSA Mixer Levels ...
> alsactl: get_control:249: Cannot read control '2,0,0,Mic Capture Volume,0': Invalid argument

Hm.  Does alsamixer show that guilty control?

I ran strace on alsactl and it consults a very small number of files
while doing a 'store' operation, so there are very few places that
Mic Capture control could be hiding.  You might try using strace to
see what turns up. (If the error bothers you, of course.)