All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: James.Bottomley@SteelEye.com (James Bottomley)
Cc: dave.anglin@nrc.ca, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Expect defunct, kill -9 panics kernel?
Date: Sun, 11 Feb 2007 15:59:37 -0500 (EST)	[thread overview]
Message-ID: <200702112059.l1BKxboZ010491__35286.3322398209$1416624285$gmane$org@hiauly1.hia.nrc.ca> (raw)
In-Reply-To: <1171226106.3406.47.camel@mulgrave.il.steeleye.com> from "James Bottomley" at Feb 11, 2007 02:35:06 pm

> Right, now here's a bit of really useful detective work:
> 
> In the same piece of disassembly can you see what happens to %r26 ...
> the first argument to __wake_up_common() which is the wait queue?  It
> may be clobbered, but if it isn't by the time we fault we know that
> 0x45f10250 is the address of the wait queue.  If we're incredibly lucky,
> it's a symbol in the vmlinux, can you see if it is (and if it's valid)?

In the code I'm looking at, r26 is copied to r7 near the beginning of
__wake_up_common().  r7 is 0 in the register dump.  Of course, Carlos'
kernel may differ.

Dave
-- 
J. David Anglin                                  dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

       reply	other threads:[~2007-02-11 20:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1171226106.3406.47.camel@mulgrave.il.steeleye.com>
2007-02-11 20:59 ` John David Anglin [this message]
     [not found] <200702101937.l1AJb7Uo014941@hiauly1.hia.nrc.ca>
2007-02-11  1:50 ` [parisc-linux] Expect defunct, kill -9 panics kernel? James Bottomley
     [not found] ` <1171158607.3373.54.camel@mulgrave.il.steeleye.com>
     [not found]   ` <119aab440702110909r2018a297k98b4f1baed54821a@mail.gmail.com>
2007-02-11 17:17     ` John David Anglin
2007-02-11 19:19     ` James Bottomley
     [not found]     ` <1171221592.3406.32.camel@mulgrave.il.steeleye.com>
     [not found]       ` <119aab440702111221k19b2643em26ac943399274b9f@mail.gmail.com>
     [not found]         ` <119aab440702111222v3562f308v9808b4dea7b73d59@mail.gmail.com>
2007-02-11 20:35           ` James Bottomley
     [not found] <119aab440702100916q504101b1xe99f65ff5945e712@mail.gmail.com>
2007-02-10 18:35 ` James Bottomley

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='200702112059.l1BKxboZ010491__35286.3322398209$1416624285$gmane$org@hiauly1.hia.nrc.ca' \
    --to=dave@hiauly1.hia.nrc.ca \
    --cc=James.Bottomley@SteelEye.com \
    --cc=dave.anglin@nrc.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 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.