All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Matthew <jackdachef@gmail.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>, Ed Tomlinson <edt@aei.ca>
Subject: Re: Fwd: Fwd: laptop / computer hardlocks during execution of 32bit applications(binaries) on 64bit system (Gentoo)
Date: Thu, 10 Jan 2008 13:57:31 -0800	[thread overview]
Message-ID: <478694CB.4000306@zytor.com> (raw)
In-Reply-To: <e85b9d30801101352hf66826eqe436e61310c96f14@mail.gmail.com>

Matthew wrote:
>> Do you have the error dump output to go along with this, too?
>>
> 
> no, unfortunately no kernel crash dump on disk ;( (I hope I understood
> it right, I'm pretty noobish concerning collection of error data ;) )
> 
> I only have the console-output of the hardlock in:
> http://kerneloftruth.neucode.org/other/crash_ia32_64/not_tainted/

That's fine, but that was collected with the vmlinux image you sent me, 
right?

	-hpa

  reply	other threads:[~2008-01-10 21:58 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 [this message]
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
     [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=478694CB.4000306@zytor.com \
    --to=hpa@zytor.com \
    --cc=edt@aei.ca \
    --cc=jackdachef@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@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.