From: Soeren Sonnenburg <kernel@nn7.de>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: oops on checking for changes of usb input devices
Date: Thu, 10 Jun 2004 08:06:21 +0200 [thread overview]
Message-ID: <1086847579.24322.34.camel@localhost> (raw)
Hi!
When I attach a ps2 mouse and keyboard through a ps2->usb adapter and
then do a rescan for changes in input devices I keep getting this oops.
This is kernel 2.6.7-rc2 on powerbook G4. A way to trigger this is to
reload/restart pbbuttonsd.
Any ideas ?
Soeren
kernel: Oops: kernel access of bad area, sig: 11 [#1]
kernel: NIP: 66696C6C LR: C029B0FC SP: EF367E10 REGS: ef367d60 TRAP: 0400 Not tainted
kernel: MSR: 40009032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
kernel: TASK = efbd8050[2952] 'pbbuttonsd' THREAD: ef366000Last syscall: 5
kernel: GPR00: 66696C6C EF367E10 EFBD8050 EFC8C8A0 ED62713C 00000000 CD7D56B0 EF367DA0
kernel: GPR08: 00000000 00000000 C0417F04 00000004 80000488 1002578C 00000000 100C0000
kernel: GPR16: 00000000 00000000 100CA208 100CC7E8 100CC2A8 100CC608 1001E24C 10000000
kernel: GPR24: 10010000 00000000 1001E25C ED62713C ED62713C C0520468 C04179C8 00000010
kernel: NIP [66696c6c] 0x66696c6c
kernel: LR [c029b0fc] input_accept_process+0x3c/0x44
kernel: Call trace:
kernel: [c029dcd8] evdev_open+0x64/0x104
kernel: [c029c070] input_open_file+0x98/0x1cc
kernel: [c006b970] chrdev_open+0xe0/0x16c
kernel: [c00605ec] dentry_open+0x150/0x23c
kernel: [c0060498] filp_open+0x64/0x68
kernel: [c0060958] sys_open+0x68/0xa0
kernel: [c0005ea0] ret_from_syscall+0x0/0x44
udev[20103]: removing device node '/dev/input/event4'
next reply other threads:[~2004-06-10 6:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-10 6:06 Soeren Sonnenburg [this message]
2004-06-10 7:27 ` oops on checking for changes of usb input devices Denis Vlasenko
[not found] ` <200406100200.50146.dtor_core@ameritech.net>
2004-06-10 9:59 ` Soeren Sonnenburg
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=1086847579.24322.34.camel@localhost \
--to=kernel@nn7.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.