From: Con Kolivas <kernel@kolivas.org>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.61-mm1
Date: Sun, 16 Feb 2003 12:03:31 +1100 [thread overview]
Message-ID: <200302161203.31899.kernel@kolivas.org> (raw)
In-Reply-To: <20030215154154.1fcb9737.akpm@digeo.com>
On Sun, 16 Feb 2003 10:41 am, Andrew Morton wrote:
> Con Kolivas <kernel@kolivas.org> wrote:
> > I'm getting the same problem as 2.5.60-mm2 during boot:
> >
> > bad: scheduling while atomic!
> > Call Trace:
> > [<c0112ab1>] do_schedule+0x3d/0x2f4
> > [<c0112fb5>] wait_for_completion+0x8d/0xd0
> > [<c0112dac>] default_wake_function+0x0/0x1c
> > [<c0112dac>] default_wake_function+0x0/0x1c
> > [<c0122219>] create_workqueue+0x125/0x178
> > [<c010508e>] init+0x2a/0x17c
> > [<c0105064>] init+0x0/0x17c
> > [<c0106e5d>] kernel_thread_helper+0x5/0xc
>
> This appears to be due to smalldevfs disagreeing with dcache_rcu over
> dcache_lock conventions.
>
> I'll drop out smalldevfs until Adam returns, and has time to look at it,
Backing out that patch fixes it thanks.
Con
next prev parent reply other threads:[~2003-02-16 0:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-15 7:13 2.5.61-mm1 Andrew Morton
2003-02-15 7:13 ` 2.5.61-mm1 Andrew Morton
2003-02-15 7:25 ` 2.5.61-mm1 Nick Piggin
2003-02-15 7:25 ` 2.5.61-mm1 Nick Piggin
2003-02-15 11:27 ` 2.5.61-mm1 Con Kolivas
2003-02-15 23:41 ` 2.5.61-mm1 Andrew Morton
2003-02-16 1:03 ` Con Kolivas [this message]
2003-02-15 14:29 ` 2.5.61-mm1 Ed Tomlinson
2003-02-15 14:29 ` 2.5.61-mm1 Ed Tomlinson
2003-02-16 0:12 ` 2.5.61-mm1 James H. Cloos Jr.
2003-02-16 0:29 ` 2.5.61-mm1 Andrew Morton
2003-02-17 11:38 ` 2.5.61-mm1 Maneesh Soni
2003-02-17 11:29 ` 2.5.61-mm1 Andrew Morton
2003-02-17 22:44 ` 2.5.61-mm1 Cliff White
2003-02-17 22:44 ` 2.5.61-mm1 Cliff White
-- strict thread matches above, loose matches on Subject: below --
2003-02-17 22:50 2.5.61-mm1 Cliff White
2003-02-17 23:13 ` 2.5.61-mm1 Matthew Wilcox
2003-02-17 23:52 ` 2.5.61-mm1 Cliff White
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=200302161203.31899.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=akpm@digeo.com \
--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.