From: "Christopher Friesen" <cfriesen@nortel.com>
To: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: looking for help tracing oops -- resolved
Date: Tue, 06 Sep 2005 09:24:36 -0600 [thread overview]
Message-ID: <431DB4B4.6040907@nortel.com> (raw)
In-Reply-To: <431925C4.60509@nortel.com>
Thanks for all the tips, guys.
I managed to get the problem to occur on a vanilla kernel with just the
proprietary module loaded. Contacted the vendor, they got me to try out
a new driver, problem appears to be fixed.
Looks like the module wasn't properly tracking refcounts, so it was
being unloaded when there were still dangling references. Oops.
Thanks,
Chris
prev parent reply other threads:[~2005-09-06 15:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-03 4:25 looking for help tracing oops Christopher Friesen
2005-09-03 9:55 ` Jiri Slaby
2005-09-04 3:46 ` Zwane Mwaikambo
2005-09-06 15:24 ` Christopher Friesen [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=431DB4B4.6040907@nortel.com \
--to=cfriesen@nortel.com \
--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