LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Matthew <jackdachef@gmail.com>
To: "Ingo Molnar" <mingo@redhat.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	linux-kernel@vger.kernel.org, "Ed Tomlinson" <edt@aei.ca>,
	"Thomas Gleixner" <tglx@linutronix.de>
Subject: Re: Fwd: Fwd: laptop / computer hardlocks during execution of 32bit applications(binaries) on 64bit system (Gentoo)
Date: Tue, 15 Jan 2008 18:11:33 +0100	[thread overview]
Message-ID: <e85b9d30801150911p791651e8hf0406490ad1811ee@mail.gmail.com> (raw)
In-Reply-To: <200801141716.38380.edt@aei.ca>

> Ingo,
>
> 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.
>
> Thanks,
> Ed Tomlinson
>
>
>

++

Ingo,
this probably has to do something with the random unmotivated
hardlocks which I suffered from with 2.6.23

when I used 2.6.23-based kernels my rig from time to time (sometimes 2
times a day) just locked and wouldn't react to keyboard-input or magic
sysrq key anymore
if I have a more precise look at my memory (in my head) it probably
happened more often around usage with realplayer (<-- at least that
app; 32bit on amd64) [perhaps also with 32bit thunderbird]
the next suspect is nvidia-drivers: with earlier versions this
happened more often for me (that's at least the "feeling" I have)

so you guys might want to start with those 3 points (thunderbird,
realplayer, nvidia-drivers);
considerung use / test with latest cfs-backports would also be a good
idea, with early backports I had some problems, whereas it's now
perfectly stable (fair group scheduling not enabled)

unfortunately I can't / couldn't reproduce it
in addition to that I'm pretty busy right now so I can't investigate
any further ...

hope you also find the culprit for that buggy ;)

Regards
Mat

  reply	other threads:[~2008-01-15 17:11 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-29 19:57 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 [this message]
2008-01-15 22:09                                   ` Ingo Molnar
2008-01-15 23:41                                     ` Ed Tomlinson
     [not found]         ` <20080108113820.GA16380@elte.hu>
2008-01-08 11:52           ` Matthew
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=e85b9d30801150911p791651e8hf0406490ad1811ee@mail.gmail.com \
    --to=jackdachef@gmail.com \
    --cc=edt@aei.ca \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --subject='Re: Fwd: Fwd: laptop / computer hardlocks during execution of 32bit applications(binaries) on 64bit system (Gentoo)' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).