From: joel.soete@freebel.net
To: Randolph Chung <randolph@tausq.org>
Cc: "Carlos O'Donell Jr." <carlos@baldric.uwo.ca>,
parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] kdb_v21 branch updated to -pa26, and kallsyms cross-compile
Date: Wed, 05 Jun 2002 17:57:20 +0200 (CEST) [thread overview]
Message-ID: <1023292640.3cfe34e07e65b@webmail.tiscalinet.be> (raw)
In-Reply-To: <20020604154954.GA29187@tausq.org>
Hi all,
It seems that the b2000 I used to test gcc-3.2 does not crash anymore :) with
all kernels :)) (pl 2.4.18 or my stuff on 2.4.19)? (I feel that fs corruption
occurs and was not detected immideately?)
Well I come back to you to see what should be the useable kdb config (to
investigate the network problem with kernel compiled with gcc-3.1 or -3.2).
Mine is now:
CONFIG_MAGIC_SYSRQ=Y
CONFIG_KDB=Y
CONFIG_KDB_MODULES=Y
# CONFIG_KDB_OFF IS NOT SET
CONFIG_KALLSYMS=Y
Thanks a lot,
Joel
Quoting Randolph Chung <randolph@tausq.org>:
> > I think there are two maybe three places where kdb initializes
> > certain structures during startup. I'm going to have to check
> > those paths to see how far it gets before dying.
> >
> > Any comments from the crowd would be helpfull :)
> >
> > /me goes off to add some printk's and extra check
>
> i've been offline for a bit so i might have missed something... but
> aiui
> the symptom you've been seeing is that it hangs at the "If this is the
> last message you see" message? has anyone tried to compile a kernel
> with
> early bootup messages (there's a #define in pdc_cons.c to enable this)
> and see if they get farther?
>
> there are some debugging stuff that you can turn on in
> arch/parisc/kernel/unwind.c ... that piece of code has caused some hangs
>
> in the past, you might want to enable those printks as well.
>
> randolph
> --
> @..@ http://www.TauSq.org/
> (----)
> ( >__< )
> ^^ ~~ ^^
>
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
>
>
-------------------------------------------------
This mail sent through Tiscali Webmail (http://webmail.tiscali.be)
next prev parent reply other threads:[~2002-06-05 16:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-27 4:13 [parisc-linux] kdb_v21 branch updated to -pa26, and kallsyms cross-compile Carlos O'Donell Jr.
2002-05-28 14:27 ` Patrick Caulfield
2002-05-28 14:49 ` Orac
2002-05-28 14:58 ` Patrick Caulfield
2002-05-28 17:29 ` Carlos O'Donell Jr.
2002-05-29 7:51 ` Patrick Caulfield
2002-05-29 12:21 ` Carlos O'Donell Jr.
2002-05-29 14:12 ` Patrick Caulfield
2002-05-29 15:01 ` Carlos O'Donell Jr.
2002-05-29 16:24 ` Patrick Caulfield
2002-05-29 17:26 ` Carlos O'Donell Jr.
2002-05-29 18:07 ` Patrick Caulfield
2002-05-30 14:36 ` Patrick Caulfield
[not found] ` <20020530133515.B15631@systemhalted>
2002-05-31 7:28 ` Patrick Caulfield
2002-05-31 12:54 ` Carlos O'Donell Jr.
2002-06-04 11:55 ` Patrick Caulfield
2002-06-04 12:44 ` Carlos O'Donell Jr.
2002-06-04 15:49 ` Randolph Chung
2002-06-04 16:31 ` joel.soete
2002-06-04 17:27 ` Carlos O'Donell Jr.
2002-06-04 18:19 ` Patrick Caulfield
2002-06-05 15:57 ` joel.soete [this message]
2002-06-05 17:21 ` Randolph Chung
2002-06-05 18:59 ` Carlos O'Donell Jr.
2002-06-06 15:41 ` joel.soete
2002-06-07 11:43 ` [parisc-linux] Verify stack trace address - Joel Carlos O'Donell Jr.
2002-06-07 15:07 ` joel.soete
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=1023292640.3cfe34e07e65b@webmail.tiscalinet.be \
--to=joel.soete@freebel.net \
--cc=carlos@baldric.uwo.ca \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=randolph@tausq.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