All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: linux-kernel@vger.kernel.org
Cc: DSA <debian-admin@lists.debian.org>, linux-input@vger.kernel.org
Subject: Re: 2.6.32.1: BUG and panic: unable to handle kernel NULL pointer dereference at 000000000000001f
Date: Tue, 22 Dec 2009 13:04:16 +0100	[thread overview]
Message-ID: <871vindxkv.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20091215162736.GS13850@anguilla.noreply.org> (Peter Palfrader's message of "Tue, 15 Dec 2009 17:27:37 +0100")

Peter Palfrader <weasel@debian.org> writes:


> [    5.304749] BUG: unable to handle kernel NULL pointer dereference at 000000000000001f
> ..
> [    5.308739] Call Trace:
> [    5.308739]  [<ffffffff810c3840>] kstrdup+0x40/0x70
> [    5.308739]  [<ffffffff81150d77>] sysfs_new_dirent+0xf7/0x110
> [    5.308739]  [<ffffffff8115121d>] create_dir+0x3d/0xc0
> [    5.308739]  [<ffffffff81090af1>] ? autoremove_wake_function+0x11/0x40
> [    5.308739]  [<ffffffff811512d4>] sysfs_create_dir+0x34/0x50
> [    5.308739]  [<ffffffff8138e7ea>] ? kobject_get+0x1a/0x30
> [    5.308739]  [<ffffffff8138e961>] kobject_add_internal+0xe1/0x1e0
> [    5.308739]  [<ffffffff8138eb78>] kobject_add_varg+0x38/0x60
> [    5.308739]  [<ffffffff8138ec15>] kobject_init_and_add+0x75/0x90
> [    5.308739]  [<ffffffff81150560>] ? sysfs_ilookup_test+0x0/0x20
> [    5.308739]  [<ffffffff8115082d>] ? sysfs_find_dirent+0x2d/0x40
> [    5.308739]  [<ffffffff81150ec1>] ? sysfs_addrm_finish+0x21/0x250
> [    5.308739]  [<ffffffff8138e7ea>] ? kobject_get+0x1a/0x30
> [    5.308739]  [<ffffffff810e6fe4>] ? kmem_cache_alloc+0x84/0xc0
> [    5.308739]  [<ffffffff814238d4>] bus_add_driver+0x94/0x260
> [    5.308739]  [<ffffffff81424ed9>] driver_register+0x79/0x160
> [    5.308739]  [<ffffffff815a28a3>] __hid_register_driver+0x43/0x80
> [    5.308739]  [<ffffffff81a3d7ff>] ? gyration_init+0x0/0x1b
> [    5.308739]  [<ffffffff81a3d818>] gyration_init+0x19/0x1b

Seems to be caused by the "gyration driver" whatever that is. Do you
have such a USB device?  

It could be some module mismatch, it looks suspicious
and from a quick look the gyration driver does nothing bad 
in that init path. Try a make clean and remove/rebuild/reinstall all the modules
on the target system.

If that doesn't help perhaps disable CONFIG_HID_GYRATION,
but from your other oops something more seems to be broken anyways.

> [    5.308739]  [<ffffffff81009048>] do_one_initcall+0x38/0x1a0
> [    5.308739]  [<ffffffff81a0e6b5>] kernel_init+0x172/0x1ca
> [    5.308739]  [<ffffffff81036a0a>] child_rip+0xa/0x20
> [    5.308739]  [<ffffffff81a0e543>] ? kernel_init+0x0/0x1ca
> [    5.308739]  [<ffffffff81036a00>] ? child_rip+0x0/0x20

-Andi

-- 
ak@linux.intel.com -- Speaking for myself only.

  parent reply	other threads:[~2009-12-22 12:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-15 16:27 2.6.32.1: BUG and panic: unable to handle kernel NULL pointer dereference at 000000000000001f Peter Palfrader
2009-12-22 11:47 ` Peter Palfrader
2009-12-22 12:04 ` Andi Kleen [this message]
2009-12-22 18:33   ` Peter Palfrader
2009-12-22 18:42     ` Andi Kleen
2009-12-22 19:01       ` Peter Palfrader
2009-12-22 18:57     ` Peter Palfrader
2009-12-24 13:04       ` Peter Palfrader
2009-12-26 17:12         ` Andi Kleen

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=871vindxkv.fsf@basil.nowhere.org \
    --to=andi@firstfloor.org \
    --cc=debian-admin@lists.debian.org \
    --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 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.