From: joshk@triplehelix.org (Joshua Kwan)
To: "David S. Miller" <davem@redhat.com>
Cc: sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [2.6] busybox EFAULT on sparc64
Date: Thu, 19 Aug 2004 09:09:37 +0000 [thread overview]
Message-ID: <20040819090937.GG8070@triplehelix.org> (raw)
In-Reply-To: <20040818184303.1ae13c98.davem@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 900 bytes --]
On Wed, Aug 18, 2004 at 06:43:03PM -0700, David S. Miller wrote:
> Oops, it's possible that the bug fixed by this patch
> might fix your problem...
It doesn't. :(
RMIK opesdiaefuda lc
VS one ot(x2flsse)
Setting up filesystem, please wait ...
mount: Mounting tmpfs oKre ai:Atmtdt ilii!
n 0PesL- ortr otebo rm
/mnt failed: Bad address
mount: Mounting shm on /mnt failed: Bad address
(May I note that sparc64 serial output for printks continues to miss every
other character, making reading kernel messages and hence debugging a
nightmare.
VS one ot(xtflsse)
is
VFS: Mounted root (ext2 filesystem), I think.)
This is 2.6.8 with your new two patches applied on top of each other.
--
Joshua Kwan
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 881 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: joshk@triplehelix.org (Joshua Kwan)
To: "David S. Miller" <davem@redhat.com>
Cc: sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [2.6] busybox EFAULT on sparc64
Date: Thu, 19 Aug 2004 02:09:37 -0700 [thread overview]
Message-ID: <20040819090937.GG8070@triplehelix.org> (raw)
In-Reply-To: <20040818184303.1ae13c98.davem@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 900 bytes --]
On Wed, Aug 18, 2004 at 06:43:03PM -0700, David S. Miller wrote:
> Oops, it's possible that the bug fixed by this patch
> might fix your problem...
It doesn't. :(
RMIK opesdiaefuda lc
VS one ot(x2flsse)
Setting up filesystem, please wait ...
mount: Mounting tmpfs oKre ai:Atmtdt ilii!
n 0PesL- ortr otebo rm
/mnt failed: Bad address
mount: Mounting shm on /mnt failed: Bad address
(May I note that sparc64 serial output for printks continues to miss every
other character, making reading kernel messages and hence debugging a
nightmare.
VS one ot(xtflsse)
is
VFS: Mounted root (ext2 filesystem), I think.)
This is 2.6.8 with your new two patches applied on top of each other.
--
Joshua Kwan
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 881 bytes --]
next prev parent reply other threads:[~2004-08-19 9:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-18 23:55 [2.6] busybox EFAULT on sparc64 Joshua Kwan
2004-08-18 23:55 ` Joshua Kwan
2004-08-19 0:04 ` Joshua Kwan
2004-08-19 0:04 ` Joshua Kwan
2004-08-19 0:06 ` David S. Miller
2004-08-19 0:06 ` David S. Miller
2004-08-19 0:07 ` David S. Miller
2004-08-19 0:07 ` David S. Miller
2004-08-19 1:43 ` David S. Miller
2004-08-19 1:43 ` David S. Miller
2004-08-19 9:09 ` Joshua Kwan [this message]
2004-08-19 9:09 ` Joshua Kwan
2004-08-19 16:52 ` David S. Miller
2004-08-19 16:52 ` David S. Miller
2004-08-20 5:02 ` David S. Miller
2004-08-20 5:02 ` David S. Miller
2004-08-27 0:57 ` Joshua Kwan
2004-08-27 1:06 ` David S. Miller
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=20040819090937.GG8070@triplehelix.org \
--to=joshk@triplehelix.org \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@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 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.