mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Bryan O'Sullivan" <bos@serpentine.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.5.72] Oops on x86_64 running 32-bit code
Date: 18 Jun 2003 15:51:11 -0700	[thread overview]
Message-ID: <1055976671.25153.80.camel@serpentine.internal.keyresearch.com> (raw)
In-Reply-To: <20030618224516.GF3543@wotan.suse.de>

On Wed, 2003-06-18 at 15:45, Andi Kleen wrote:

> Looks quite garbled. Is it reproducible?

Not yet.  I'll let you know if I see anything.

On an unrelated note, the trouble with running BK in 32-bit mode seems
to be back:

~ $ bk help
system: No child processes
system: No child processes
less: Bad file descriptor
system: No child processes

This time, there are no syslog errors or other reports to indicate
what's up.  I can't strace it to see where it's dying, because 64-bit
strace won't handle 32-bit code.

	<b


  reply	other threads:[~2003-06-18 22:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-18 22:40 Bryan O'Sullivan
2003-06-18 22:45 ` Andi Kleen
2003-06-18 22:51   ` Bryan O'Sullivan [this message]
2003-06-18 23:06     ` Andi Kleen
2003-06-18 23:14       ` Bryan O'Sullivan

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=1055976671.25153.80.camel@serpentine.internal.keyresearch.com \
    --to=bos@serpentine.com \
    --cc=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®