From: "Carlos O'Donell Jr." <carlos@baldric.uwo.ca>
To: Patrick Caulfield <patrick@tykepenguin.com>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] kdb_v21 branch updated to -pa26, and kallsyms cross-compile
Date: Wed, 29 May 2002 11:01:18 -0400 [thread overview]
Message-ID: <20020529110118.A3691@systemhalted> (raw)
In-Reply-To: <20020529141231.GG9919@tykepenguin.com>; from patrick@tykepenguin.com on Wed, May 29, 2002 at 03:12:31PM +0100
>
> That's only set like that as a last-dich attempt to get it to work :-(
>
> I'm going to have to give up on this, I can't spend all week trying to get it to
> work. What I don't understand is that I move a working .config to the new kernel
> source and both the serial console AND the scsi stop working.
>
> Ah well, it was a nice idea while it lasted. It's just a bit hard debugging code
> when the only error you get is "Stack pointer and cr30 do not cor
> respond" repeated endlessly....
>
> patrick
>
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)
...
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 :)
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'?
==========
--- ./linux/arch/parisc/kernel/traps.c Tue May 21 00:01:37 2002
+++ ./linux/arch/parisc/kernel/traps.c Tue May 21 00:30:42 2002
@@ -189,10 +189,25 @@
}
else
{
- /* Stack Dump! */
- printk(KERN_CRIT "WARNING! Stack pointer and cr30 do not correspond!\n");
- printk(KERN_CRIT "Dumping virtual address stack instead\n");
- dump_stack((unsigned long)__va(stack_start), (unsigned long)__va(sp), 0);
+
+ stack_start = sp & ~(INIT_TASK_SIZE - 1);
+ if (stack_start == cr30) {
+
+ /* We're in a non-interrupt stack and cr30 matches
+ the start of the stack */
+
+ dump_stack(stack_start, sp, 0);
+
+ }
+ else
+ {
+
+ /* Stack Dump! */
+ printk(KERN_CRIT "WARNING! Stack pointer and cr30 do not correspond!\n");
+ printk(KERN_CRIT "Dumping virtual address stack instead\n");
+ dump_stack((unsigned long)__va(stack_start), (unsigned long)__va(sp), 0);
+
+ }
}
}
#endif
==========
next prev parent reply other threads:[~2002-05-29 15:01 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. [this message]
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
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=20020529110118.A3691@systemhalted \
--to=carlos@baldric.uwo.ca \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=patrick@tykepenguin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.