From: "D. Bahi" <dbahi@enterasys.com>
To: Jeff Dike <jdike@addtoit.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: Thu, 24 Feb 2005 18:13:30 -0500 [thread overview]
Message-ID: <421E5F9A.6030109@enterasys.com> (raw)
In-Reply-To: <200411240242.iAO2gI7p006614@ccure.user-mode-linux.org>
[-- Attachment #1: Type: text/plain, Size: 471 bytes --]
This happens everytime i try to load an application of ours that
uses shmem for syslog...
Jeff Dike wrote:
>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
>
>
>
--
db
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 187 bytes --]
next prev parent reply other threads:[~2005-02-24 23:13 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
2005-02-24 23:13 ` D. Bahi [this message]
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=421E5F9A.6030109@enterasys.com \
--to=dbahi@enterasys.com \
--cc=jdike@addtoit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox