linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Christian Kujau <evil@g-house.de>
To: linuxppc-dev@lists.linuxppc.org
Cc: trini@kernel.crashing.org
Subject: Re: ppc32 lockups with 2.6
Date: Fri, 21 Nov 2003 16:25:52 +0100	[thread overview]
Message-ID: <3FBE2E80.3080805@g-house.de> (raw)
In-Reply-To: <3FBA2959.80609@g-house.de>


hi again (and sorry to contact you directly, Tom),

i did not make it with kgdb, but rather compiled kernels over and over
again this week. my gcc-3.3.2 won't compile on a faster i386, so
crosscompiling was not an option :-(

i went down to 2.5.56 and found that even this kernel has the same
symptoms. in short: upon using "tulip", the machine freezes, "3c59x" is
loaded, but not working. (no routing).

i went even down to 2.5.30 to find out, that this kernel is *working*!
both tulip and 3c59x get loaded and are working. i did not test long,
don't know if it will freeze after a day or so, but i think not, as the
described freezes with newer kernel occur instantly.

the thing is, 2.5.31 ist not compiling, nor is 2.5.3x, except this very
2.5.30. same config, same compiler. 2.5.30 compile over and over again,
newer kernels (2.5.31...up to 2.5.46) *do not compile*. so it's pretty
hard to find out *when* the symptoms occur, to dig into this very patch
and finally find out *why*.

i *hope* 2.5.31 or at least 2.5.32 is the bad one. i am curently looking
through the 2.5.31 patch and sorted out ppc-related stuff, to make it
compile, then shuffle a few bits back in so, that it will compile and i
hopefully get my freeze. yes, you can see that this kind of working is
rather...er..crap. but i can't do better at the moment :-(

thanks for reading,
Christian.
--
BOFH excuse #27:

radiosity depletion


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-11-21 15:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-02 20:31 ppc32 lockups with 2.6 Christian Kujau
2003-11-06 21:34 ` Christian
2003-11-10 18:50   ` linas
2003-11-10 20:32     ` Tom Rini
2003-11-10 22:39     ` Christian
2003-11-10 23:57       ` linas
2003-11-11  0:25         ` Christian
2003-11-11 15:36           ` Tom Rini
2003-11-13  0:59             ` Christian Kujau
2003-11-13 17:47               ` Tom Rini
2003-11-13 23:56                 ` Christian Kujau
2003-11-14 15:57                   ` Tom Rini
2003-11-18 12:33                   ` Christian Kujau
2003-11-18 14:14                     ` Christian Kujau
2003-11-21 15:25                       ` Christian Kujau [this message]
2003-11-21 17:54                         ` Tom Rini

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=3FBE2E80.3080805@g-house.de \
    --to=evil@g-house.de \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=trini@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).