From: Al Viro <viro@ZenIV.linux.org.uk>
To: Berthold Cogel <cogel@uni-koeln.de>
Cc: linux-kernel@vger.kernel.org, nigel@nigel.suspend2.net,
dtor@mail.ru, jikos@jikos.cz, akpm@linux-foundation.org,
linux-usb-owner@vger.kernel.org
Subject: Re: Oops in evdev_disconnect for kernel 2.6.23.12
Date: Sun, 6 Jan 2008 20:15:59 +0000 [thread overview]
Message-ID: <20080106201559.GU27894@ZenIV.linux.org.uk> (raw)
In-Reply-To: <47812E5B.6080000@uni-koeln.de>
On Sun, Jan 06, 2008 at 08:39:07PM +0100, Berthold Cogel wrote:
> >>If I'm able to reproduce the oops with my patched kernel, I will gladly
> >>follow your advice.
> >
> >AFAICS, lkml.org/lkml/2007/7/24/20 is the same patch...
>
> Ok! It happened again....
>
> I was able to reproduce the Oops twice. Once with my patched kernel
> (2.6.23.12 patched with tuxonice-3.0-rc3-for-2.6.23.9 on Debian
> stable/testing/unstable) and the second time with a vanilla 2.6.23.12
> kernel. So this isn't related to Tuxonice.
Apply the patch in aforementioned posting and see if it fixes the things?
next prev parent reply other threads:[~2008-01-06 20:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-01 19:26 Oops in evdev_disconnect for kernel 2.6.23.12 Berthold Cogel
2008-01-01 20:35 ` Berthold Cogel
2008-01-01 21:17 ` Nigel Cunningham
2008-01-05 9:30 ` Andrew Morton
2008-01-05 6:52 ` Al Viro
2008-01-06 0:14 ` Berthold Cogel
2008-01-06 0:17 ` Al Viro
2008-01-06 19:39 ` Berthold Cogel
2008-01-06 20:15 ` Al Viro [this message]
2008-01-06 21:15 ` Berthold Cogel
2008-01-06 23:45 ` Al Viro
2008-01-07 20:54 ` Berthold Cogel
2008-02-02 2:58 ` Martin Bauer
2008-02-03 9:33 ` Martin Bauer
2008-01-06 1:50 ` Nigel Cunningham
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=20080106201559.GU27894@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=cogel@uni-koeln.de \
--cc=dtor@mail.ru \
--cc=jikos@jikos.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-owner@vger.kernel.org \
--cc=nigel@nigel.suspend2.net \
/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