From: Luca Falavigna <dktrkranz@gmail.com>
To: Daniel Walker <dwalker@mvista.com>, Ingo Molnar <mingo@elte.hu>
Cc: john cooper <john.cooper@timesys.com>, linux-kernel@vger.kernel.org
Subject: Re: [BUG] Softlockup detected with linux-2.6.14-rt6
Date: Wed, 16 Nov 2005 01:16:24 +0100 [thread overview]
Message-ID: <437A7A58.8050209@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0511151206000.29907@dhcp153.mvista.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Daniel Walker ha scritto:
|
| Wasn't this thread related to a real lock up? I thought Luca said that
| the stack trace came from his printer.
|
| I thought it might be related to the __delay troubles ..
|
| Daniel
Yes, stack trace was generated by console line printer because system
was completely stucked.
Actually I am testing linux-2.6.14-rt13. If this problem come out again,
I will notify you ASAP.
Regards,
- --
Luca
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iQEVAwUBQ3p6VpK+HIH6ZZ2zAQK/Owf9HvYGrO5IRZFuHByM/KlhoZ/5Abc2vSsk
/J4aZAsWOSlJOC55N6PsTa5iDIGa7ddKH4ieb1ckNGxUxc8baFSCiuWq/dJta57T
VRdkh588nPWaSQ9lIQSb5jy4RP8J8uyPc+FQVs//W+sj5YtXsikcB7Jh70GOBKGD
VOdMTI0bTmD/GahNwGcLGbZDGrVDvfwT0t9tXqCyC4SrQhQfWjyExYArej1hfACL
xAAM0WTNoi9e1DTeq9YSBXQnfTWj0eyjIWaRNhDcIjPBk3IPumF2xIPlg8nUHpZE
gazTuzSzZNerXQV62gof8opQUfrLdP/9XR57kRdw0fGRo06a1qZktA==
=e2JM
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2005-11-16 0:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-14 16:00 [BUG] Softlockup detected with linux-2.6.14-rt6 Luca Falavigna
2005-11-14 19:48 ` john cooper
2005-11-15 15:32 ` Ingo Molnar
2005-11-15 17:03 ` john cooper
2005-11-15 20:00 ` Ingo Molnar
2005-11-15 20:07 ` Daniel Walker
2005-11-16 0:16 ` Luca Falavigna [this message]
2005-11-18 15:18 ` Luca Falavigna
2005-11-18 18:33 ` K.R. Foley
2005-11-19 0:50 ` Luca Falavigna
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=437A7A58.8050209@gmail.com \
--to=dktrkranz@gmail.com \
--cc=dwalker@mvista.com \
--cc=john.cooper@timesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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.