Bug 5503 - Logitech Mouse causes oops
Summary: Logitech Mouse causes oops
Status: CLOSED CODE_FIX
Alias: None
Product: IO/Storage
Classification: Unclassified
Component: Block Layer (show other bugs)
Hardware: i386 Linux
: P2 normal
Assignee: Dmitry Torokhov
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-26 15:06 UTC by David Gardner
Modified: 2006-03-21 13:17 UTC (History)
4 users (show)

See Also:
Kernel Version: 2.6.14 rc5 mm1
Subsystem:
Regression: ---
Bisected commit-id:

Attachments
bootup output (12.29 KB, text/plain)
2005-10-26 15:07 UTC, David Gardner 		Details
.config file (61.37 KB, text/plain)
2005-10-27 11:39 UTC, David Gardner 		Details
Add an attachment (proposed patch, testcase, etc.)

Description David Gardner 2005-10-26 15:06:26 UTC 
Most recent kernel where this bug did not occur:2.6.14 rc3 mm1
Distribution:SLES 9 sp2
Hardware Environment:xseries x370
Software Environment:2.6.14 rc5 mm1
Problem Description:
During the bootup process I get an oops - 

io scheduler cfq registered<4>logips2pp: Detected unknown logitech mouse model 1

Unable to handle kernel NULL pointer dereference at virtual address 00000064
 printing eip:
c02874e0
*pde = 004a8001
Oops: 0000 [#1]
SMP 
last sysfs file: 
Modules linked in:
CPU:    4
EIP:    0060:[<c02874e0>]    Not tainted VLI
EFLAGS: 00010286   (2.6.14-rc5-mm1) 
input: PS/2 Logitech Mouse//class/input as input2
EIP is at elevator_put+0x0/0x30
eax: 00000000   ebx: 00000000   ecx: c04ede40   edx: 00000000
esi: c966fe0c   edi: c03f6d50   ebp: c029be40   esp: dfe41f5c
ds: 007b   es: 007b   ss: 0068
Process swapper (pid: 1, threadinfo=dfe40000 task=dfe00a90)
Stack: c0287677 c966fe0c ffffffff c03f6d50 c028a829 000000c0 fffffff4 00000000 
       00000008 c0486a8b c966256c c039d990 00000007 c03a00ef c03f6d14 c049b70c 
       00000000 00000000 00000000 c0466aa3 00000000 dfe40000 00000000 dfe40000 
Call Trace:
 [<c0287677>] elevator_init+0x17/0xa0
 [<c028a829>] blk_init_queue_node+0xc9/0x130
 [<c0486a8b>] floppy_init+0xdb/0x5e0
 [<c0466aa3>] do_initcalls+0x23/0xc0
 [<c0100415>] init+0x105/0x240
 [<c0100310>] init+0x0/0x240
 [<c01029c5>] kernel_thread_helper+0x5/0x10
Code: 85 c0 74 12 8b 12 8b 02 0f 18 00 90 81 fa 84 64 3f c0 75 d7 eb 05 89 d3 8d
 76 00 89 d8 5b 5e 5f c3 8d 76 00 8d bc 27 00 00 00 00 <8b> 50 64 85 d2 74 1b b8
 00 e0 ff ff 21 e0 8b 40 10 c1 e0 07 8d 
 <0>Kernel panic - not syncing: Attempted to kill init!


Steps to reproduce:
Boot with 2.6.14 rc5 mm1 kernel
Comment 1 David Gardner 2005-10-26 15:07:33 UTC 
Created attachment 6395 [details]
bootup output
Comment 2 Andrew Morton 2005-10-26 15:22:44 UTC 
This is surely unrelated to the input code: looks like a block layer
bug.

Please attach the .config.
Comment 3 David Gardner 2005-10-27 10:30:18 UTC 
Where would I find the .config? Thanks.
Comment 4 David Gardner 2005-10-27 11:39:18 UTC 
Created attachment 6400 [details]
.config file 

Here is the .config. Was not thinking during my last comment.
Comment 5 Andrew Morton 2005-11-03 23:21:03 UTC 
Allegedly this is fixed in Linus's current tree.  Please
test ftp://ftp.kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.14-git6.gz
and update this report, thanks.
Comment 6 Dmitry Torokhov 2005-12-20 15:12:07 UTC 
Moving out of input devices...
Note You need to log in before you can comment on or make changes to this bug.