Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Patrick Caulfield <patrick@tykepenguin.com>
To: parisc-linux@lists.parisc-linux.org
Cc: "Carlos O'Donell Jr." <carlos@baldric.uwo.ca>
Subject: Re: [parisc-linux] kdb_v21 branch updated to -pa26, and kallsyms cross-compile
Date: Wed, 29 May 2002 17:24:38 +0100	[thread overview]
Message-ID: <20020529162438.GJ9919@tykepenguin.com> (raw)
In-Reply-To: <20020529110118.A3691@systemhalted>

On Wed, May 29, 2002 at 11:01:18AM -0400, Carlos O'Donell Jr. wrote:
> >
> 
> You can't always copy a .config from kernel to kernel. The kernel source
> dictates what will be _in_ the .config. I usually run 'make mrproper'
> and then have 'make oldconfig' or 'make ???config' recreate the config files
> to suit the material in the kernel.
> 
> When switching to a new source tree I recommend:
> make mrproper
> make oldconfig
> make menuconfig (to suit your tastes)

Oh, I'm doing that. I just tried it again, it was either that or throw it out
of the window.

Is there parisc version of the kdb patch I could try applying to a kernel
source I know works maybe ?

> As for the endless 'Stack pointer and cr30 do not correspond!'....
> 
> I believe that is a bug in traps.c and I have code to give a proper dump.
> I haven't been able to get anyone who knows to explain how the dump_stack in 
> traps should _really_ work :)

Thanks, I'll try that out.
 
> AFAI understand the following works (I've tested it on my kernels with what 
> looks to be a successfull dump while doing some bad things (props to Bame
> for helping me out) ;)
> 
> BTW, what led me to this solution is that the printk in the else is
> completely bogus... so I rewrote the else.
> 
> Q: When do you get 'Stack pointer and cr30 do not correspond'?

When it hits my buggy code :-) 

patrick

  reply	other threads:[~2002-05-29 16:24 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 [this message]
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
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=20020529162438.GJ9919@tykepenguin.com \
    --to=patrick@tykepenguin.com \
    --cc=carlos@baldric.uwo.ca \
    --cc=parisc-linux@lists.parisc-linux.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