From: Adrian Bunk <bunk@fs.tum.de>
To: Andrew Morton <akpm@osdl.org>, David Woodhouse <dwmw2@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.3-mm4
Date: Sat, 28 Feb 2004 00:51:18 +0100 [thread overview]
Message-ID: <20040227235118.GF5499@fs.tum.de> (raw)
In-Reply-To: <20040225185536.57b56716.akpm@osdl.org>
On Wed, Feb 25, 2004 at 06:55:36PM -0800, Andrew Morton wrote:
>...
> All 267 patches:
>...
> sleep_on-needs_lock_kernel.patch
> sleep_on(): check for lock_kernel
>...
FYI:
This gives the following on my computer:
<-- snip -->
Feb 27 22:47:37 r063144 kernel: lp0 off-line
Feb 27 22:47:37 r063144 kernel: Badness in interruptible_sleep_on_timeout at kernel/sched.c:2271
Feb 27 22:47:37 r063144 kernel: Call Trace:
Feb 27 22:47:37 r063144 kernel: [interruptible_sleep_on_timeout+271/288] interruptible_sleep_on_timeout+0x10f/0x120
Feb 27 22:47:37 r063144 kernel: [default_wake_function+0/16] default_wake_function+0x0/0x10
Feb 27 22:47:37 r063144 kernel: [parport_release+160/341] parport_release+0xa0/0x155
Feb 27 22:47:37 r063144 kernel: [printk+285/368] printk+0x11d/0x170
Feb 27 22:47:37 r063144 kernel: [lp_error+61/176] lp_error+0x3d/0xb0
Feb 27 22:47:37 r063144 kernel: [lp_check_status+134/208] lp_check_status+0x86/0xd0
Feb 27 22:47:37 r063144 kernel: [lp_wait_ready+71/128] lp_wait_ready+0x47/0x80
Feb 27 22:47:37 r063144 kernel: [lp_write+292/912] lp_write+0x124/0x390
Feb 27 22:47:37 r063144 kernel: [vfs_write+176/256] vfs_write+0xb0/0x100
Feb 27 22:47:37 r063144 kernel: [sys_write+56/96] sys_write+0x38/0x60
Feb 27 22:47:37 r063144 kernel: [syscall_call+7/11] syscall_call+0x7/0xb
Feb 27 22:47:37 r063144 kernel:
Feb 27 22:47:47 r063144 kernel: Badness in interruptible_sleep_on_timeout at kernel/sched.c:2271
<-- snip -->
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2004-02-27 23:51 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-26 2:55 2.6.3-mm4 Andrew Morton
2004-02-26 8:22 ` 2.6.3-mm4 Alexander Hoogerhuis
2004-02-26 8:48 ` 2.6.3-mm4 Marc-Christian Petersen
2004-02-26 8:51 ` 2.6.3-mm4 Nuno Silva
2004-02-27 0:48 ` 2.6.3-mm4 Greg KH
2004-02-26 15:50 ` 2.6.3-mm4 David Martínez Moreno
2004-02-26 15:59 ` 2.6.3-mm4 Christoph Hellwig
2004-02-26 16:30 ` 2.6.3-mm4 (compile stats) John Cherry
2004-02-26 18:59 ` Mike Fedyk
2004-02-26 19:26 ` John Cherry
2004-02-26 18:50 ` 2.6.3-mm4 Matthias Hentges
2004-02-26 23:35 ` 2.6.3-mm4, sensors broken Prakash K. Cheemplavam
2004-02-27 0:03 ` Andrew Morton
2004-02-27 8:58 ` Prakash K. Cheemplavam
2004-02-27 0:11 ` 2.6.3-mm4 J.A. Magallon
2004-02-27 0:46 ` 2.6.3-mm4 Greg KH
2005-05-19 6:24 ` 2.6.3-mm4 Greg KH
2004-02-27 8:35 ` 2.6.3-mm4 Jean Delvare
2005-05-19 6:24 ` 2.6.3-mm4 Jean Delvare
2004-02-27 18:16 ` 2.6.3-mm4 Mike Fedyk
2005-05-19 6:24 ` 2.6.3-mm4 Mike Fedyk
2004-02-27 19:59 ` 2.6.3-mm4 Jean Delvare
2005-05-19 6:24 ` 2.6.3-mm4 Jean Delvare
2004-02-29 7:51 ` 2.6.3-mm4 Mike Fedyk
2005-05-19 6:24 ` 2.6.3-mm4 Mike Fedyk
2004-02-29 10:11 ` 2.6.3-mm4 Jean Delvare
2005-05-19 6:24 ` 2.6.3-mm4 Jean Delvare
2004-02-27 16:48 ` 2.6.3-mm4 Prakash K. Cheemplavam
2005-05-19 6:24 ` 2.6.3-mm4 Prakash K. Cheemplavam
2004-02-27 9:00 ` 2.6.3-mm4 Prakash K. Cheemplavam
2004-02-27 23:51 ` Adrian Bunk [this message]
2004-03-01 8:25 ` MM VM patches was: 2.6.3-mm4 Mike Fedyk
2004-03-01 8:44 ` Nick Piggin
2004-03-01 9:05 ` Mike Fedyk
2004-03-01 9:27 ` Nick Piggin
2004-03-01 9:47 ` Mike Fedyk
2004-03-01 9:10 ` Nick Piggin
2004-03-01 9:52 ` [PATCH] 2.6.4-rc1-mm1: vm-kswapd-incremental-min (was Re: MM VM patches was: 2.6.3-mm4) Nick Piggin
2004-03-01 10:18 ` Andrew Morton
2004-03-01 10:29 ` Nick Piggin
[not found] <A6974D8E5F98D511BB910002A50A6647615F33F5@hdsmsx402.hd.intel.com>
2004-02-26 22:40 ` 2.6.3-mm4 Len Brown
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=20040227235118.GF5499@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=akpm@osdl.org \
--cc=dwmw2@infradead.org \
--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 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.