From: "BERTRAND Joël" <joel.bertrand@systella.fr>
To: sparclinux@vger.kernel.org
Subject: gcc 4.2 or kernel bug ?
Date: Fri, 08 Feb 2008 10:53:42 +0000 [thread overview]
Message-ID: <47AC34B6.4000302@systella.fr> (raw)
Hello,
On a U60 SMP running debian/testing, 2.6.24 kernel, I can seen in dmesg :
Mem-info:
Normal per-cpu:
CPU 0: Hot: hi: 90, btch: 15 usd: 56 Cold: hi: 30, btch: 7
usd: 23
CPU 2: Hot: hi: 90, btch: 15 usd: 0 Cold: hi: 30, btch: 7
usd: 0
Active:98801 inactive:19262 dirty:68 writeback:0 unstable:0
free:530 slab:3845 mapped:6871 pagetables:553 bounce:0
Normal free:4104kB min:4040kB low:5048kB high:6056kB active:790408kB
inactive:15
4096kB present:1023992kB pages_scanned:33 all_unreclaimable? no
lowmem_reserve[]: 0 0
Normal: 449*8kB 1*16kB 1*32kB 1*64kB 1*128kB 1*256kB 0*512kB 0*1024kB
0*2048kB 0
*4096kB 0*8192kB = 4088kB
Swap cache: add 150320, delete 132225, find 212550/233466, race 0+1
Free swap = 1682128kB
Total swap = 1951792kB
Free swap: 1682128kB
360340 pages of RAM
233704 reserved pages
41539 pages shared
18049 pages swap cached
68 pages dirty
0 pages writeback
6871 pages mapped
3845 pages slab
553 pages pagetables
swapper: page allocation failure. order:1, mode:0x4020
Call Trace:
[00000000004b67e0] __slab_alloc+0x248/0x660
[00000000004b8c00] __kmalloc_track_caller+0xe8/0x100
[0000000000634b20] __alloc_skb+0x48/0x100
[00000000005b662c] happy_meal_rx+0x114/0x420
[00000000005b7954] happy_meal_interrupt+0x7c/0xe0
[000000000048efcc] handle_IRQ_event+0x34/0xa0
[0000000000490a38] handle_fasteoi_irq+0xa0/0x140
[000000000042ef48] handler_irq+0x90/0xc0
[00000000004208b4] tl0_irq5+0x1c/0x20
[0000000000474108] __rcu_process_callbacks+0x90/0x280
[0000000000474318] rcu_process_callbacks+0x20/0x40
[00000000004667d4] tasklet_action+0x7c/0x160
[0000000000466054] __do_softirq+0xbc/0x100
[00000000004660fc] do_softirq+0x64/0x80
[0000000000432ae8] timer_interrupt+0x90/0x100
[00000000004209d4] tl0_irq14+0x1c/0x20
Running kernel was build with gcc 4.2. Can 2.6.24 kernel be built with
this release of gcc ?
Regards,
JKB
next reply other threads:[~2008-02-08 10:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 10:53 BERTRAND Joël [this message]
2008-02-08 11:05 ` gcc 4.2 or kernel bug ? BERTRAND Joël
2008-02-08 12:24 ` David Miller
2008-02-08 12:25 ` David Miller
2008-02-08 12:41 ` BERTRAND Joël
2008-02-09 11:49 ` BERTRAND Joël
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=47AC34B6.4000302@systella.fr \
--to=joel.bertrand@systella.fr \
--cc=sparclinux@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.