public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: khromy@lnuxlab.ath.cx (khromy)
To: linux-kernel@vger.kernel.org
Subject: 2.5.53-mm3: bad: scheduling while atomic!
Date: Sun, 29 Dec 2002 15:41:36 -0500	[thread overview]
Message-ID: <20021229204136.GA24616@lnuxlab.ath.cx> (raw)

Running 2.5.53-mm3, I got the following:

bad: scheduling while atomic!
Call Trace:
 [<c0114381>] do_schedule+0x3d/0x2c8
 [<c011d9b0>] schedule_timeout+0x80/0xa0
 [<c011d924>] process_timeout+0x0/0xc
 [<c0115315>] io_schedule_timeout+0x11/0x1c
 [<c01de5de>] blk_congestion_wait+0x8a/0xa0
 [<c0115a54>] autoremove_wake_function+0x0/0x38
 [<c0115a54>] autoremove_wake_function+0x0/0x38
 [<c012fbb4>] try_to_free_pages+0x3c/0xbc
 [<c012a33c>] __alloc_pages+0x1b4/0x260
 [<c012a410>] __get_free_pages+0x28/0x64
 [<c012c7e6>] cache_grow+0xb6/0x20c
 [<c012c9cf>] __cache_alloc_refill+0x93/0x220
 [<c012cb96>] cache_alloc_refill+0x3a/0x58
 [<c012cf1d>] kmem_cache_alloc+0x45/0xc8
 [<c0136460>] pte_chain_alloc+0x38/0x68
 [<c0130eea>] copy_page_range+0x2be/0x3f0
 [<c0115f8b>] copy_mm+0x283/0x348
 [<c0116a4f>] copy_process+0x61b/0xb24
 [<c0116fd6>] do_fork+0x7e/0x134
 [<c0107478>] sys_fork+0x18/0x2c
 [<c01089af>] syscall_call+0x7/0xb

dpkg: page allocation failure. order:0, mode:0x20
dpkg: page allocation failure. order:0, mode:0x20
xmms: page allocation failure. order:5, mode:0x20
xmms: page allocation failure. order:4, mode:0x20
xmms: page allocation failure. order:3, mode:0x20

-- 
L1:	khromy		;khromy(at)lnuxlab.ath.cx

             reply	other threads:[~2002-12-29 20:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-29 20:41 khromy [this message]
2002-12-29 20:49 ` 2.5.53-mm3: bad: scheduling while atomic! khromy
2002-12-30  5:41 ` Andrew Morton

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=20021229204136.GA24616@lnuxlab.ath.cx \
    --to=khromy@lnuxlab.ath.cx \
    --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