The network crash when I leave the laptop alone

Bug #232536 reported by nuhr
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Well. When i leave the laptop alone, with downloads active, about the 30 minutes or more, the network crash and i do:

sudo /etc/init.d/networking restart

With these comand, I can enjoy of the network because the network's state is good.
What is it? Salutes, NuhR.

Note:

Laptop: Packard Bell Easynote MX51-b-048
Network card (Wifi): Atheros AR5006EG
I use the wifi conection
I have 2 GB of memory Ram and 1 gb of swap
I think that i start to have this problem with Gutsy and I think that with Feisty no, but it isn't credible.
When start the problem, the charge of the system is of 1,12 and my habitual charge is of 0,08 or 0,30.
When start the problem, a misterious processor's use is active
Whe i do a "top" i can see that the process "ksoftirqd/1" is consuming a 100% of cpu!!! help!

Well, the line of the command "uname-a" is:

Linux linux 2.6.24-18-generic #1 SMP Wed May 28 19:28:38 UTC 2008 x86_64 GNU/Linux

With the Kernel of the Intrepid Ibex the problem is the same.

Tags: cft-2.6.27
nuhr (duyelp)
description: updated
nuhr (duyelp)
description: updated
Revision history for this message
Dereck Wonnacott (dereck) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description does not yet have enough information.

Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at [WWW] https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance!

Changed in linux:
status: New → Incomplete
nuhr (duyelp)
Changed in linux:
assignee: satanic → ubuntu-kernel-team
description: updated
nuhr (duyelp)
Changed in linux:
status: Incomplete → In Progress
Revision history for this message
nuhr (duyelp) wrote :
Revision history for this message
nuhr (duyelp) wrote :
nuhr (duyelp)
Changed in linux:
status: In Progress → New
nuhr (duyelp)
Changed in linux:
status: New → In Progress
Revision history for this message
Brian Murray (brian-murray) wrote :

I'm changing this bug's status away from 'In Progress' since no one is currently actively working on fixing the bug.

Changed in linux:
importance: Undecided → Medium
status: In Progress → Triaged
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

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 installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Ralph Janke (txwikinger) wrote :

The Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . It contains the 2.6.27 Ubuntu kernel. It would be great if you could test and verify if this is still an issue. The status is being set to Incomplete until we receive further feedback. Thanks.

Changed in linux:
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

Revision history for this message
nuhr (duyelp) wrote :
description: updated
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Can you also test the latest pre-release of Jaunty, Alpha 3 - http://cdimage.ubuntu.com/releases/jaunty/ . You should be able to test via a LiveCD. Please let us know your results. If the issue remains, please also attach your dmesg output after you experience the Network crash. Thanks.

Revision history for this message
Ike Panhc (ikepanhc) wrote :

I am using Lenovo SL400 with ath5k chips and ubuntu intrepid

wireless works fine with me.

If you have the same situation again, could you have record of the "iwconfig" output to make sure the link to AP is still fine?

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Having received no further feedback, I'm closing this per previous comment. Thanks.

Changed in linux (Ubuntu):
status: Incomplete → Fix Released
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.