On 13/06/13 19:13, Cristian Rodríguez wrote:

El 13/06/13 12:46, James Knott escribió:

...

I've noticed sometimes it takes a long time for my ThinkPad E520 to reboot when running openSUSE 12.3. When this occurs and I press Esc, I see the following displayed for a couple of minutes or so before it progresses. This does not happen every time and I don't see any pattern to when it does. Just wanted to say that I had the exact same problem (Thinkpad T530). Boot time is always much too long, shutdown time varies a lot but can be very long as well.

I'll try the debugging tips provided in this thread as soon as I can. Ph. A. -- *Philippe Andersson* Unix System Administrator IBA Particle Therapy | Tel: +32-10-475.983 Fax: +32-10-487.707 eMail: pan@iba-group.com http://www.iba-worldwide.com

Cristian Rodríguez wrote:

attach the resulting shutdown-log.txt as a reply to this message, so we can see what it is taking a long time to stop. Here it is.

* Cristian Rodríguez [06-14-13 17:27]:

El vie 14 jun 2013 17:02:12 CLT, James Knott escribió:

...

Cristian Rodríguez wrote:

...

attach the resulting shutdown-log.txt as a reply to this message, so we can see what it is taking a long time to stop. Here it is.

You missed the most important part of the instructions.. booting with

systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M

Otherwise the shutdown log is of no use for debugging.

And posted a *too* large file to the list. Please seek a host for those files rather than penalize those w/o unlimited internet usage. Quite unthoughtful action! -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

* James Knott [06-14-13 17:53]:

Patrick Shanahan wrote:

...

And posted a *too* large file to the list. Please seek a host for those files rather than penalize those w/o unlimited internet usage. Quite unthoughtful action!

I thought this list didn't pass attachments, so I sent it to Christian, as well as the list, to ensure he got it.

With that in mind, perhaps you should send it again in case someone missed it. :^( ps: a very thoughtful response! -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Cristian Rodríguez wrote:

El vie 14 jun 2013 17:02:12 CLT, James Knott escribió:

...

Cristian Rodríguez wrote:

...

attach the resulting shutdown-log.txt as a reply to this message, so we can see what it is taking a long time to stop. Here it is.

Hi:

You missed the most important part of the instructions.. booting with

systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M

Otherwise the shutdown log is of no use for debugging.

I added it to the "Optional Kernel Command Line Parameter" box in the boot loader settings. Is there somewhere else I should have put it? I didn't type it in by hand, as this problem only occurs occasionally and I'd have to type it in every time, whether it was going to fail or not. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Cristian Rodríguez wrote:

NO, they should be there, however you did not boot the system which such parameters the time you collected the shutdown log.

As I said, I added it to that boot parameters box and it's been there through several reboots, including the one before that shutdown. I put it there immediately after I received the instructions from you and it was still there when I checked a couple of hours ago. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Andrey Borzenkov wrote:

В Fri, 14 Jun 2013 19:13:59 -0400 James Knott пишет:

...

Cristian Rodríguez wrote:

...

NO, they should be there, however you did not boot the system which such parameters the time you collected the shutdown log.

As I said, I added it to that boot parameters box and it's been there through several reboots, including the one before that shutdown. [ 0.000000] Command line: root=/dev/disk/by-id/ata-WDC_WD3200BEKT-08PVMT1_WD-WXD1A8136034-part6 resume=/dev/disk/by-id/ata-WDC_WD3200BEKT-08PVMT1_WD-WXD1A8136034-part5 splash=silent quiet video=1366x768

Whatever you did kernel was not booted with these parameters.

Well then, how do I get it too boot with those parameters, if not using that box? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Andrey Borzenkov wrote:

Which bootloader are you using?

Grub. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Andrey Borzenkov wrote:

В Sun, 16 Jun 2013 18:27:30 -0400 James Knott пишет:

...

Andrey Borzenkov wrote:

...

Which bootloader are you using? Grub.

Could you show /boot/grub/menu.lst?

# Modified by YaST2. Last modification on Thu Jun 13 13:45:08 EDT 2013 # THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader # For the new kernel it try to figure out old parameters. In case we are not able to recognize it (e.g. change of flavor or strange install order ) it it use as fallback installation parameters from /etc/sysconfig/bootloader default 0 timeout 8 ##YaST - generic_mbr gfxmenu (hd0,5)/boot/message ##YaST - activate ###Don't change this comment - YaST2 identifier: Original name: linux### title Desktop root (hd0,5) kernel /boot/vmlinuz-3.7.10-1.11-desktop root=/dev/disk/by-id/ata-WDC_WD3200BEKT-08PVMT1_WD-WXD1A8136034-part6 resume=/dev/disk/by-id/ata-WDC_WD3200BEKT-08PVMT1_WD-WXD1A8136034-part5 splash=silent quiet video=1366x768 showopts systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M vga=0x317 initrd /boot/initrd-3.7.10-1.11-desktop ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe root (hd0,5) kernel /boot/vmlinuz-3.7.10-1.11-desktop root=/dev/disk/by-id/ata-WDC_WD3200BEKT-08PVMT1_WD-WXD1A8136034-part6 showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe vga=0x317 initrd /boot/initrd-3.7.10-1.11-desktop ###Don't change this comment - YaST2 identifier: Original name: windows 2### title Windows 7 rootnoverify (hd0,1) chainloader +1 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 17/06/13 14:31, Wolfgang Rosenauer wrote:

Do you use a crypto partition on your Thinkpad? I don't.

I have NFS and SMB/CIFS mountpoints, but all these are only mounted manually when they are needed. The shutdown time doesn't seem impacted by whether they were mounted or not. Cheers. Bye. Ph. A. -- *Philippe Andersson* Unix System Administrator IBA Particle Therapy | Tel: +32-10-475.983 Fax: +32-10-487.707 eMail: pan@iba-group.com http://www.iba-worldwide.com

Il 17/06/2013 09:31, Wolfgang Rosenauer ha scritto:

Hi,

I'm not sure if that is the same behaviour for me. Actually I don't think so but the subject hits my problem exactly ;-)

