Ubuntu
linux package

ath5k phy0: failed to wakeup the MAC Chip

Bug #574944 reported by Anibal on 2010-05-04

This bug affects 6 people

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Expired	Medium	Unassigned

Bug Description

The first time I just lost the connection to Internet, and I cannot reconnect again (WEP encryption), and after a few minutes I lost the signal. I reboot and the wireless card just don't work. The module wasn't loaded. Then I reboot a few times and doesn't work again. The problem repeats from Karmic and the upgrade to Lucid don't fix the issue and randomly the wireless card work. In the syslog appears this:

kernel: [ 7348.540075] No probe response from AP 00:15:d0:40:cc:bd after 500ms, disconnecting.
wpa_supplicant[981]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
NetworkManager: <info> (wlan0): supplicant connection state: completed -> disconnected
NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning
kernel: [ 7348.815906] ath5k phy0: failed to wakeup the MAC Chip
kernel: [ 7348.815913] ath5k phy0: can't reset hardware (-5)
kernel: [ 7348.925810] ath5k phy0: failed to wakeup the MAC Chip

I might expect this issue it's fix soon.

Best Regards,

Aníbal.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-22-generic 2.6.32-22.33
Regression: Yes
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: anibal 1809 F.... pulseaudio
Card0.Amixer.info:
Card hw:0 'NVidia'/'HDA NVidia at 0xf4380000 irq 19'
   Mixer name : 'Realtek ALC268'
   Components : 'HDA:10ec0268,10250127,00100003 HDA:11c11040,10250127,00100200'
   Controls : 22
   Simple ctrls : 13
Date: Tue May 4 01:27:55 2010
EcryptfsInUse: Yes
Frequency: Once a day.
HibernationDevice: RESUME=UUID=71caf50f-9251-49f1-810f-34939714ed7a
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
Lsusb:
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 064e:a101 Suyin Corp. Acer CrystalEye Webcam
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer, inc. Aspire 4520
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=1fbb293e-87e2-4987-8a0d-85f9c0ef901c ro vga=791 quiet quiet splash
ProcEnviron:
LANG=es_CL.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34
SourcePackage: linux
dmi.bios.date: 08/15/2007
dmi.bios.vendor: Acer
dmi.bios.version: v1.3619
dmi.board.name: Mono
dmi.board.vendor: Acer, Inc.
dmi.board.version: Not Applicable
dmi.chassis.type: 1
dmi.chassis.vendor: Acer, Inc.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAcer:bvrv1.3619:bd08/15/2007:svnAcer,inc.:pnAspire4520:pvrNotApplicable:rvnAcer,Inc.:rnMono:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A:
dmi.product.name: Aspire 4520
dmi.product.version: Not Applicable
dmi.sys.vendor: Acer, inc.

Tags:

Revision history for this message

Anibal (elkan9) wrote on 2010-05-04:

