Based on previous comments I'm marking this "Fix Released" since we
haven't heard back from Adna.
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
Error on shutdown --> ipw 3945: error sending cmd #07 to daemon: timeout after
500ms
https://bugs.launchpad.net/bugs/71510
I'm in the same situation as Juan Pablo. Unsubscribing myself from the
bug.
--
Error on shutdown --> ipw 3945: error sending cmd #07 to daemon: timeout after
500ms
https://bugs.launchpad.net/bugs/71510
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
Adna, since you are the original bug reporter, care to confirm this is
resolved with Intrepid. Alpha5 just came out so you should be able to
test via a LiveCD. Thanks.
--
Error on shutdown --> ipw 3945: error sending cmd #07 to daemon: timeout after
500ms
https://bugs.launchpad.net/bugs/71510
Intrepid is using iwl3945 for me. I've never seen this message in
Intrepid using iwl3945.
[EMAIL PROTECTED]:~$ dpkg -l | grep linux-image-2.6.27-
ii linux-image-2.6.27-1-generic 2.6.27-1.2
Linux kernel image for version 2.6.27 on x86
[EMAIL PROTECTED]:~$ l
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering is this still an issue
for you? Can you try with latest Ubuntu release? Thanks in advance.
--
Error on shutdow
For those experiencing issues with Gutsy, care to test with a Hardy
Alpha release? Jonathan Amir commented that this appears to be resolved
with a newer Hardy Alpha release. Hardy Alpha2 and subsequent releases
contain an updated version of the kernel. You can download and try the
new Hardy Hero
** Attachment added: "lspci-vvnn.log"
http://launchpadlibrarian.net/11459486/lspci-vvnn.log
--
Error on shutdown --> ipw 3945: error sending cmd #07 to daemon: timeout after
500ms
https://bugs.launchpad.net/bugs/71510
You received this bug notification because you are a member of Ubuntu
Bugs
** Attachment added: "uname-a.log"
http://launchpadlibrarian.net/11459476/uname-a.log
--
Error on shutdown --> ipw 3945: error sending cmd #07 to daemon: timeout after
500ms
https://bugs.launchpad.net/bugs/71510
You received this bug notification because you are a member of Ubuntu
Bugs, whic
** Attachment added: "version.log"
http://launchpadlibrarian.net/11459483/version.log
--
Error on shutdown --> ipw 3945: error sending cmd #07 to daemon: timeout after
500ms
https://bugs.launchpad.net/bugs/71510
You received this bug notification because you are a member of Ubuntu
Bugs, whic
I confirm the problem on Ubuntu Gutsy
ipw3945 crashes randomly on my hp laptop dv6500.
After it crashes the only thing to do is restart the system, I agree to the
fact that this is not an irrelevant problem (even if i am trying to live with
it)
** Attachment added: "dmesg.log"
http://launchp
Yes as said years ago ;) This error is just at the sutdown for me and it
exists in edgy,feisty and also now gutsy.
--
Error on shutdown --> ipw 3945: error sending cmd #07 to daemon: timeout after
500ms
https://bugs.launchpad.net/bugs/71510
You received this bug notification because you are a me
Probably this bug is the same https://bugs.launchpad.net/ubuntu/+source
/linux-source-2.6.22/+bug/109887 but as the initial reporter said it has
ocurred to him only at shutdown, so the people with the same trouble at
random times should go to Bug #109887 and report there their problem.
Also note t
I tried it on Hardy Heron Alpha2 and it seems to be working fine. There were a
couple of problems but I don't know if they are related to this bug:
1) After waking up the network-manager takes a long time (more than a minute)
until it starts to reconnect to a wireless network again. During that t
Hardy Heron Alpha2 was recently released. It contains an updated
version of the kernel. You can download and try the new Hardy Heron
Alpha2 release from http://cdimage.ubuntu.com/releases/hardy/alpha-2/ .
You should be able to then test the new kernel via the LiveCD. If you
can, please verify if
Leann,
This bug report describes two issues, some get the error when shutting down,
others like me get them random. And as Ryan says, it makes my computer
unusable, because I need a reboot every time it happens. I understand the
situation of the kernel team and priority next release. However th
Ryan,
I apologize for any issues you may be experiencing with the Gutsy Gibbon
release. We really do try to release the best possible distribution we
can. The reports made by users like yourself are very helpful to us and
we really value your feedback. However, the intermittent connectivity
you
Leann,
Are you kidding me? Something that makes the driver UNUSABLE (the
machine disconnects completely at random, and this is my work laptop!)
does not meet the criteria for a stable release bug? This kernel never
should have been release with that bug in it.
The problem with this distribution i
Hmm... I'm not sure it is that clear that it should only be fixed for
Hardy. I don't know exactly what of my network problems are related to
this bug, but it feels like my wireless network isn't working as
expected (in a hard to define way... sometimes it will refuse to switch
to a wiredconnection,
I'm retargetting this report against the upcoming Hardy kernel hence the
'hardy-kernel-candidate' tag. However, against linux-ubuntu-
modules-2.6.22 this bug does not meet the criteria for a stable release
update and is being marked as Won't Fix. You can learn more about the
stable release update
I can comfirm this issue on my Dell XPS m1330.
Looks like the issue appears more often when the NIC is under load.
After the crash iwlist eth1 scanning returns eth1 does not support scanning. It
crashes completely.
http://tenfjord.net/paul/dmesg.log
http://tenfjord.net/paul/lspci-vvnn.log
http://
I second rhersel message. Confirming on 2.6.22.14 as well (latest Gutsy
7.10), on a Lenovo R60e, with exactly the same message.
--
Error on shutdown --> ipw 3945: error sending cmd #07 to daemon: timeout after
500ms
https://bugs.launchpad.net/bugs/71510
You received this bug notification because
I can confirm it for 2.6.22-14 as well. Happens approx. every second shutdown.
Error message is:
[ 6204.672000] ipw3945: Error sending cmd #07 to daemon: time out after 500ms.
--
Error on shutdown --> ipw 3945: error sending cmd #07 to daemon: timeout after
500ms
https://bugs.launchpad.net/bugs/
** Changed in: linux-ubuntu-modules-2.6.22 (Ubuntu)
Status: Confirmed => Triaged
--
Error on shutdown --> ipw 3945: error sending cmd #07 to daemon: timeout after
500ms
https://bugs.launchpad.net/bugs/71510
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Attachment added: "lspci-vvnn.log"
http://launchpadlibrarian.net/10066408/lspci-vvnn.log
** Changed in: linux-ubuntu-modules-2.6.22 (Ubuntu)
Status: Incomplete => Confirmed
--
Error on shutdown --> ipw 3945: error sending cmd #07 to daemon: timeout after
500ms
https://bugs.launchp
** Attachment added: "dmesg.log"
http://launchpadlibrarian.net/10066404/dmesg.log
--
Error on shutdown --> ipw 3945: error sending cmd #07 to daemon: timeout after
500ms
https://bugs.launchpad.net/bugs/71510
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: "version.log"
http://launchpadlibrarian.net/10066402/version.log
--
Error on shutdown --> ipw 3945: error sending cmd #07 to daemon: timeout after
500ms
https://bugs.launchpad.net/bugs/71510
You received this bug notification because you are a member of Ubuntu
Bugs, whic
The easiest way to see this message is to switch to VT1 and run "sudo
reboot".
** Attachment added: "uname-a.log"
http://launchpadlibrarian.net/10066401/uname-a.log
--
Error on shutdown --> ipw 3945: error sending cmd #07 to daemon: timeout after
500ms
https://bugs.launchpad.net/bugs/71510
Y
Now that the 7.10 Gutsy Gibbon release of Ubuntu is out, can someone
confirm this issue still exists. You can download and try the new
version of Ubuntu from http://www.ubuntu.com/getubuntu/download . Please
report back your results. If the issue is still present in the new
release, please attach
In my case a TP-Link WR543 wireless router was causing the problem. A
firmware upgrade helped. I cannot confirm the error message on shutdown
though.
--
Error on shutdown --> ipw 3945: error sending cmd #07 to daemon: timeout after
500ms
https://bugs.launchpad.net/bugs/71510
You received this bu
Setting as confirmed in l-u-m-2.6.22, as I can see the message when shutting
down gutsy.
l-u-m version 2.6.22-12.32
** Changed in: linux-ubuntu-modules-2.6.22 (Ubuntu)
Status: New => Confirmed
--
Error on shutdown --> ipw 3945: error sending cmd #07 to daemon: timeout after
500ms
https:
** Changed in: linux-ubuntu-modules-2.6.22 (Ubuntu)
Sourcepackagename: linux-source-2.6.22 => linux-ubuntu-modules-2.6.22
--
Error on shutdown --> ipw 3945: error sending cmd #07 to daemon: timeout after
500ms
https://bugs.launchpad.net/bugs/71510
You received this bug notification because you a
[ 475.112000] ipw3945: Error sending LEDS_CMD: time out after 500ms.
[ 475.712000] ipw3945: Error sending LEDS_CMD: time out after 500ms.
[ 476.212000] ipw3945: Error sending cmd #07 to daemon: time out after 500ms.
[ 477.408000] ipw3945: Error sending SCAN_ABORT_CMD: time out after 500ms.
[ 4
I can confirm that it also happens to 2.6.22.
And what is even more annoying it happens after I upload ~200-600MB to another
computer. WiFi connectivity crashes completely then.
The error message is the same as Bogdan's
(https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/71510/com
I can see this in up-to-date Gutsy every time I shut down.
Strangely I can't find anything in the logs about it, with just one
exception a few days ago:
$ grep "Error sending" /var/log/*
kern.log:Aug 12 14:35:32 cimer kernel: [75812.852000] ipw3945: Error sending
LEDS_CMD: time out after 500ms.
I've seen this error in Feisty Beta before suspending. After waking up, I end
up with no wireless (the wifi light in my laptop is turned off, trying to
enable it with hotkey doesn't work).
This happens sometimes only (with no apparent reason), so if i suspend ->
resume again, wifi is back.
--
** Also affects: linux-source-2.6.20 (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
Error on shutdown --> ipw 3945: error sending cmd #07 to daemon: timeout after
500ms
https://launchpad.net/bugs/71510
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubun
** Changed in: Ubuntu
Sourcepackagename: None => linux-source-2.6.17
Importance: Undecided => Medium
Assignee: Brian Murray => (unassigned)
Status: Needs Info => Confirmed
--
Error on shutdown --> ipw 3945: error sending cmd #07 to daemon: timeout after
500ms
https://launchpad.net
wow that took some time for an answer ;)
this occurs on ubuntu edgy eft (you have to switch splash and quiete
mode off in your /boot/grub/menu.lst to see this error when you
shutdown/reboot) but should be normally notable on every edgy
K/X/Ed/ubuntu which uses the this wlan daemon.
So again the p
Thanks for taking the time to report this bug and helping to make Ubuntu
better. With which version of Ubuntu did you notice this issue? Thanks
in advance.
** Changed in: Ubuntu
Assignee: (unassigned) => Brian Murray
Status: Unconfirmed => Needs Info
--
Error on shutdown --> ipw 39
40 matches
Mail list logo
