three emails for the same subject... :S (\_ /) copy the bunny to your profile (0.o ) to help him achieve world domination. (> <) come join the dark side. /_|_\ (we have cookies.) On Tue, Jun 12, 2012 at 11:22 PM, Victor Silva wrote:

I got a ubuntu livecd with gparted lets see what happens. About using thesystem as root. I only run pacman related commands as root have a user I use for mostly day tasks. This user is *NOT* on sudo, basically cause I like to enforce my self to login as root and think about what I'm doing. Also sudo is cumbersome to use in some instances as buil-in commands are not avaliable.

So the only thing I've run as root was the pacman -Syu and followed the arch announces regarding the updates. Nothing bad there I'mho. And the problem I'm facing now has nothing to do with my system usage. Imho either I have a bad sector or something went broken for some instances of the system like mine or the other guy who also reported on the forums.

Regards, Victor

2012/6/12 Attila Vangel

...

Hi, I am not familiar with the problem, but I think the easiest way (if you are not against graphical tools) is to grab a live cd (or "live usb dongle") containing gparted (it's not a bad thing to have, anyway), but I am not an expert at this.

What really surprises me is that you use your system as root !?! I would not dare to do that. I tend to add my user to various groops according to the arch wiki documentation where neeeded, and for the other commands I think I can safely run as root I alias them to be 'sudo <command>', and I maintain this list of safe commands in /etc/sudoers (edited by visudo (you can change the editor of it, just google it)), so that these commands can be executed without entering the password all the time... Maybe not the best thing still, but I guess it's OK with me.

Regards, Attila

2012/6/12 Victor Silva : <snip>

...

Folks after the last upgrade I can no longer shutdown nor reboot my machine (I'm using it as root). The command simply hangs and nothing happens. <snip>

...

I was asked to perform a fsck which failed.It reported /dev/sda5 was mounted. Is there any proper way I should use to call fsck? I did create a /fsck file on / is there other more appropriate command to do it? Problably you asked for my fstab expecting an error like this right? Would it be better to run fsck from a livecd?

regards,

Victor

I do have this exact error messega as I've posted before. I will check htop and post the output here. So now some questions which come out are: is it somehow related to bad sectors? Shutdown is the locked process with the message:

INFO: task [shutdown] blocked for more than 120 seconds.

Still I've made a forced reboot via sysctl and on the next session I've also hit this problem. About xfs_fsr (which I assume is some kind of fsck right?) I need to run fsck from a live cd, I just got one and will try it tonight. So basically we are talking about the samething, still I'm not sure of what is going wrong and sincerely I'm bit afriad of having a system just messed up because of a failing disk. How can I cover this scenario? Regards, Victor 2012/6/12 pants

It sounds like you might have had a process in uninterpretable sleep. This happens sometimes when a process is in a system call and stops working. You can check for this by launching htop and seeing if any processes are permanently in the 'D' state (in the column labeled 'S'). Alternatively, look in /var/log/errors.log and see if you can find messages which look like:

...

INFO: task [processinfo] blocked for more than 120 seconds.

If you do have a process in this state, you won't be able to kill it or unmount the filesystem that it's stuck modifying. Your best bet is to manually kill everything you can, manually umount everything you can, and then force the system down. It sucks, I've had to do this with processes stuck writing to a RAID and then have to wait for a few days while the whole thing is resynced.

It also probably isn't the fault of an upgrade, just some piece of buggy software that finally hit its error. I know that xfs_fsr will quickly and deterministically go into it when run on a filesystem which is almost full.

Good luck!

pants.

On Tue, Jun 12, 2012 at 05:22:43PM -0300, Victor Silva wrote:

...

I got a ubuntu livecd with gparted lets see what happens. About using thesystem as root. I only run pacman related commands as root have a user I use for mostly day tasks. This user is *NOT* on sudo, basically cause I like to enforce my self to login as root and think about what I'm doing. Also sudo is cumbersome to use in some instances as buil-in commands are not avaliable.

So the only thing I've run as root was the pacman -Syu and followed the arch announces regarding the updates. Nothing bad there I'mho. And the problem I'm facing now has nothing to do with my system usage. Imho either I have a bad sector or something went broken for some instances of the system like mine or the other guy who also reported on the forums.

Regards, Victor

2012/6/12 Attila Vangel

...

Hi, I am not familiar with the problem, but I think the easiest way (if you are not against graphical tools) is to grab a live cd (or "live usb dongle") containing gparted (it's not a bad thing to have, anyway), but I am not an expert at this.

What really surprises me is that you use your system as root !?! I would not dare to do that. I tend to add my user to various groops according to the arch wiki documentation where neeeded, and for the other commands I think I can safely run as root I alias them to be 'sudo <command>', and I maintain this list of safe commands in /etc/sudoers (edited by visudo (you can change the editor of it, just google it)), so that these commands can be executed without entering the password all the time... Maybe not the best thing still, but I guess it's OK with me.

Regards, Attila

2012/6/12 Victor Silva : <snip>

...

Folks after the last upgrade I can no longer shutdown nor reboot my machine (I'm using it as root). The command simply hangs and nothing happens. <snip>

...

I was asked to perform a fsck which failed.It reported /dev/sda5 was mounted. Is there any proper way I should use to call fsck? I did create a /fsck file on / is there other more appropriate command to do it? Problably you asked for my fstab expecting an error like this right? Would it be better to run fsck from a livecd?

regards,

Victor

On Tue, 12 Jun 2012 13:42:01 -0700 pants wrote:

check the SMART status of the drives,

I've recently found Pmagic livecd to be very cool for this. Simply click the disk health icon on the desktop.

Oki I reverted to the old kernel and I'm back to the old scenario how can I properly downgrade a kernel? Regards and thx for the help so far guys. This community rocks. 2012/6/13 Victor Silva

2012/6/13 Kevin Chadwick

...

On Tue, 12 Jun 2012 13:42:01 -0700 pants wrote:

...

check the SMART status of the drives,

I've recently found Pmagic livecd to be very cool for this. Simply click the disk health icon on the desktop.

Folks I've messed things even more I did a kernel downgrade, downloaded kernel 3.3.7 from arch time machine and did pacman -U kernel26-2.6.39.3-1-x86_64.pkg.tar.xz System rebuilt modules and so on. After reboot it seems to report my /boot is not a valid partition type with ext2fs. Still grub which is installed there works and I can boot my windows. My plan now is download a live cd do a chroot to my old arch and try to update the kernel for the old state is it manageable?

2012/6/14 gt

On Wed, Jun 13, 2012 at 11:14:06PM -0300, Victor Silva wrote:

...

Oki I reverted to the old kernel and I'm back to the old scenario how can I properly downgrade a kernel?

Regards and thx for the help so far guys. This community rocks.

Since you have already reverted to the old kernel, you don't further need to downgrade it, as you have already downgraded it.

(Assuming, you did a pacman -U <old-kernel>)

I did it for the kenel which hangs, the one before it does not boot as described on the previous posts. So somehow I need to find the last working configuration. Also is shutdown -F a dangerous practice? Cause this works for me.

On Thu, Jun 14, 2012 at 12:18:17AM -0300, Victor Silva wrote:

2012/6/14 gt

...

Since you have already reverted to the old kernel, you don't further need to downgrade it, as you have already downgraded it.

(Assuming, you did a pacman -U <old-kernel>)

I did it for the kenel which hangs, the one before it does not boot as described on the previous posts. So somehow I need to find the last working configuration. Also is shutdown -F a dangerous practice? Cause this works for me.

from the man page, -F switch forces a fsck on reboot. So, i don't think it is dangerous.

It reports a problem reading /boot partition saying something about it being not a valid ext2

I see /boot is ext4 There was a time recently when a kernel bug gave invalid warnings about other filesystem types like ext2, ext3 before mounting ext4 so it could be a red herring, is the exact error gone too quick to note. I presume by Vanilla you mean an arch package? p.s. If you can edit the kernel commandline you can change the init part to init=/bin/sh and hitting b to boot It's limited in what can be done but that way you may be able to troubleshoot some things more quickly by using the built in kernel commands, see if there is a reboot command. If there is it is internal and not from any filesystem. If it works you could then do it again and this time mount your root filesystem and try the reboot command from that. There are also kernel debug configs like printk but I'm not sure that's the route to go down yet. ________________________________________________________ Why not do something good every day and install BOINC. ________________________________________________________

Yeah by vanilla I mean the stock kernel. I dont get what do you mean by: be a red herring, is the exact error gone too quick to note.

red herring as in possibly false or irrelevent error message.

is the exact error gone too quick to note.

Does it flash up before you can get a picture or write down the error message.

Well I can chroot as I did to revert to the old kernel so changing grub menu seems harder than chroot. My main problem is that reverting to the old kernel did not work.

when the grub menu comes up hit the e key move down a line hit e key again change init=/dev/?? to init=/bin/sh hit b key ________________________________________________________ Why not do something good every day and install BOINC. ________________________________________________________

2012/6/15 Ralf Mardorf

On Thu, 2012-06-14 at 11:37 -0300, Victor Silva wrote:

...

Also, is there a procedure I can use to have multiple kernels?

Don't name the packages/kernels "linux". Name them linux, linux-1, linux-2 etc.?!

You also could get different kernels from the repositories, of course not different versions of "linux", but e.g. "linux" + "linux-rt".

$ ls /mnt/archlinux/boot/vmlinuz* /mnt/archlinux/boot/vmlinuz-linux /mnt/archlinux/boot/vmlinuz-linux-rt

Oki. I will try it on the weekend. There seems to be an official bug now: https://bugs.archlinux.org/task/30136

I will provide them the link of our discussion.

Arch always did that automatically for me. I do know that you can set up defaults and fallbacks in KDE just like in Windows. I'm not sure about GNOME, though, as I have used KDE for a while. -----Original Message----- From: arch-general-bounces@archlinux.org [mailto:arch-general-bounces@archlinux.org] On Behalf Of Nelson Marambio Sent: Thursday, June 14, 2012 4:52 PM To: arch-general@archlinux.org Subject: [arch-general] Muting internal speakers Since the change from Win 7 to Arch there is just one function I really miss up to now. Perhaps someone of you can help me out. Is it possible that Arch deactivates the internal speakers of my laptop when I plug in my USB-headset and turn input / output to this ? In Windows I could define the USB headset as default for in-/output so Win made a fallback to internal speakers only when I plugged out the headset again. It would be really great if Arch was that comfortable too. I know in GNOME there are just two clicks to do for switching to another audio hardware but ... :D Warm regards, Nelson.

You can try instaling pulseaudio and pavucontrol , in pavucontrol you can set default device. -- Using Opera's revolutionary email client: http://www.opera.com/mail/

Hello, pulseaudio[1] has that functionality. You should check it out. On KDE , Kmix supports pulseaudio and I am pretty sure it support auto switching too. Regards, --Chris Sakalis [1] - https://wiki.archlinux.org/index.php/Pulseaudio On Fri, Jun 15, 2012 at 12:13 AM, Eric Ryan Jones wrote:

Arch always did that automatically for me.  I do know that you can set up defaults and fallbacks in KDE just like in Windows.  I'm not sure about GNOME, though, as I have used KDE for a while.

-----Original Message----- From: arch-general-bounces@archlinux.org [mailto:arch-general-bounces@archlinux.org] On Behalf Of Nelson Marambio Sent: Thursday, June 14, 2012 4:52 PM To: arch-general@archlinux.org Subject: [arch-general] Muting internal speakers

Since the change from Win 7 to Arch there is just one function I really miss up to now. Perhaps someone of you can help me out.

Is it possible that Arch deactivates the internal speakers of my laptop when I plug in my USB-headset and turn input / output to this ?

In Windows I could define the USB headset as default for in-/output so Win made a fallback to internal speakers only when I plugged out the headset again.

It would be really great if Arch was that comfortable too. I know in GNOME there are just two clicks to do for switching to another audio hardware but ... :D

Warm regards, Nelson.

On Fri, Jun 15, 2012 at 5:04 PM, Heiko Baums wrote:

Am Fri, 15 Jun 2012 10:17:45 +0300 schrieb Chris Sakalis :

...

Hello, pulseaudio[1] has that functionality. You should check it out. On KDE , Kmix supports pulseaudio and I am pretty sure it support auto switching too.

PulseAudio is more or less crap. It still doesn't support (semi-)professional audio cards.

If you don't really need it's super-duper extra functions like gaplessly moving a stream from one sound card to another you better don't bother with PA. It rather makes things worse than better.

Yes, why not repeat that opinion in every thread where pulse is brought up? Its not like its repetitive.

I don't have a solution for the original question, because I don't use two sound cards at the same time, but there are other and better ways to disable the internal notebook speakers.

Usually you can choose in every application which sound card to be used (sometimes in it's config files). I guess there are software mixers for every desktop environment which let you choose the sound card, which shall be used.

Which sounds an awful lot like slimmed-down pulseaudio to me. At the OP - pulseaudio may (or may not) help in your situation. The 'default' device is not the same as a Windows default device in the sense that currently playing streams will not be automatically moved. I use a script to do that (change default device and move all streams, I think I may even have posted it up on the pulse wiki), but (AFAIK) there aren't any 'hooks' for activating such scripts within pulseaudio when a new card is detected. Not sure if udev can do that, I just press a shortcut to run the script when I plug in my external headphones/sound card.

PS: On Fri, 2012-06-15 at 12:56 +0200, Ralf Mardorf wrote:

I agree with Heiko Baums and Oon-Ee Ng, this is possible because ...

If PA should be able to solve the OP's issue, then it's unimportant what issues PA could cause.

If somebody replies with a guess, that PA might solve the issue on GNOME, because KMix is able to solve it, then a hint, that PA could cause serious issues IMO is ok.

I suspect that PA already is installed, since the OP referred to GNOME. Less people run GNOME without PA. So neither doesn't PA cause an issue for the OP, nor does it satisfy the OP's needs.

Am Fri, 15 Jun 2012 18:06:20 +0800 schrieb Oon-Ee Ng :

Yes, why not repeat that opinion in every thread where pulse is brought up? Its not like its repetitive.

Yes, why not repeat that suggestion installing PulseAudio in every thread where somebody has a simple question about selecting an audio card? It's not like it's repetitive. And the most useless suggestion anyway. Heiko

On Fri, 2012-06-15 at 13:00 +0100, Mauro Santos wrote:

Have you actually tried using the latest pulseaudio for a couple of weeks? For supported hardware it sure does something somewhat similar to what the OP wants.

It sure seems you have some gripe with pulseaudio and/or pulseaudio's upstream and are on a personal crusade to bash it every time you can. Pulseaudio is not perfect but neither is alsa, if alsa only solves the problem then fine, if some user has better luck with pulseaudio+alsa so be it, the user will decide for itself if it sucks or not so just let it rest.

Ubuntu Studio Precise chips with a new version of PA and a PA Jack bridge. RME HDSPe AIO started working when PA was removed, it didn't work with PA. Regarding to this thread it's irrelevant. BOT as mentioned before, the OP seem to use GNOME, so it's likely that he already has PA installed. Audio out is ok, so PA doesn't cause trouble, but it also doesn't auto-mute the speakers. So EVERYBODY who brings up to install or not install PA does babble and doesn't help. Are there settings for PA, ALSA some GNOME mixer or what ever, that enables what the OP needs?

Am Fri, 15 Jun 2012 13:00:56 +0100 schrieb Mauro Santos :

Have you actually tried using the latest pulseaudio for a couple of weeks? For supported hardware it sure does something somewhat similar to what the OP wants.

It sure seems you have some gripe with pulseaudio and/or pulseaudio's upstream and are on a personal crusade to bash it every time you can. Pulseaudio is not perfect but neither is alsa, if alsa only solves the problem then fine, if some user has better luck with pulseaudio+alsa so be it, the user will decide for itself if it sucks or not so just let it rest.

I haven't tried using the latest PA for a couple of weeks, because I've got an M-Audio Audiophile 24/96. And this is one of those (semi-)professional audio cards which are not supported by PA. So, yes, I have made my experiences. It's not a personal crusade, and it's not bashing. It's just my personal experiences with PA, which totally doesn't work with my audio card. The problems that I have in those discussions, why I "bash" it (as you call it), are those: 1. PA may work with some certain sound cards (only consumer sound cards), but not with every sound and audio card. Still it always gets hyped as the ultimate sound server by the PA fanboys, which allegedly solves every problem and question. But unfortunately those fanboys are usually only those users who only know their own SoundBlaster or AC'97 onboard sound card and simply ignore the fact that there are some other, more professional audio cards. So they think if PA works for them, it has to work for everybody else, which is totally wrong. 2. Those PA fanboys ignore the fact, that PA indeed is an additional layer which can indeed cause additional issues, which make it harder to find the real reason for those issues. 3. Even the PA developers blame ALSA, which works perfectly with those more professional audio cards out-of-the-box, for the bugs in PA, even if it was clear that it is PA's fault. 4. The PA developers try to having made PA to a new de facto Linux standard - that's at least my impression -, even if it doesn't support every sound and audio card. From a de facto Linux standard it can be expected that it supports every hardware of that kind. Until this is not the case it just has to be called crap, if it's treated as a standard. 5. It's somehow related to 4. At least the GNOME developers and some distribution developers force the users to install PA as a dependency of GNOME or the whole distro. This probably isn't a problem for those PA fanboys with some consumer cards. But it is a very big problem for people who own a better sound or audio card, which doesn't work with PA. Those people not only want but even need a working sound output. 6. The PA fanboys always answer every sound related question by suggesting to install PA, regardless of the question and if the problem can be easily solved in other ways. 7. The PA fanboys seem to be persuaded that PA doesn't have and never will have any bugs. 8. PA is just overrated regarding its features. Maybe there are use cases for PA, maybe it can make some things a bit easier for some people. But it's in most cases not necessary as some PA fanboys are always claiming. And this is not bashing. Those are just facts. If PA would be treated as a normal and optional piece of software which can be installed or not, and if it would not be treated as a de facto Linux standard, and if the users would not be forced to install PA as a dependency, I would have absolutely no problem with PA. But as long as the situation is as I described above, you always will read such comments, if someone mentions PA. Either PA has to support every sound and audio card incl. the (semi-)professional audio cards as they are meant to be used (not crippled down to stereo cards) or PA has to be removed as a dependency from every desktop environment and distro. And the PA fanboys should consider if it's really necessary to install PA to solve a problem or to answer a question, or if there are easier ways (in user friendlyness and in KISS). And they should ask before, if PA would even make sense for the questioner. That's the point. Heiko

Am 15.06.2012 18:05, schrieb Oon-Ee Ng:

Having a bit more time to think now, to the OP, if this discussion hasn't scared you off,

Well, I have to confess that I became a bit meek by following the discussion. Actually I just wanted to get a solution to my "problem".:) Oon-Ee, It would be great if you can send me your script or tell me the article in the wiki. Heiko, by installing GNOME, pulseaudio was installed as dependency I guess. So please don't blame for starting with pulse, ok ? ^^ After all I am confused if my installation uses ALSA or pulse now. I installed ALSA but the ALSAmixer shows me the volume level of pulse ??? If you made the experience that pulse failed where ALSA succeeded there is nothing to say against it. But I have to deal with my consumer-card (it's really an HDA-chip by Intel) and thus I can't contribute something relevant. What I learned from this discussion 1) there are several sound-layer (OSS, ALSA, pulse, Jack (?)) 2) several layer can work together but also can result conflicts (nothing but logical) Spoken without any irony: thank you all for this experience. I already have at least two more question and I will use this mailinglist with pleasure ! P.S.: Don't care about the headline from GMX. German Mail-Provider sometimes handle mails writen in English very hysterical. I try to train the server-located Spamfilter with every new mail from this ML but it will take a while.

On Fri, 2012-06-15 at 20:13 +0200, Ralf Mardorf wrote:

OSS (obsolete) and ALSA are the instances that are needed for audio. Pulse and Jack are "layers".

Sorry for my broken English. You need one of both, the obsolete OSS or the current used ALSA. Stuff similar to PA and jackd, there were (are) others too, handle the audio streams in different ways, but usually use ALSA as backend. Firewire audio devices might be something special.

Am Fri, 15 Jun 2012 20:00:10 +0200 schrieb Nelson Marambio :

Heiko, by installing GNOME, pulseaudio was installed as dependency I guess.

That's one of the problems I have with PA, indeed. ;-)

So please don't blame for starting with pulse, ok ?

I don't blame you, but I blame the people who always at once suggest installing and using PA as the ultimate solution and answer for everything. And I blame the developers who force the users to installing PA as a dependency. If PA is working for you, you want to deal with PA and PA solves your problem, it's totally OK for me.

^^ After all I am confused if my installation uses ALSA or pulse now. I installed ALSA but the ALSAmixer shows me the volume level of pulse ???

I guess alsamixer only shows its own volume level. PA can set its own volume level which is, of course, relative to the ALSA level. Just turn up the volume to the highest level in PA and switch the volume level in alsamixer. I guess then you will have a clue.

If you made the experience that pulse failed where ALSA succeeded there is nothing to say against it. But I have to deal with my consumer-card (it's really an HDA-chip by Intel) and thus I can't contribute something relevant.

What I learned from this discussion

1) there are several sound-layer (OSS, ALSA, pulse, Jack (?)) 2) several layer can work together but also can result conflicts (nothing but logical)

That's absolutely right. With one exception, OSS and ALSA are two different sound drivers on the same level. OSS is the older one, and I don't know if there's still an up-to-date version. ALSA has a OSS plugin for compatibility reasons. PulseAudio and Jack are two sound servers which are on the layer on top of ALSA or OSS. Heiko

On 15/06/2012 8:30 PM, Oon-Ee Ng wrote:

Still not on my laptop, but I searched around, posted it a while back on the pulseaudio wiki. Here it is

http://www.freedesktop.org/wiki/Software/PulseAudio/FAQ#How_do_I_switch_the_...

Again, not sure if by now there's a way to run this script whenever a card is plugged in and out, if you do find that let me know =). Like I said, I just bind the script to a shortcut key using xbindkeys

I'm not sure how 'recommended' it is, but there is a method of running scripts when devices are plugged in using udev rules. There is a guide here http://www.banquise.org/hardware/how-to-automatically-run-a-script-after-ins... though it involves being able to identify which device your usb sound device is. (Rather than blindingly following the example I recommend reading through http://www.reactivated.net/writing_udev_rules.html to understand what you are doing)

On Mon, 2012-06-18 at 15:41 +0200, Ralf Mardorf wrote:

On Mon, 2012-06-18 at 08:34 -0400, Stephen E. Baker wrote:

...

it involves being able to identify which device your usb sound device is.

"So run: udevinfo -a -p /sys/block/sda (replace sda with you device)" - http://www.banquise.org/hardware/how-to-automatically-run-a-script-after-ins...

What is the name for the sound device?

FWIW, you get unique device name listed in /proc/asound/

A Swissonic device spinymouse@precise:~$ ls -hAl /proc/asound/ | grep card3 dr-xr-xr-x 2 root root 0 Jun 18 15:14 card3 lrwxrwxrwx 1 root root 5 Jun 18 15:14 U0x170b0x11 -> card3 A Korg device spinymouse@precise:~$ ls -hAl /proc/asound/ | grep card3 dr-xr-xr-x 2 root root 0 Jun 18 15:14 card3 lrwxrwxrwx 1 root root 5 Jun 18 15:14 nanoKONTROL -> card3

but what names are used for "udevinfo -a -p /sys/block/[...]"?

spinymouse@precise:~$ ls /sys/block/ loop0 loop2 loop4 loop6 ram0 ram10 ram12 ram14 ram2 ram4 ram6 ram8 sda sr0 loop1 loop3 loop5 loop7 ram1 ram11 ram13 ram15 ram3 ram5 ram7 ram9 sdb

Resp. in /sys/"whatever"

On 18/06/2012 9:48 AM, Ralf Mardorf wrote:

On Mon, 2012-06-18 at 15:41 +0200, Ralf Mardorf wrote:

...

On Mon, 2012-06-18 at 08:34 -0400, Stephen E. Baker wrote:

...

it involves being able to identify which device your usb sound device is. "So run: udevinfo -a -p /sys/block/sda (replace sda with you device)" - http://www.banquise.org/hardware/how-to-automatically-run-a-script-after-ins...

What is the name for the sound device?

FWIW, you get unique device name listed in /proc/asound/

A Swissonic device spinymouse@precise:~$ ls -hAl /proc/asound/ | grep card3 dr-xr-xr-x 2 root root 0 Jun 18 15:14 card3 lrwxrwxrwx 1 root root 5 Jun 18 15:14 U0x170b0x11 -> card3 A Korg device spinymouse@precise:~$ ls -hAl /proc/asound/ | grep card3 dr-xr-xr-x 2 root root 0 Jun 18 15:14 card3 lrwxrwxrwx 1 root root 5 Jun 18 15:14 nanoKONTROL -> card3

but what names are used for "udevinfo -a -p /sys/block/[...]"?

spinymouse@precise:~$ ls /sys/block/ loop0 loop2 loop4 loop6 ram0 ram10 ram12 ram14 ram2 ram4 ram6 ram8 sda sr0 loop1 loop3 loop5 loop7 ram1 ram11 ram13 ram15 ram3 ram5 ram7 ram9 sdb Resp. in /sys/"whatever"

/sys/block/ is block devices (i.e. hard drives, potential ram drives, loop back devices), so it wouldn't be in there. I'm not sure where in /sys it would be, but if you check the last few lines dmesg after plugging it in it should tell you.

On Mon, 2012-06-18 at 10:43 -0400, Ray Kohler wrote:

Try /sys/class/sound/card0 (or card1, or whatever number).

Without USB spinymouse@precise:~$ ls /sys/class/sound card0 card2 controlC1 dmmidi dmmidi2 midi midi2 midiC1D0 pcmC0D0c pcmC1D0c pcmC2D0c seq card1 controlC0 controlC2 dmmidi1 hwC0D0 midi1 midiC0D0 midiC2D0 pcmC0D0p pcmC1D0p pcmC2D0p timer With USB spinymouse@precise:~$ ls /sys/class/sound card0 card3 controlC2 dmmidi1 hwC0D0 midi2 midiC1D0 pcmC0D0c pcmC1D0p seq card1 controlC0 controlC3 dmmidi2 midi midi3 midiC2D0 pcmC0D0p pcmC2D0c timer card2 controlC1 dmmidi dmmidi3 midi1 midiC0D0 midiC3D0 pcmC1D0c pcmC2D0p :) Should be ok for the needs of the OP, since he doesn't need just one special device. OT: I was thinking of another issue that happens to rtirq users. Some unique names changed, e.g. ICE1712 became ice1, so we can't distinguish between ICE1712 and ICE1724 anymore to set up the prio for soft IRQs and even for other cards rtirq settings needs to be different for different kernel versions.

On Jun 16, 2012 4:48 AM, "Heiko Baums" wrote:

Am Sat, 16 Jun 2012 00:05:11 +0800 schrieb Oon-Ee Ng :

...

That load of drivel below isn't bashing? You refer to fanboys and proceed to list a whole loss of statements not made by anyone in this thread. And then you insist that for pulse to be standard it must conform to your standards, which by the way something like cups also fails. Man, I can't believe my office photocopier can't print out stapled copies using cups, it shouldn't be called a standard until it can do that....

Not to mention the multiple times you assume that pulse is being forced on everyone just because it's a dependency of some software. May as well complain how X is being forced on everyone.

You, sir, are a troll.

That's funny. A troll is calling someone else, who just wrote facts, a troll. But you may keep comparing apples with oranges, if it makes you happy.

Your "facts" are opinions and assumptions, mostly about putting words in the mythical "pulse fanboy's" mouth. Not to mention totally unhelpful to the discussion.

If your photocopier can't print out staple copies using cups, this is totally different from not being able to hear any sound, because you only have a professional audio card and the sound server you are forced to use is not able to handle this audio card. And cups is not the only printing server. You see the difference?

Your previous email indicated sounds could be heard, but only stereo sound. Afaik that's the case for most 5.1 and all 7.1 cards. How is that different from cups not supporting advanced options in my printer? Because pulse is the only existing sound server? You can't and won't use pulse, fine, just don't use it. Jack or pure alsa still work. Just stop pretending that your arbitrary criteria for pulse is in any way an inalienable truth. Just to summarize, it seems your two main gripes are lack of support for semi pro cards and being "forced" to use it. The former is not likely to change, the latter is patently untrue seeing as how you are already not using it.

Heiko

On Sat, Jun 16, 2012 at 9:36 AM, Heiko Baums wrote:

Am Sat, 16 Jun 2012 08:23:54 +0800 schrieb Oon-Ee Ng :

...

Your "facts" are opinions and assumptions, mostly about putting words in the mythical "pulse fanboy's" mouth. Not to mention totally unhelpful to the discussion.

I would say, your nonsense is unhelpful. And my "facts" are facts. Just read them again, and read all other discussions about questions or problems regarding PA, and you will see it.

How is that relevant to this discussion? Or is it now common practice to bring up things posted elsewhere by different people just to prove your point? Straw men are useful that way. Especially when you have an 'either PA is good and awesome or its a useless piece of crap' viewpoint. <snip a lot of repeated stuff>

...

Just stop pretending that your arbitrary criteria for pulse is in any way an inalienable truth. Just to summarize, it seems your two main gripes are lack of support for semi pro cards and being "forced" to use it. The former is not likely to change, the latter is patently untrue seeing as how you are already not using it.

Not untrue, it's true. I have such an audio card and I tested PA myself. I bet you don't have such an audio card, you don't know how they work and you haven't tested PA with them. So who should stop pretending anything? You or me?

Sigh, please read before replying. The LATTER is untrue, I'm not saying that your card works with PA (though you yourself said it does, to a degree, meaning in stereo). You should stop pretending to being forced to use PA (or that anyone in Linux is forced to use PA), because THAT is untrue. In other words, gripe 1 = support for semi-pro cards, gripe 2 = being forced to use PA. Gripe 1 is not likely to change, whether you like it or not. PA is an abstraction which means the application using it doesn't need to care about coding for ALSA. Upstream's decision for now is that supporting non-stereo or 5.1 cards is not yet worth the hassle. Gripe 2 is untrue and just FUD, especially on an Arch Linux list where the developers (wonder in particular) have practically bent over backwards accommodating users who want the choice.

And then you insist that for pulse to be standard it must conform to your standards, which by the way something like cups also fails. Man, I can't believe my office photocopier can't print out stapled copies using cups, it shouldn't be called a standard until it can do that....

ANYONE can easily unplug and send a photocopier back because it doesn't print on thick enough paper for quality business cards.

You, sir, are a troll.

He may be a Troll for hijacking the thread, though I haven't followed the thread closely enough to say so. You are a worse Troll because you haven't added any value at all. 9./ PA doesn't work with a grsecurity kernel. Unfortunately many manufacturers of high quality cards don't support Linux at all anyway. I can understand his annoyance when he has found one and it's been broken by PA which he's had to spend lots of time disabling. If Arch has doen everything it can to make this easier, then wow those upstream devs are arrogant or blind to all the uses of their software. I notice Gnome3 doesn't provide focus window without raise upon click as all other Window managers do and easily configurable out of the box too. ________________________________________________________ Why not do something good every day and install BOINC. ________________________________________________________

On Sat, 2012-06-16 at 15:30 +0100, Kevin Chadwick wrote:

He may be a Troll for hijacking the thread, though I haven't followed the thread closely enough to say so.

He isn't a troll since there where stupid recommendations to install PA to a system where PA already is installed. The PA "fanboys" recommended it, before thinking and Heiko just said, that it's not smart to recommend PA, as soon as audio doesn't work.

You are a worse Troll because you haven't added any value at all.

No, IIRC he was the only one who at least linked to a scrip that can be used with a shortcut or launcher and mentioned, that it might be possible to add some lines that take care of mounted USB devices. So again, much noise regarding to big nothing :D.

On Fri, 15 Jun 2012 11:04:30 +0200 Heiko Baums wrote:

Am Fri, 15 Jun 2012 10:17:45 +0300 schrieb Chris Sakalis :

...

Hello, pulseaudio[1] has that functionality. You should check it out. On KDE , Kmix supports pulseaudio and I am pretty sure it support auto switching too.

PulseAudio is more or less crap. It still doesn't support (semi-)professional audio cards.

If you don't really need it's super-duper extra functions like gaplessly moving a stream from one sound card to another you better don't bother with PA. It rather makes things worse than better.

I don't have a solution for the original question, because I don't use two sound cards at the same time, but there are other and better ways to disable the internal notebook speakers.

Usually you can choose in every application which sound card to be used (sometimes in it's config files). I guess there are software mixers for every desktop environment which let you choose the sound card, which shall be used.

Btw., isn't there a button on the notebook which can mute those speakers?

Heiko

Talk about serious sour grapes .. I have 2 sound cards one internal and a USB one with PA gives me a lot less bother than ALSA did .. Pete -- Linux 7-of-9 3.3.8-1-ARCH #1 SMP PREEMPT Tue Jun 5 15:20:32 CEST 2012 x86_64 GNU/Linux

Am Fri, 15 Jun 2012 18:22:45 +0800 schrieb ShichaoGao :

True! Maybe many people got the bad impression of PA in previous versions.

Wrong! Maybe many people got the bad impression of PA, because PA just still doesn't work with their audio cards, and because PA still causes more problems than it solves. There are only a very few SoundBlaster and AC'97 onboard sound cards which are supported by PA. Maybe PA works with those sound cards. But it doesn't work with other ones like the (semi-)professional audio cards. And most of PA's features - well, every useful feature - is available by ALSA and/or the audio applications themselves. Nevertheless installing PA just adds a new additional layer that can cause problems. So finding the reason for a bug is unnecessarily more complicated than without PA. Oh yes, I forgot, PA doesn't and never will have any bugs. Bugs are always only caused by ALSA, which works absolute flawlessly, even with those (semi-)professional audio cards. Heiko

Am Fri, 15 Jun 2012 06:27:47 -0700 schrieb David Benfell :

I think it *might* be possible to configure PulseAudio to work correctly. But in my experience, only LinuxMint has gotten this right out of the box.

Unfortunately not. The configuration methods you find in the web, in several forums and mailing lists is just a workaround. Well, I wouldn't even call it workaround, because those professional audio cards are crippled down to simple stereo cards by those configurations. PA is not able to handle those audio cards as they are meant to be handled.

And in the majority of these cases over the last few years, removing pulseaudio was the *only* thing I had to do to get sound working.

I must admit that I'm not a GNOME user, I'm using Xfce, but I don't think that it is the right way to force the users to install PA as a dependency, even if PA can be uninstalled afterwards. On the other hand I read that it's not that easy to just uninstall PA. Heiko

Am Fri, 15 Jun 2012 16:08:40 -0700 schrieb David Benfell :

I found it more annoying to uninstall pulseaudio than difficult. And it's fair to say I was already annoyed, so there has also been a cathartic element to it.

Basically, using whatever package manager was appropriate to the distribution, I searched and removed pulse*, remembering that some packages that list pulseaudio as a dependency are in fact meta-packages that simply exist to bring in all associated packages and which can in fact be removed once you have a functioning installation (though you may find you want to mark other desired packages as manually selected).

This sounds like PA isn't a dependency for GNOME any longer? This would mean that it's just a downstream bug, and PA should be handled as an optional dependency or not as a dependency at all by the distros. Heiko

Hi, You have rather new laptop, right? So most probable is that you have soundcard based on HDA chipset, you could check this with this command (type it in your favourite terminal emulator, like xterm or gnome-terminal): $ lsmod | grep hda If you see something like "snd_hda_codec" it means that you have it :) Now from Kernel documentation: "Another related problem is the automatic mute of speaker output by headphone plugging. This feature is implemented in most cases, but not on every preset model or codec-support code. In anyway, try a different model option if you have such a problem. Some other models may match better and give you more matching functionality. If none of the available models works, send a bug report. See the bug report section for details." It basically means that driver for your card is buggy, or is wrongly advertised by BIOS to kernel and bad driver is assign to handle the card. In that situation you could try to manually assign it. At [1] you've got comprehensible thread what to do with it. I hope that help :) [1] http://ubuntuforums.org/showthread.php?t=1043568 ---- Pozdrawiam Łukasz Redynk W dniu 14.06.2012 22:52, Nelson Marambio pisze:

Since the change from Win 7 to Arch there is just one function I really miss up to now. Perhaps someone of you can help me out.

Is it possible that Arch deactivates the internal speakers of my laptop when I plug in my USB-headset and turn input / output to this ?

In Windows I could define the USB headset as default for in-/output so Win made a fallback to internal speakers only when I plugged out the headset again.

It would be really great if Arch was that comfortable too. I know in GNOME there are just two clicks to do for switching to another audio hardware but ... :D

Warm regards, Nelson.

W dniu 15.06.2012 17:53, Oon-Ee Ng pisze:

On Jun 15, 2012 9:19 PM, "Łukasz Redynk" wrote

...

It basically means that driver for your card is buggy, or is wrongly advertised by BIOS to kernel and bad driver is assign to handle the card. In that situation you could try to manually assign it. At [1] you've got comprehensible thread what to do with it. I hope that help :)

No it wouldn't because he was talking about a separate USB device.

Ok, I've missed the USB part and thought it's about mini jack connection, my bad. -- Pozdrawiam Łukasz Redynk

On Tue, Jun 12, 2012 at 05:53:36PM -0300, Victor Silva wrote:

Logs here: http://pastebin.com/0BMzruNJ Nothing happens, this is the point. I can still use the system normally after the shutdown command. It does not turn X off. It does not shutdown just after the broadcast. This is what I consider extremelly strange. AS you pointed out I could have something waiting to be unmounted so I did a umount -a and kill -9 -1 to be sure nothing was hanging. Still could not shutdown.

by the way thanks a lot for all the insights so far guys. I'm sure we can work it out :)

...3 or 4 recent bug reports [0]. Your problem is the kde's fine "nepomuk" software [1]. I find it a pretty thorough achievment to let this stuff crash this way. What version of extra/kdebase-runtime do you have installed? cheers! mar77i [0] http://www.google.ch/search?q=nepomuk+error+4+in+libstreams.so

Sorry for double posting but just sat and though and I realized nopomuk isprobably unrelated since the problem also happens if I'm on tty and never start the x server. 2012/6/12 Victor Silva

So can I justremove it and check what happens? This makes sense as nepomuk keeps indexing all the contents of the machine. I will try to remove it and check what happens. Which part of the logs gave you the hint about nepomuk?

Regards, Victor

2012/6/12 Martti Kühne

...

On Tue, Jun 12, 2012 at 05:53:36PM -0300, Victor Silva wrote:

...

Logs here: http://pastebin.com/0BMzruNJ Nothing happens, this is the point. I can still use the system normally after the shutdown command. It does not turn X off. It does not shutdown just after the broadcast. This is what I consider extremelly strange. AS you pointed out I could have something waiting to be unmounted so I did a umount -a and kill -9 -1 to be sure nothing was hanging. Still could not shutdown.

by the way thanks a lot for all the insights so far guys. I'm sure we can work it out :)

...3 or 4 recent bug reports [0]. Your problem is the kde's fine "nepomuk" software [1]. I find it a pretty thorough achievment to let this stuff crash this way. What version of extra/kdebase-runtime do you have installed?

cheers! mar77i

[0] http://www.google.ch/search?q=nepomuk+error+4+in+libstreams.so

2012/6/12 Martti Kühne

On Tue, Jun 12, 2012 at 06:26:59PM -0300, Victor Silva wrote:

...

So can I justremove it and check what happens? This makes sense as nepomuk keeps indexing all the contents of the machine. I will try to remove it and check what happens. Which part of the logs gave you the hint about nepomuk?

Regards, Victor

well, that's what I could tell from the log you posted in [0]. line 21 contained a program name and a shared object.

sorry, and sorry for saying "that was the problem". I should have made clearer these things aren't usually the culprit. the process in question isn't running when you log in to tty, though? and tty also hangs comparably to what you described with X?

There was a way that made old kernels dump all syslog to tty12, which I think was removed from syslog.conf. I only know I left it in however, if shutting down immediately crashes, sleep 2 && shutdown; <ctrl-alt-f12> could work...

Also, please answer below, not above previous posts.

cheers! mar77i

[0] http://pastebin.com/HjwGvDsp

Oki, I'm new to the mailing lists so sorry if I missbehave a bit. :) A thing I've noticed is for some reason /dev/sdb5 which is my /boot partition in another harddisk keeps mounted after the boot process which was not the previous behaviour as far as I can remmember. I googled a bit and found no reasons to make it noauto. Can it be related to the problem? Regards, Victor

2012/6/14 David C. Rankin

On 06/12/2012 02:06 PM, Victor Silva wrote:

...

Folks sorry for cross posting this at forum and mailing lists but so far no solution came there.

Folks after the last upgrade I can no longer shutdown nor reboot my machine (I'm using it as root). The command simply hangs and nothing happens. I've done some research and found https://bbs.archlinux.org/**viewtopic.php?id=141155https://bbs.archlinux.org/viewtopic.php?id=141155 this but that does not seems to be my issue. I'm clueless which logs can I provide you in order to diagnose what can be the problem? Important thing, I have only 1 session running and the system report going down still it never gets past the tty broadcast as it seems.

Ideas?

I had a similar problem that began several months ago with my box hanging on shutdown or reboot. This problem was related to samba shares not being unmounted. To get around the problem a created an entry in '/etc/rc.local.shutdown' to call a script to unmount the drives. This solved the problem. The script I call simply checks whether there is still an entry in /etc/mtab for the share and if so, manually unmounts the share:

[[ $UID -eq 0 ]] && umountcmd=umount || umountcmd="sudo umount"

if grep -q mnt\/phx-cfg /etc/mtab; then echo "umount /mnt/phx-cfg" $umountcmd /mnt/phx-cfg fi

if grep -q mnt\/phx-david /etc/mtab; then echo "umount /mnt/phx-david" $umountcmd /mnt/phx-david fi

if grep -q mnt\/phx /etc/mtab; then echo "umount /mnt/phx" $umountcmd /mnt/phx fi

if grep -q mnt\/win /etc/mtab; then echo "umount /mnt/win" $umountcmd /mnt/win fi

if grep -q mnt\/pv /etc/mtab; then echo "umount /mnt/pv" $umountcmd /mnt/pv fi

exit 0

If you are experiencing shutdown hangs do to lingering mount issues, then something similar to this setup may help. (I never did figure out why the normal shutdown scripts didn't do this automatically)

-- David C. Rankin, J.D.,P.E.

I have no shares. Can I somehow try to umount everything in mtab? I'm not familiar with the internal workings of mtab. I will read a bit. Also the only thing I assume could be hanging is my external HD which I disconnected having no effect on the problem behavior. Still I reported that my /boot partition was being mounted and listed on kde file manager (forgot its name) which was not default behavior. So could be the case that /boot is hanging my shoutdown? I don't get the reason umount -a && shutdown -h now did not do the trick. I ask gently again if you could inform me why did the "magic reboot" did work while shutdown did not. Regards, Victor

On 06/15/2012 08:29 AM, David C. Rankin wrote:

On 06/14/2012 03:12 PM, Victor Silva wrote:

...

I have no shares. Can I somehow try to umount everything in mtab? I'm not familiar with the internal workings of mtab. I will read a bit. Also the only thing I assume could be hanging is my external HD which I disconnected having no effect on the problem behavior. Still I reported that my /boot partition was being mounted and listed on kde file manager (forgot its name) which was not default behavior. So could be the case that /boot is hanging my shoutdown? I don't get the reason umount -a && shutdown -h now did not do the trick.

I ask gently again if you could inform me why did the "magic reboot" did work while shutdown did not.

Regards, Victor

Victor,

I am no expert in the shutdown logic that Arch uses, but it is fairly easy to follow. During shutdown, /etc/rc.shutdown is called and the 'umount_all' command is supposed to take care of unmounting all non-api filesystems. If you have specific commands you need run in _addition to_ what is done by rc.shutdown, then you can put those commands in /etc/rc.local.shutdown. The /etc/rc.local.shutdown must be executable to be called (chmod +x) or (chmod 0755). The rc.local.shutdown file is called close to the beginning of rc.shutdown.

Looking at your mtab file and comparing to mine, I do not have any usb drives connected to my system. Somebody more familiar with issues related to usb drives will need to comment. You might want to try Guillermo's shutdown modified as follows:

umount -arfl -t usbfs,fuseblk

I don't know if that will do it, but you have 5 fuseblk filesystems and 1 usbfs mounted. I don't know how Arch handles their unmounting.

Lastly, I do not use the gnome gvfs-fuse-daemon. That is another entry to look at and make sure it isn't the issue. Maybe try your rc.local.shutdown with:

umount -arfl -t usbfs,fuseblk killall gvfs-fuse-daemon # or whatever that process actually runs as

While reading through this to see how much it relates to my shutdown issues, I have noticed this. With gvfs-fuse-daemon install I noticed in top it is being run with what I would think is an incorrect command. /usr/lib/gvfs//gvfs-fuse-daemon -f /home/user/.gvfs The double slash is not a typo on my part that is how it is listed. Do you see the same results when seeing how the gvfs daemon is being run on the system? I am going to try reinstalling it and seeing if it will install properly and not be run with the double slash. Have not noticed this until today.

2012/6/15 Don deJuan

On 06/15/2012 08:29 AM, David C. Rankin wrote:

...

On 06/14/2012 03:12 PM, Victor Silva wrote:

...

I have no shares. Can I somehow try to umount everything in mtab? I'm not familiar with the internal workings of mtab. I will read a bit. Also the only thing I assume could be hanging is my external HD which I disconnected having no effect on the problem behavior. Still I reported that my /boot partition was being mounted and listed on kde file manager (forgot its name) which was not default behavior. So could be the case that /boot is hanging my shoutdown? I don't get the reason umount -a && shutdown -h now did not do the trick.

I ask gently again if you could inform me why did the "magic reboot" did work while shutdown did not.

Regards, Victor

Victor,

I am no expert in the shutdown logic that Arch uses, but it is fairly easy to follow. During shutdown, /etc/rc.shutdown is called and the 'umount_all' command is supposed to take care of unmounting all non-api filesystems. If you have specific commands you need run in _addition to_ what is done by rc.shutdown, then you can put those commands in /etc/rc.local.shutdown. The /etc/rc.local.shutdown must be executable to be called (chmod +x) or (chmod 0755). The rc.local.shutdown file is called close to the beginning of rc.shutdown.

Looking at your mtab file and comparing to mine, I do not have any usb drives connected to my system. Somebody more familiar with issues related to usb drives will need to comment. You might want to try Guillermo's shutdown modified as follows:

umount -arfl -t usbfs,fuseblk

I don't know if that will do it, but you have 5 fuseblk filesystems and 1 usbfs mounted. I don't know how Arch handles their unmounting.

Lastly, I do not use the gnome gvfs-fuse-daemon. That is another entry to look at and make sure it isn't the issue. Maybe try your rc.local.shutdown with:

umount -arfl -t usbfs,fuseblk killall gvfs-fuse-daemon # or whatever that process actually runs as

Well just tried reinstalling made no difference. So I guess I will be looking it why it is starting that way. It may or may not be related to the shutdown issues. But other than this one thing my symptoms seem to match this minus the screen turning red when freezing. I will post back here if I sort anything out that may help this problem.

I wil try this at home but I'1m at work atm, https://bugs.archlinux.org/task/30136 ry this kernel paramether reboot=pci More info: http://intosimple.blogspot.com.br/2012/06/reboot-on-dell-latitude-e6520-with...

On 06/15/2012 02:48 PM, Victor Silva wrote:

...

2012/6/15 Don deJuan

On 06/15/2012 08:29 AM, David C. Rankin wrote:

...

On 06/14/2012 03:12 PM, Victor Silva wrote:

...

I have no shares. Can I somehow try to umount everything in mtab? I'm

...

not familiar with the internal workings of mtab. I will read a bit. Also the only thing I assume could be hanging is my external HD which I disconnected having no effect on the problem behavior. Still I reported that my /boot partition was being mounted and listed on kde file manager (forgot its name) which was not default behavior. So could be the case that /boot is hanging my shoutdown? I don't get the reason umount -a && shutdown -h now did not do the trick.

I ask gently again if you could inform me why did the "magic reboot" did work while shutdown did not.

Regards, Victor

Victor,

I am no expert in the shutdown logic that Arch uses, but it is fairly easy to follow. During shutdown, /etc/rc.shutdown is called and the 'umount_all' command is supposed to take care of unmounting all non-api filesystems. If you have specific commands you need run in _addition to_ what is done by rc.shutdown, then you can put those commands in /etc/rc.local.shutdown. The /etc/rc.local.shutdown must be executable to be called (chmod +x) or (chmod 0755). The rc.local.shutdown file is called close to the beginning of rc.shutdown.

Looking at your mtab file and comparing to mine, I do not have any usb drives connected to my system. Somebody more familiar with issues related to usb drives will need to comment. You might want to try Guillermo's shutdown modified as follows:

umount -arfl -t usbfs,fuseblk

I don't know if that will do it, but you have 5 fuseblk filesystems and 1 usbfs mounted. I don't know how Arch handles their unmounting.

Lastly, I do not use the gnome gvfs-fuse-daemon. That is another entry to look at and make sure it isn't the issue. Maybe try your rc.local.shutdown with:

umount -arfl -t usbfs,fuseblk killall gvfs-fuse-daemon # or whatever that process actually runs as

Well just tried reinstalling made no difference. So I guess I will be

looking it why it is starting that way. It may or may not be related to the shutdown issues. But other than this one thing my symptoms seem to match this minus the screen turning red when freezing. I will post back here if I sort anything out that may help this problem.

I wil try this at home but I'1m at work atm,

https://bugs.archlinux.org/**task/30136https://bugs.archlinux.org/task/30136 ry this kernel paramether reboot=pci More info: http://intosimple.blogspot.**com.br/2012/06/reboot-on-dell-** latitude-e6520-with-arch.htmlhttp://intosimple.blogspot.com.br/2012/06/reboot-on-dell-latitude-e6520-with...

After reading more into that parameter I found this http://linux.koolsolutions.**com/2009/08/04/howto-fix-** linux-hangfreeze-during-**reboots-and-restarts/http://linux.koolsolutions.com/2009/08/04/howto-fix-linux-hangfreeze-during-...

They show more options. I am going to try the one you suggested shortly and if that does not work do the other suggested option in the link I posted. Thanks for pointing out your findings.

A new kernel update was avaliable fo me today. I hoped it could fix some of the issues we were facing. In fact now I have tons of errors, dbus seems screwd and many other things, among the problems I have now is that X fails with no screen found (both nv and nvidia drivers) and I have no network interfaces I fail to get eth0 up. So *DO NOT UPDATE YOUR KERNELS *I'm quite sad as this is a even bigger mistake than the last one. So I

2012/6/15 Don deJuan think I need to chroot again rever to the old kernel... Anyone else expecting this kind of problem? Btw the reboor parameters for the kernel (which I've tested before the upgrade) also did not work. Regards, Victor

2012/6/16 Victor Silva

2012/6/15 Victor Silva

...

2012/6/15 Don deJuan

...

On 06/15/2012 02:48 PM, Victor Silva wrote:

...

2012/6/15 Don deJuan

On 06/15/2012 08:29 AM, David C. Rankin wrote:

...

On 06/14/2012 03:12 PM, Victor Silva wrote:

...

I have no shares. Can I somehow try to umount everything in mtab? > I'm not > familiar with the internal workings of mtab. I will read a bit. Also > the > only thing I assume could be hanging is my external HD which I > disconnected > having no effect on the problem behavior. Still I reported that my > /boot > partition was being mounted and listed on kde file manager (forgot > its > name) which was not default behavior. So could be the case that > /boot is > hanging my shoutdown? I don't get the reason umount -a && shutdown > -h now > did not do the trick. > > I ask gently again if you could inform me why did the "magic reboot" > did > work while shutdown did not. > > Regards, > Victor > > Victor,

I am no expert in the shutdown logic that Arch uses, but it is fairly easy to follow. During shutdown, /etc/rc.shutdown is called and the 'umount_all' command is supposed to take care of unmounting all non-api filesystems. If you have specific commands you need run in _addition to_ what is done by rc.shutdown, then you can put those commands in /etc/rc.local.shutdown. The /etc/rc.local.shutdown must be executable to be called (chmod +x) or (chmod 0755). The rc.local.shutdown file is called close to the beginning of rc.shutdown.

Looking at your mtab file and comparing to mine, I do not have any usb drives connected to my system. Somebody more familiar with issues related to usb drives will need to comment. You might want to try Guillermo's shutdown modified as follows:

umount -arfl -t usbfs,fuseblk

I don't know if that will do it, but you have 5 fuseblk filesystems and 1 usbfs mounted. I don't know how Arch handles their unmounting.

Lastly, I do not use the gnome gvfs-fuse-daemon. That is another entry to look at and make sure it isn't the issue. Maybe try your rc.local.shutdown with:

umount -arfl -t usbfs,fuseblk killall gvfs-fuse-daemon # or whatever that process actually runs as

Well just tried reinstalling made no difference. So I guess I will be

looking it why it is starting that way. It may or may not be related to the shutdown issues. But other than this one thing my symptoms seem to match this minus the screen turning red when freezing. I will post back here if I sort anything out that may help this problem.

I wil try this at home but I'1m at work atm,

https://bugs.archlinux.org/**task/30136https://bugs.archlinux.org/task/30136 ry this kernel paramether reboot=pci More info: http://intosimple.blogspot.**com.br/2012/06/reboot-on-dell-** latitude-e6520-with-arch.htmlhttp://intosimple.blogspot.com.br/2012/06/reboot-on-dell-latitude-e6520-with...

After reading more into that parameter I found this http://linux.koolsolutions.**com/2009/08/04/howto-fix-** linux-hangfreeze-during-**reboots-and-restarts/http://linux.koolsolutions.com/2009/08/04/howto-fix-linux-hangfreeze-during-...

They show more options. I am going to try the one you suggested shortly and if that does not work do the other suggested option in the link I posted. Thanks for pointing out your findings.

A new kernel update was avaliable fo me today. I hoped it could fix some of the issues we were facing. In fact now I have tons of errors, dbus seems screwd and many other things, among the problems I have now is that X fails with no screen found (both nv and nvidia drivers) and I have no network interfaces I fail to get eth0 up. So *DO NOT UPDATE YOUR KERNELS *I'm quite sad as this is a even bigger mistake than the last one. So I think I need to chroot again rever to the old kernel... Anyone else expecting this kind of problem? Btw the reboor parameters for the kernel (which I've tested before the upgrade) also did not work.

Regards, Victor

I solved many issues still when I try to boot now I get the following

errors:

*Jun 16 13:55:48 localhost kernel: [ 10.463651] microcode: failed to load file amd-ucode/microcode_amd.bin Jun 16 13:55:48 localhost kernel: [ 10.464913] microcode: failed to load file amd-ucode/microcode_amd.bin Jun 16 13:55:48 localhost kernel: [ 10.466051] microcode: failed to load file amd-ucode/microcode_amd.bin Jun 16 13:55:48 localhost kernel: [ 10.467189] microcode: failed to load file amd-ucode/microcode_amd.bin Jun 16 13:55:48 localhost kernel: [ 10.468305] microcode: failed to load file amd-ucode/microcode_amd.bin Jun 16 13:55:48 localhost kernel: [ 10.469389] microcode: failed to load file amd-ucode/microcode_amd.bin Jun 16 13:55:48 localhost kernel: [ 11.920779] sd 6:0:0:0: [sdc] No Caching mode page present Jun 16 13:55:48 localhost kernel: [ 11.920880] sd 6:0:0:0: [sdc] Assuming drive cache: write through Jun 16 13:55:48 localhost kernel: [ 11.924824] sd 6:0:0:0: [sdc] No Caching mode page present Jun 16 13:55:48 localhost kernel: [ 11.924924] sd 6:0:0:0: [sdc] Assuming drive cache: write through Jun 16 13:55:48 localhost kernel: [ 11.931887] sd 6:0:0:0: [sdc] No Caching mode page present Jun 16 13:55:48 localhost kernel: [ 11.931982] sd 6:0:0:0: [sdc] Assuming drive cache: write through * Are my kernel sources messed? I'm still unable the shutdown. Anyone got any ideas which can help? :(

I've solved this issue by adding microcode to modules array in rc.conf thou I've never used this before. Still I'm unable to shutdown. Regards, Victor

2012/6/18 Victor Silva

2012/6/16 Victor Silva

...

2012/6/16 Victor Silva

...

2012/6/15 Victor Silva

...

2012/6/15 Don deJuan

...

On 06/15/2012 02:48 PM, Victor Silva wrote:

...

2012/6/15 Don deJuan

On 06/15/2012 08:29 AM, David C. Rankin wrote: > > On 06/14/2012 03:12 PM, Victor Silva wrote: >> >> I have no shares. Can I somehow try to umount everything in mtab? >>> I'm not >>> familiar with the internal workings of mtab. I will read a bit. >>> Also the >>> only thing I assume could be hanging is my external HD which I >>> disconnected >>> having no effect on the problem behavior. Still I reported that my >>> /boot >>> partition was being mounted and listed on kde file manager (forgot >>> its >>> name) which was not default behavior. So could be the case that >>> /boot is >>> hanging my shoutdown? I don't get the reason umount -a && shutdown >>> -h now >>> did not do the trick. >>> >>> I ask gently again if you could inform me why did the "magic >>> reboot" did >>> work while shutdown did not. >>> >>> Regards, >>> Victor >>> >>> >> Victor, >> >> I am no expert in the shutdown logic that Arch uses, but it is >> fairly >> easy to follow. During shutdown, /etc/rc.shutdown is called and the >> 'umount_all' command is supposed to take care of unmounting all >> non-api >> filesystems. If you have specific commands you need run in >> _addition to_ >> what is done by rc.shutdown, then you can put those commands in >> /etc/rc.local.shutdown. The /etc/rc.local.shutdown must be >> executable to >> be called (chmod +x) or (chmod 0755). The rc.local.shutdown file is >> called close to the beginning of rc.shutdown. >> >> Looking at your mtab file and comparing to mine, I do not have any >> usb drives connected to my system. Somebody more familiar with >> issues >> related to usb drives will need to comment. You might want to try >> Guillermo's shutdown modified as follows: >> >> umount -arfl -t usbfs,fuseblk >> >> I don't know if that will do it, but you have 5 fuseblk >> filesystems >> and 1 usbfs mounted. I don't know how Arch handles their unmounting. >> >> Lastly, I do not use the gnome gvfs-fuse-daemon. That is another >> entry to look at and make sure it isn't the issue. Maybe try your >> rc.local.shutdown with: >> >> umount -arfl -t usbfs,fuseblk >> killall gvfs-fuse-daemon # or whatever that process actually runs >> as >> >> >> >> Well just tried reinstalling made no difference. So I guess I will > be > looking it why it is starting that way. It may or may not be related > to the > shutdown issues. But other than this one thing my symptoms seem to > match > this minus the screen turning red when freezing. I will post back > here if I > sort anything out that may help this problem. > > I wil try this at home but I'1m at work atm, > https://bugs.archlinux.org/**task/30136https://bugs.archlinux.org/task/30136 ry this kernel paramether reboot=pci More info: http://intosimple.blogspot.**com.br/2012/06/reboot-on-dell-** latitude-e6520-with-arch.htmlhttp://intosimple.blogspot.com.br/2012/06/reboot-on-dell-latitude-e6520-with...

After reading more into that parameter I found this http://linux.koolsolutions.**com/2009/08/04/howto-fix-** linux-hangfreeze-during-**reboots-and-restarts/http://linux.koolsolutions.com/2009/08/04/howto-fix-linux-hangfreeze-during-...

They show more options. I am going to try the one you suggested shortly and if that does not work do the other suggested option in the link I posted. Thanks for pointing out your findings.

A new kernel update was avaliable fo me today. I hoped it could fix some of the issues we were facing. In fact now I have tons of errors, dbus seems screwd and many other things, among the problems I have now is that X fails with no screen found (both nv and nvidia drivers) and I have no network interfaces I fail to get eth0 up. So *DO NOT UPDATE YOUR KERNELS *I'm quite sad as this is a even bigger mistake than the last one. So I think I need to chroot again rever to the old kernel... Anyone else expecting this kind of problem? Btw the reboor parameters for the kernel (which I've tested before the upgrade) also did not work.

Regards, Victor

I solved many issues still when I try to boot now I get the following

errors:

*Jun 16 13:55:48 localhost kernel: [ 10.463651] microcode: failed to load file amd-ucode/microcode_amd.bin Jun 16 13:55:48 localhost kernel: [ 10.464913] microcode: failed to load file amd-ucode/microcode_amd.bin Jun 16 13:55:48 localhost kernel: [ 10.466051] microcode: failed to load file amd-ucode/microcode_amd.bin Jun 16 13:55:48 localhost kernel: [ 10.467189] microcode: failed to load file amd-ucode/microcode_amd.bin Jun 16 13:55:48 localhost kernel: [ 10.468305] microcode: failed to load file amd-ucode/microcode_amd.bin Jun 16 13:55:48 localhost kernel: [ 10.469389] microcode: failed to load file amd-ucode/microcode_amd.bin Jun 16 13:55:48 localhost kernel: [ 11.920779] sd 6:0:0:0: [sdc] No Caching mode page present Jun 16 13:55:48 localhost kernel: [ 11.920880] sd 6:0:0:0: [sdc] Assuming drive cache: write through Jun 16 13:55:48 localhost kernel: [ 11.924824] sd 6:0:0:0: [sdc] No Caching mode page present Jun 16 13:55:48 localhost kernel: [ 11.924924] sd 6:0:0:0: [sdc] Assuming drive cache: write through Jun 16 13:55:48 localhost kernel: [ 11.931887] sd 6:0:0:0: [sdc] No Caching mode page present Jun 16 13:55:48 localhost kernel: [ 11.931982] sd 6:0:0:0: [sdc] Assuming drive cache: write through * Are my kernel sources messed? I'm still unable the shutdown. Anyone got any ideas which can help? :(

I've solved this issue by adding microcode to modules array in rc.conf thou I've never used this before. Still I'm unable to shutdown.

Regards, Victor

Folks I'm still investigating the issue. After I try to reboot kernel log gave me this hint: Jun 18 02:30:48 localhost kernel: [ 600.432301] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jun 18 02:30:48 localhost kernel: [ 600.432303] shutdown D 0000000000000001 0 2902 2897 0x00000000 Jun 18 02:30:48 localhost kernel: [ 600.432305] ffff8801c39fbe30 0000000000000086 ffff8801ca2cafa0 ffff8801c39fbfd8 Jun 18 02:30:48 localhost kernel: [ 600.432308] ffff8801c39fbfd8 ffff8801c39fbfd8 ffff880199ae07f0 ffff8801ca2cafa0 Jun 18 02:30:48 localhost kernel: [ 600.432310] 0007ffffffffffff ffff880222b0ee00 0000000000000000 0000000000000000 Jun 18 02:30:48 localhost kernel: [ 600.432312] Call Trace: Jun 18 02:30:48 localhost kernel: [ 600.432315] [<ffffffff81084c22>] ? default_wake_function+0x12/0x20 Jun 18 02:30:48 localhost kernel: [ 600.432317] [<ffffffff8119c3b0>] ? __sync_filesystem+0x90/0x90 Jun 18 02:30:48 localhost kernel: [ 600.432319] [<ffffffff81222f38>] ? blk_finish_plug+0x18/0x50 Jun 18 02:30:48 localhost kernel: [ 600.432321] [<ffffffff814689c9>] schedule+0x29/0x70 Jun 18 02:30:48 localhost kernel: [ 600.432323] [<ffffffff81469455>] rwsem_down_failed_common+0xc5/0x160 Jun 18 02:30:48 localhost kernel: [ 600.432325] [<ffffffff81117d22>] ? do_writepages+0x22/0x50 Jun 18 02:30:48 localhost kernel: [ 600.432327] [<ffffffff8119c3b0>] ? __sync_filesystem+0x90/0x90 Jun 18 02:30:48 localhost kernel: [ 600.432329] [<ffffffff81469525>] rwsem_down_read_failed+0x15/0x17 Jun 18 02:30:48 localhost kernel: [ 600.432331] [<ffffffff8124afc4>] call_rwsem_down_read_failed+0x14/0x30 Jun 18 02:30:48 localhost kernel: [ 600.432333] [<ffffffff814678a7>] ? down_read+0x17/0x20 Jun 18 02:30:48 localhost kernel: [ 600.432335] [<ffffffff81171db0>] iterate_supers+0x80/0xf0 Jun 18 02:30:48 localhost kernel: [ 600.432337] [<ffffffff8119c4e0>] sys_sync+0x30/0x70 Jun 18 02:30:48 localhost kernel: [ 600.432338] [<ffffffff8146a7a9>] system_call_fastpath+0x16/0x1b

Google came up with: http://www.gossamer-threads.com/lists/linux/kernel/1306758

Can it be the same semaphore issue?

A guy pinpointed to a pattern on the forums: * * *arti74 wrote:* *What I've noticed yet - htop shows 100% CPU usage on that command: /bin/mount -o realtime /dev/sda4 /mnt/usbhd-sda4 - I can't kill it, shutdown or reboot can't kill it either. Interesting thing is, that I don't have sda4 partition at all. My fstab:* *# /etc/fstab: static file system information. # # <file system> <mount point> <type> <options> <dump> <pass>* *devpts /dev/pts devpts defaults 0 0 /dev/sda2 / ext4 defaults 0 1 /dev/sda6 /home ext4 defaults 0 1 /dev/sdb1 /mnt/FA auto defaults,nosuid,nodev,uhelper=udisks,uid=1000,gid=100,dmask=0077,fmask=0177 0 0 /dev/sda3 /var reiserfs defaults 0 1 shm /dev/shm tmpfs nodev,nosuid 0 0* *uname -r 3.4.2-2-ARCH* I have the SAME problem so it seems we discovered what is wrong. No ideas about how to fix thou.

2012/6/18 Victor Silva

2012/6/18 Victor Silva

...

2012/6/16 Victor Silva

...

2012/6/16 Victor Silva

...

2012/6/15 Victor Silva

...

2012/6/15 Don deJuan

...

On 06/15/2012 02:48 PM, Victor Silva wrote:

> 2012/6/15 Don deJuan > > On 06/15/2012 08:29 AM, David C. Rankin wrote: >> >> On 06/14/2012 03:12 PM, Victor Silva wrote: >>> >>> I have no shares. Can I somehow try to umount everything in mtab? >>>> I'm not >>>> familiar with the internal workings of mtab. I will read a bit. >>>> Also the >>>> only thing I assume could be hanging is my external HD which I >>>> disconnected >>>> having no effect on the problem behavior. Still I reported that >>>> my /boot >>>> partition was being mounted and listed on kde file manager >>>> (forgot its >>>> name) which was not default behavior. So could be the case that >>>> /boot is >>>> hanging my shoutdown? I don't get the reason umount -a && >>>> shutdown -h now >>>> did not do the trick. >>>> >>>> I ask gently again if you could inform me why did the "magic >>>> reboot" did >>>> work while shutdown did not. >>>> >>>> Regards, >>>> Victor >>>> >>>> >>> Victor, >>> >>> I am no expert in the shutdown logic that Arch uses, but it is >>> fairly >>> easy to follow. During shutdown, /etc/rc.shutdown is called and the >>> 'umount_all' command is supposed to take care of unmounting all >>> non-api >>> filesystems. If you have specific commands you need run in >>> _addition to_ >>> what is done by rc.shutdown, then you can put those commands in >>> /etc/rc.local.shutdown. The /etc/rc.local.shutdown must be >>> executable to >>> be called (chmod +x) or (chmod 0755). The rc.local.shutdown file is >>> called close to the beginning of rc.shutdown. >>> >>> Looking at your mtab file and comparing to mine, I do not have >>> any >>> usb drives connected to my system. Somebody more familiar with >>> issues >>> related to usb drives will need to comment. You might want to try >>> Guillermo's shutdown modified as follows: >>> >>> umount -arfl -t usbfs,fuseblk >>> >>> I don't know if that will do it, but you have 5 fuseblk >>> filesystems >>> and 1 usbfs mounted. I don't know how Arch handles their >>> unmounting. >>> >>> Lastly, I do not use the gnome gvfs-fuse-daemon. That is another >>> entry to look at and make sure it isn't the issue. Maybe try your >>> rc.local.shutdown with: >>> >>> umount -arfl -t usbfs,fuseblk >>> killall gvfs-fuse-daemon # or whatever that process actually runs >>> as >>> >>> >>> >>> Well just tried reinstalling made no difference. So I guess I >> will be >> looking it why it is starting that way. It may or may not be >> related to the >> shutdown issues. But other than this one thing my symptoms seem to >> match >> this minus the screen turning red when freezing. I will post back >> here if I >> sort anything out that may help this problem. >> >> I wil try this at home but I'1m at work atm, >> > https://bugs.archlinux.org/**task/30136https://bugs.archlinux.org/task/30136 > ry this kernel paramether reboot=pci > More info: > http://intosimple.blogspot.**com.br/2012/06/reboot-on-dell-** > latitude-e6520-with-arch.htmlhttp://intosimple.blogspot.com.br/2012/06/reboot-on-dell-latitude-e6520-with... > > After reading more into that parameter I found this http://linux.koolsolutions.**com/2009/08/04/howto-fix-** linux-hangfreeze-during-**reboots-and-restarts/http://linux.koolsolutions.com/2009/08/04/howto-fix-linux-hangfreeze-during-...

They show more options. I am going to try the one you suggested shortly and if that does not work do the other suggested option in the link I posted. Thanks for pointing out your findings.

A new kernel update was avaliable fo me today. I hoped it could fix some of the issues we were facing. In fact now I have tons of errors, dbus seems screwd and many other things, among the problems I have now is that X fails with no screen found (both nv and nvidia drivers) and I have no network interfaces I fail to get eth0 up. So *DO NOT UPDATE YOUR KERNELS *I'm quite sad as this is a even bigger mistake than the last one. So I think I need to chroot again rever to the old kernel... Anyone else expecting this kind of problem? Btw the reboor parameters for the kernel (which I've tested before the upgrade) also did not work.

Regards, Victor

I solved many issues still when I try to boot now I get the following

errors:

*Jun 16 13:55:48 localhost kernel: [ 10.463651] microcode: failed to load file amd-ucode/microcode_amd.bin Jun 16 13:55:48 localhost kernel: [ 10.464913] microcode: failed to load file amd-ucode/microcode_amd.bin Jun 16 13:55:48 localhost kernel: [ 10.466051] microcode: failed to load file amd-ucode/microcode_amd.bin Jun 16 13:55:48 localhost kernel: [ 10.467189] microcode: failed to load file amd-ucode/microcode_amd.bin Jun 16 13:55:48 localhost kernel: [ 10.468305] microcode: failed to load file amd-ucode/microcode_amd.bin Jun 16 13:55:48 localhost kernel: [ 10.469389] microcode: failed to load file amd-ucode/microcode_amd.bin Jun 16 13:55:48 localhost kernel: [ 11.920779] sd 6:0:0:0: [sdc] No Caching mode page present Jun 16 13:55:48 localhost kernel: [ 11.920880] sd 6:0:0:0: [sdc] Assuming drive cache: write through Jun 16 13:55:48 localhost kernel: [ 11.924824] sd 6:0:0:0: [sdc] No Caching mode page present Jun 16 13:55:48 localhost kernel: [ 11.924924] sd 6:0:0:0: [sdc] Assuming drive cache: write through Jun 16 13:55:48 localhost kernel: [ 11.931887] sd 6:0:0:0: [sdc] No Caching mode page present Jun 16 13:55:48 localhost kernel: [ 11.931982] sd 6:0:0:0: [sdc] Assuming drive cache: write through * Are my kernel sources messed? I'm still unable the shutdown. Anyone got any ideas which can help? :(

I've solved this issue by adding microcode to modules array in rc.conf thou I've never used this before. Still I'm unable to shutdown.

Regards, Victor

Folks I'm still investigating the issue. After I try to reboot kernel log gave me this hint: Jun 18 02:30:48 localhost kernel: [ 600.432301] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jun 18 02:30:48 localhost kernel: [ 600.432303] shutdown D 0000000000000001 0 2902 2897 0x00000000 Jun 18 02:30:48 localhost kernel: [ 600.432305] ffff8801c39fbe30 0000000000000086 ffff8801ca2cafa0 ffff8801c39fbfd8 Jun 18 02:30:48 localhost kernel: [ 600.432308] ffff8801c39fbfd8 ffff8801c39fbfd8 ffff880199ae07f0 ffff8801ca2cafa0 Jun 18 02:30:48 localhost kernel: [ 600.432310] 0007ffffffffffff ffff880222b0ee00 0000000000000000 0000000000000000 Jun 18 02:30:48 localhost kernel: [ 600.432312] Call Trace: Jun 18 02:30:48 localhost kernel: [ 600.432315] [<ffffffff81084c22>] ? default_wake_function+0x12/0x20 Jun 18 02:30:48 localhost kernel: [ 600.432317] [<ffffffff8119c3b0>] ? __sync_filesystem+0x90/0x90 Jun 18 02:30:48 localhost kernel: [ 600.432319] [<ffffffff81222f38>] ? blk_finish_plug+0x18/0x50 Jun 18 02:30:48 localhost kernel: [ 600.432321] [<ffffffff814689c9>] schedule+0x29/0x70 Jun 18 02:30:48 localhost kernel: [ 600.432323] [<ffffffff81469455>] rwsem_down_failed_common+0xc5/0x160 Jun 18 02:30:48 localhost kernel: [ 600.432325] [<ffffffff81117d22>] ? do_writepages+0x22/0x50 Jun 18 02:30:48 localhost kernel: [ 600.432327] [<ffffffff8119c3b0>] ? __sync_filesystem+0x90/0x90 Jun 18 02:30:48 localhost kernel: [ 600.432329] [<ffffffff81469525>] rwsem_down_read_failed+0x15/0x17 Jun 18 02:30:48 localhost kernel: [ 600.432331] [<ffffffff8124afc4>] call_rwsem_down_read_failed+0x14/0x30 Jun 18 02:30:48 localhost kernel: [ 600.432333] [<ffffffff814678a7>] ? down_read+0x17/0x20 Jun 18 02:30:48 localhost kernel: [ 600.432335] [<ffffffff81171db0>] iterate_supers+0x80/0xf0 Jun 18 02:30:48 localhost kernel: [ 600.432337] [<ffffffff8119c4e0>] sys_sync+0x30/0x70 Jun 18 02:30:48 localhost kernel: [ 600.432338] [<ffffffff8146a7a9>] system_call_fastpath+0x16/0x1b

Google came up with: http://www.gossamer-threads.com/lists/linux/kernel/1306758

Can it be the same semaphore issue?

A guy pinpointed to a pattern on the forums: * * *arti74 wrote:*

*What I've noticed yet - htop shows 100% CPU usage on that command: /bin/mount -o realtime /dev/sda4 /mnt/usbhd-sda4 - I can't kill it, shutdown or reboot can't kill it either. Interesting thing is, that I don't have sda4 partition at all. My fstab:*

*# /etc/fstab: static file system information. # # <file system> <mount point> <type> <options> <dump> <pass>*

*devpts /dev/pts devpts defaults 0 0 /dev/sda2 / ext4 defaults 0 1 /dev/sda6 /home ext4 defaults 0 1 /dev/sdb1 /mnt/FA auto defaults,nosuid,nodev,uhelper=udisks,uid=1000,gid=100,dmask=0077,fmask=0177 0 0 /dev/sda3 /var reiserfs defaults 0 1 shm /dev/shm tmpfs nodev,nosuid 0 0*

*uname -r 3.4.2-2-ARCH*

I have the SAME problem so it seems we discovered what is wrong. No ideas about how to fix thou.

Has the new kernel update fixed the issue?

2012/7/1 Victor Silva

2012/6/19 Victor Silva

...

2012/6/18 Victor Silva

...

2012/6/18 Victor Silva

...

2012/6/16 Victor Silva

...

2012/6/16 Victor Silva

...

2012/6/15 Victor Silva

> > > 2012/6/15 Don deJuan > >> On 06/15/2012 02:48 PM, Victor Silva wrote: >> >>> 2012/6/15 Don deJuan >>> >>> On 06/15/2012 08:29 AM, David C. Rankin wrote: >>>> >>>> On 06/14/2012 03:12 PM, Victor Silva wrote: >>>>> >>>>> I have no shares. Can I somehow try to umount everything in >>>>>> mtab? I'm not >>>>>> familiar with the internal workings of mtab. I will read a bit. >>>>>> Also the >>>>>> only thing I assume could be hanging is my external HD which I >>>>>> disconnected >>>>>> having no effect on the problem behavior. Still I reported that >>>>>> my /boot >>>>>> partition was being mounted and listed on kde file manager >>>>>> (forgot its >>>>>> name) which was not default behavior. So could be the case that >>>>>> /boot is >>>>>> hanging my shoutdown? I don't get the reason umount -a && >>>>>> shutdown -h now >>>>>> did not do the trick. >>>>>> >>>>>> I ask gently again if you could inform me why did the "magic >>>>>> reboot" did >>>>>> work while shutdown did not. >>>>>> >>>>>> Regards, >>>>>> Victor >>>>>> >>>>>> >>>>> Victor, >>>>> >>>>> I am no expert in the shutdown logic that Arch uses, but it is >>>>> fairly >>>>> easy to follow. During shutdown, /etc/rc.shutdown is called and >>>>> the >>>>> 'umount_all' command is supposed to take care of unmounting all >>>>> non-api >>>>> filesystems. If you have specific commands you need run in >>>>> _addition to_ >>>>> what is done by rc.shutdown, then you can put those commands in >>>>> /etc/rc.local.shutdown. The /etc/rc.local.shutdown must be >>>>> executable to >>>>> be called (chmod +x) or (chmod 0755). The rc.local.shutdown file >>>>> is >>>>> called close to the beginning of rc.shutdown. >>>>> >>>>> Looking at your mtab file and comparing to mine, I do not have >>>>> any >>>>> usb drives connected to my system. Somebody more familiar with >>>>> issues >>>>> related to usb drives will need to comment. You might want to try >>>>> Guillermo's shutdown modified as follows: >>>>> >>>>> umount -arfl -t usbfs,fuseblk >>>>> >>>>> I don't know if that will do it, but you have 5 fuseblk >>>>> filesystems >>>>> and 1 usbfs mounted. I don't know how Arch handles their >>>>> unmounting. >>>>> >>>>> Lastly, I do not use the gnome gvfs-fuse-daemon. That is >>>>> another >>>>> entry to look at and make sure it isn't the issue. Maybe try your >>>>> rc.local.shutdown with: >>>>> >>>>> umount -arfl -t usbfs,fuseblk >>>>> killall gvfs-fuse-daemon # or whatever that process actually >>>>> runs as >>>>> >>>>> >>>>> >>>>> Well just tried reinstalling made no difference. So I guess I >>>> will be >>>> looking it why it is starting that way. It may or may not be >>>> related to the >>>> shutdown issues. But other than this one thing my symptoms seem >>>> to match >>>> this minus the screen turning red when freezing. I will post back >>>> here if I >>>> sort anything out that may help this problem. >>>> >>>> I wil try this at home but I'1m at work atm, >>>> >>> https://bugs.archlinux.org/**task/30136https://bugs.archlinux.org/task/30136 >>> ry this kernel paramether reboot=pci >>> More info: >>> http://intosimple.blogspot.**com.br/2012/06/reboot-on-dell-** >>> latitude-e6520-with-arch.htmlhttp://intosimple.blogspot.com.br/2012/06/reboot-on-dell-latitude-e6520-with... >>> >>> >> After reading more into that parameter I found this >> http://linux.koolsolutions.**com/2009/08/04/howto-fix-** >> linux-hangfreeze-during-**reboots-and-restarts/http://linux.koolsolutions.com/2009/08/04/howto-fix-linux-hangfreeze-during-... >> >> They show more options. I am going to try the one you suggested >> shortly and if that does not work do the other suggested option in the link >> I posted. Thanks for pointing out your findings. >> >> A new kernel update was avaliable fo me today. I hoped it could fix > some of the issues we were facing. In fact now I have tons of errors, dbus > seems screwd and many other things, among the problems I have now is that X > fails with no screen found (both nv and nvidia drivers) and I have no > network interfaces I fail to get eth0 up. So > *DO NOT UPDATE YOUR KERNELS > *I'm quite sad as this is a even bigger mistake than the last one. > So I think I need to chroot again rever to the old kernel... > Anyone else expecting this kind of problem? > Btw the reboor parameters for the kernel (which I've tested before > the upgrade) also did not work. > > Regards, > Victor > > I solved many issues still when I try to boot now I get the following errors:

*Jun 16 13:55:48 localhost kernel: [ 10.463651] microcode: failed to load file amd-ucode/microcode_amd.bin Jun 16 13:55:48 localhost kernel: [ 10.464913] microcode: failed to load file amd-ucode/microcode_amd.bin Jun 16 13:55:48 localhost kernel: [ 10.466051] microcode: failed to load file amd-ucode/microcode_amd.bin Jun 16 13:55:48 localhost kernel: [ 10.467189] microcode: failed to load file amd-ucode/microcode_amd.bin Jun 16 13:55:48 localhost kernel: [ 10.468305] microcode: failed to load file amd-ucode/microcode_amd.bin Jun 16 13:55:48 localhost kernel: [ 10.469389] microcode: failed to load file amd-ucode/microcode_amd.bin Jun 16 13:55:48 localhost kernel: [ 11.920779] sd 6:0:0:0: [sdc] No Caching mode page present Jun 16 13:55:48 localhost kernel: [ 11.920880] sd 6:0:0:0: [sdc] Assuming drive cache: write through Jun 16 13:55:48 localhost kernel: [ 11.924824] sd 6:0:0:0: [sdc] No Caching mode page present Jun 16 13:55:48 localhost kernel: [ 11.924924] sd 6:0:0:0: [sdc] Assuming drive cache: write through Jun 16 13:55:48 localhost kernel: [ 11.931887] sd 6:0:0:0: [sdc] No Caching mode page present Jun 16 13:55:48 localhost kernel: [ 11.931982] sd 6:0:0:0: [sdc] Assuming drive cache: write through * Are my kernel sources messed? I'm still unable the shutdown. Anyone got any ideas which can help? :(

I've solved this issue by adding microcode to modules array in rc.conf thou I've never used this before. Still I'm unable to shutdown.

Regards, Victor

Folks I'm still investigating the issue. After I try to reboot kernel log gave me this hint: Jun 18 02:30:48 localhost kernel: [ 600.432301] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jun 18 02:30:48 localhost kernel: [ 600.432303] shutdown D 0000000000000001 0 2902 2897 0x00000000 Jun 18 02:30:48 localhost kernel: [ 600.432305] ffff8801c39fbe30 0000000000000086 ffff8801ca2cafa0 ffff8801c39fbfd8 Jun 18 02:30:48 localhost kernel: [ 600.432308] ffff8801c39fbfd8 ffff8801c39fbfd8 ffff880199ae07f0 ffff8801ca2cafa0 Jun 18 02:30:48 localhost kernel: [ 600.432310] 0007ffffffffffff ffff880222b0ee00 0000000000000000 0000000000000000 Jun 18 02:30:48 localhost kernel: [ 600.432312] Call Trace: Jun 18 02:30:48 localhost kernel: [ 600.432315] [<ffffffff81084c22>] ? default_wake_function+0x12/0x20 Jun 18 02:30:48 localhost kernel: [ 600.432317] [<ffffffff8119c3b0>] ? __sync_filesystem+0x90/0x90 Jun 18 02:30:48 localhost kernel: [ 600.432319] [<ffffffff81222f38>] ? blk_finish_plug+0x18/0x50 Jun 18 02:30:48 localhost kernel: [ 600.432321] [<ffffffff814689c9>] schedule+0x29/0x70 Jun 18 02:30:48 localhost kernel: [ 600.432323] [<ffffffff81469455>] rwsem_down_failed_common+0xc5/0x160 Jun 18 02:30:48 localhost kernel: [ 600.432325] [<ffffffff81117d22>] ? do_writepages+0x22/0x50 Jun 18 02:30:48 localhost kernel: [ 600.432327] [<ffffffff8119c3b0>] ? __sync_filesystem+0x90/0x90 Jun 18 02:30:48 localhost kernel: [ 600.432329] [<ffffffff81469525>] rwsem_down_read_failed+0x15/0x17 Jun 18 02:30:48 localhost kernel: [ 600.432331] [<ffffffff8124afc4>] call_rwsem_down_read_failed+0x14/0x30 Jun 18 02:30:48 localhost kernel: [ 600.432333] [<ffffffff814678a7>] ? down_read+0x17/0x20 Jun 18 02:30:48 localhost kernel: [ 600.432335] [<ffffffff81171db0>] iterate_supers+0x80/0xf0 Jun 18 02:30:48 localhost kernel: [ 600.432337] [<ffffffff8119c4e0>] sys_sync+0x30/0x70 Jun 18 02:30:48 localhost kernel: [ 600.432338] [<ffffffff8146a7a9>] system_call_fastpath+0x16/0x1b

Google came up with: http://www.gossamer-threads.com/lists/linux/kernel/1306758

Can it be the same semaphore issue?

A guy pinpointed to a pattern on the forums: * * *arti74 wrote:*

*What I've noticed yet - htop shows 100% CPU usage on that command: /bin/mount -o realtime /dev/sda4 /mnt/usbhd-sda4 - I can't kill it, shutdown or reboot can't kill it either. Interesting thing is, that I don't have sda4 partition at all. My fstab: *

*# /etc/fstab: static file system information. # # <file system> <mount point> <type> <options> <dump> <pass>*

*devpts /dev/pts devpts defaults 0 0 /dev/sda2 / ext4 defaults 0 1 /dev/sda6 /home ext4 defaults 0 1 /dev/sdb1 /mnt/FA auto defaults,nosuid,nodev,uhelper=udisks,uid=1000,gid=100,dmask=0077,fmask=0177 0 0 /dev/sda3 /var reiserfs defaults 0 1 shm /dev/shm tmpfs nodev,nosuid 0 0*

*uname -r 3.4.2-2-ARCH*

I have the SAME problem so it seems we discovered what is wrong. No ideas about how to fix thou.

Has the new kernel update fixed the issue?

After the last update with 3.4.4-2-ARCH #1 SMP PREEMPT Sun Jun 24 18:59:47 CEST 2012 x86_64 GNU/Linux

rules seem to be working again :)

