From: Marc Koschewski <marc@osknowledge.org>
To: Ian McDonald <imcdnzl@gmail.com>
Cc: Marc Koschewski <marc@osknowledge.org>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.15-rc2-mm1
Date: Wed, 23 Nov 2005 20:50:54 +0100 [thread overview]
Message-ID: <20051123195052.GA7446@stiffy.osknowledge.org> (raw)
In-Reply-To: <cbec11ac0511231133m63bec4ddi455fa769dd22906b@mail.gmail.com>
* Ian McDonald <imcdnzl@gmail.com> [2005-11-24 08:33:36 +1300]:
> On 11/24/05, Marc Koschewski <marc@osknowledge.org> wrote:
> > Just booted into 2.6.15-rc2-mm1. The 'mouse problem' (as reported earlier) still
> > persists, moreover, some stuff's now really not gonna work anymore. I logged in
> > via gdm once and rebooted.
> >
> > Ragards,
> > Marc
> >
>
> Mouse problem is userspace. See bug 340202 on the Debian site.
>
> Ian
===
Package: udev
Version: 0.074-3
Severity: critical
Justification: breaks the whole system
When running Linux 2.6.15-rc1+, the new nested class devices used by the
input class prevent /dev/input/ from being created, rendering X
unusable.
===
The problem over here exists _only_ in the -mm series, not plain 2.6.15-rc1
or 2.6.15-rc2. What's up then!? I use udev 0.74-3 as well. Mysterious...
marc@stiffy:~$ uname -a
Linux stiffy 2.6.15-rc2-marc #1 PREEMPT Sun Nov 20 22:09:22 CET 2005 i686 GNU/Linux
marc@stiffy:~$
Regards,
Marc
next prev parent reply other threads:[~2005-11-23 19:50 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-23 11:35 2.6.15-rc2-mm1 Andrew Morton
2005-11-23 13:35 ` 2.6.15-rc2-mm1 Serge E. Hallyn
2005-11-23 14:15 ` 2.6.15-rc2-mm1 Michal Piotrowski
2005-11-23 19:22 ` 2.6.15-rc2-mm1 Andrew Morton
2005-11-24 9:04 ` 2.6.15-rc2-mm1 Harald Welte
2005-11-23 14:24 ` 2.6.15-rc2-mm1 thunder7
2005-11-23 17:50 ` 2.6.15-rc2-mm1 Marc Koschewski
2005-11-23 19:33 ` 2.6.15-rc2-mm1 Ian McDonald
2005-11-23 19:50 ` Marc Koschewski [this message]
2005-11-23 20:12 ` 2.6.15-rc2-mm1 Greg KH
2005-11-23 20:23 ` 2.6.15-rc2-mm1 Marc Koschewski
2005-11-23 19:38 ` 2.6.15-rc2-mm1 Andrew Morton
2005-11-24 2:06 ` Mouse issues in -mm Frank Sorenson
2005-11-24 3:26 ` Dmitry Torokhov
2005-11-24 6:14 ` Frank Sorenson
2005-11-25 22:31 ` Dmitry Torokhov
2005-11-24 9:40 ` Marc Koschewski
2005-11-25 22:27 ` Dmitry Torokhov
2005-11-26 2:52 ` Marc Koschewski
2005-11-26 3:50 ` Dmitry Torokhov
2005-11-23 20:25 ` 2.6.15-rc2-mm1 Benoit Boissinot
2005-11-23 22:35 ` [-mm patch] init/main.c: dummy mark_rodata_ro() should be static Adrian Bunk
2005-11-23 22:46 ` Randy.Dunlap
2005-11-23 22:54 ` Adrian Bunk
2005-11-24 4:21 ` Dave Jones
2005-11-24 5:05 ` Andrew Morton
2005-11-24 5:06 ` Adrian Bunk
2005-11-24 5:14 ` [-mm patch] " Adrian Bunk
2005-11-24 7:56 ` Arjan van de Ven
2005-11-25 15:49 ` Adrian Bunk
2005-11-24 7:56 ` [-mm patch] init/main.c: " Arjan van de Ven
2005-11-24 0:20 ` 2.6.15-rc2-mm1 J.A. Magallon
2005-11-24 0:27 ` 2.6.15-rc2-mm1 Andrew Morton
2005-11-24 3:18 ` 2.6.15-rc2-mm1 KAMEZAWA Hiroyuki
2005-11-24 5:02 ` 2.6.15-rc2-mm1 Andrew Morton
2005-11-25 13:36 ` [PATCH] oprofile : Use vmalloc_node() in alloc_cpu_buffers() Eric Dumazet
2005-11-24 18:48 ` 2.6.15-rc2-mm1 Alexandre Buisse
2005-11-26 5:49 ` 2.6.15-rc2-mm1 Valdis.Kletnieks
-- strict thread matches above, loose matches on Subject: below --
2005-11-23 11:35 2.6.15-rc2-mm1 Andrew Morton
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=20051123195052.GA7446@stiffy.osknowledge.org \
--to=marc@osknowledge.org \
--cc=akpm@osdl.org \
--cc=imcdnzl@gmail.com \
--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.