From: "Carlos O'Donell Jr." <carlos@baldric.uwo.ca>
To: Randolph Chung <tausq@debian.org>
Cc: patrick@tykepenguin.com, parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] kdb getting healthier? (PCI guru needed, that's you willy!)
Date: Thu, 6 Jun 2002 09:21:15 -0400 [thread overview]
Message-ID: <20020606092115.C6900@systemhalted> (raw)
Randolph,
I think I was able to get kdb to stop dying inside unwind_table_init.
--- unwind.c.orig Thu Jun 6 08:51:02 2002
+++ unwind.c Thu Jun 6 08:51:49 2002
@@ -106,7 +106,7 @@
table->base_addr = base_addr;
table->gp = gp;
table->start = base_addr + start[0].region_start;
- table->end = base_addr + end[-1].region_end;
+ table->end = base_addr + end[0].region_end - sizeof(struct unwind_table_entry);
table->table = (struct unwind_table_entry *)table_start;
table->length = end - start;
table->next = NULL;
Is this a gcc-ism we're seeing?
Note-to-self: Look at .S produced from compiling unwind.c
On another note, we have no code that calls unwind_table_add so I've
#if'd it out. Which makes me wonder... which change was the fix?
Time to go back to square one and try them out independantly.
The kernel still goes into an infinite loop of unknown origin:
---
PCI or EISA Bus Adapter 0 is not registered...
---
(see ./arch/parisc/kernel/pci.c' -> PCI_PORT_IN)
Don't know where this gets called from, or how the ugly macro
expands :)
Sadly I think I zapped my VGA out on the 712/60 (A common occurence?).
It no longer produces _any_ video signals.
I may have to drag a 715/50 back to my house...
c.
next reply other threads:[~2002-06-06 13:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 13:21 Carlos O'Donell Jr. [this message]
2002-06-06 14:09 ` [parisc-linux] kdb getting healthier? (PCI guru needed, that's you willy!) Matthew Wilcox
2002-06-06 14:43 ` Carlos O'Donell Jr.
2002-06-06 16:19 ` John David Anglin
2002-06-06 18:57 ` Carlos O'Donell Jr.
2002-06-06 19:35 ` John David Anglin
2002-06-07 15:08 ` Carlos O'Donell Jr.
2002-06-07 16:42 ` John David Anglin
2002-06-07 16:48 ` Matthew Wilcox
2002-06-07 17:01 ` John David Anglin
2002-06-07 17:06 ` Matthew Wilcox
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=20020606092115.C6900@systemhalted \
--to=carlos@baldric.uwo.ca \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=patrick@tykepenguin.com \
--cc=tausq@debian.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