linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sedat Dilek <sedat.dilek@gmail.com>
To: Tony Luck <tony.luck@intel.com>
Cc: linux-next@vger.kernel.org, Christoph Lameter <cl@linux.com>,
	Pekka Enberg <penberg@kernel.org>
Subject: Re: ia64 dies in slab code on next-20120906
Date: Thu, 6 Sep 2012 21:39:29 +0200	[thread overview]
Message-ID: <CA+icZUU81KR1tM2-+qOYiQHRGASfOBvvMa_ZiCTT481Lbprg1Q@mail.gmail.com> (raw)
In-Reply-To: <CA+8MBbKmaaiEJ363E2PU-=6KJ4u+ZsQ1ywjb0nWMrp4xaSCeLw@mail.gmail.com>

On Thu, Sep 6, 2012 at 8:39 PM, Tony Luck <tony.luck@intel.com> wrote:
> Worked fine yesterday on next-20120905, crashes today. First sign of trouble
> was an unaligned access, then a NULL dereference. SL*B related bits of
> my config:
>
> CONFIG_SLUB_DEBUG=y
> # CONFIG_SLAB is not set
> CONFIG_SLUB=y
> CONFIG_SLABINFO=y
> # CONFIG_SLUB_DEBUG_ON is not set
> # CONFIG_SLUB_STATS is not set
>

I fell over the same issue, comparing the diff between next-20120905
and next-20120906 shows the culprit lies in the
"slab/common-for-cgroups" GIT branch.
That stuff was in "slab/next" and came to today's linux-next, but now removed.

I try with reverting all commits came with "slab/common-for-cgroups"
in next-20120906.

- Sedat -

[1] http://git.kernel.org/?p=linux/kernel/git/penberg/linux.git;a=shortlog;h=refs/heads/slab/common-for-cgroups
[2] http://git.kernel.org/?p=linux/kernel/git/penberg/linux.git;a=shortlog;h=refs/heads/slab/next

