From: "Chris Down" <chris@alcor.co.uk>
To: "'Joakim Tjernlund'" <joakim.tjernlund@transmode.se>,
<linuxppc-embedded@ozlabs.org>
Subject: RE: Badness in 2.6.15-rc1 on 8xx
Date: Mon, 28 Nov 2005 10:01:09 -0000 [thread overview]
Message-ID: <003301c5f402$a81a3950$0101a8c0@sirius> (raw)
In-Reply-To: <F6AD7E21CDF4E145A44F61F43EE6D9393FE122@tmnt04.transmode.se>
From: linuxppc-embedded-bounces@ozlabs.org
[mailto:linuxppc-embedded-bounces@ozlabs.org] On Behalf Of Joakim Tjernlund
Sent: 25 November 2005 13:28
To: linuxppc-embedded@ozlabs.org
Subject: Badness in 2.6.15-rc1 on 8xx
Anyone seen this when booting 2.6.15-rc1 on 8xx?
Mount-cache hash table entries: 512
Badness in dma_alloc_init at arch/ppc/kernel/dma-mapping.c:346
Call trace:
[c00039e8] check_bug_trap+0x80/0xa8
[c0003c1c] program_check_exception+0x20c/0x480
[c00031e0] ret_from_except_full+0x0/0x4c
[c01b86b8] dma_alloc_init+0x40/0xcc
[c000225c] init+0x8c/0x288
[c00050ac] kernel_thread+0x44/0x60
NET: Registered protocol family 16
The kernel boots just fine into user space so it seems harmless, but I
suspect it will bite me later.
I am currently working with 2.6.15-rc1 on MPC852 and I am seeing a similar
problem.
Badness in dma_alloc_init at arch/ppc/kernel/dma-mapping.c:346
Call trace:
[c00036f8] check_bug_trap+0xa4/0xb8
[c0003f9c] program_check_exception+0x2f0/0x4c4
[c0003320] ret_from_except_full+0x0/0x4c
[c024c530] dma_alloc_init+0x3c/0xbc
[c0002280] init+0xbc/0x25c
[c000538c] kernel_thread+0x44/0x60
Have not had time to look at it yet, however I was not getting this on
2.6.11.
Chris
next prev parent reply other threads:[~2005-11-28 10:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-25 13:28 Badness in 2.6.15-rc1 on 8xx Joakim Tjernlund
2005-11-28 10:01 ` Chris Down [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-25 14:21 Demke Torsten-atd012
2005-11-25 21:41 Joakim Tjernlund
2005-11-28 10:08 ` Ingo Hornberger
2005-11-28 10:57 ` Ingo Hornberger
2005-11-28 10:52 Joakim Tjernlund
2005-11-28 11:33 ` Chris Down
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='003301c5f402$a81a3950$0101a8c0@sirius' \
--to=chris@alcor.co.uk \
--cc=joakim.tjernlund@transmode.se \
--cc=linuxppc-embedded@ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox