From: Thomas Sattler <tsattler@gmx.de>
To: Oleg Nesterov <oleg@tv-sign.ru>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>, Ingo Molnar <mingo@elte.hu>
Subject: Re: 2.6.22-rc6 spurious hangs
Date: Thu, 28 Jun 2007 23:31:02 +0200 [thread overview]
Message-ID: <46842896.50201@gmx.de> (raw)
In-Reply-To: <20070628181044.GA613@tv-sign.ru>
[-- Attachment #1: Type: text/plain, Size: 504 bytes --]
> Could you also show the result of sysrq-T ?
I was so happy that I could trigger it that fast ...
... that I forgot to press Alt-Sysrq-t before reboot.
:-(
But, I could trigger it again. :-)
This time I can offer:
- Debug output from Oleg's patch (11x, every 30s)
- Alt-Sysrq-t (3x, about 30s between them)
There is no lockdep stuff but lockdep must have
been running. It's enabled and did not fire
before the the bug was triggered.
The logfile is attached.
(yes it is, I checked twice)
Thomas
[-- Attachment #2: messages.gz --]
[-- Type: application/gzip, Size: 28637 bytes --]
next prev parent reply other threads:[~2007-06-28 21:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-28 14:00 2.6.22-rc6 spurious hangs Thomas Sattler
2007-06-28 14:47 ` Oleg Nesterov
2007-06-28 14:58 ` Thomas Sattler
2007-06-28 15:00 ` Ingo Molnar
[not found] ` <20070628150826.GA487@tv-sign.ru>
2007-06-28 17:35 ` Thomas Sattler
2007-06-28 17:49 ` Thomas Sattler
2007-06-28 18:10 ` Oleg Nesterov
2007-06-28 21:31 ` Thomas Sattler [this message]
2007-06-29 7:13 ` Thomas Sattler
2007-06-29 13:09 ` Oleg Nesterov
2007-06-29 13:16 ` Ingo Molnar
2007-06-29 13:58 ` Oleg Nesterov
2007-06-29 14:10 ` Ingo Molnar
2007-06-29 16:59 ` Dmitry Torokhov
2007-06-29 17:23 ` Oleg Nesterov
2007-06-29 21:21 ` Mauro Carvalho Chehab
2007-06-29 21:34 ` Markus Rechberger
2007-06-30 14:19 ` Oleg Nesterov
2007-07-01 18:54 ` Thomas Sattler
2007-07-01 19:47 ` Oleg Nesterov
2007-07-02 4:48 ` Thomas Sattler
2007-06-29 11:15 ` Tomi Orava
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=46842896.50201@gmx.de \
--to=tsattler@gmx.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@tv-sign.ru \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox