From: Dave Airlie <airlied@gmail.com>
To: tytso@mit.edu, linux-kernel@vger.kernel.org
Subject: Re: [REGRESSION] X doesn't work with 2.6.33 (can't find any input devices)
Date: Fri, 5 Mar 2010 15:18:11 +1000 [thread overview]
Message-ID: <21d7e9971003042118hf455ce5y7e839754d95440e@mail.gmail.com> (raw)
In-Reply-To: <20100303151720.GA3191@thunk.org>
On Thu, Mar 4, 2010 at 1:17 AM, <tytso@mit.edu> wrote:
> After working around lvm breakage so I could at least boot 2.6.33, I'm
> now finding the next problem --- X doesn't work. If I let X come up,
> it doesn't find any mouse or keyboard devices, so my machine becomes
> useless and I have to power cycle it unless I can log in remotely and
> reboot it.
>
> It worked just *fine* using 2.6.33-rc4. I have no xorg.conf file (X
> is autoconfiguring itself) and I'm using an Ubuntu 9.10 userspace.
>
> I've enclosed the dmesg output (which shows the input devices
> correctly being detected by the kernel) and the Xorg.0.log file from
> the previous boot, where X does not come up.
>
> At this point, I'm not going to be able to dogfood test my ext4
> patches I plan to push to Linus, since 2.6.33 is completely useless to
> me. Hopefully running the regression tests under KVM is going to have
> to be good enough.
>
Are you using 32 on 64 or anything like that?
15e184afa83a45cf8bafdb9dc906b97a8fbc974f is the only thing I can
see that might be close to changing something.
Dave.
prev parent reply other threads:[~2010-03-05 5:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 15:17 tytso
2010-03-03 15:20 ` David Miller
2010-03-05 4:40 ` tytso
2010-03-05 5:11 ` Dave Airlie
2010-03-07 1:13 ` tytso
2010-03-05 5:18 ` Dave Airlie [this message]
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=21d7e9971003042118hf455ce5y7e839754d95440e@mail.gmail.com \
--to=airlied@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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
all inboxes | Powered by JetHome®