public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wang Jian <larkwang@gmail.com>
To: Jens Axboe <axboe@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.12.1 problems I meet (please CC: me)
Date: Thu, 30 Jun 2005 14:44:12 +0800	[thread overview]
Message-ID: <cce092220506292344264b9a53@mail.gmail.com> (raw)
In-Reply-To: <20050630063721.GB2243@suse.de>

[root@devel root]# gcc --version
gcc (GCC) 3.3.2 (Mandrake Linux 10.0 3.3.2-6mdk)

I will try 2.6.12.2 and report back.

On 6/30/05, Jens Axboe <axboe@suse.de> wrote:
> On Thu, Jun 30 2005, Wang Jian wrote:
> > Hi,
> >
> > I use a customized kernel to do packets analysis. The analysis code is
> > linked into kernel. It will vmalloc() nearly 128M (a little less) when
> > initialized.
> >
> > The original code runs on 2.6.10 and works fine. The platform is a
> > general P4 with 100M ethernet. The user space system is a 8M compressed
> > ramdisk image which is a 32M filesystem.
> >
> > Now I want to make it work on 2.6.12+ and on Athlon64 platform, for
> > better driver and better CPU/NIC performance.
> >
> > I have a P4 box (compilation bed, CB), a 2-way Athlon64 box (test bed,
> > TB).
> >
> > The problems are:
> >
> > 1. I port the code directly to 2.6.12.1 on CB, and it compiles ok. But
> > during boot, the kernel boot with error "unknown bus type 0" and freeze.
> > Especially, it can't detect harddisk's partition table. I use "quiet" to
> > strip non-error message and hand copy error messages
> 
> Which compiler? 2.6.12.2 should work for you, looks like you are hit my
> the memcpy reordering bug.
> 
> --
> Jens Axboe
> 
>

  reply	other threads:[~2005-06-30  6:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-30  5:46 2.6.12.1 problems I meet (please CC: me) Wang Jian
     [not found] ` <20050629230020.28a1c129.rdunlap@xenotime.net>
2005-06-30  6:22   ` Wang Jian
2005-06-30  6:37 ` Jens Axboe
2005-06-30  6:44   ` Wang Jian [this message]
2005-06-30  8:28     ` Wang Jian
2005-06-30 10:31 ` Wang Jian

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=cce092220506292344264b9a53@mail.gmail.com \
    --to=larkwang@gmail.com \
    --cc=axboe@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