From: Ian Pilcher <i.pilcher@comcast.net>
To: linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at kernel/workqueue.c:104!
Date: Fri, 08 Oct 2004 13:19:52 -0500 [thread overview]
Message-ID: <ck6lo8$lh8$1@sea.gmane.org> (raw)
In-Reply-To: <ck4q19$tne$1@sea.gmane.org>
Ian Pilcher wrote:
> I hit this trying to install Fedora Core 3 test 1 or test 2. Anyone
> who's interested can see the output at:
>
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=127862
>
> This is obviously one for Red Hat (although they appear massively
> uninterested), but I was just wondering if anyone on this list can point
> me towards a good spot to start digging.
>
To ask the question a different way, what can a user-level program do
that will cause queue_work (in kernel/workqueue.c) to be called?
Thanks!
--
========================================================================
Ian Pilcher i.pilcher@comcast.net
========================================================================
next prev parent reply other threads:[~2004-10-08 18:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-08 1:20 kernel BUG at kernel/workqueue.c:104! Ian Pilcher
2004-10-08 18:19 ` Ian Pilcher [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-23 16:02 Karl Hiramoto
2005-08-24 17:01 ` Parag Warudkar
2005-08-29 8:29 ` 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='ck6lo8$lh8$1@sea.gmane.org' \
--to=i.pilcher@comcast.net \
--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