From: Florian Lohoff <flo@rfc822.org>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: 2.4.5 in cvs - Did anyone try ?
Date: Sat, 16 Jun 2001 11:14:43 +0200 [thread overview]
Message-ID: <20010616111443.A9156@paradigm.rfc822.org> (raw)
In-Reply-To: <20010616041455.A19841@bacchus.dhis.org>; from ralf@oss.sgi.com on Sat, Jun 16, 2001 at 04:14:55AM +0200
On Sat, Jun 16, 2001 at 04:14:55AM +0200, Ralf Baechle wrote:
> On Fri, Jun 15, 2001 at 09:04:33PM +0200, Florian Lohoff wrote:
>
> > i am just trying 2.4.5 on an Indy and i have no luck. The kernel
> > gets confused very fast on the root ext2 filesystem the 2.4.3 continues
> > to boot from. It is spitting our "EXT2: Bit already set for inode x"
> > and hangs in a tight loop.
>
> There was a stupid braino in include/asm-mips/bitops.h, make sure you
> have revision 1.16 of that file.
I have 1.16 of that file.
Flo
--
Florian Lohoff flo@rfc822.org +49-5201-669912
Why is it called "common sense" when nobody seems to have any?
next prev parent reply other threads:[~2001-06-16 9:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-15 19:04 2.4.5 in cvs - Did anyone try ? Florian Lohoff
2001-06-16 2:14 ` Ralf Baechle
2001-06-16 9:14 ` Florian Lohoff [this message]
2001-06-19 3:39 ` mipsel-linux-ld problem ´¿¬L©ú
2001-06-19 3:39 ` ´¿¬L©ú
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=20010616111443.A9156@paradigm.rfc822.org \
--to=flo@rfc822.org \
--cc=linux-mips@oss.sgi.com \
--cc=ralf@oss.sgi.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