From: "Rune Torgersen" <runet@innovsys.com>
To: <linuxppc-dev@ozlabs.org>
Subject: RE: sched while atomic
Date: Wed, 16 Feb 2005 14:13:40 -0600 [thread overview]
Message-ID: <DCEAAC0833DD314AB0B58112AD99B93B8592B9@ismail.innsys.innovsys.com> (raw)
2.6.11rc2 and rc4 gives roughly the same message on an MPC8266
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
scheduling while atomic: swapper/0x00000002/0
Call trace:
[c0006c30] dump_stack+0x18/0x28
[c01ba970] schedule+0x670/0x674
[c0003f20] syscall_exit_work+0x108/0x10c
[c0244fc4] proc_root_init+0x144/0x150
[00000000] 0x0
[c023a5fc] start_kernel+0x138/0x164
[000035fc] 0x35fc
NET: Registered protocol family 16
Kernel boots normally after this, and everything seems to work
> -----Original Message-----
> From: linuxppc-dev-bounces@ozlabs.org=20
> [mailto:linuxppc-dev-bounces@ozlabs.org] On Behalf Of=20
> danny@mailmij.org
> Sent: Thursday, February 03, 2005 17:15
> To: linuxppc-dev@ozlabs.org
> Subject: sched while atomic
>=20
>=20
> Latest 2.6.11rc* give me this interesting message at boot:
> Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
> scheduling while atomic: swapper/0x00000002/0
> Call trace:
> [c01c7580] schedule+0x640/0x6bc
> [c0004698] syscall_exit_work+0x120/0x124
> [c00a5414] proc_device_tree_init+0x7c/0x98
> [c02be9b4] proc_root_init+0x14c/0x158
> [c02a660c] start_kernel+0x178/0x1b0
> [00003a5c] 0x3a5c
>=20
> Since it doesn't happen on x86, I first thought it was=20
> because of the ppc=20
> specific init of the device_tree, but commenting this out=20
> just lets it=20
> happen somewhere else. It seems schedule is called when it=20
> returns from a=20
> syscall, which seems normal behaviour to me, but the recent=20
> preempt_disable() in start_kernel makes the scheduler give=20
> these warnings.
> So what's happening?=20
>=20
> Also, I think this is already know for a while:
> /lib/modules/2.6.11-rc3/kernel/drivers/video/vga16fb.ko needs unknown=20
> symbol vgacon_remap_base
>=20
> regards,
>=20
> danny
>=20
>=20
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
>=20
>=20
next reply other threads:[~2005-02-16 20:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-16 20:13 Rune Torgersen [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-03 23:14 sched while atomic danny
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=DCEAAC0833DD314AB0B58112AD99B93B8592B9@ismail.innsys.innovsys.com \
--to=runet@innovsys.com \
--cc=linuxppc-dev@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