public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Thomas Meyer <thomas@m3y3r•de>
To: Rusty Russell <rusty@rustcorp•com.au>
Cc: rpjday@crashcourse•ca, linux-next@vger•kernel.org,
	LKML <linux-kernel@vger•kernel.org>
Subject: Re: kernel BUG at kernel/workqueue.c:169 (was: linux-next: Tree for June 16)
Date: Mon, 23 Jun 2008 22:10:44 +0200	[thread overview]
Message-ID: <1214251844.486003446b64c@213.133.104.17> (raw)
In-Reply-To: <200806231315.54490.rusty@rustcorp.com.au>

Zitat von Rusty Russell <rusty@rustcorp•com.au>:

> On Saturday 21 June 2008 04:48:37 Thomas Meyer wrote:
> > I tried to bisect this one, but without a consistent result.
> 
> That's always suspicious...
> 
> > Another thing i tried is to change <linux/kernel.h>:
> 
> This will also cause almost everything to be rebuilt.  I find it hard to 
> believe this is the culprit; does a "make clean" also fix it?
> 
Sorry! I compared the created binary and both are equal. So above commit
revertion or the change of linux/kernel.h has nothing to do with the non
working usb wlan stick.

Sometimes it works, sometimes not. And when it's non-working then i also get the
BUG at kernel/workqueue in my dmesg.
 

Sorry for all the bustle.

greets
thomas

      reply	other threads:[~2008-06-23 20:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-16  9:01 linux-next: Tree for June 16 Stephen Rothwell
2008-06-16 21:28 ` kernel BUG at kernel/workqueue.c:169 (was: linux-next: Tree for June 16) Thomas Meyer
2008-06-20 18:48   ` Thomas Meyer
2008-06-23  3:15     ` Rusty Russell
2008-06-23 20:10       ` Thomas Meyer [this message]

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=1214251844.486003446b64c@213.133.104.17 \
    --to=thomas@m3y3r$(echo .)de \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=rpjday@crashcourse$(echo .)ca \
    --cc=rusty@rustcorp$(echo .)com.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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