From: "H . J . Lu" <hjl@lucon.org>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: Florian Lohoff <flo@rfc822.org>,
Raoul Borenius <borenius@shuttle.de>,
linux-mips@oss.sgi.com
Subject: Re: Kernel crash on boot with current cvs (todays)
Date: Tue, 12 Jun 2001 09:37:15 -0700 [thread overview]
Message-ID: <20010612093715.A20012@lucon.org> (raw)
In-Reply-To: <20010612135306.A26214@bacchus.dhis.org>; from ralf@oss.sgi.com on Tue, Jun 12, 2001 at 01:53:06PM +0200
On Tue, Jun 12, 2001 at 01:53:06PM +0200, Ralf Baechle wrote:
> On Tue, Jun 12, 2001 at 12:09:27PM +0200, Florian Lohoff wrote:
>
> > I got a hint that it might be the compile to produce this bug - I was
> > suggested to use some gcc 3.0 prerelease. I now checked again and i am
> > already using some gcc 3.0
>
> It's not a tool related bug but a genuine kernel bug in our semaphore code.
> Which - unfortunately is a bit of headache to fix but is more or less the #1
> on the list of my instabilities right now.
I have some kernel crashes which are cured by some gcc/binutils changes
which I don't believe should make any differences. I thought I could
take out the mips64 and -march patches. But wtithout them, the user
applications seem ok, but the kernel crashes in all different places.
I have to put them back in. They may be kernel bugs and my gcc/binutils
changes may just hide them.
BTW, what is the current 2.4 kernel patches for Algorithmics P6032?
Thanks.
H.J.
next prev parent reply other threads:[~2001-06-12 16:37 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-10 22:03 Kernel crash on boot with current cvs (todays) Florian Lohoff
2001-06-11 3:53 ` Keith Owens
2001-06-11 19:12 ` Florian Lohoff
2001-06-12 1:01 ` Maciej W. Rozycki
2001-06-12 1:01 ` Keith M Wesolowski
2001-06-12 1:22 ` Maciej W. Rozycki
2001-06-12 2:05 ` Keith Owens
2001-06-11 4:42 ` Ralf Baechle
2001-06-11 14:50 ` Raoul Borenius
2001-06-12 10:09 ` Florian Lohoff
2001-06-12 11:53 ` Ralf Baechle
2001-06-12 16:37 ` H . J . Lu [this message]
[not found] ` <20010613100602.A17124@bunny.shuttle.de>
2001-06-13 10:56 ` Florian Lohoff
2001-06-13 11:34 ` Keith Owens
2001-06-13 12:05 ` Ralf Baechle
2001-06-13 12:19 ` ksymoops changes for mips (was Kernel crash on boot with current cvs) Keith Owens
2001-06-16 9:22 ` Ralf Baechle
2001-06-27 2:21 ` ksymoops changes for mips Keith Owens
2001-06-28 14:32 ` Thiemo Seufer
2001-07-31 3:57 ` Keith Owens
2001-07-31 4:30 ` Keith Owens
2001-08-03 6:10 ` Keith Owens
2001-08-03 10:07 ` Thiemo Seufer
2001-06-13 13:44 ` Kernel crash on boot with current cvs (todays) Maciej W. Rozycki
2001-06-13 14:07 ` Keith Owens
2001-06-13 15:08 ` Maciej W. Rozycki
2001-06-16 9:24 ` Ralf Baechle
2001-06-13 11:37 ` Raoul Borenius
2001-06-13 11:46 ` Keith Owens
2001-06-13 11:46 ` Keith Owens
2001-06-13 13:16 ` Raoul Borenius
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=20010612093715.A20012@lucon.org \
--to=hjl@lucon.org \
--cc=borenius@shuttle.de \
--cc=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