It works but again I have a core stuck in 100% use. renice did not solve the trick. Any ideas?

2012/6/14 Guillermo Leira

...

[[ $UID -eq 0 ]] && umountcmd=umount || umountcmd="sudo umount"

if grep -q mnt\/phx-cfg /etc/mtab; then echo "umount /mnt/phx-cfg" $umountcmd /mnt/phx-cfg fi

if grep -q mnt\/phx-david /etc/mtab; then echo "umount /mnt/phx-david" $umountcmd /mnt/phx-david fi

if grep -q mnt\/phx /etc/mtab; then echo "umount /mnt/phx" $umountcmd /mnt/phx fi

if grep -q mnt\/win /etc/mtab; then echo "umount /mnt/win" $umountcmd /mnt/win fi

if grep -q mnt\/pv /etc/mtab; then echo "umount /mnt/pv" $umountcmd /mnt/pv fi

exit 0

If you are experiencing shutdown hangs do to lingering mount issues, then something similar to this setup may help. (I never did figure out why the normal shutdown scripts didn't do this automatically)

I had the same problema, but I used

umount -arfl -t nfs,nfs4,smbfs,cifs

and it works... :-)

Best Regards

Guillermo Leira

I've tried Guillermo approach and Davids too no luck. Maybe this can help, here are the contents of my mtab is something strange? *cat /etc/mtab rootfs / rootfs rw 0 0 proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0 sys /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0 dev /dev devtmpfs rw,nosuid,relatime,size=4054576k,nr_inodes=1013644,mode=755 0 0 run /run tmpfs rw,nosuid,nodev,relatime,mode=755 0 0 /dev/sdb3 / ext4 rw,relatime,user_xattr,acl,barrier=1,data=ordered 0 0 devpts /dev/pts devpts rw,relatime,mode=600,ptmxmode=000 0 0 shm /dev/shm tmpfs rw,nosuid,nodev,relatime 0 0 binfmt /proc/sys/fs/binfmt_misc binfmt_misc rw,relatime 0 0 /dev/sdb5 /media/usbhd-sdb5 ext4 rw,relatime,user_xattr,acl,barrier=1,data=ordered 0 0 /dev/sdb1 /media/System_Reserved fuseblk rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096 0 0 /dev/sda3 /media/usbhd-sda3 fuseblk rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096 0 0 /dev/sda1 /media/usbhd-sda1 fuseblk rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096 0 0 /dev/sda2 /media/usbhd-sda2 fuseblk rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096 0 0 /dev/sdc1 /media/HITACHI fuseblk rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096 0 0 /dev/sdb5 /boot ext4 rw,relatime,user_xattr,acl,barrier=1,data=ordered 0 0 none /proc/bus/usb usbfs rw,relatime,devgid=121,devmode=664,busgid=108,busmode=775 0 0 gvfs-fuse-daemon /home/imanewbie/.gvfs fuse.gvfs-fuse-daemon rw,nosuid,nodev,relatime,user_id=1000,group_id=100 0 0* Regards, Victor