Do you use a crypto partition on your Thinkpad? Since that seems my reason for my Thinkpad not shutting down (or shutthing down only after a few minutes): https://bugzilla.novell.com/show_bug.cgi?id=810456

Unfortunately this is one of my systemd examples which do annoy me and apparently even openSUSE systemd maintainers have no idea since this bug is three months old.

Wolfgang

I would like to include myself into the list of the "slow shutdown process issue" users. I am using a lenovo Z470 with etx4 and no crypto filesystem. I noticed different behaviour between running on battery and power supply, but in both case the shutdown process takes several minutes to complete, and this is pretty annoying. Cheers, -- Marco Calistri (amdturion) opensuse 12.3 (Dartmouth) 64 bit Kernel 3.7.10-1.11-desktop Gnome 3.6.2 Intel® Core™ i5-2410M CPU @ 2.30GHz × 4 - Intel® Sandybridge Mobile -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Il 17/06/2013 15:55, Cristian Rodríguez ha scritto:

El 17/06/13 14:47, Marco Calistri escribió:

...

I noticed different behaviour between running on battery and power supply, but in both case the shutdown process takes several minutes to complete, and this is pretty annoying.

No debug log, no diagnosis, no fix, share yours please ;)

Cristian, You are right but I want just add a "+1" to the shutdown topic. Which kind of logs you think is worth I verify in order to discover something useful? I will provide it ASAP, since I am far from my openSUSE machine in this moment. Cheers, -- Marco Calistri (amdturion) opensuse 12.3 (Dartmouth) 64 bit - Kernel 3.7.10-1.4-desktop Gnome 3.6.2 Intel® Core™ i5-2410M CPU @ 2.30GHz × 4 - Intel® Sandybridge Mobile -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Il 17/06/2013 17:31, Wolfgang Rosenauer ha scritto:

Am 17.06.2013 20:55, schrieb Cristian Rodríguez:

...

El 17/06/13 14:47, Marco Calistri escribió:

...

I noticed different behaviour between running on battery and power supply, but in both case the shutdown process takes several minutes to complete, and this is pretty annoying.

No debug log, no diagnosis, no fix, share yours please ;)

So how about commenting on my bug since I'll deliver whatever my system can output as debugging? I shared mine but no solution so far. I can provide more debugging information if someone tells me what is needed.

Wolfgang

Sirs, No upstart version for openSUSE? Ubuntu has not this kind of issues related to init scripts and so on... Cheers, -- Marco Calistri (amdturion) opensuse 12.3 (Dartmouth) 64 bit - Kernel 3.7.10-1.4-desktop Gnome 3.6.2 Intel® Core™ i5-2410M CPU @ 2.30GHz × 4 - Intel® Sandybridge Mobile -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org