From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Valdis.Kletnieks@vt.edu
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: mmotm 2010-05-11-18-20 uploaded
Date: Thu, 13 May 2010 14:32:27 -0300 [thread overview]
Message-ID: <4BEC37AB.2020505@redhat.com> (raw)
In-Reply-To: <10741.1273768199@localhost>
Valdis.Kletnieks@vt.edu wrote:
> On Thu, 13 May 2010 13:20:50 -0300, Mauro Carvalho Chehab said:
>> Dmitry Torokhov wrote:
>>> On Thu, May 13, 2010 at 11:06:34AM -0400, Valdis.Kletnieks@vt.edu wrote:
>>>> On Tue, 11 May 2010 18:21:22 PDT, akpm@linux-foundation.org said:
>>>>> The mm-of-the-moment snapshot 2010-05-11-18-20 has been uploaded to
>>>>>
>>>>> http://userweb.kernel.org/~akpm/mmotm/
>>>> Dell Latitude E6500, x86_64 kernel.
>>>>
>>>> Boots to single user prompt, but has issues on the way there. Possibly
>>>> very important - I was definitely *not* typing at the time (as I had hit
>>>> return on the LUKS passphrase for the disk at 36 seconds after boot, and
>>>> I didn't get the # prompt for single-user for another minute or two (probably
>>>> due to udev having issues due to the oops). So I have no idea what it was
>>>> trying to get a keycode for...
>>>>
>>> Udev probably tries to remap special keys on your keyboard...
>>>
>>>> [ 40.717136] udev: starting version 154
>>>> [ 41.710153] BUG: unable to handle kernel NULL pointer dereference at (null)
>>>> [ 41.711007] IP: [<ffffffff813bb996>] input_default_getkeycode_from_index+0x4e/0x5b
>>>> [ 41.711007] PGD 11d318067 PUD 118af1067 PMD 0
>>>> [ 41.711007] Oops: 0002 [#1] PREEMPT SMP
>>>> [ 41.711007] last sysfs file: /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-4/idVendor
>>>> [ 41.711007] CPU 0
>>>> [ 41.711007] Modules linked in:
>>>> [ 41.711007]
>>>> [ 41.711007] Pid: 2501, comm: keymap Not tainted 2.6.34-rc7-mmotm0511 #2 0X564R/Latitude E6500
>>>>
>>>> [ 41.711007] RIP: 0010:[<ffffffff813bb996>] [<ffffffff813bb996>] input_default_getkeycode_from_index+0x4e/0x5b
>>> I think this is Mauro's big keycode additions.
>> Yes, it is likely. It may be caused by some bad conflict resolution between both git trees.
>> I'll handle this bug.
>
> Feel free to let me know if there's any testing/instrumentation you want done...
>
Ok. I probably won't have time for handing it until next week, as I'll be traveling
tomorrow for a short trip.
--
Cheers,
Mauro
next prev parent reply other threads:[~2010-05-13 17:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 1:21 mmotm 2010-05-11-18-20 uploaded akpm
2010-05-12 16:50 ` mmotm 2010-05-11-18-20 uploaded (aio build) Randy Dunlap
2010-05-12 17:07 ` Jeff Moyer
2010-05-12 17:09 ` Randy Dunlap
2010-05-12 19:42 ` mmotm 2010-05-11-18-20 uploaded (aio build; add numa) Randy Dunlap
2010-05-12 19:52 ` mmotm 2010-05-11 - dies in pm_qos_update_request() Valdis.Kletnieks
2010-05-12 21:07 ` Rafael J. Wysocki
2010-05-12 22:12 ` Valdis.Kletnieks
2010-05-12 22:33 ` Rafael J. Wysocki
2010-05-13 14:34 ` Valdis.Kletnieks
2010-05-13 22:24 ` Rafael J. Wysocki
2010-05-14 23:43 ` mark gross
2010-05-13 22:32 ` Rafael J. Wysocki
2010-05-12 20:39 ` [PATCH -mmotm] misc: fix ad525X_dpot build Randy Dunlap
2010-05-12 20:53 ` Hennerich, Michael
2010-05-12 20:39 ` [PATCH -mmotm] backlight: fix adp8860_bl build errors Randy Dunlap
2010-05-12 20:54 ` Hennerich, Michael
2010-05-13 15:06 ` mmotm 2010-05-11-18-20 uploaded Valdis.Kletnieks
2010-05-13 16:02 ` Dmitry Torokhov
2010-05-13 16:20 ` Mauro Carvalho Chehab
2010-05-13 16:29 ` Valdis.Kletnieks
2010-05-13 17:32 ` Mauro Carvalho Chehab [this message]
2010-05-19 23:34 ` Mauro Carvalho Chehab
2010-05-20 4:57 ` Mauro Carvalho Chehab
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=4BEC37AB.2020505@redhat.com \
--to=mchehab@redhat.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).