Acer Aspire 7250 laptop with Atheros AR9485 freezes when Enabling Wireless in 12.04

Bug #989566 reported by janmartin
32
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Linux
New
Undecided
Unassigned
linux (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

freezes when Enabling Wireless

Acer Aspire 7250
AMD Dual-Core-Processor E300
17.3 " HD + LED LCD
AMD Radeon HD 6310
8 GB DDR3 Memory
500 GB HDD
DVD-Super Multi DL drive
Acer Nplify 802.11 b/g/n
6-cell Li-ion battery

Running 64 bit Ubuntu 12.04:
cernel: 3.2.0-24-generic

When ever I am clicking "Enable Wireless" the laptop freezes immediately.
I then need to press the ON/OFF button to restart.

WORKAROUND: sudo gedit /etc/modprobe.d/blacklist.conf

add the line:
blacklist atl1c

(2) Open Terminal and issue the command:
sudo update-initramfs -u

Restart Laptop.

lspci -k:

06:00.0 Network controller: Atheros Communications Inc. AR9485 Wireless Network Adapter (rev 01)
 Subsystem: Lite-On Communications Inc Device 6617
 Kernel driver in use: ath9k
 Kernel modules: ath9k

dmesg:

[ 12.279014] ath9k 0000:06:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 12.279072] ath9k 0000:06:00.0: setting latency timer to 64
[ 12.290070] ath: EEPROM regdomain: 0x65
[ 12.290078] ath: EEPROM indicates we should expect a direct regpair map
[ 12.290087] ath: Country alpha2 being used: 00
[ 12.290091] ath: Regpair used: 0x65
[ 12.290731] cfg80211: Updating information on frequency 2412 MHz for a 20 MHz width channel with regulatory rule:
[ 12.290742] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
[ 12.290747] cfg80211: Updating information on frequency 2417 MHz for a 20 MHz width channel with regulatory rule:
[ 12.290753] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
[ 12.290758] cfg80211: Updating information on frequency 2422 MHz for a 20 MHz width channel with regulatory rule:
[ 12.290764] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
[ 12.290769] cfg80211: Updating information on frequency 2427 MHz for a 20 MHz width channel with regulatory rule:
[ 12.290775] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
[ 12.290780] cfg80211: Updating information on frequency 2432 MHz for a 20 MHz width channel with regulatory rule:
[ 12.290786] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
[ 12.290790] cfg80211: Updating information on frequency 2437 MHz for a 20 MHz width channel with regulatory rule:
[ 12.290796] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
[ 12.290801] cfg80211: Updating information on frequency 2442 MHz for a 20 MHz width channel with regulatory rule:
[ 12.290806] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
[ 12.290811] cfg80211: Updating information on frequency 2447 MHz for a 20 MHz width channel with regulatory rule:
[ 12.290817] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
[ 12.290821] cfg80211: Updating information on frequency 2452 MHz for a 20 MHz width channel with regulatory rule:
[ 12.290827] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
[ 12.290832] cfg80211: Updating information on frequency 2457 MHz for a 20 MHz width channel with regulatory rule:
[ 12.290838] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
[ 12.290842] cfg80211: Updating information on frequency 2462 MHz for a 20 MHz width channel with regulatory rule:
[ 12.290848] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
[ 12.290853] cfg80211: Updating information on frequency 2467 MHz for a 20 MHz width channel with regulatory rule:
[ 12.290858] cfg80211: 2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
[ 12.290863] cfg80211: Updating information on frequency 2472 MHz for a 20 MHz width channel with regulatory rule:
[ 12.290869] cfg80211: 2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
[ 12.290874] cfg80211: Disabling freq 2484 MHz as custom regd has no rule that fits a 20 MHz wide channel
[ 12.295031] cfg80211: Ignoring regulatory request Set by core since the driver uses its own custom regulatory domain
[ 12.314656] ieee80211 phy0: Selected rate control algorithm 'ath9k_rate_control'
[ 12.316637] Registered led device: ath9k-phy0
[ 12.316669] ieee80211 phy0: Atheros AR9485 Rev:1 mem=0xffffc90005a80000, irq=17
[ 12.612571] init: failsafe main process (779) killed by TERM signal
[ 12.747420] type=1400 audit(1335515214.867:7): apparmor="STATUS" operation="profile_replace" name="/sbin/dhclient" pid=868 comm="apparmor_parser"
[ 12.755276] type=1400 audit(1335515214.875:8): apparmor="STATUS" operation="profile_replace" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=868 comm="apparmor_parser"
[ 12.755772] type=1400 audit(1335515214.875:9): apparmor="STATUS" operation="profile_replace" name="/usr/lib/connman/scripts/dhclient-script" pid=868 comm="apparmor_parser"
[ 12.757052] type=1400 audit(1335515214.879:10): apparmor="STATUS" operation="profile_load" name="/usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper" pid=867 comm="apparmor_parser"
[ 12.777234] type=1400 audit(1335515214.899:11): apparmor="STATUS" operation="profile_load" name="/usr/lib/telepathy/mission-control-5" pid=871 comm="apparmor_parser"

