From: Keith Owens <kaos@ocs.com.au>
To: Andrew Over <ajo@acm.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Oops on removing via-rhine [2.4.10-ac11]
Date: Fri, 12 Oct 2001 10:04:26 +1000 [thread overview]
Message-ID: <32326.1002845066@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Thu, 11 Oct 2001 14:09:43 MST." <20011011140943.A10576@yeah.cx>
On Thu, 11 Oct 2001 14:09:43 -0700,
Andrew Over <ajo@acm.org> wrote:
>This oops is reasonably easy to reproduce (reinsert and remove
>via-rhine enough times and it happens)
>>>EIP; c0129840 <__free_pages_ok+10/1c0> <=====
>Trace; c01acd3e <pci_release_regions+6e/80>
>Trace; c0129f1a <__free_pages+1a/20>
>Trace; c0129f44 <free_pages+24/30>
>Trace; c010b6bc <pci_free_consistent+1c/20>
>Trace; e08fdbaa <_end+2066e636/20670a8c>
>Trace; e08fe860 <_end+2066f2ec/20670a8c>
>Trace; c01ad01e <pci_unregister_driver+3e/60>
>Trace; e08fdc0a <_end+2066e696/20670a8c>
>Trace; e08fe860 <_end+2066f2ec/20670a8c>
Oops in module delete may not get the symbol tables for the deleted
module if they have already been removed from /proc/ksyms. I suggest
you create /var/log/ksymoops, man insmod. Then insmod and rmmod will
save the symbol tables after each module load or unload, you can point
ksymoops at the saved symbols from before the failing rmmod. That will
give a better ksymoops decode.
next prev parent reply other threads:[~2001-10-12 0:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-11 21:09 Andrew Over
2001-10-12 0:04 ` Keith Owens [this message]
2001-10-12 1:24 ` Andrew Over
2001-10-13 10:55 ` Urban Widmark
2001-10-15 19:10 ` Andrew Over
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=32326.1002845066@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=ajo@acm.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®