From: Eugene Crosser <crosser@average.org>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Re: Reproducible kernel oops on PPP session start
Date: Sat, 10 Jan 2004 15:00:24 +0300 [thread overview]
Message-ID: <1073736024.7742.12.camel@pccross.average.org> (raw)
In-Reply-To: <1073483871.2816.9.camel@pccross.average.org>
Marcel,
With 2.6.1 out, I did some further investigation of the oops when
establishing PPP connection. First of all, apparently oops happens on
7th attempt, after 6 successful sessions. Next, I selected console VGA
mode with smaller font, and got the full Oops dump:
http://www.average.org/btoops/
(first picture is vanilla 2.6.1, second is 2.6.1-mh1)
As far as I can tell from analyzing the dump, and objdump of l2cap.o
object, BUG() happens when "sk_set_owner(sk, THIS_MODULE);" in
net/bluetooth/l2cap.c line 353 encounters zero refcount of the module.
So, probably somebody incorrectly decreases the l2cap's refcount
elsewhere...
Any ideas on that?
Eugene
next prev parent reply other threads:[~2004-01-10 12:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 11:42 Reproducible kernel oops on PPP session start Eugene Crosser
2004-01-07 12:15 ` [Bluez-devel] " Marcel Holtmann
2004-01-07 13:57 ` Eugene Crosser
2004-01-10 12:00 ` Eugene Crosser [this message]
2004-01-10 12:11 ` Eugene Crosser
2004-01-11 14:59 ` Marcel Holtmann
2004-01-12 6:33 ` Eugene Crosser
2004-01-12 13:22 ` Marcel Holtmann
2004-01-12 14:52 ` Eugene Crosser
2004-01-12 15:15 ` Marcel Holtmann
2004-01-12 21:22 ` Eugene Crosser
2004-01-12 21:35 ` Marcel Holtmann
2004-01-12 22:02 ` Eugene Crosser
2004-01-13 17:32 ` Marcel Holtmann
2004-01-13 19:33 ` Marcel Holtmann
2004-01-13 21:32 ` Eugene Crosser
2004-01-13 23:14 ` Marcel Holtmann
2004-01-07 14:05 ` Edd Dumbill
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=1073736024.7742.12.camel@pccross.average.org \
--to=crosser@average.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=marcel@holtmann.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