Please fix this.

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/989566/+editstatus and add the package name in the text box next to the word Package.

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

tags: added: bot-comment
Revision history for this message
janmartin (janmartin3-googlemail) wrote :

Seems this worked before 12.04?

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in linux.

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://help.ubuntu.com/community/ReportingBugs.

affects: ubuntu → linux (Ubuntu)
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.4kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). 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.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-rc4-precise/

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: needs-upstream-testing precise
Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: kernel-bug-exists-upstream
Revision history for this message
janmartin (janmartin3-googlemail) wrote :

It seems this is related to atl1c somehow:
http://linuxnorth.wordpress.com/2011/10/23/wireless-less/

sudo gedit /etc/modprobe.d/blacklist.conf

add the line:

blacklist atl1c

(2) Open Terminal and issue the command:

sudo update-initramfs -u

Restart Laptop is a workaround.
No more wired Ethernet anymore, but the laptop does not crash anymore too.

tags: added: atl1c
Revision history for this message
janmartin (janmartin3-googlemail) wrote :
affects: linux (Ubuntu) → ubuntu
Changed in ubuntu:
status: Incomplete → New
affects: ubuntu → linux (Ubuntu)
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
CU2 (j.holzhausen) wrote :

Please see here:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/919815

This workaround will solve the issue. Enable Wireless and set "Boot from LAN" to first in bios.

You will get an error message when Notebook starts, but silly thing it works ;-)

Regards,
Joerg

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

janmartin, 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 CD images are available from http://cdimage.ubuntu.com/releases/ .

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 kernel in the daily 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 and 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.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream-VERSION-NUMBER', where VERSION-NUMBER is the version number of the kernel you tested.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream-VERSION-NUMBER', where VERSION-NUMBER is the version number of the kernel you tested.

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the tag: 'kernel-unable-to-test-upstream'.

Please let us know your results. Thank you for your understanding.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

tags: added: needs-kernel-logs
removed: atl1c kernel-bug-exists-upstream
tags: added: amd64
description: updated
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
CU2 (j.holzhausen) wrote :

Why is this marked as expired. I'll install the new release of Ubuntu 12.10 straight after release date and then I`ll see and report on the changes.
Thanks & Regards

Changed in linux (Ubuntu):
status: Expired → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

CU2, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Bug Control and Ubuntu Bug Squad article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette

When opening up the new report, please feel free to subscribe me to it. Thank you for your understanding.

Status -> Incomplete as missing requested action items from https://bugs.launchpad.net/ubuntu/+source/linux/+bug/989566/comments/8 .

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
logger32 (logger32) wrote :

I have the same pb.

freezes when Enabling Wireless

Acer Aspire 7250
AMD Dual-Core-Processor E300
17.3 " HD + LED LCD
AMD Radeon HD 6310
8 GB DDR3 Memory
500 GB HDD
DVD-Super Multi DL drive
Acer Nplify 802.11 b/g/n
6-cell Li-ion battery

Running 64 bit Ubuntu 12.04.

Revision history for this message
penalvch (penalvch) wrote :
Revision history for this message
William Smith (wrsmith-y) wrote :

I have been working with this problem as well, although I ended up with a slightly different workaround. I blacklisted ath9k, ath9k_common, and ath9k_hw, and disabled wireless networking.

I tried Ubuntu 12.04 on this computer, and it was working nicely for a while, until I did a dist-upgrade a few days ago and rebooted. It would freeze a few seconds after it got to the UI prompt. It had already some wifi networks stored, that it connected to automatically.

I tried OpenSuse 12 - same thing. It froze during the installation process.

Fedora 17 would boot to the UI in a live CD, but as soon as I selected any one of the wireless networks to connect to, it would freeze.

So this is not an Ubuntu problem, per se, but it affects Ubuntu.

I blacklisted ath9k, ath9k_common, and ath9k_hw and got Fedora 17 working stably. I have the 3.3.4-5.fc17.x86_64 kernel

Revision history for this message
penalvch (penalvch) wrote :
Revision history for this message
CU2 (j.holzhausen) wrote : Re: [Bug 989566] Re: Acer Aspire 7250 laptop with Atheros AR9485 freezes when Enabling Wireless in 12.04

This weekend I installed the new release of Ubuntu 12.10 with a complete
new installation. This solved the issue for me. Everyting is working
now. No further freezes during many re-starts (warm & cold) boot.

Best regards and many thank to all the developer.

Am 14.10.2012 12:52, schrieb logger32:
> I have the same pb.
>
> freezes when Enabling Wireless
>
> Acer Aspire 7250
> AMD Dual-Core-Processor E300
> 17.3 " HD + LED LCD
> AMD Radeon HD 6310
> 8 GB DDR3 Memory
> 500 GB HDD
> DVD-Super Multi DL drive
> Acer Nplify 802.11 b/g/n
> 6-cell Li-ion battery
>
> Running 64 bit Ubuntu 12.04.
>
> ** Also affects: linux
> Importance: Undecided
> Status: New
>

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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