From: Ed Tomlinson <edt@aei.ca>
To: Ingo Molnar <mingo@elte.hu>
Cc: Matthew <jackdachef@gmail.com>, "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Roland McGrath <roland@redhat.com>
Subject: Re: Fwd: Fwd: laptop / computer hardlocks during execution of 32bit applications(binaries) on 64bit system (Gentoo)
Date: Tue, 15 Jan 2008 18:41:34 -0500 [thread overview]
Message-ID: <200801151841.35714.edt@aei.ca> (raw)
In-Reply-To: <20080115220952.GD2665@elte.hu>
On January 15, 2008, Ingo Molnar wrote:
>
> * Ed Tomlinson <edt@aei.ca> wrote:
>
> > This is _not_ a regression. This has been occuring for ages here. A
> > backport of this fix to 2.6.23 would be a very good thing - IMHO its
> > something that should go into stable asap.
>
> the problem is that this bug was only present in x86.git. I.e. neither
> 2.6.24 nor 2.6.23 has this particular bug.
>
> perhaps something else in x86.git fixed your box, but this
> x86.git-specific hang 'took over its place', and now that it got fixed,
> you've got a working box? In any case, please monitor your box, it might
> still lock up the same way it did previously ...
I am now testing with a .24-rc7+fix kernel. So far so good. Running gentoo's 32 bit
firefox with flash 9 is a good way to trigger the problem here as is running Delftship (freeship)
under wine. The problem is usually worst with a fully preemptive kernel. I have been using both on
a kernel with preempt and have an uptime of 22 hours - this is really good. I have rarely been able
to get this much uptime using these apps. If it manages to run for a few more days without a lockup
it would really be worth trying to figure out what in .24 fixes the problem...
THANKS!
Ed Tomlinson
next prev parent reply other threads:[~2008-01-15 23:41 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-29 19:57 laptop / computer hardlocks during execution of 32bit applications(binaries) on 64bit system (Gentoo) Matthew
2007-12-29 23:04 ` Fwd: " Matthew
2007-12-30 0:28 ` Miguel Botón
2008-01-02 8:40 ` Ingo Molnar
[not found] ` <e85b9d30801080333y3d6668ccgf20f9666d0326884@mail.gmail.com>
2008-01-08 11:40 ` Fwd: " Matthew
2008-01-09 0:58 ` H. Peter Anvin
2008-01-10 9:05 ` Matthew
2008-01-10 9:42 ` Ingo Molnar
2008-01-10 12:43 ` Matthew
2008-01-10 12:48 ` Ingo Molnar
2008-01-10 12:59 ` Matthew
2008-01-10 13:24 ` Ingo Molnar
2008-01-10 13:08 ` Ed Tomlinson
2008-01-10 13:32 ` Ingo Molnar
2008-01-10 15:56 ` Matthew
2008-01-10 16:38 ` Ed Tomlinson
2008-01-10 23:35 ` Zan Lynx
2008-01-10 21:10 ` Matthew
2008-01-10 21:17 ` H. Peter Anvin
2008-01-10 21:52 ` Matthew
2008-01-10 21:57 ` H. Peter Anvin
2008-01-10 22:28 ` Matthew
2008-01-10 22:30 ` H. Peter Anvin
2008-01-10 22:53 ` Matthew
2008-01-14 16:13 ` Ingo Molnar
2008-01-14 16:47 ` Matthew
2008-01-14 17:00 ` Ingo Molnar
2008-01-14 22:16 ` Ed Tomlinson
2008-01-15 17:11 ` Matthew
2008-01-15 22:09 ` Ingo Molnar
2008-01-15 23:41 ` Ed Tomlinson [this message]
[not found] ` <20080108113820.GA16380@elte.hu>
2008-01-08 11:52 ` Matthew
-- strict thread matches above, loose matches on Subject: below --
2008-01-11 2:22 Fwd: " Ed Tomlinson
2008-01-14 16:16 ` Ingo Molnar
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=200801151841.35714.edt@aei.ca \
--to=edt@aei.ca \
--cc=hpa@zytor.com \
--cc=jackdachef@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=roland@redhat.com \
--cc=tglx@linutronix.de \
/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.