All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Burgess <jburgess777@googlemail.com>
To: Gregoire Favre <Gregoire.Favre@gmail.com>, ak@suse.de
Cc: linux-dvb@linuxtv.org, v4l-dvb-maintainer@linuxtv.org,
	Markus Rechberger <mrechberger@gmail.com>,
	linux-kernel@vger.kernel.org, Lee Revell <rlrevell@joe-job.com>
Subject: Re: [PATCH] Re: More than 2Gb problem (dvb related) ?
Date: Tue, 01 May 2007 23:11:55 +0100	[thread overview]
Message-ID: <1178057515.25218.24.camel@localhost.localdomain> (raw)
In-Reply-To: <20070501094153.GC6895@gmail.com>

On Tue, 2007-05-01 at 11:41 +0200, Gregoire Favre wrote:
> Hello again,
> 
> just forgot this :
> 
> ksymoops 2.4.11 on x86_64 2.6.21.  Options used
>      -V (default)
>      -k /proc/ksyms (default)
>      -l /proc/modules (default)
>      -o /lib/modules/2.6.21/ (default)
>      -m /usr/src/linux/System.map (default)
> 
> Warning: You did not tell me where to find symbol information.  I will
> assume that the log matches the kernel and modules that are running
> right now and I'll use the default options above for symbol resolution.
> If the current kernel and/or modules do not match the log, you can get
> more accurate output by telling me the kernel version and where to find
> map, modules, ksyms etc.  ksymoops -h explains the options.
> 
> Error (regular_file): read_ksyms stat /proc/ksyms failed
> No modules in ksyms, skipping objects
> No ksyms, skipping lsmod
> SGI XFS with large block/inode numbers, no debug enabled
> ehci_hcd 0000:00:1a.7: debug port 1
> ehci_hcd 0000:00:1d.7: debug port 1
> kernel BUG at mm/slab.c:2736!
> CPU 1 
> Pid: 9445, comm: cx88[0] dvb Tainted: P       2.6.21 #1
> RIP: 0010:[<ffffffff8025e44e>]  [<ffffffff8025e44e>] cache_alloc_refill+0x1de/0x530
> Using defaults from ksymoops -t elf64-x86-64 -a i386:x86-64
> RSP: 0000:ffff81010ff31d30  EFLAGS: 00010002
> RAX: 0000000000000000 RBX: 000000000000003c RCX: 0000000000000000
> RDX: ffff81017fc6e400 RSI: 0000000000000004 RDI: ffff81017fc02180
> RBP: ffff81017fc6e400 R08: 00000000ffffffff R09: 0000000000000004
> R10: 0000000000000020 R11: 0000000000000001 R12: ffff81017fc02140
> R13: ffff81017fc002c0 R14: 0000000000000000 R15: ffff81017fc13000
> FS:  0000000000000000(0000) GS:ffff81017fc36540(0000) knlGS:0000000000000000
> CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
> CR2: 00007fff05c58de8 CR3: 0000000129142000 CR4: 00000000000006e0
> Stack:  0000000000000000 ffffffff805ea9b0 ffff81017fc02180 ffff810000000004
>  ffffc2000067bfff 0000000000000286 0000000000000030 ffff81015fb4cf80
>  0000000000006000 0000000000000004 ffff81017d4e90e0 ffffffff802bfaf3
> Call Trace:
>  [<ffffffff802bfaf3>] __kmalloc+0x63/0x70
>  [<ffffffff802b80be>] __vmalloc_area_node+0x6e/0x160
>  [<ffffffff887fc7c0>] :video_buf:videobuf_dma_init_kernel+0x50/0xd0
>  [<ffffffff887fcc8e>] :video_buf:videobuf_iolock+0x7e/0x100
>  [<ffffffff8883bfe4>] :cx8802:cx8802_buf_prepare+0xb4/0x120
>  [<ffffffff887fc034>] :video_buf:videobuf_read_start+0xb4/0x150
>  [<ffffffff888023e6>] :video_buf_dvb:videobuf_dvb_thread+0x46/0x170
>  [<ffffffff8029d6d0>] keventd_create_kthread+0x0/0x90
>  [<ffffffff888023a0>] :video_buf_dvb:videobuf_dvb_thread+0x0/0x170
>  [<ffffffff8029d6d0>] keventd_create_kthread+0x0/0x90
>  [<ffffffff802334f9>] kthread+0xd9/0x120
>  [<ffffffff802283bf>] schedule_tail+0x3f/0xb0
>  [<ffffffff802600e8>] child_rip+0xa/0x12
>  [<ffffffff8029d6d0>] keventd_create_kthread+0x0/0x90
>  [<ffffffff80233420>] kthread+0x0/0x120
>  [<ffffffff802600de>] child_rip+0x0/0x12
> Code: 0f 0b eb fe f7 44 24 18 00 20 00 00 0f 85 af 02 00 00 83 3c 
> 
> 
> >>RIP; ffffffff8025e44e <cache_alloc_refill+1de/530>   <=====
> 
> >>RDX; ffff81017fc6e400 <phys_startup_64+ffff81017fa6e300/ffffffff7fffff00>
> >>RDI; ffff81017fc02180 <phys_startup_64+ffff81017fa02080/ffffffff7fffff00>
> >>RBP; ffff81017fc6e400 <phys_startup_64+ffff81017fa6e300/ffffffff7fffff00>
> >>R08; 00000000ffffffff <phys_startup_64+ffdffeff/ffffffff7fffff00>
> >>R12; ffff81017fc02140 <phys_startup_64+ffff81017fa02040/ffffffff7fffff00>
> >>R13; ffff81017fc002c0 <phys_startup_64+ffff81017fa001c0/ffffffff7fffff00>
> >>R15; ffff81017fc13000 <phys_startup_64+ffff81017fa12f00/ffffffff7fffff00>
> 
> Trace; ffffffff802bfaf3 <__kmalloc+63/70>
> Trace; ffffffff802b80be <__vmalloc_area_node+6e/160>
> Trace; ffffffff887fc7c0 <_end+81646fc/7ef67f3c>
> Trace; ffffffff887fcc8e <_end+8164bca/7ef67f3c>
> Trace; ffffffff8883bfe4 <_end+81a3f20/7ef67f3c>
> Trace; ffffffff887fc034 <_end+8163f70/7ef67f3c>
> Trace; ffffffff888023e6 <_end+816a322/7ef67f3c>
> Trace; ffffffff8029d6d0 <keventd_create_kthread+0/90>
> Trace; ffffffff888023a0 <_end+816a2dc/7ef67f3c>
> Trace; ffffffff8029d6d0 <keventd_create_kthread+0/90>
> Trace; ffffffff802334f9 <kthread+d9/120>
> Trace; ffffffff802283bf <schedule_tail+3f/b0>
> Trace; ffffffff802600e8 <child_rip+a/12>
> Trace; ffffffff8029d6d0 <keventd_create_kthread+0/90>
> Trace; ffffffff80233420 <kthread+0/120>
> Trace; ffffffff802600de <child_rip+0/12>
> 
> Code;  ffffffff8025e44e <cache_alloc_refill+1de/530>
> 0000000000000000 <_RIP>:
> Code;  ffffffff8025e44e <cache_alloc_refill+1de/530>   <=====
>    0:   0f 0b                     ud2a      <=====
> Code;  ffffffff8025e450 <cache_alloc_refill+1e0/530>
>    2:   eb fe                     jmp    2 <_RIP+0x2>
> Code;  ffffffff8025e452 <cache_alloc_refill+1e2/530>
>    4:   f7 44 24 18 00 20 00      testl  $0x2000,0x18(%rsp)
> Code;  ffffffff8025e459 <cache_alloc_refill+1e9/530>
>    b:   00 
> Code;  ffffffff8025e45a <cache_alloc_refill+1ea/530>
>    c:   0f 85 af 02 00 00         jne    2c1 <_RIP+0x2c1>
> Code;  ffffffff8025e460 <cache_alloc_refill+1f0/530>
>   12:   83 3c 00 00               cmpl   $0x0,(%rax,%rax,1)
> 
> 
> 1 warning and 1 error issued.  Results may not be reliable.


