From: David Woodhouse <dwmw2@infradead.org>
To: mark.langsdorf@amd.com
Cc: mtd@infradead.org
Subject: Re: Debugging an oops
Date: Tue, 21 Nov 2000 16:50:46 +0000 [thread overview]
Message-ID: <628.974825446@redhat.com> (raw)
In-Reply-To: <0FA1031B65A9D111960900805F9FA8E103B9F1D6@txexmta8.amd.com>
mark.langsdorf@amd.com said:
> The EIP shows that the oops is occurring in my version of write32,
> called from vsprintf(?) and cfi_amdext_write_bytes_32,
> Aiee, killing interrupt handler
> Scheduling in interrupt
Does your map write32 function schedule? Try to obtain a semaphore?
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
prev parent reply other threads:[~2000-11-21 16:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-21 16:40 Debugging an oops mark.langsdorf
2000-11-21 16:50 ` David Woodhouse [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=628.974825446@redhat.com \
--to=dwmw2@infradead.org \
--cc=mark.langsdorf@amd.com \
--cc=mtd@infradead.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.