From: Martin Steigerwald <Martin@lichtvoll.de>
To: helmut@hullen.de, linux-kernel@vger.kernel.org
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [regression?] hang with 2.6.37 on a BTRFS test machine
Date: Sun, 23 Jan 2011 14:44:03 +0100 [thread overview]
Message-ID: <201101231444.10680.Martin@lichtvoll.de> (raw)
In-Reply-To: <BePhzVUT1uB@helmut.hullen.de>
[-- Attachment #1: Type: Text/Plain, Size: 2026 bytes --]
CCs restored. Its usual to keep CCs on Linux kernel related mailing lists.
Am Sunday 23 January 2011 schrieb Helmut Hullen:
> Hallo, Martin,
>
> Du meintest am 23.01.11:
> > I have something I do not have the slightest clue on how to track
> > down:
> >
> > Occasionally with 2.6.37 plain vanilla my ThinkPad T23 freezes in
> > such a way, that when I type a command at the prompt, nothing will
> > happen anymore. Same goes for login into a tty. Even dmesg is not
> > executed anymore. My KDE session doesn't react to clicks anymore,
> > except for window movement. Most of the time the mouse pointer is
> > still movable, but sometimes it is frozen as well. But the latter
> > might be a different problem with X.org.
>
> Maybe it's the same problem ... I have (among my machines) a Thinkpad
> T22 on which I have run btrfs with kernel 2.6.37-rc4. Sometimes it
> hung, too. But it's an old machine, with old RAM, with some old disks.
Is the hung comparable to what I have seen? I.e. mouse pointer and stuff
still works, but when entering a command the shell does hang?
I can't completely rule out a hardware related problem as well, but then
with 2.6.36 the machine now just works again as if nothing happened - its
mostly running at 733 MHz instead of 1.13 GHz and the fan still expels a
steady stream of lukewarm air. I think I have to run it with 2.6.36 at
least a week to see whether its stable with that one. Its not important to
run it with 2.6.37 so thats not a problem. Its just my Amarok machine.
Maybe it would be a good idea when you compare with 2.6.36 as well...
> It has hung some time ago also without any btrfs partition and with
> older kernel(s).
>
> But I'll test again.
I will also continue to test with a 2.6.37 on a workstation at work, but
there only some scratch partition uses BTRFS. My T23 has / and /home on
it.
Ciao,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-01-23 13:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-23 12:06 [regression?] hang with 2.6.37 on a BTRFS test machine Martin Steigerwald
2011-01-23 13:13 ` Helmut Hullen
2011-01-23 13:44 ` Martin Steigerwald [this message]
2011-01-23 14:13 ` Helmut Hullen
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=201101231444.10680.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=helmut@hullen.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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.