From: Dipankar Sarma <dipankar@in.ibm.com>
To: Bernhard Rosenkraenzer <bero@arklinux.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
jan malstrom <xanon@snacksy.com>,
linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.12-mm1 (kernel BUG at fs/open.c:935!)
Date: Tue, 21 Jun 2005 04:15:44 +0530 [thread overview]
Message-ID: <20050620224544.GF4562@in.ibm.com> (raw)
In-Reply-To: <200506202341.19426.bero@arklinux.org>
On Mon, Jun 20, 2005 at 11:41:18PM +0200, Bernhard Rosenkraenzer wrote:
> On Monday 20 June 2005 23:22, Dipankar Sarma wrote:
> > > > > Jun 20 14:38:07 hades kernel: kernel BUG at fs/open.c:935!
> >
> > Does it always happen with kded and always on reiser4 or does it happen
> > with other FS ? I tested with Jan's .config and couldn't reproduce it
> > in my P4 box. What exactly are you running in your machine ?
>
> I'm seeing the same thing on a P4 box with ext3, so it's probably not
> filesystem related.
Did you too see the problem with KDE userland ? It
always seem to happen with kded doing fcntl() or fcntl64().
>
> I'm using gcc 3.4.4, binutils 2.16.90.0.3 - maybe it's yet another <kernel
> developer>gcc bug</kernel developer><gcc developer>piece of crappy code in
> the kernel that should never have worked with another version</gcc
> developer> ;)
I am behind in my lab machines - gcc 3.2.2/3.2.3 binutils 2.14.x or so.
I am going find a box with newer userland and test 2.6.12-mm1 with
KDE to see if I can reproduce it there.
Thanks
Dipankar
next prev parent reply other threads:[~2005-06-20 23:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-20 13:04 2.6.12-mm1 (kernel BUG at fs/open.c:935!) jan malstrom
2005-06-20 20:21 ` Dipankar Sarma
2005-06-20 21:18 ` Rafael J. Wysocki
2005-06-20 21:22 ` Dipankar Sarma
2005-06-20 21:41 ` Bernhard Rosenkraenzer
2005-06-20 22:45 ` Dipankar Sarma [this message]
2005-06-20 23:06 ` Bernhard Rosenkraenzer
2005-06-21 1:06 ` syrius.ml
2005-06-20 21:48 ` Rafael J. Wysocki
2005-06-21 11:29 ` Rafael J. Wysocki
2005-06-20 21:39 ` Alexey Dobriyan
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=20050620224544.GF4562@in.ibm.com \
--to=dipankar@in.ibm.com \
--cc=akpm@osdl.org \
--cc=bero@arklinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=xanon@snacksy.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