All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarod Wilson <jarod@redhat.com>
To: Valdis.Kletnieks@vt.edu
Cc: akpm@linux-foundation.org,
	Mauro Carvalho Chehab <mchehab@redhat.com>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
	linux-input@vger.kernel.org
Subject: Re: mmotm 2010-07-19-16-37 uploaded
Date: Tue, 20 Jul 2010 16:38:42 -0400	[thread overview]
Message-ID: <20100720203841.GL13176@redhat.com> (raw)
In-Reply-To: <6434.1279658492@localhost>

On Tue, Jul 20, 2010 at 04:41:32PM -0400, Valdis.Kletnieks@vt.edu wrote:
> On Mon, 19 Jul 2010 16:38:09 PDT, akpm@linux-foundation.org said:
> > The mm-of-the-moment snapshot 2010-07-19-16-37 has been uploaded to
> > 
> >    http://userweb.kernel.org/~akpm/mmotm/
> 
> (Andrew - did we lose a bunch of -swedish-chef-fix-fix-fix.patch files? This is the second
> thing that I reported back in May, worked in mm-rc3-0701, but dies in -rc5-0719...)
> 
> [   50.949361] BUG: unable to handle kernel NULL pointer dereference at (null)
> [   50.950978] IP: [<(null)>] (null)
> [   50.952045] PGD 11b7b0067 PUD 119d9c067 PMD 0
> [   50.954744] Oops: 0010 [#1] PREEMPT SMP
> [   50.954744] last sysfs file: /sys/devices/pci0000:00/0000:00:1b.0/device
> [   50.954744] CPU 0
> [   50.954744] Modules linked in: microcode(+) [last unloaded: scsi_wait_scan]
> [   50.954744]
> [   50.967468] Pid: 2994, comm: keymap Tainted: G        W   2.6.35-rc5-mmotm0719 #1 0X564R/Latitude E6500
> [   50.967468] RIP: 0010:[<0000000000000000>]  [<(null)>] (null)
> [   50.967468] RSP: 0018:ffff88011e7e5cb0  EFLAGS: 00010046
> [   50.967468] RAX: 0000000000000000 RBX: ffff88011d8b5000 RCX: 0000000000000000
> [   50.967468] RDX: ffff88011e7e5cc8 RSI: ffff88011e7e5cc8 RDI: ffff88011d8b5000
> [   50.967468] RBP: ffff88011e7e5d28 R08: 0890000000000000 R09: 0000000000000001
> [   50.967468] R10: ffff88011d8b5858 R11: ffff88011d8b5840 R12: 0000000000000000
> [   50.967468] R13: 00000000000000a4 R14: ffff88011d8b5840 R15: 0000000000000296
> [   50.967468] FS:  00007fea0676e720(0000) GS:ffff880002600000(0000) knlGS:0000000000000000
> [   50.967468] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [   50.967468] CR2: 0000000000000000 CR3: 000000011f72b000 CR4: 00000000000406f0
> [   50.967468] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> [   50.967468] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> [   50.967468] Process keymap (pid: 2994, threadinfo ffff88011e7e4000, task ffff88011e620100)
> [   50.967468] Stack:
> [   50.967468]  ffffffff813b4b54 ffff88011e7e5cc8 0000008100000246 00000081000000a4
> [   50.967468] <0> 0000000000000004 0000000000000000 ffff88011e7e5cc4 00007fffe9f95f00
> [   50.967468] <0> ffff88011b4a3300 ffff88011e7e5d28 0000000000000081 fffffffffffffff2
> [   50.967468] Call Trace:
> [   50.967468]  [<ffffffff813b4b54>] ? input_set_keycode+0xbc/0x13c
> [   50.967468]  [<ffffffff813b7ee2>] evdev_do_ioctl+0x24c/0x816
> [   51.016215]  [<ffffffff813b84e6>] ? evdev_ioctl_handler+0x3a/0x81
> [   51.018336]  [<ffffffff813b84e6>] ? evdev_ioctl_handler+0x3a/0x81
> [   51.021130]  [<ffffffff813b8510>] evdev_ioctl_handler+0x64/0x81
> [   51.022519]  [<ffffffff813b854a>] evdev_ioctl+0xb/0xd
> [   51.024439]  [<ffffffff810e91a0>] vfs_ioctl+0x31/0xa2
> [   51.026408]  [<ffffffff810e9b1f>] do_vfs_ioctl+0x496/0x4c9
> [   51.028337]  [<ffffffff810e9ba9>] sys_ioctl+0x57/0x96
> [   51.030245]  [<ffffffff8100272b>] system_call_fastpath+0x16/0x1b
> [   51.032123] Code:  Bad RIP value.
> [   51.034015] RIP  [<(null)>] (null)
> [   51.037307]  RSP <ffff88011e7e5cb0>
> [   51.038270] CR2: 0000000000000000
> [   51.038270] ---[ end trace 84b562a00a6053a0 ]---
> 
> And things go downhill from there...

This looks like the same trace we got in the Red Hat bugzilla a few days
ago, and for which I submitted this:

https://patchwork.kernel.org/patch/112791/

-- 
Jarod Wilson
jarod@redhat.com


  reply	other threads:[~2010-07-20 20:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-19 23:38 mmotm 2010-07-19-16-37 uploaded akpm
2010-07-20 20:35 ` mmotm 2010-07-19 - e1000e vs. pm_qos_update_request issues Valdis.Kletnieks
2010-07-20 21:07   ` Andrew Morton
2010-07-20 21:07     ` Andrew Morton
2010-07-21  7:12     ` [PATCH] " Florian Mickler
2010-07-21 22:12       ` mark gross
2010-07-22  4:05       ` Valdis.Kletnieks
2010-07-22 21:58         ` Rafael J. Wysocki
2010-07-22 22:37       ` Jeff Kirsher
2010-07-22 22:37         ` Jeff Kirsher
2010-07-21 22:09     ` mark gross
2010-07-21 22:09       ` mark gross
2010-07-20 20:41 ` mmotm 2010-07-19-16-37 uploaded Valdis.Kletnieks
2010-07-20 20:38   ` Jarod Wilson [this message]
     [not found]   ` <201007201350.28961.dmitry.torokhov@gmail.com>
2010-07-20 21:11     ` Valdis.Kletnieks
2010-07-20 21:41       ` Jarod Wilson
2010-07-25 18:00         ` Mauro Carvalho Chehab
2010-07-21 12:54 ` mmotm 2010-07-19 - more pm_qos woes - audio this time Valdis.Kletnieks
2010-07-21 12:54   ` Valdis.Kletnieks
2010-07-21 12:59   ` Mark Brown
2010-07-21 12:59     ` [alsa-devel] " Mark Brown

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=20100720203841.GL13176@redhat.com \
    --to=jarod@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 \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@redhat.com \
    /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.