From: Vojtech Pavlik <vojtech@suse.cz>
To: rvalles <rvalles@es.gnu.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: joydev: kernel panic accessing /dev/js0 with 2.6.2-rc1-bk1
Date: Sun, 25 Jan 2004 09:44:25 +0100 [thread overview]
Message-ID: <20040125084425.GA610@ucw.cz> (raw)
In-Reply-To: <20040125060731.GA5797@217-126-33-148.uc.nombres.ttd.es>
On Sun, Jan 25, 2004 at 07:07:31AM +0100, rvalles wrote:
> > If you also could get the function where EIP is, that'd be great.
> Oops! Did I really post all the stack trace and forgot about the current
> function? Well, I wonder what was I thinking. Here it is:
>
> EIP is at hidinput_hid_event+0x8f/0x2a0
>
> Also, had to boot from a Knoppix 3.3 for some stuff, and verified, with jstest,
> that the pad seems to be working well with its kernel (2.4.22-xfs).
>
> I also forgot to tell you that I've got CONFIG_HID_FF and CONFIG_LOGITECH_FF
> enabled on my 2.6.2-rc1-bk1.
>
> cc me on reply. I'm not suscribed into linux-kernel.
Ok, now I see how and where it happens. But I need the device HID
desriptor dump. Please enable DEBUG and DEBUG_DATA in hid-core.c,
and send me the output it produces into 'dmesg'. If you want to avoid
the crash, simply disable hid-input in kernel config for the experiment.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
next parent reply other threads:[~2004-01-25 8:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040125060731.GA5797@217-126-33-148.uc.nombres.ttd.es>
2004-01-25 8:44 ` Vojtech Pavlik [this message]
[not found] <20040124090354.GA5285@217-126-33-148.uc.nombres.ttd.es>
2004-01-24 10:55 ` joydev: kernel panic accessing /dev/js0 with 2.6.2-rc1-bk1 Vojtech Pavlik
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=20040125084425.GA610@ucw.cz \
--to=vojtech@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=rvalles@es.gnu.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