From: Dimitry Andric <dimitry.andric@tomtom.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] hidp kernel panic on 2.4.25 mh15
Date: Wed, 30 Mar 2005 21:39:43 +0200 [thread overview]
Message-ID: <424B007F.3090200@tomtom.com> (raw)
In-Reply-To: <20050330163950.GA15198@externe.net>
Guylhem Aznar wrote:
>>This is a NULL pointer dereference, but I am not quite good in decoding
>>the trace backs of ARM.
Try enabling CONFIG_DEBUG_USER, CONFIG_DEBUG_KERNEL and
CONFIG_DEBUG_ERRORS in your kernel configuration file (you can find
these options under the Kernel Hacking menuconfig item), and then
reproducing the crash. This should give a complete stack trace with
function names, making it a lot easier to see what goes wrong.
> # modprobe hidp
> Using /lib/modules/2.4.29-guylhem/kernel/drivers/input/input.o
> Using /lib/modules/2.4.29-guylhem/kernel/net/bluetooth/hidp/hidp.o
Why is the subject about 2.4.25, when this indicates 2.4.29?
-------------------------------------------------------
This SF.net email is sponsored by Demarc:
A global provider of Threat Management Solutions.
Download our HomeAdmin security software for free today!
http://www.demarc.com/Info/Sentarus/hamr30
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-03-30 19:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-29 18:23 [Bluez-devel] hidp kernel panic on 2.4.25 mh15 Guylhem Aznar
2005-03-29 20:59 ` Marcel Holtmann
2005-03-30 16:39 ` Guylhem Aznar
2005-03-30 19:39 ` Dimitry Andric [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=424B007F.3090200@tomtom.com \
--to=dimitry.andric@tomtom.com \
--cc=bluez-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