All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <Martin@lichtvoll.de>
To: xfs@oss.sgi.com
Cc: tuxonice-devel@lists.tuxonice.net, linux-kernel@vger.kernel.org
Subject: Re: hangs with MTRR_SANITIZER? - no, something else
Date: Sun, 30 Nov 2008 00:02:45 +0100	[thread overview]
Message-ID: <200811300002.45669.Martin@lichtvoll.de> (raw)
In-Reply-To: <200811290824.38750.Martin@lichtvoll.de>

Am Samstag 29 November 2008 schrieb Martin Steigerwald:
> Hi!
>
> CC'd to linux-kernel mailinglist, as that might be something that goes
> beyond any possible TuxOnIce or XFS issues. I know I am using TuxOnIce
> which is not part of the mainline kernel. And I am even using an
> inofficial patch - which I will use again unchanged for the non
> MTRR_SANITIZER kernel, in order to know whether its the MTRR_SANITIZER
> thing. And anyway before knowing whether it might be MTRR_SANITIZER
> related I need to run the non MTRR_SANITIZER kernel for at least a week
> and have quite some hibernate cycles. If someone else had issues with
> MTRR_SANITIZER I would like to hear about it. Also if someone thinks I
> am completely off track on trying to track this down I appreciate a
> hint.

Ok, its not MTRR_SANITIZER. It hung again on hibernate, again before any 
serious hibernating work has started. I will add debug output to my 
pre-hibernate script as it might hang already in there, maybe while 
disabling the network. I want to know whether it hangs before calling the 
hibernate script or after it. I think I will go for the latest official 
hibernate patch instead of using the inofficial one, although I am not 
convinced that it makes much of a difference. Lets see.

The syncs I added to my pre-hibernate seemed to help. KDE configuration is 
intact. As a safeguard I rsync ~/.kde to a backup directory before 
hibernating anyway.

Lets see what ideas I have to continue that Sherlock Holmes game ;)

I am puzzled that it only happens on my ThinkPad T42, not on the T23 and 
neither on the Dell workstation - till now.

Goodnight ;-),
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

WARNING: multiple messages have this Message-ID (diff)
From: Martin Steigerwald <Martin@lichtvoll.de>
To: xfs@oss.sgi.com
Cc: tuxonice-devel@lists.tuxonice.net, linux-kernel@vger.kernel.org
Subject: Re: hangs with MTRR_SANITIZER? - no, something else
Date: Sun, 30 Nov 2008 00:02:45 +0100	[thread overview]
Message-ID: <200811300002.45669.Martin@lichtvoll.de> (raw)
In-Reply-To: <200811290824.38750.Martin@lichtvoll.de>

Am Samstag 29 November 2008 schrieb Martin Steigerwald:
> Hi!
>
> CC'd to linux-kernel mailinglist, as that might be something that goes
> beyond any possible TuxOnIce or XFS issues. I know I am using TuxOnIce
> which is not part of the mainline kernel. And I am even using an
> inofficial patch - which I will use again unchanged for the non
> MTRR_SANITIZER kernel, in order to know whether its the MTRR_SANITIZER
> thing. And anyway before knowing whether it might be MTRR_SANITIZER
> related I need to run the non MTRR_SANITIZER kernel for at least a week
> and have quite some hibernate cycles. If someone else had issues with
> MTRR_SANITIZER I would like to hear about it. Also if someone thinks I
> am completely off track on trying to track this down I appreciate a
> hint.

Ok, its not MTRR_SANITIZER. It hung again on hibernate, again before any 
serious hibernating work has started. I will add debug output to my 
pre-hibernate script as it might hang already in there, maybe while 
disabling the network. I want to know whether it hangs before calling the 
hibernate script or after it. I think I will go for the latest official 
hibernate patch instead of using the inofficial one, although I am not 
convinced that it makes much of a difference. Lets see.

The syncs I added to my pre-hibernate seemed to help. KDE configuration is 
intact. As a safeguard I rsync ~/.kde to a backup directory before 
hibernating anyway.

Lets see what ideas I have to continue that Sherlock Holmes game ;)

I am puzzled that it only happens on my ThinkPad T42, not on the T23 and 
neither on the Dell workstation - till now.

Goodnight ;-),
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

  reply	other threads:[~2008-11-29 23:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-25 21:44 truncated files Martin Steigerwald
2008-11-25 22:27 ` Dave Chinner
2008-11-26  8:49   ` Martin Steigerwald
2008-11-26 22:59     ` Dave Chinner
2008-11-28 22:02       ` Martin Steigerwald
2008-11-28 22:39         ` Martin Steigerwald
2008-11-29  7:24           ` hangs with MTRR_SANITIZER? (was: Re: truncated files) Martin Steigerwald
2008-11-29  7:24             ` Martin Steigerwald
2008-11-29 23:02             ` Martin Steigerwald [this message]
2008-11-29 23:02               ` hangs with MTRR_SANITIZER? - no, something else Martin Steigerwald
2008-12-08  8:40               ` [TuxOnIce-devel] hangs with MTRR_SANITIZER? - solved Martin Steigerwald
2008-12-08  8:40                 ` Martin Steigerwald

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200811300002.45669.Martin@lichtvoll.de \
    --to=martin@lichtvoll.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tuxonice-devel@lists.tuxonice.net \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.