From: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>
To: "fredoxygene@free.fr" <fredoxygene@free.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: kernel BUG at kernel/workqueue.c:323!
Date: Mon, 27 Aug 2007 01:33:17 +0200 [thread overview]
Message-ID: <6bffcb0e0708261633r5de8296di53aca3def4ebbdcd@mail.gmail.com> (raw)
In-Reply-To: <1188125967.46d15d0f87c01@imp.free.fr>
Hi,
On 26/08/07, fredoxygene@free.fr <fredoxygene@free.fr> wrote:
> PROBLEM: kernel BUG at kernel/workqueue.c:323!
>
> Summary :
> Happened while i was transferring a huge amount of data on wifi (ipw3945).
> Computer is a Fujitsu/Siemens Si 1520 / T5500, running Unbuntu Feisty 7.04.
>
> Follows :
> - dmesg output with "kernel bug"
> - scripts/ver_linux output
> - others thinks like lspci -vvv, etc...
>
> Feel free to ask i you need some more details or if i can help (by doing some
> testings or other stuffs)
>
> dmesg output :
> [ 178.752000] ieee80211_crypt: registered algorithm 'TKIP'
> [ 196.120000] eth1: no IPv6 routers present
> [ 1548.228000] ipw3945: Error sending LEDS_CMD: time out after 500ms.
> [ 1548.924000] ipw3945: Error sending cmd #07 to daemon: time out after 500ms.
> [ 1550.524000] ipw3945: Error sending SCAN_ABORT_CMD: time out after 500ms.
> [ 1551.024000] ipw3945: Error sending cmd #08 to daemon: time out after 500ms.
> [ 1551.524000] ipw3945: Error sending ADD_STA: time out after 500ms.
> [ 1552.024000] ipw3945: Error sending SCAN_ABORT_CMD: time out after 500ms.
> [ 1561.536000] ipw3945: Error sending LEDS_CMD: time out after 500ms.
> [ 1561.712000] ADDRCONF(NETDEV_UP): eth1: link is not ready
> [ 1582.928000] ADDRCONF(NETDEV_UP): eth1: link is not ready
> [ 1611.024000] ipw3945: Error sending LEDS_CMD: time out after 500ms.
> [ 1611.524000] ipw3945: Error sending LEDS_CMD: time out after 500ms.
> [ 1611.796000] ------------[ cut here ]------------
> [ 1611.796000] kernel BUG at kernel/workqueue.c:323!
"Problems building with kernel v2.6.20
The work queue structure changed with 2.6.20. In addition,
pci_module_init was deprecated. The three patches below in Patches
were provided by Mattiaa Dongili to correct this behavior. Download
them and apply them to ipw3945-1.1.3 James"
http://ipw3945.sourceforge.net/
Regards,
Michal
--
LOG
http://www.stardust.webpages.pl/log/
prev parent reply other threads:[~2007-08-26 23:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-26 10:59 fredoxygene
2007-08-26 23:33 ` Michal Piotrowski [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=6bffcb0e0708261633r5de8296di53aca3def4ebbdcd@mail.gmail.com \
--to=michal.k.k.piotrowski@gmail.com \
--cc=fredoxygene@free.fr \
--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
all inboxes | Powered by JetHome®