public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: Shiner Chen <shiner.chen@gmail.com>,
	K G Srivastava <kg.srivastava@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBI error on 64bit Machine
Date: Wed, 03 Jan 2007 19:18:13 +0200	[thread overview]
Message-ID: <1167844693.20245.18.camel@sauron> (raw)
In-Reply-To: <f9fe74a60612150559x4bcb9eedlfe9675b6be70682@mail.gmail.com>

Hello,

On Fri, 2006-12-15 at 21:59 +0800, Shiner Chen wrote:
> Dear all,
> 
> Recently, I get the source code on the ubi-2.6.git tree. I compiled
> the kernel on x86-32 arch and erverything is ok,but on x86-64,I met
> some problems as follows
> Environment
> operation system:Red hat Enterprise Server 4.3(kernel 2.6.19 including
> the UBI,gcc 3.5)
> hardware:x86-64

On Fri, 2006-12-15 at 18:58 +0530, K G Srivastava wrote: 
> Hi,
>   I am trying to setup UBI over mtdram/nandsim on a AMD 64-bit (1.66
> MHz) Turion Dual core machine. The MTD device is of size 128 MB and
> the UBI volume is of size 111 MB. I have tried it on Intel P-4 CPU
> 2.66GHz and it works fine. But as soon as i do a modprobe for ubi
> module, the kernel gives an oops. Can you please tell me if UBI works
> fine on 64-bit architecture or if there are any known issues and if
> there are any fixes available. The trace of the same is as follows -

May you please try the newest UBI? There is a chance that it will work
better on 64-bit machines now.

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)

      parent reply	other threads:[~2007-01-03 17:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-15 13:59 UBI error on 64bit Machine Shiner Chen
2006-12-15 14:07 ` Artem Bityutskiy
     [not found]   ` <f9fe74a60612150616h4b423eabr2678eb78d8bdfb35@mail.gmail.com>
2006-12-15 14:26     ` Artem Bityutskiy
2007-01-03 17:18 ` Artem Bityutskiy [this message]

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=1167844693.20245.18.camel@sauron \
    --to=dedekind@infradead.org \
    --cc=kg.srivastava@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=shiner.chen@gmail.com \
    /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