From: Vojtech Pavlik <vojtech@suse.cz>
To: Soeren Sonnenburg <kernel@nn7.de>
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 13:21:28 +0100 [thread overview]
Message-ID: <20040315122127.GA776@ucw.cz> (raw)
In-Reply-To: <1079349195.1721.14.camel@localhost>
On Mon, Mar 15, 2004 at 12:13:16PM +0100, Soeren Sonnenburg wrote:
> > > 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 ?
It's a kernel bug, definitely. And it's interesting to know that it
happens on device _removal_, that means HID could be freeing the device
structs earlier than evdev is stopping to use them.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
next prev parent reply other threads:[~2004-03-15 12:20 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
2004-03-15 12:21 ` Vojtech Pavlik [this message]
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=20040315122127.GA776@ucw.cz \
--to=vojtech@suse.cz \
--cc=benh@kernel.crashing.org \
--cc=kernel@nn7.de \
--cc=linux-kernel@vger.kernel.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.