> And he console log.
>
> PID hash table entries: 4096 (order: 1, 32768 bytes)
> Dentry cache hash table entries: 262144 (order: 7, 2097152 bytes)
> Inode-cache hash table entries: 131072 (order: 6, 1048576 bytes)
> Memory: 2047920k/2086064k available (13992k code, 38144k reserved,
> 6012k data, 880k init)
> kernel unaligned access to 0xca2ffc55fb373e95, ip=0xa0000001001be550
> swapper[0]: error during unaligned kernel access
>  -1 [1]
> Modules linked in:
>
> Pid: 0, CPU 0, comm:              swapper
> psr : 00001010084a2018 ifs : 800000000000060f ip  :
> [<a0000001001be550>]    Not tainted (3.6.0-rc4-zx1-smp-next-20120906)
> ip is at new_slab+0x90/0x680
> unat: 0000000000000000 pfs : 000000000000060f rsc : 0000000000000003
> rnat: 9666960159966a59 bsps: a0000001001441c0 pr  : 9666960159965a59
> ldrs: 0000000000000000 ccv : 0000000000000000 fpsr: 0009804c8a70433f
> csd : 0000000000000000 ssd : 0000000000000000
> b0  : a0000001001be500 b6  : a00000010112cb20 b7  : a0000001011660a0
> f6  : 0fff7f0f0f0f0e54f0000 f7  : 0ffe8c5c1000000000000
> f8  : 1000d8000000000000000 f9  : 100068800000000000000
> f10 : 10005f0f0f0f0e54f0000 f11 : 1003e0000000000000078
> r1  : a00000010155eef0 r2  : 0000000000000000 r3  : fffffffffffc1638
> r8  : e0000040600081b8 r9  : ca2ffc55fb373e95 r10 : 0000000000000000
> r11 : e000004040001646 r12 : a000000101287e20 r13 : a000000101280000
> r14 : 0000000000004000 r15 : 0000000000000078 r16 : ca2ffc55fb373e75
> r17 : e000004040040000 r18 : fffffffffffc1646 r19 : e000004040001646
> r20 : fffffffffffc15f8 r21 : 000000000000004d r22 : a00000010132fa68
> r23 : 00000000000000ed r24 : 0000000000000000 r25 : 0000000000000000
> r26 : 0000000000000001 r27 : a0000001012b8500 r28 : a00000010135f4a0
> r29 : 0000000000000000 r30 : 0000000000000000 r31 : 0000000000000001
> Unable to handle kernel NULL pointer dereference (address 0000000000000018)
> swapper[0]: Oops 11003706212352 [2]
> Modules linked in:
>
> Pid: 0, CPU 0, comm:              swapper
> psr : 0000121008022018 ifs : 800000000000cc18 ip  :
> [<a0000001004dc8f1>]    Not tainted (3.6.0-rc4-zx1-smp-next-20120906)
> ip is at __copy_user+0x891/0x960
> unat: 0000000000000000 pfs : 0000000000000813 rsc : 0000000000000003
> rnat: 0000000000000000 bsps: 0000000000000000 pr  : 9666960159961765
> ldrs: 0000000000000000 ccv : 0000000000000000 fpsr: 0009804c0270033f
> csd : 0000000000000000 ssd : 0000000000000000
> b0  : a00000010004b550 b6  : a00000010004b740 b7  : a00000010000c750
> f6  : 000000000000000000000 f7  : 1003e9e3779b97f4a7c16
> f8  : 1003e0a00000010001550 f9  : 100068800000000000000
> f10 : 10005f0f0f0f0e54f0000 f11 : 1003e0000000000000078
> r1  : a00000010155eef0 r2  : a0000001012870b0 r3  : a0000001012870b8
> r8  : 0000000000000298 r9  : 0000000000000013 r10 : 0000000000000000
> r11 : 9666960159961a65 r12 : a000000101287010 r13 : a000000101280000
> r14 : a000000101287068 r15 : a000000101287080 r16 : 0000000000000298
> r17 : 0000000000000010 r18 : 0000000000000018 r19 : a000000101287310
> r20 : 0000000000000290 r21 : 0000000000000000 r22 : 0000000000000000
> r23 : a000000101386f58 r24 : 0000000000000000 r25 : 000000007fffffff
> r26 : a000000101287078 r27 : a0000001013c69b0 r28 : 0000000000000000
> r29 : 0000000000000014 r30 : 0000000000000000 r31 : 0000000000000813
> --
> To unsubscribe from this list: send the line "unsubscribe linux-next" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2012-09-06 19:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-06 18:39 ia64 dies in slab code on next-20120906 Tony Luck
2012-09-06 19:39 ` Sedat Dilek [this message]
2012-09-06 20:13   ` Sedat Dilek
2012-09-06 20:13 ` Christoph Lameter
2012-09-06 20:26   ` Luck, Tony
2012-09-06 20:33     ` Christoph Lameter
2012-09-06 20:45       ` Sedat Dilek
2012-09-06 21:00         ` Sedat Dilek
2012-09-07  8:13           ` Sedat Dilek
2012-09-06 23:41       ` Luck, Tony
2012-09-07  1:26 ` Stephen Rothwell
2012-09-08 18:27   ` Christoph Lameter
2012-09-08 21:34     ` Sedat Dilek
2012-09-08 22:27       ` Christoph Lameter
2012-09-09  6:44         ` Sedat Dilek
2012-09-10  3:24     ` Stephen Rothwell
2012-09-10  6:59       ` Pekka Enberg
2012-09-10  8:28         ` Sedat Dilek
2012-09-10 17:52     ` Luck, Tony

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=CA+icZUU81KR1tM2-+qOYiQHRGASfOBvvMa_ZiCTT481Lbprg1Q@mail.gmail.com \
    --to=sedat.dilek@gmail.com \
    --cc=cl@linux.com \
    --cc=linux-next@vger.kernel.org \
    --cc=penberg@kernel.org \
    --cc=tony.luck@intel.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 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).