[athk5] wireless crashes after short time of inactivity

[Alexander]

after short time of inactivity wireless crashes. Sometimes, wireless can be re-eactivated by manually re-loading the module "mac80211" and afterwards "ath5k". This problem appears in all lucid kernel releases so far.

I am using Linux 2.6.32-23-generic #37-Ubuntu SMP Fri Jun 11 08:03:28 UTC 2010 x86_64 GNU/Linux
my laptop is a sony vgn-n21s/w.
my hardware is 06:00.0 Ethernet controller: Atheros Communications Inc. AR5001 Wireless Network Adapter (rev 01)

[Jeremy Foshee (jeremyfoshee)]

Hi Alexander,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/daily/current/ . If the issue remains, please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 601443

Also, if you could 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.]

[Alexander (ak71vie)]

Dear Jeremy,

I have downloaded the image "maverick-alternate-amd64.iso" and tried to
install it.

Is there a way to run the new image in parallel to the existing WITHOUT
overwriting the existing partitions on my laptop?

please let me know.

best, Alexander.

On 07/08/2010 05:15 PM, Jeremy Foshee wrote:
> Hi Alexander,
>
> Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/daily/current/ . If the issue remains, please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.
>
> apport-collect -p linux 601443
>
> Also, if you could 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: needs-kernel-logs
>
> ** Tags added: needs-upstream-testing
>
> ** Tags added: kj-triage
>
> ** Changed in: linux (Ubuntu)
> Status: New => Incomplete
>
>

[Alexander (ak71vie)]

Dear Jeremy,

I have downloaded the image "maverick-alternate-amd64.iso" and tried to install it.

Is there a way to run the new image in parallel to the existing WITHOUT overwriting the existing partitions on my laptop?

please let me know.

best, Alexander.

[Alexander (ak71vie)]

to not override my current installation, I downloaded the ISO image http://cdimage.ubuntu.com/daily-live/current/ instead. With this image, it took quite some time until the computer recognized the wireless network, but then the connection kept alive.

So, this particular problem seems to be solved.

thank you again, Alexander.

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu development release http://cdimage.ubuntu.com/daily-live/current/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

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