All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Ebbert <cebbert@redhat.com>
To: Stefan Priebe - FH <studium@profihost.com>
Cc: linux-kernel@vger.kernel.org, stefan@priebe.ws,
	David Chinner <dgc@sgi.com>
Subject: Re: XFS or Kernel Problem / Bug
Date: Wed, 24 Jan 2007 09:57:05 -0500	[thread overview]
Message-ID: <45B773C1.7090805@redhat.com> (raw)
In-Reply-To: <45B70D69.20500@profihost.com>

Stefan Priebe - FH wrote:
> Hi!
>
> I do everything you like :-) if we can find the bug.
>
> So here are the files (2.6.18.6):
> http://server055.de-nserver.de/filemap.o
> http://server055.de-nserver.de/filemap.s
>
>>
>> If you can, post the file mm/filemap.o from your build directory to some
>> website.
>> And do 'make mm/filemap.s' and post that file too.
>>
>
That doesn't match your oops at all.  Did you use a different compiler
and/or
different kernel build options?



  reply	other threads:[~2007-01-24 14:56 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060801141545.B2326184@wobbly.melbourne.sgi.com>
     [not found] ` <44CED76B.20507@profihost.com>
     [not found]   ` <20060801142755.C2326184@wobbly.melbourne.sgi.com>
     [not found]     ` <44CED8F4.9080208@profihost.com>
     [not found]       ` <20060801143212.D2326184@wobbly.melbourne.sgi.com>
     [not found]         ` <44CEDA1D.5060607@profihost.com>
     [not found]           ` <20060801143803.E2326184@wobbly.melbourne.sgi.com>
     [not found]             ` <44CF36FB.6070606@profihost.com>
     [not found]               ` <20060802090915.C2344877@wobbly.melbourne.sgi.com>
     [not found]                 ` <44D07AB7.3020409@profihost.com>
     [not found]                   ` <20060802201805.A2360409@wobbly.melbourne.sgi.com>
2007-01-21 12:30                     ` XFS or Kernel Problem / Bug Stefan Priebe - FH
2007-01-22  6:18                       ` David Chinner
2007-01-22  7:51                         ` Stefan Priebe - FH
2007-01-22  8:03                           ` David Chinner
2007-01-22  8:07                             ` Stefan Priebe - FH
2007-01-23  1:10                               ` David Chinner
2007-01-23  8:31                                 ` Stefan Priebe - FH
2007-01-22  9:42                             ` Stefan Priebe - FH
2007-01-23 19:49                       ` Chuck Ebbert
2007-01-24  7:40                         ` Stefan Priebe - FH
2007-01-24 14:57                           ` Chuck Ebbert [this message]
2007-01-24 15:03                             ` Stefan Priebe - FH
2007-01-24 15:13                               ` Chuck Ebbert
2007-01-24 15:34                                 ` Stefan Priebe - FH
2007-01-24 16:51                                   ` Chuck Ebbert
2007-01-24 17:16                                     ` Stefan Priebe - FH
2007-01-24 17:56                                       ` Chuck Ebbert
2007-01-24 19:27                                         ` Stefan Priebe - FH
2007-01-25 20:52                                           ` Chuck Ebbert
2007-01-25 21:29                                             ` Stefan Priebe - FH
2007-01-30 10:44                                               ` Stefan Priebe - FH

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=45B773C1.7090805@redhat.com \
    --to=cebbert@redhat.com \
    --cc=dgc@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stefan@priebe.ws \
    --cc=studium@profihost.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 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.