From: Robert Love <rml@tech9.net>
To: Helge Hafting <helge.hafting@broadpark.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Some backtraces (2.5.40-bk4 smp+preempt)
Date: 05 Oct 2002 16:02:25 -0400 [thread overview]
Message-ID: <1033848146.11402.4066.camel@phantasy> (raw)
In-Reply-To: <3D9F4A8A.190A6B5F@broadpark.no>
On Sat, 2002-10-05 at 16:24, Helge Hafting wrote:
Thanks for the report...
> bad: scheduling while atomic!
> Call Trace:
> [<c0117351>] schedule+0x3d/0x4f4
> [<c0117bfd>] wait_for_completion+0x111/0x1c4
> [<c011784c>] default_wake_function+0x0/0x34
> [<c011784c>] default_wake_function+0x0/0x34
> [<c0119563>] set_cpus_allowed+0x217/0x240
> [<c01195dc>] migration_thread+0x50/0x53c
> [<c011958c>] migration_thread+0x0/0x53c
> [<c0105591>] kernel_thread_helper+0x5/0xc
Known. Not a problem but needs to be fixed. set_cpus_allowed() sleeps
with preemption disabled.
> bad: scheduling while atomic!
> Call Trace: [<c0117351>] schedule+0x3d/0x4f4
> [<c0117bfd>] wait_for_completion+0x111/0x1c4
> [<c011784c>] default_wake_function+0x0/0x34
> [<c011784c>] default_wake_function+0x0/0x34
> [<c0119563>] set_cpus_allowed+0x217/0x240
> [<c0120c45>] ksoftirqd+0x51/0xe0
> [<c0120bf4>] ksoftirqd+0x0/0xe0
> [<c0105591>] kernel_thread_helper+0x5/0xc
Same thing.
> bad: scheduling while atomic!
> Call Trace:
> [<c0117351>] schedule+0x3d/0x4f4
> [<c0117bfd>] wait_for_completion+0x111/0x1c4
> [<c011784c>] default_wake_function+0x0/0x34
> [<c011784c>] default_wake_function+0x0/0x34
> [<c0119563>] set_cpus_allowed+0x217/0x240
> [<c012a7b6>] worker_thread+0x9e/0x4ac
> [<c012a718>] worker_thread+0x0/0x4ac
> [<c0107521>] ret_from_fork+0x5/0x14
> [<c011784c>] default_wake_function+0x0/0x34
> [<c011784c>] default_wake_function+0x0/0x34
> [<c0105591>] kernel_thread_helper+0x5/0xc
Same.
> mtrr: v2.0 (20020519)
> mtrr: your CPUs had inconsistent fixed MTRR settings
> mtrr: probably your BIOS does not setup all CPUs
This is really an annoying "message". Nearly every machine I see prints
this. Can we just get rid of this?
> bad: scheduling while atomic!
> Call Trace:
> [<c0117351>] schedule+0x3d/0x4f4
> [<c0117bfd>] wait_for_completion+0x111/0x1c4
> [<c011784c>] default_wake_function+0x0/0x34
> [<c011784c>] default_wake_function+0x0/0x34
> [<c0119563>] set_cpus_allowed+0x217/0x240
> [<c012a7b6>] worker_thread+0x9e/0x4ac
> [<c012a718>] worker_thread+0x0/0x4ac
> [<c0107521>] ret_from_fork+0x5/0x14
> [<c011784c>] default_wake_function+0x0/0x34
> [<c011784c>] default_wake_function+0x0/0x34
> [<c0105591>] kernel_thread_helper+0x5/0xc
Same.
> Debug: sleeping function called from illegal context at
> /usr/src/linux/include/a
> sm/semaphore.h:119
> Call Trace:
> [<c0119b84>] __might_sleep+0x54/0x58
> [<c02ac327>] snd_trident_alloc_pages+0x4b/0xdc
> [<c02a7969>] snd_trident_playback_hw_params+0xc5/0x190
> [<c0280d12>] snd_pcm_hw_params+0xca/0x294
> [<c0280f47>] snd_pcm_hw_params_user+0x6b/0xb4
> [<c0284dc8>] snd_pcm_common_ioctl1+0x15c/0x2bc
> [<c0285346>] snd_pcm_playback_ioctl1+0x41e/0x42c
> [<c02856ef>] snd_pcm_kernel_playback_ioctl+0x27/0x30
> [<c028574b>] snd_pcm_kernel_ioctl+0x23/0x40
> [<c0277cf9>] snd_pcm_oss_change_params+0x429/0x66c
> [<c02476d6>] sym_queue_scsiio+0x1fa/0x204
> [<c0243ddf>] sym_start_next_ccbs+0xd7/0x10c
> [<c0277f6e>] snd_pcm_oss_get_active_substream+0x32/0x50
> [<c02789cc>] snd_pcm_oss_get_block_size+0x10/0x28
> [<c0279d56>] snd_pcm_oss_ioctl+0x38a/0x768
> [<c015b2bb>] sys_ioctl+0x27f/0x2fb
> [<c01075c3>] syscall_call+0x7/0xb
I believe this is known, too.
Thank you,
Robert Love
prev parent reply other threads:[~2002-10-05 19:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-05 20:24 Helge Hafting
2002-10-05 20:02 ` Robert Love [this message]
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=1033848146.11402.4066.camel@phantasy \
--to=rml@tech9.net \
--cc=helge.hafting@broadpark.no \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®