Looks like you hit:
	BUG_ON(flags & ~(GFP_DMA | GFP_LEVEL_MASK | __GFP_NO_GROW));

I guess this was due to the vmalloc_32() change now passing in
GFP_DMA32. Looks like that could be a problem with the
x86_64-mm-vmalloc-32 patch. Andi?

	Jon



  reply	other threads:[~2007-05-01 22:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-27 11:10 More than 2Gb problem (dvb related) ? Gregoire Favre
2007-04-27 20:46 ` Markus Rechberger
2007-04-27 21:03   ` Gregoire Favre
2007-04-27 22:00   ` [linux-dvb] " Jon Burgess
2007-04-27 22:06     ` Lee Revell
2007-04-27 22:37       ` Jon Burgess
2007-04-28 17:17       ` [PATCH] " Jon Burgess
2007-04-28 20:14         ` Jon Burgess
2007-04-29 14:07           ` Gregoire Favre
2007-04-30  0:22           ` [linux-dvb] " Oliver Endriss
2007-04-30 16:52           ` Gregoire Favre
2007-04-30 18:05             ` Jon Burgess
2007-05-01  9:39               ` Gregoire Favre
2007-05-01  9:41               ` Gregoire Favre
2007-05-01 22:11                 ` Jon Burgess [this message]
2007-05-02  9:35                   ` Andi Kleen
2007-05-02 12:17                     ` Gregoire Favre
2007-05-05  7:36                     ` Gregoire Favre
2007-05-01 15:58         ` [linux-dvb] " Oliver Endriss
2007-05-01 20:03           ` Gregoire Favre

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=1178057515.25218.24.camel@localhost.localdomain \
    --to=jburgess777@googlemail.com \
    --cc=Gregoire.Favre@gmail.com \
    --cc=ak@suse.de \
    --cc=linux-dvb@linuxtv.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mrechberger@gmail.com \
    --cc=rlrevell@joe-job.com \
    --cc=v4l-dvb-maintainer@linuxtv.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.