From: James Bottomley <James.Bottomley@SteelEye.com>
To: "Carlos O'Donell" <carlos@systemhalted.org>
Cc: John David Anglin <dave@hiauly1.hia.nrc.ca>,
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 13:19:52 -0600 [thread overview]
Message-ID: <1171221592.3406.32.camel__9339.49033865265$1416624284$gmane$org@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <119aab440702110909r2018a297k98b4f1baed54821a@mail.gmail.com>
On Sun, 2007-02-11 at 12:09 -0500, Carlos O'Donell wrote:
> How do I validate your guess? Look for a null or bogus curr->func when
> scheduling?
Disassemble the piece in vmlinux for __wait_common and check that the
instruction that faulted is where the code gets the curr->func.
James
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2007-02-11 19:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
[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] <1171226106.3406.47.camel@mulgrave.il.steeleye.com>
2007-02-11 20:59 ` John David Anglin
[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='1171221592.3406.32.camel__9339.49033865265$1416624284$gmane$org@mulgrave.il.steeleye.com' \
--to=james.bottomley@steeleye.com \
--cc=carlos@systemhalted.org \
--cc=dave.anglin@nrc.ca \
--cc=dave@hiauly1.hia.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.