All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: "D. Bahi" <dbahi@enterasys.com>
Cc: uml devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] UML 2.4 shmem.c changes? panic w/ backtrace
Date: Tue, 23 Nov 2004 21:42:18 -0500	[thread overview]
Message-ID: <200411240242.iAO2gI7p006614@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Tue, 23 Nov 2004 11:01:57 EST." <41A35EF5.4080302@enterasys.com>

dbahi@enterasys.com said:
> i know things are hot and heavy in 2.6 but i hope somebody can spare a
> thought about this panic i'm struggling to understand. 

Is this easily reproduced?

The stack isn't ringing any bells with me, particularly since none of my code
appears on the stack until the bug has already happened.

				Jeff



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  parent reply	other threads:[~2004-11-24  0:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-23 16:01 [uml-devel] UML 2.4 shmem.c changes? panic w/ backtrace D. Bahi
2004-11-23 20:13 ` Blaisorblade
2004-11-24  2:42 ` Jeff Dike [this message]
2005-02-24 23:13   ` D. Bahi
2005-02-28 19:44     ` Jeff Dike
2005-03-02 14:07       ` Blaisorblade
2005-03-02 17:01         ` Blaisorblade
2005-03-02 17:03           ` D. Bahi

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=200411240242.iAO2gI7p006614@ccure.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=dbahi@enterasys.com \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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.