From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Shuah Khan <shuahkhan@gmail.com>,
Ming Lei <ming.lei@canonical.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Shuah Khan <shuahkh@osg.samsung.com>
Subject: Re: Linux 4.2-rc1
Date: Wed, 8 Jul 2015 21:00:30 +0200 [thread overview]
Message-ID: <20150708190030.GA26346@gmail.com> (raw)
In-Reply-To: <CA+55aFy-iZ2g8xKZW---LgUHaVMbqLZ_oadw=Vbg0g78dfH9PA@mail.gmail.com>
* Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Wed, Jul 8, 2015 at 9:32 AM, Shuah Khan <shuahkhan@gmail.com> wrote:
> >
> > I am seeing the following NULL pointer dereference on my test system:
> >
> > [ 3.640599] BUG: unable to handle kernel NULL pointer dereference at 0000000000000080
> > [ 3.640609] IP: [<ffffffff814f1463>] firmware_uevent+0x23/0x80
>
> Decoding the "Code:" line shows that this is the "->fw_id" dereference in
>
> if (add_uevent_var(env, "FIRMWARE=%s", fw_priv->buf->fw_id))
> return -ENOMEM;
>
> and that "fw_priv->buf" pointer is NULL.
>
> However, I don't see anything that looks like it should have changed
> any of this since 4.1.
>
> Adding the appropriate firmware people to the cc.
Btw., FWIW, a couple of days ago I started seeing a similar crash pattern when I
updated my randconfig testing system to v4.2-rc1:
cfg80211: Kicking the queue
cfg80211: Exceeded CRDA call max attempts. Not calling CRDA
BUG: unable to handle kernel NULL pointer dereference at 0000000000000080
IP: [<ffffffff81b5e978>] firmware_uevent+0x1a/0xae
PGD 0
Oops: 0000 [#1] SMP
CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.2.0-rc1-01514-g4a704ed-dirty #411
Hardware name: System manufacturer System Product Name/A8N-E, BIOS ASUS A8N-E ACPI BIOS Revision 1008 08/22/2005
task: ffff88003d4f0000 ti: ffff88003d4f8000 task.ti: ffff88003d4f8000
RIP: 0010:[<ffffffff81b5e978>] [<ffffffff81b5e978>] firmware_uevent+0x1a/0xae
RSP: 0018:ffff88003d4fba38 EFLAGS: 00010202
RAX: 0000000000000000 RBX: ffff88003ac05668 RCX: 0000000000000003
RDX: 0000000000000001 RSI: ffffffff83822d1a RDI: ffff88003ac05668
RBP: ffff88003ae68008 R08: 000000003ac057f4 R09: 000000010013ffff
R10: ffffffffffffffff R11: ffffffff84f831e0 R12: ffff88003ae68018
R13: 0000000000000000 R14: 0000000000000000 R15: ffffffff838947a7
FS: 0000000000000000(0000) GS:ffff88003fd00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000000000000080 CR3: 0000000003a50000 CR4: 00000000000006a0
Stack:
0000000000000003 ffff88003ac05668 ffff88003ae68008 ffffffff81b4a0fa
ffff88003d50e1a8 00000000fffffffe ffffffff838947a7 0000000000000002
000000003ac057e1 ffff88003ac05668 ffff88003ae68018 ffffffff831606f0
Call Trace:
[<ffffffff81b4a0fa>] ? dev_uevent+0x284/0x312
[<ffffffff81721d70>] ? kobject_uevent_env+0x304/0x54b
[<ffffffff810efa3d>] ? do_raw_spin_lock+0x30/0x5e
[<ffffffff81b49cc2>] ? device_del+0x287/0x2c5
[<ffffffff81b5fdda>] ? _request_firmware+0x71b/0xca2
[<ffffffff8197a961>] ? r100_cp_init+0x254/0x692
[<ffffffff8197ef71>] ? r300_startup.constprop.0+0x2da/0x36b
[<ffffffff8197f534>] ? r300_init+0x2e9/0x3a9
[<ffffffff8193a451>] ? radeon_device_init+0xbf1/0xe95
[<ffffffff8193cf1c>] ? radeon_driver_load_kms+0x10f/0x24c
[<ffffffff818e83fc>] ? drm_dev_register+0xec/0x19b
[<ffffffff818eae62>] ? drm_get_pci_dev+0x1d0/0x2d2
[<ffffffff81764fc7>] ? local_pci_probe+0x34/0xa2
[<ffffffff81765b4e>] ? pci_device_probe+0x131/0x187
[<ffffffff81b4e21a>] ? driver_probe_device+0x160/0x3a8
[<ffffffff81b4e500>] ? __driver_attach+0x9e/0xd4
[<ffffffff81b4e462>] ? driver_probe_device+0x3a8/0x3a8
[<ffffffff81b4c326>] ? bus_for_each_dev+0x89/0x9b
[<ffffffff81b4cdc9>] ? bus_add_driver+0x151/0x2ee
[<ffffffff81b4f24d>] ? driver_register+0xe8/0x147
[<ffffffff84e32e71>] ? r128_init+0x1f/0x1f
[<ffffffff84dc54f5>] ? do_one_initcall+0x11e/0x25b
[<ffffffff810cc1af>] ? parse_args+0x327/0x414
[<ffffffff84dc574c>] ? kernel_init_freeable+0x11a/0x1dc
[<ffffffff84dc4994>] ? initcall_blacklist+0xc1/0xc1
[<ffffffff82e90a01>] ? rest_init+0x75/0x75
[<ffffffff82e90a07>] ? kernel_init+0x6/0x14c
[<ffffffff82ecd1df>] ? ret_from_fork+0x3f/0x70
[<ffffffff82e90a01>] ? rest_init+0x75/0x75
Code: c7 c6 3d 7f 80 83 31 c0 e8 f3 c8 bc ff 5a 48 98 c3 55 48 89 fd 53 48 89 f3 48 c7 c6 1a 2d 82 83 51 48 8b 87 90 02 00 00 48 89 df <48> 8b 90 80 00 00 00 31 c0 e8 c9 2f bc ff 85 c0 0f 95 c0 0f b6
RIP [<ffffffff81b5e978>] firmware_uevent+0x1a/0xae
RSP <ffff88003d4fba38>
CR2: 0000000000000080
---[ end trace 3ab09bb9b953b39a ]---
Haven't had the time to dig into it yet.
Thanks,
Ingo
prev parent reply other threads:[~2015-07-08 19:00 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-05 20:22 Linux 4.2-rc1 Linus Torvalds
2015-07-05 23:01 ` Guenter Roeck
2015-07-07 5:50 ` linux-next: stats (Was: Linux 4.2-rc1) Stephen Rothwell
2015-07-07 5:50 ` Stephen Rothwell
2015-07-07 12:56 ` Build failure on ARM64 for Linux 4.2-rc1 was: Linux 4.2-rc1 Mark Langsdorf
2015-07-09 16:46 ` Mark Langsdorf
2015-07-09 16:46 ` Mark Langsdorf
2015-07-09 16:59 ` Peter Zijlstra
2015-07-09 16:59 ` Peter Zijlstra
2015-07-13 16:55 ` Mark Langsdorf
2015-07-13 16:55 ` Mark Langsdorf
2015-07-08 16:32 ` Shuah Khan
2015-07-08 17:05 ` Casey Schaufler
2015-07-08 17:33 ` Shuah Khan
2015-07-08 17:55 ` Casey Schaufler
2015-07-08 17:55 ` Casey Schaufler
2015-07-08 17:17 ` Linus Torvalds
2015-07-08 17:29 ` Linus Torvalds
2015-07-08 17:47 ` Casey Schaufler
2015-07-08 18:03 ` Stephen Smalley
2015-07-08 18:07 ` William Roberts
2015-07-08 18:45 ` Casey Schaufler
2015-07-09 0:58 ` Ming Lei
2015-07-09 3:17 ` Linus Torvalds
2015-07-09 5:00 ` Ming Lei
2015-07-09 13:10 ` Shuah Khan
2015-07-09 13:44 ` Shuah Khan
2015-07-09 13:47 ` Shuah Khan
2015-07-09 14:45 ` Greg Kroah-Hartman
2015-07-09 17:40 ` Shuah Khan
2015-07-10 16:58 ` Shuah Khan
2015-07-10 17:11 ` Linus Torvalds
[not found] ` <55A03A33.8060405@osg.samsung.com>
[not found] ` <CA+55aFzDu9acMKHJFkxzg+1jeHNpGRhmM=pu2z-so5QYTMbvcA@mail.gmail.com>
2015-07-10 21:57 ` Shuah Khan
2015-07-10 22:36 ` Ming Lei
2015-07-08 19:00 ` Ingo Molnar [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=20150708190030.GA26346@gmail.com \
--to=mingo@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@canonical.com \
--cc=shuahkh@osg.samsung.com \
--cc=shuahkhan@gmail.com \
--cc=torvalds@linux-foundation.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.