AlsaDevices.txt Edit (585 bytes, text/plain; charset="utf-8")
AplayDevices.txt Edit (277 bytes, text/plain; charset="utf-8")
ArecordDevices.txt Edit (274 bytes, text/plain; charset="utf-8")
BootDmesg.txt Edit (44.6 KiB, text/plain; charset="utf-8")
CRDA.txt Edit (257 bytes, text/plain; charset="utf-8")
Card0.Amixer.values.txt Edit (2.5 KiB, text/plain; charset="utf-8")
Card0.Codecs.codec.0.txt Edit (7.3 KiB, text/plain; charset="utf-8")
Card0.Codecs.codec.1.txt Edit (141 bytes, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (1.4 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.3 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (521 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (14.6 KiB, text/plain; charset="utf-8")
PciMultimedia.txt Edit (590 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (626 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.3 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.3 KiB, text/plain; charset="utf-8")
RfKill.txt Edit (124 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (102.5 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (230.1 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (1.0 MiB, text/plain; charset="utf-8")

Revision history for this message

Jeremy Foshee (jeremyfoshee) wrote on 2010-05-04:

Hi Anibal,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags:	added: kj-triage
Changed in linux (Ubuntu):
status:	New → Incomplete

Revision history for this message

Anibal (elkan9) wrote on 2010-05-04:

Jeremy, I downloaded the last daily kernel, and didn't work, the issue it's right there. Today my wireless card just work fine twice, the other times just don't work. The syslog says this:

May 4 14:35:07 rock gdm-binary[1107]: WARNING: Unable to load file '/etc/gdm/custom.conf': No existe el fichero ó directorio
May 4 14:35:07 rock gdm-simple-slave[1196]: WARNING: Unable to load file '/etc/gdm/custom.conf': No existe el fichero ó directorio
May 4 14:35:07 rock dhcpd: Wrote 1 leases to leases file.
May 4 14:35:07 rock gdm-binary[1107]: WARNING: Unable to find users: no seat-id found
May 4 14:35:07 rock dhcpd:
May 4 14:35:07 rock dhcpd: No subnet declaration for wlan0 (0.0.0.0).
May 4 14:35:07 rock dhcpd: ** Ignoring requests on wlan0. If this is not what
May 4 14:35:07 rock dhcpd: you want, please write a subnet declaration
May 4 14:35:07 rock dhcpd: in your dhcpd.conf file for the network segment
May 4 14:35:07 rock dhcpd: to which interface wlan0 is attached. **
May 4 14:35:07 rock dhcpd:
May 4 14:35:07 rock dhcpd:
May 4 14:35:07 rock dhcpd: Not configured to listen on any interfaces!
May 4 14:35:07 rock acpid: client connected from 1206[0:0]
May 4 14:35:07 rock acpid: 1 client rule loaded
May 4 14:35:08 rock ntop[1072]: ASN: ...found 111435 lines
May 4 14:35:08 rock ntop[1072]: ASN: ....Used 7560 KB of memory (24 per entry)
May 4 14:35:08 rock ntop[1072]: I18N: Default language (from ntop host) is 'C'
May 4 14:35:08 rock ntop[1072]: I18N: This instance of ntop supports 0 additional language(s)
May 4 14:35:08 rock ntop[1072]: IP2CC: Checking for IP address <-> Country Code mapping file
May 4 14:35:08 rock ntop[1072]: IP2CC: Loading file '/etc/ntop/p2c.opt.table'
May 4 14:35:08 rock gdm-binary[1107]: WARNING: GdmDisplay: display lasted 0,307605 second

I really don't know why the card start when it's want.

tags:

removed: amd64 apport-bug kj-triage lucid needs-upstream-testing networking regression-release

Anibal (elkan9) on 2010-05-04

tags:	added: amd64 apport-bug kj-triage lucid networking regression-release
Changed in linux (Ubuntu):
status:	Incomplete → New
status:	New → Incomplete

Anibal (elkan9) on 2010-05-04

Changed in linux (Ubuntu):
status:	Incomplete → New

Revision history for this message

Anibal (elkan9) wrote on 2010-05-04:

I install the linux-backport-headers for lucid, and the problem still there. I also change the nm-system-settings.conf without efects.

Jeremy Foshee (jeremyfoshee) on 2010-05-05

Changed in linux (Ubuntu):
status:	New → Triaged
importance:	Undecided → Medium

Revision history for this message

Anibal (elkan9) wrote on 2010-05-05: Re: [Bug 574944] Re: ath5k phy0: failed to wakeup the MAC Chip

Jeremy,

Last night the wireless card start at boot, and be stable for the last 10
hours. I didn't make a reboot becouse I need the connection right now. I
attach the dmesg output later.

2010/5/5 Jeremy Foshee <email address hidden>

> ** Changed in: linux (Ubuntu)
> Status: New => Triaged
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
>
> --
> ath5k phy0: failed to wakeup the MAC Chip
> https://bugs.launchpad.net/bugs/574944
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message

Anibal (elkan9) wrote on 2010-05-05:

dmesginfo.txt Edit (46.1 KiB, text/plain; charset=US-ASCII; name="dmesginfo.txt")

Here is the dmesg file.

2010/5/5 Anibal Ayala <email address hidden>

> Jeremy,
>
> Last night the wireless card start at boot, and be stable for the last 10
> hours. I didn't make a reboot becouse I need the connection right now. I
> attach the dmesg output later.
>
> 2010/5/5 Jeremy Foshee <email address hidden>
>
> ** Changed in: linux (Ubuntu)
>> Status: New => Triaged
>>
>> ** Changed in: linux (Ubuntu)
>> Importance: Undecided => Medium
>>
>> --
>> ath5k phy0: failed to wakeup the MAC Chip
>> https://bugs.launchpad.net/bugs/574944
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>
>

Revision history for this message

Anibal (elkan9) wrote on 2010-05-05:

dmesg_fail.txt Edit (57.5 KiB, text/plain; charset=US-ASCII; name="dmesg_fail.txt")
dmesg_start_fail.txt Edit (43.4 KiB, text/plain; charset=US-ASCII; name="dmesg_start_fail.txt")
dmesg_start_work.txt Edit (46.1 KiB, text/plain; charset=US-ASCII; name="dmesg_start_work.txt")

Hi, I attach 3 files with dmesg, in 3 different situations:

-when start ok
-when fail after start
-when just don't start

Right now after 5 to 10 reboot and halt, the ath0 start ok, but after a few
minutes, maybe 20, just stop to work.

May it help

2010/5/5 Anibal Ayala <email address hidden>

> Here is the dmesg file.
>
> 2010/5/5 Anibal Ayala <email address hidden>
>
> Jeremy,
>>
>> Last night the wireless card start at boot, and be stable for the last 10
>> hours. I didn't make a reboot becouse I need the connection right now. I
>> attach the dmesg output later.
>>
>> 2010/5/5 Jeremy Foshee <email address hidden>
>>
>> ** Changed in: linux (Ubuntu)
>>> Status: New => Triaged
>>>
>>> ** Changed in: linux (Ubuntu)
>>> Importance: Undecided => Medium
>>>
>>> --
>>> ath5k phy0: failed to wakeup the MAC Chip
>>> https://bugs.launchpad.net/bugs/574944
>>> You received this bug notification because you are a direct subscriber
>>> of the bug.
>>>
>>
>>
>

Revision history for this message

Anibal (elkan9) wrote on 2010-05-15:

There someone who knows more about this problem?

Revision history for this message

Anibal (elkan9) wrote on 2010-05-15:

I try with the live cd of 10.04, and the ath5k don't work. I will try with Jaunty. May it works.

Revision history for this message

Stas Zytkiewicz (stas-zytkiewicz) wrote on 2010-05-22:

#10

I have the same problems on a acer one A150.
The solution for me was to download the linux-image-generic from karmic, 2.6.31-20, and install it with dpkg -i
Reboot with the karmic kernel and now the card functions properly again. (As it did in karmic)

Revision history for this message

Anibal (elkan9) wrote on 2010-05-23:

#11

Hi, I'll verify your solution and I'll posted if it's work for me.

2010/5/22 Stas Zytkiewicz <email address hidden>

> I have the same problems on a acer one A150.
> The solution for me was to download the linux-image-generic from karmic,
> 2.6.31-20, and install it with dpkg -i
> Reboot with the karmic kernel and now the card functions properly again.
> (As it did in karmic)
>
> --
> ath5k phy0: failed to wakeup the MAC Chip
> https://bugs.launchpad.net/bugs/574944
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message

Anibal (elkan9) wrote on 2010-05-23:

#12

But I used Lucid right now, I have to verify what package is installed on my
system.

2010/5/23 Anibal Ayala <email address hidden>

> Hi, I'll verify your solution and I'll posted if it's work for me.
>
> 2010/5/22 Stas Zytkiewicz <email address hidden>
>
> I have the same problems on a acer one A150.
>> The solution for me was to download the linux-image-generic from karmic,
>> 2.6.31-20, and install it with dpkg -i
>> Reboot with the karmic kernel and now the card functions properly again.
>> (As it did in karmic)
>>
>> --
>> ath5k phy0: failed to wakeup the MAC Chip
>> https://bugs.launchpad.net/bugs/574944
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>
>

Revision history for this message

Anibal (elkan9) wrote on 2010-05-24:

#13

Ok, I did what you said with the Karmic kernel, but didn't work. I try with
a live session of Jaunty and didn't work too. I suspect is a hardware
problem. I don't know yet.

2010/5/23 Anibal Ayala <email address hidden>

> But I used Lucid right now, I have to verify what package is installed on
> my system.
>
> 2010/5/23 Anibal Ayala <email address hidden>
>
> Hi, I'll verify your solution and I'll posted if it's work for me.
>>
>> 2010/5/22 Stas Zytkiewicz <email address hidden>
>>
>> I have the same problems on a acer one A150.
>>> The solution for me was to download the linux-image-generic from karmic,
>>> 2.6.31-20, and install it with dpkg -i
>>> Reboot with the karmic kernel and now the card functions properly again.
>>> (As it did in karmic)
>>>
>>> --
>>> ath5k phy0: failed to wakeup the MAC Chip
>>> https://bugs.launchpad.net/bugs/574944
>>> You received this bug notification because you are a direct subscriber
>>> of the bug.
>>>
>>
>>
>

Revision history for this message

penalvch (penalvch) wrote on 2013-09-28:

#14

Anibal, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily kernel folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.12-rc1

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Changed in linux (Ubuntu):
status:	Triaged → Incomplete

Revision history for this message

Anibal (elkan9) wrote on 2013-09-28:

#15

Christopher, actually this bug occurs specifically with my home internet
conection. I run the script you sent, and post it later.

Regards.
El sep 28, 2013 2:43 p.m., "Christopher M. Penalver" <
<email address hidden>> escribió:

> Anibal, this bug was reported a while ago and there hasn't been any
> activity in it recently. We were wondering if this is still an issue? If
> so, could you please test for this with the latest development release
> of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
> /daily-live/current/ .
>
> If it remains an issue, could you please run the following command in
> the development release from a Terminal
> (Applications->Accessories->Terminal), as it will automatically gather
> and attach updated debug information to this report:
>
> apport-collect -p linux <replace-with-bug-number>
>
> Also, could you please test the latest upstream kernel available following
> https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional
> upstream developers to examine the issue. Please do not test the daily
> kernel folder, but the one all the way at the bottom. Once you've tested
> the upstream kernel, please comment on which kernel version specifically
> you tested. If this bug is fixed in the mainline kernel, please add the
> following tags:
> kernel-fixed-upstream
> kernel-fixed-upstream-VERSION-NUMBER
>
> where VERSION-NUMBER is the version number of the kernel you tested. For
> example:
> kernel-fixed-upstream-v3.12-rc1
>
> This can be done by clicking on the yellow circle with a black pencil icon
> next to the word Tags located at the bottom of the bug description. As
> well, please remove the tag:
> needs-upstream-testing
>
> If the mainline kernel does not fix this bug, please add the following
> tags:
> kernel-bug-exists-upstream
> kernel-bug-exists-upstream-VERSION-NUMBER
>
> As well, please remove the tag:
> needs-upstream-testing
>
> Once testing of the upstream kernel is complete, please mark this bug's
> Status as Confirmed. Please let us know your results. Thank you for your
> understanding.
>
> ** Changed in: linux (Ubuntu)
> Status: Triaged => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/574944
>
> Title:
> ath5k phy0: failed to wakeup the MAC Chip
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/574944/+subscriptions
>

Christopher, actually this bug occurs specifically with my home internet
conection. I run the script you sent, and post it later.

Regards.
El sep 28, 2013 2:43 p.m., "Christopher M. Penalver" <
christopher.m.penalver@gmail.com> escribió:

> Anibal, this bug was reported a while ago and there hasn't been any
> activity in it recently. We were wondering if this is still an issue? If
> so, could you please test for this with the latest development release
> of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
> /daily-live/current/ .
>
> If it remains an issue, could you please run the following command in
> the development release from a Terminal
> (Applications->Accessories->Terminal), as it will automatically gather
> and attach updated debug information to this report:
>
> apport-collect -p linux <replace-with-bug-number>
>
> Also, could you please test the latest upstream kernel available following
> https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional
> upstream developers to examine the issue. Please do not test the daily
> kernel folder, but the one all the way at the bottom. Once you've tested
> the upstream kernel, please comment on which kernel version specifically
> you tested. If this bug is fixed in the mainline kernel, please add the
> following tags:
> kernel-fixed-upstream
> kernel-fixed-upstream-VERSION-NUMBER
>
> where VERSION-NUMBER is the version number of the kernel you tested. For
> example:
> kernel-fixed-upstream-v3.12-rc1
>
> This can be done by clicking on the yellow circle with a black pencil icon
> next to the word Tags located at the bottom of the bug description. As
> well, please remove the tag:
> needs-upstream-testing
>
> If the mainline kernel does not fix this bug, please add the following
> tags:
> kernel-bug-exists-upstream
> kernel-bug-exists-upstream-VERSION-NUMBER
>
> As well, please remove the tag:
> needs-upstream-testing
>
> Once testing of the upstream kernel is complete, please mark this bug's
> Status as Confirmed. Please let us know your results. Thank you for your
> understanding.
>
> ** Changed in: linux (Ubuntu)
>        Status: Triaged => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/574944
>
> Title:
>   ath5k phy0: failed to wakeup the MAC Chip
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/574944/+subscriptions
>

Revision history for this message

Launchpad Janitor (janitor) wrote on 2013-11-28:

#16

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status:	Incomplete → Expired

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.

Ubuntulinux package

ath5k phy0: failed to wakeup the MAC Chip

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
linux package