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: Tom Rini <trini@kernel.crashing.org>
Subject: Re: ppc32 lockups with 2.6
Date: Tue, 18 Nov 2003 13:33:48 +0100	[thread overview]
Message-ID: <3FBA11AC.8090408@g-house.de> (raw)
In-Reply-To: <3FB41A14.3040108@g-house.de>


hi,

2.6.0-test9 with kgdb compiled fine then, but i did not get a serial
cable yet.

i took another approach, i wanted to see since when the lockups occur. i
was testing 2.5 kernels on i386 and alpha, but i've started to test 2.6
on ppc pretty late. so, what i see is, that i can boot to 2.6.0-test4
(former kernel version down to 2.5.72 did not even compile cleanly).
i can set up eth0 and i can watch "ifconfig eth0" then. "ping
192.168.1.10" (eth0) is working, but routing seems broken. (i have to
show the details later on).

"ping 192.168.1.11" fails and print a lot to the syslog as you can see
in line 581 in:

http://nerdbynature.de/bits/sheep/network/2.6.0-test4/messages.gz

during bootup i had to use SYSREQ-E to quit a process, that wanted to
use the ethernet-device (snort?)
(SYSREQ-K should have been enough perhaps).

here's the config for this 2.6.0-test4 kernel
http://nerdbynature.de/bits/sheep/network/2.6.0-test4/config

i will go on with 2.6.0-tes5 now....

Thank you,
Christian.
--
BOFH excuse #229:

wrong polarity of neutron flow


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

  parent reply	other threads:[~2003-11-18 12:33 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 [this message]
2003-11-18 14:14                     ` Christian Kujau
2003-11-21 15:25                       ` Christian Kujau
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=3FBA11AC.8090408@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).