From: Karol Kozimor <sziwan@hell.org.pl>
To: linux-kernel@vger.kernel.org
Cc: linux-xfs@oss.sgi.com
Subject: Re: 2.6.2-rc1-mm2
Date: Sat, 24 Jan 2004 01:51:44 +0100 [thread overview]
Message-ID: <20040124005144.GA30881@hell.org.pl> (raw)
In-Reply-To: <1h670-8J-5@gated-at.bofh.it>
Thus wrote Andrew Morton:
> - There is a new debug check in here which drops a stack trace when a piece
> of code calls one of the sleep_on() functions without lock_kernel() held.
> This is almost certainly a bug. Please try to identify (from the trace)
> which subsystem is the culprit and copy its maintainer when reporting such
> traces.
#v+
Linux version 2.6.2-rc1-mm2 (sziwan@nadir) (gcc version 3.3.2) #11 Fri Jan 23 22:45:18 CET 2004
[...]
Badness in interruptible_sleep_on at kernel/sched.c:2230
Call Trace:
[<c011aa82>] interruptible_sleep_on+0xd1/0xd6
[<c011a784>] default_wake_function+0x0/0x12
[<c01df0b1>] pagebuf_daemon+0x0/0x230
[<c01df2c6>] pagebuf_daemon+0x215/0x230
[<c01df087>] pagebuf_daemon_wakeup+0x0/0x2a
[<c01df0b1>] pagebuf_daemon+0x0/0x230
[<c0109255>] kernel_thread_helper+0x5/0xb
[...]
XFS mounting filesystem hda5
Badness in interruptible_sleep_on at kernel/sched.c:2230
Call Trace:
[<c011aa82>] interruptible_sleep_on+0xd1/0xd6
[<c011a784>] default_wake_function+0x0/0x12
[<c01df2c6>] pagebuf_daemon+0x215/0x230
[<c01df087>] pagebuf_daemon_wakeup+0x0/0x2a
[<c01df0b1>] pagebuf_daemon+0x0/0x230
[<c0109255>] kernel_thread_helper+0x5/0xb
Ending clean XFS mount for filesystem: hda5
#v-
[there was more of that, omitted]
Best regards,
--
Karol 'sziwan' Kozimor
sziwan@hell.org.pl
next parent reply other threads:[~2004-01-24 0:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1h670-8J-5@gated-at.bofh.it>
2004-01-24 0:51 ` Karol Kozimor [this message]
2004-01-23 15:08 2.6.2-rc1-mm2 Jan Ischebeck
2004-01-23 18:39 ` 2.6.2-rc1-mm2 Andrew Morton
2004-01-23 19:15 ` 2.6.2-rc1-mm2 Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2004-01-23 9:37 2.6.2-rc1-mm2 Andrew Morton
2004-01-23 9:37 ` 2.6.2-rc1-mm2 Andrew Morton
2004-01-23 13:30 ` 2.6.2-rc1-mm2 Thomas Schlichter
2004-01-23 17:59 ` 2.6.2-rc1-mm2 john stultz
2004-01-23 17:59 ` 2.6.2-rc1-mm2 john stultz
2004-01-23 15:12 ` 2.6.2-rc1-mm2 Ed Tomlinson
2004-01-23 15:12 ` 2.6.2-rc1-mm2 Ed Tomlinson
2004-01-23 18:43 ` 2.6.2-rc1-mm2 Andrew Morton
2004-01-23 18:43 ` 2.6.2-rc1-mm2 Andrew Morton
2004-01-24 0:46 ` 2.6.2-rc1-mm2 Ed Tomlinson
2004-01-24 0:46 ` 2.6.2-rc1-mm2 Ed Tomlinson
2004-01-23 23:29 ` 2.6.2-rc1-mm2 J.A. Magallon
2004-01-24 6:59 ` 2.6.2-rc1-mm2 Greg KH
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=20040124005144.GA30881@hell.org.pl \
--to=sziwan@hell.org.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
/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.