Linux PARISC architecture development
 help / color / mirror / Atom feed
From: joel.soete@freebel.net
To: "Carlos O'Donell Jr." <carlos@baldric.uwo.ca>
Cc: joel.soete@freebel.net, Randolph Chung <randolph@tausq.org>,
	parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Verify stack trace address - Joel
Date: Fri, 07 Jun 2002 17:07:17 +0200 (CEST)	[thread overview]
Message-ID: <1023462437.3d00cc25b2b82@webmail.tiscalinet.be> (raw)
In-Reply-To: <20020607074303.B10393@systemhalted>

Hi C,

Two news (a bad and a good as usual).

I had actually an hardware problem with this test b2000 so that I could not any
more reboot it.
So the bad news is that I could not verify anything right now.

For the good news is that we have maintenance contract and the problem occurs
now during the launch of stm under hpux.

So I can open a call and pieces are already order to repair it Monday.

Quoting "Carlos O'Donell Jr." <carlos@baldric.uwo.ca>:

> > 
> > Stack: 10408600 Cannot find unwind entry for 0x1010c9c0
> > 
> > Call Trace: 
> >         [<1010c880>]
>             ^^^^^^^^
> 
> > Cannot find unwind entry for 0x1010c9c0
>                                ^^^^^^^^^^
> 
> Can you find that address in your System.map to verify where that is?
> If it's in unwind_table_init then the 'end[-1]' fix might be what is
> needed.
> 

I will check it asap and let you inform

> 
> For some reason device detection becomes bogus and broken with
> kdb enabled. So far we've seen SCSI, Serial, PCI/EISA all die with
> kdb enabled. Maybe they're not dead and just moving _really_ slowly.
> 
> I'm going camping this weekend, so it's anyones game until Monday
> afternoon (which I have off too!!) :)
> 
Have a nice week-end,
    Joel


-------------------------------------------------
This mail sent through Tiscali Webmail (http://webmail.tiscali.be)

      reply	other threads:[~2002-06-07 15:09 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
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 [this message]

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=1023462437.3d00cc25b2b82@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