From: Soeren Sonnenburg <kernel@nn7.de>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: 2.6.4 - powerbook 15" - usb oops+backtrace
Date: Mon, 15 Mar 2004 12:13:16 +0100 [thread overview]
Message-ID: <1079349195.1721.14.camel@localhost> (raw)
In-Reply-To: <20040313121027.GA7434@ucw.cz>
On Sat, 2004-03-13 at 13:10, Vojtech Pavlik wrote:
> On Fri, Mar 12, 2004 at 02:25:36PM +0100, Soeren Sonnenburg wrote:
> > Hi!
> >
> > I got this oops when inserting mouse/keyboard (both usb).
> >
> > usb 1-1: new low speed USB device using address 4
> > input: USB HID v1.00 Mouse [Cypress Sem USB Mouse] on usb-0001:01:18.0-1
> > Oops: kernel access of bad area, sig: 11 [#1]
> > NIP: 5A5A5A58 LR: C026D8B0 SP: ED6B1E10 REGS: ed6b1d60 TRAP: 0401 Not
> > tainted
> > MSR: 40009032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
> > TASK = edb87320[1332] 'pbbuttonsd' Last syscall: 5
> > GPR00: 5A5A5A5A ED6B1E10 EDB87320 C1991894 E2DB789C 00000000 E7909300
> > ED6B1DC0
> > GPR08: 00000000 00000000 C03DA5A0 00000005 84000428
> > Call trace:
> > [c02704ac] evdev_open+0x64/0x104
> > [c026e814] input_open_file+0x98/0x1cc
> > [c00675a8] chrdev_open+0xe0/0x16c
> > [c005c0b4] dentry_open+0x15c/0x230
> > [c005bf54] filp_open+0x64/0x68
> > [c005c43c] sys_open+0x68/0xa0
> > [c0005d3c] ret_from_syscall+0x0/0x44
> > usb 2-1: new low speed USB device using address 4
> > input: USB HID v1.00 Keyboard [PTC HID PS/2 Keyboard - PS/2 Mouse] on
> > usb-0001:01:19.0-1
> > input: USB HID v1.00 Mouse [PTC HID PS/2 Keyboard - PS/2 Mouse] on
> > usb-0001:01:19.0-1
> >
> > Thanks for any suggestions...
> >
> > I can probably give more infos as xmon is compiled in the kernel here.
>
> Is this reproducible, or does it happen only rarely? I suspect it could
> be a race somewhere ...
It happens reproducably even when booting without X (and it always the
very same oops I get). However it seems to only happen in connection
with pbbuttonsd which has to be reloaded (causing it to rescan for
changed usb hid devices) via hotplug... The oops happens when I remove a
device, which in turn causes hotplug to make pbbuttonsd rescan for
added/removed devices which then somehow triggers this oops.
So could this be pbbuttonsd's fault :? or is it indeed some kernel bug ?
Soeren
next prev parent reply other threads:[~2004-03-15 11:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-12 13:25 2.6.4 - powerbook 15" - usb oops+backtrace Soeren Sonnenburg
2004-03-13 0:23 ` Benjamin Herrenschmidt
2004-03-13 7:49 ` Soeren Sonnenburg
2004-03-13 8:37 ` Benjamin Herrenschmidt
2004-03-13 12:10 ` Vojtech Pavlik
2004-03-15 11:13 ` Soeren Sonnenburg [this message]
2004-03-15 12:21 ` Vojtech Pavlik
2004-03-15 12:53 ` 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=1079349195.1721.14.camel@localhost \
--to=kernel@nn7.de \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/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.