[opensuse] shutdown hangs after kernel update
![](https://seccdn.libravatar.org/avatar/62125288dd40f3bb08a59554fbf73db9.jpg?s=120&d=mm&r=g)
Hello, yesterday I updated the kernel using the opensuse-Updater. Since then shutdown hangs after the message "Shutting down D-Bus daemon". I attach the complete /var/log/messages of my last and actual session, inserted a comment where I pressed ctrl-alt-delete to force the reboot. This worked, but of course I got a lot of messages from reiserfs because the disks wern't unmounted properly before. The same happened yesterday. After reboot with ctrl-alt-delete I could shutdown normally (but havn't logged in again then). What can I do to make shutdown work correct again? Thanks for your hints Daniel -- Daniel Bauer photographer Basel Barcelona professional photography: http://www.daniel-bauer.com erotic art photos: http://www.bauer-nudes.com Madagascar special: http://www.fotograf-basel.ch/madagascar/
![](https://seccdn.libravatar.org/avatar/27aacf61a13c66fcc083fcf8a84823bc.jpg?s=120&d=mm&r=g)
Daniel Bauer wrote:
Hello,
yesterday I updated the kernel using the opensuse-Updater. Since then shutdown hangs after the message "Shutting down D-Bus daemon".
I attach the complete /var/log/messages of my last and actual session, inserted a comment where I pressed ctrl-alt-delete to force the reboot. This worked, but of course I got a lot of messages from reiserfs because the disks wern't unmounted properly before.
The same happened yesterday. After reboot with ctrl-alt-delete I could shutdown normally (but havn't logged in again then).
What can I do to make shutdown work correct again?
Thanks for your hints
Daniel
Danny, Take a look at bugzilla. You have been bitten by most likely the longest (by number of posts) running bug in openSuSE. If I recall it's: https://bugzilla.novell.com/show_bug.cgi?id=331747 After 139 posts, the bug has been mysteriously closed as "Won't Fix". -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/b150acea6b2203078d2a9d30bedeee91.jpg?s=120&d=mm&r=g)
David C. Rankin wrote:
Daniel Bauer wrote:
Hello,
yesterday I updated the kernel using the opensuse-Updater. Since then shutdown hangs after the message "Shutting down D-Bus daemon".
I attach the complete /var/log/messages of my last and actual session, inserted a comment where I pressed ctrl-alt-delete to force the reboot. This worked, but of course I got a lot of messages from reiserfs because the disks wern't unmounted properly before.
The same happened yesterday. After reboot with ctrl-alt-delete I could shutdown normally (but havn't logged in again then).
What can I do to make shutdown work correct again?
Thanks for your hints
Daniel
Danny,
Take a look at bugzilla. You have been bitten by most likely the longest (by number of posts) running bug in openSuSE. If I recall it's:
https://bugzilla.novell.com/show_bug.cgi?id=331747
After 139 posts, the bug has been mysteriously closed as "Won't Fix".
So solly but I missed Daniel's original posting and therefore am not sure if he is talking about 10.3 but I suspect that he is. To Daniel: I've been having this problem - of 'shutdown' hanging - ever since I installed 10.3, and irrespective of which kernel YaST upgraded the kernel to. If the OS shutdown properly without any convolutions I considered that something had gone wrong :-) and to accept it gracefully :-) . The usual thing which happened was that the shutdown started and then I got the black screen with the prompt "login: " where I then had to login as root and type "halt" before the system would shutdown. This doesn't happen anymore now with 11.0 installed. Ciao. -- If you don't succeed you run the risk of failure. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/62125288dd40f3bb08a59554fbf73db9.jpg?s=120&d=mm&r=g)
On Tuesday 24 June 2008 06:59:15, Basil Chupin wrote:
David C. Rankin wrote:
Daniel Bauer wrote:
yesterday I updated the kernel using the opensuse-Updater. Since then shutdown hangs after the message "Shutting down D-Bus daemon".
I attach the complete /var/log/messages of my last and actual session, inserted a comment where I pressed ctrl-alt-delete to force the reboot. This worked, but of course I got a lot of messages from reiserfs because the disks wern't unmounted properly before.
The same happened yesterday. After reboot with ctrl-alt-delete I could shutdown normally (but havn't logged in again then).
Take a look at bugzilla. You have been bitten by most likely the longest (by number of posts) running bug in openSuSE. If I recall it's:
https://bugzilla.novell.com/show_bug.cgi?id=331747
After 139 posts, the bug has been mysteriously closed as "Won't Fix".
So solly but I missed Daniel's original posting and therefore am not sure if he is talking about 10.3 but I suspect that he is.
To Daniel: I've been having this problem - of 'shutdown' hanging - ever since I installed 10.3, and irrespective of which kernel YaST upgraded the kernel to. If the OS shutdown properly without any convolutions I considered that something had gone wrong :-) and to accept it gracefully :-) .
This doesn't happen anymore now with 11.0 installed.
Yes, I use 10.3. Before the update to 2.6.22.18-0.2 the problem never occured, neither on my PC nor on my laptop. (I don't know how my PC would do, because I am abroad and did the update only here on the laptop.) What did you then do to avoid data loss? My shutdown process hangs before it unmounts the disks, thus with next start I get error messages from reiserfs which I don't really like... Daniel -- Daniel Bauer photographer Basel Barcelona professional photography: http://www.daniel-bauer.com erotic art photos: http://www.bauer-nudes.com Madagascar special: http://www.fotograf-basel.ch/madagascar/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/b150acea6b2203078d2a9d30bedeee91.jpg?s=120&d=mm&r=g)
Daniel Bauer wrote:
On Tuesday 24 June 2008 06:59:15, Basil Chupin wrote:
[pruned]
So solly but I missed Daniel's original posting and therefore am not sure if he is talking about 10.3 but I suspect that he is.
To Daniel: I've been having this problem - of 'shutdown' hanging - ever since I installed 10.3, and irrespective of which kernel YaST upgraded the kernel to. If the OS shutdown properly without any convolutions I considered that something had gone wrong :-) and to accept it gracefully :-) .
This doesn't happen anymore now with 11.0 installed.
Yes, I use 10.3. Before the update to 2.6.22.18-0.2 the problem never occured, neither on my PC nor on my laptop. (I don't know how my PC would do, because I am abroad and did the update only here on the laptop.)
What did you then do to avoid data loss? My shutdown process hangs before it unmounts the disks, thus with next start I get error messages from reiserfs which I don't really like...
Never suffered data loss -- perhaps because I have the drive formatted with ext3? Ciao. -- It's not possible to operate honestly using a basis of dishonesty. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/b150acea6b2203078d2a9d30bedeee91.jpg?s=120&d=mm&r=g)
Basil Chupin wrote:
Daniel Bauer wrote:
On Tuesday 24 June 2008 06:59:15, Basil Chupin wrote:
[pruned]
So solly but I missed Daniel's original posting and therefore am not sure if he is talking about 10.3 but I suspect that he is.
To Daniel: I've been having this problem - of 'shutdown' hanging - ever since I installed 10.3, and irrespective of which kernel YaST upgraded the kernel to. If the OS shutdown properly without any convolutions I considered that something had gone wrong :-) and to accept it gracefully :-) .
This doesn't happen anymore now with 11.0 installed.
Yes, I use 10.3. Before the update to 2.6.22.18-0.2 the problem never occured, neither on my PC nor on my laptop. (I don't know how my PC would do, because I am abroad and did the update only here on the laptop.)
What did you then do to avoid data loss? My shutdown process hangs before it unmounts the disks, thus with next start I get error messages from reiserfs which I don't really like...
Never suffered data loss -- perhaps because I have the drive formatted with ext3?
Ciao.
Well, I jinxed myself by replying to you and telling you that in 11.0 I've never had the system not shutdown properly. Last night the shutdown locked up solid :-( . First the screen went to init 3 and gave me the login prompt (just like with 10.3) and after I issued the 'halt' command everything just locked up. Only way out of this was to press and hold the power-on button. The first thing I did when powering up a short time ago this morning was to do e2fsck on the partition the OS is installed; the error found was that the superblock was last accessed in the future! - same (at least most of the time) as in 10.3. The interesting thing is that last night there was one upgrade put through by zypper, I think it was security related, and that upgrade was TIMEZONE 2008c-0.1. Whether this is the cause I don't know but I'll see if the OS hangs again tonight when I try to shut it down. Ciao. -- It's not possible to operate honestly using a basis of dishonesty. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/8cf2daa7694e65578c8c683f05152e5f.jpg?s=120&d=mm&r=g)
Basil Chupin wrote:
Basil Chupin wrote:
Daniel Bauer wrote:
On Tuesday 24 June 2008 06:59:15, Basil Chupin wrote:
[pruned]
So solly but I missed Daniel's original posting and therefore am not sure if he is talking about 10.3 but I suspect that he is.
To Daniel: I've been having this problem - of 'shutdown' hanging - ever since I installed 10.3, and irrespective of which kernel YaST upgraded the kernel to. If the OS shutdown properly without any convolutions I considered that something had gone wrong :-) and to accept it gracefully :-) .
This doesn't happen anymore now with 11.0 installed.
Yes, I use 10.3. Before the update to 2.6.22.18-0.2 the problem never occured, neither on my PC nor on my laptop. (I don't know how my PC would do, because I am abroad and did the update only here on the laptop.)
What did you then do to avoid data loss? My shutdown process hangs before it unmounts the disks, thus with next start I get error messages from reiserfs which I don't really like...
Never suffered data loss -- perhaps because I have the drive formatted with ext3?
Ciao.
Well, I jinxed myself by replying to you and telling you that in 11.0 I've never had the system not shutdown properly.
Last night the shutdown locked up solid :-( . First the screen went to init 3 and gave me the login prompt (just like with 10.3) and after I issued the 'halt' command everything just locked up. Only way out of this was to press and hold the power-on button.
The first thing I did when powering up a short time ago this morning was to do e2fsck on the partition the OS is installed; the error found was that the superblock was last accessed in the future! - same (at least most of the time) as in 10.3.
The interesting thing is that last night there was one upgrade put through by zypper, I think it was security related, and that upgrade was TIMEZONE 2008c-0.1. Whether this is the cause I don't know but I'll see if the OS hangs again tonight when I try to shut it down.
Ciao.
I have been experiencing system freezes on one my systems that was rock solid with 10.3 but now intermittently freezes with 11.0. Problem appears to occur only when running Gnome. I thought I had the problem licked by removing powersaved, but that was a premature conclusion. At the moment I am busy running fsck's trying to recover a resierfs filesystem on the system that the last freeze corrupted. The machine seems fine when running with no GUI (no Gnome) - at least as long as I let it sit like that which was about 2 days. Running Gnome as the user root seems ok (everything now only seems, nothing is definite for me with this behavior of OpenSuse 11) in the sense that I have left it running for 2+ hours with no issues. Running Gnome as a regular user (which is what I normally do on the machine) works for anywhere from 30 minutes to about four hours before a hard lock of the machine. -- --Moby They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -- Benjamin Franklin -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/b150acea6b2203078d2a9d30bedeee91.jpg?s=120&d=mm&r=g)
Moby wrote:
Basil Chupin wrote:
Basil Chupin wrote:
Daniel Bauer wrote:
On Tuesday 24 June 2008 06:59:15, Basil Chupin wrote:
[pruned]
So solly but I missed Daniel's original posting and therefore am not sure if he is talking about 10.3 but I suspect that he is.
To Daniel: I've been having this problem - of 'shutdown' hanging - ever since I installed 10.3, and irrespective of which kernel YaST upgraded the kernel to. If the OS shutdown properly without any convolutions I considered that something had gone wrong :-) and to accept it gracefully :-) .
This doesn't happen anymore now with 11.0 installed.
Yes, I use 10.3. Before the update to 2.6.22.18-0.2 the problem never occured, neither on my PC nor on my laptop. (I don't know how my PC would do, because I am abroad and did the update only here on the laptop.)
What did you then do to avoid data loss? My shutdown process hangs before it unmounts the disks, thus with next start I get error messages from reiserfs which I don't really like...
Never suffered data loss -- perhaps because I have the drive formatted with ext3?
Ciao.
Well, I jinxed myself by replying to you and telling you that in 11.0 I've never had the system not shutdown properly.
Last night the shutdown locked up solid :-( . First the screen went to init 3 and gave me the login prompt (just like with 10.3) and after I issued the 'halt' command everything just locked up. Only way out of this was to press and hold the power-on button.
The first thing I did when powering up a short time ago this morning was to do e2fsck on the partition the OS is installed; the error found was that the superblock was last accessed in the future! - same (at least most of the time) as in 10.3.
The interesting thing is that last night there was one upgrade put through by zypper, I think it was security related, and that upgrade was TIMEZONE 2008c-0.1. Whether this is the cause I don't know but I'll see if the OS hangs again tonight when I try to shut it down.
Ciao.
I have been experiencing system freezes on one my systems that was rock solid with 10.3 but now intermittently freezes with 11.0. Problem appears to occur only when running Gnome. I thought I had the problem licked by removing powersaved, but that was a premature conclusion. At the moment I am busy running fsck's trying to recover a resierfs filesystem on the system that the last freeze corrupted. The machine seems fine when running with no GUI (no Gnome) - at least as long as I let it sit like that which was about 2 days. Running Gnome as the user root seems ok (everything now only seems, nothing is definite for me with this behavior of OpenSuse 11) in the sense that I have left it running for 2+ hours with no issues. Running Gnome as a regular user (which is what I normally do on the machine) works for anywhere from 30 minutes to about four hours before a hard lock of the machine.
I don't run Gnome (and never have). In another thread (?in this list or opensuse-factory, cannot remember :-( ) there is mention of what appears to be a bug in the kernel which is associated with reiserfs -- but please look yourself to make sure for yourself what I state is correct. However, I do not use reiserfs so for me the problem would appear to lie elsewhere. Ciao. -- It's not possible to operate honestly using a basis of dishonesty. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/62125288dd40f3bb08a59554fbf73db9.jpg?s=120&d=mm&r=g)
On Wednesday 25 June 2008 08:06:45, Basil Chupin wrote:
Moby wrote:
Basil Chupin wrote:
Basil Chupin wrote:
Daniel Bauer wrote:
On Tuesday 24 June 2008 06:59:15, Basil Chupin wrote:
To Daniel: I've been having this problem - of 'shutdown' hanging - ever since I installed 10.3, and irrespective of which kernel YaST upgraded the kernel to. If the OS shutdown properly without any convolutions I considered that something had gone wrong :-) and to accept it gracefully :-) .
This doesn't happen anymore now with 11.0 installed.
Yes, I use 10.3. Before the update to 2.6.22.18-0.2 the problem never occured, neither on my PC nor on my laptop.
Well, I jinxed myself by replying to you and telling you that in 11.0 I've never had the system not shutdown properly.
Last night the shutdown locked up solid :-( . First the screen went to init 3 and gave me the login prompt (just like with 10.3) and after I issued the 'halt' command everything just locked up. Only way out of this was to press and hold the power-on button.
The first thing I did when powering up a short time ago this morning was to do e2fsck on the partition the OS is installed; the error found was that the superblock was last accessed in the future! - same (at least most of the time) as in 10.3.
The interesting thing is that last night there was one upgrade put through by zypper, I think it was security related, and that upgrade was TIMEZONE 2008c-0.1. Whether this is the cause I don't know but I'll see if the OS hangs again tonight when I try to shut it down.
Ciao.
Here it began with the update to kernel 2.6.22.18-0.2.
I have been experiencing system freezes on one my systems that was rock solid with 10.3 but now intermittently freezes with 11.0. Problem appears to occur only when running Gnome. I thought I had the problem licked by removing powersaved, but that was a premature conclusion.
I don't run Gnome (and never have).
I run KDE.
In another thread (?in this list or opensuse-factory, cannot remember :-( ) there is mention of what appears to be a bug in the kernel which is associated with reiserfs -- but please look yourself to make sure for yourself what I state is correct.
However, I do not use reiserfs so for me the problem would appear to lie elsewhere.
I filed a bug here: https://bugzilla.novell.com/show_bug.cgi?id=403134 To avoid data loss I now logout as user from KDE, go to a text console (from the login menu) an umount all but the system directory. However, yesterday I could not umount /home, it said it was in use. But I don't know why. I had nothing left running and I was logged out as user, so there should be no access needed to /home anymore. It's really weard. And of course I cannot umount the system directory. I had no data loss until now (I hope it stays that way!) but reiserfs always has a lot of journal-things to do when staring up... This friday I would have an appointment with an internet-café here in Barcelona that I tried to convince to use Linux because of all their problems always occuring with Windows. But if I go there now I'd get a read head, because their windows seems to be more stable than my linux (with the WLAN problems and the shutdown freeze), and he can proudly click on "start" to show me how a system can be shutdown... This is not just a rant. It would really have been a chance, but with a laptop "working" like mine, I simply have to cancel the appointment. Daniel -- Daniel Bauer photographer Basel Barcelona professional photography: http://www.daniel-bauer.com erotic art photos: http://www.bauer-nudes.com Madagascar special: http://www.fotograf-basel.ch/madagascar/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/77cb4da5f72bc176182dcc33f03a18f3.jpg?s=120&d=mm&r=g)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2008-06-25 at 10:14 +0200, Daniel Bauer wrote: ...
However, yesterday I could not umount /home, it said it was in use. But I don't know why. I had nothing left running and I was logged out as user, so there should be no access needed to /home anymore.
Try to use "lsof | grep home" to find out what's in use. The other thing you can do when something refuses to umount is to use "lazy" umount. It will minimize the damage when forcing power off.
This friday I would have an appointment with an internet-café here in Barcelona that I tried to convince to use Linux because of all their problems always occuring with Windows. But if I go there now I'd get a read head, because their windows seems to be more stable than my linux (with the WLAN problems and the shutdown freeze), and he can proudly click on "start" to show me how a system can be shutdown...
I would never install a brand new version on "outsiders". Stick to 10.3 - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIYh2rtTMYHG2NR9URAuVnAJ4wIZy58QRKUO+Hq6b693D/OGQQbgCfdrns CbbKg/i1cyXNxn0S1+BlU9Q= =L2/N -----END PGP SIGNATURE-----
![](https://seccdn.libravatar.org/avatar/62125288dd40f3bb08a59554fbf73db9.jpg?s=120&d=mm&r=g)
On Tuesday 24 June 2008 06:31:36, David C. Rankin wrote:
Daniel Bauer wrote:
Hello,
yesterday I updated the kernel using the opensuse-Updater. Since then shutdown hangs after the message "Shutting down D-Bus daemon".
I attach the complete /var/log/messages of my last and actual session, inserted a comment where I pressed ctrl-alt-delete to force the reboot. This worked, but of course I got a lot of messages from reiserfs because the disks wern't unmounted properly before.
The same happened yesterday. After reboot with ctrl-alt-delete I could shutdown normally (but havn't logged in again then).
Danny,
Take a look at bugzilla. You have been bitten by most likely the longest (by number of posts) running bug in openSuSE. If I recall it's:
https://bugzilla.novell.com/show_bug.cgi?id=331747
After 139 posts, the bug has been mysteriously closed as "Won't Fix".
-- David C. Rankin, J.D., P.E.
Oh. I've read thru those reports and I don't know, if I'm suffering from the same, because "my" hang occcurs after the message "Shutting down D-Bus daemon" while in that bug all reported that it hangs after the final message. So to be sure I opened a new bug - if it's the same, they will have to mark it as duplicate.... Any ideas how i can make the shutdown process more secure in regard of the disks, eventually manually? (I fear a data loss if I always have to reboot without properly unmounting the disks. After the hang I can press ctr-alt-F2 etc. and see the login, but cannot login anymore to the manually unmount the disks...) Daniel -- Daniel Bauer photographer Basel Barcelona professional photography: http://www.daniel-bauer.com erotic art photos: http://www.bauer-nudes.com Madagascar special: http://www.fotograf-basel.ch/madagascar/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/62125288dd40f3bb08a59554fbf73db9.jpg?s=120&d=mm&r=g)
On Monday 23 June 2008 21:45:51, Daniel Bauer wrote:
yesterday I updated the kernel using the opensuse-Updater. Since then shutdown hangs after the message "Shutting down D-Bus daemon".
update was on OpenSuse 10.3 to kernel 2.6.22.18-0.2 the problem seemed to be related to the alsa-driver-unstable-kmp package (that I have installed because I couldn't get sound on a HP pavillion dv9000 with the "normal" package). After updating the said package shutdown works normal again. (solved thru the help of the people in bugzilla https://bugzilla.novell.com/show_bug.cgi?id=403134 ) thanks Daniel -- Daniel Bauer photographer Basel Barcelona professional photography: http://www.daniel-bauer.com erotic art photos: http://www.bauer-nudes.com Madagascar special: http://www.fotograf-basel.ch/madagascar/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
Basil Chupin
-
Carlos E. R.
-
Daniel Bauer
-
David C. Rankin
-
Moby