public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Patrick Read <pread99999@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: Oops in Kernel 2.6.15 usbhid
Date: Tue, 10 Jan 2006 00:54:50 -0500	[thread overview]
Message-ID: <200601100054.51198.dtor_core@ameritech.net> (raw)
In-Reply-To: <25ac9de40601052225i48bca97dx3ad796a1cd68f1c3@mail.gmail.com>

On Friday 06 January 2006 01:25, Patrick Read wrote:
> [1.] Oops in Kernel 2.6.15 usbhid
> 
> [2.] Compiled 2.6.15 downloaded from kernel.org.  Configured, made,
> and installed.  During reboot, I get an Oops in the USB HID module. 
> This does not occur with a nearly-identical config on the same
> computer with kernel 2.6.14.5.
> 
> [3.] USB, HID, kernel, 2.6.15, module
> 

Could you please try the patch below? Thanks!

-- 
Dmitry

Signed-off-by: Dmitry Torokhov <dtor@mail.ru>
---

 drivers/usb/input/pid.c |    2 +-
 1 files changed, 1 insertion(+), 1 deletion(-)

Index: work/drivers/usb/input/pid.c
===================================================================
--- work.orig/drivers/usb/input/pid.c
+++ work/drivers/usb/input/pid.c
@@ -259,7 +259,7 @@ static int hid_pid_upload_effect(struct 
 int hid_pid_init(struct hid_device *hid)
 {
 	struct hid_ff_pid *private;
-	struct hid_input *hidinput = list_entry(&hid->inputs, struct hid_input, list);
+	struct hid_input *hidinput = list_entry(hid->inputs.next, struct hid_input, list);
 	struct input_dev *input_dev = hidinput->input;
 
 	private = hid->ff_private = kzalloc(sizeof(struct hid_ff_pid), GFP_KERNEL);

  reply	other threads:[~2006-01-10  5:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-06  6:25 PROBLEM: Oops in Kernel 2.6.15 usbhid Patrick Read
2006-01-10  5:54 ` Dmitry Torokhov [this message]
2006-01-11  8:21   ` Patrick Read
2006-01-11 14:31     ` Dmitry Torokhov
2006-01-12  1:11       ` Adrian Bunk
  -- strict thread matches above, loose matches on Subject: below --
2006-01-13 18:51 Chuck Ebbert

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=200601100054.51198.dtor_core@ameritech.net \
    --to=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pread99999@gmail.com \
    /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