This bug was filed against a series that is no longer supported and so
is being marked as Won't Fix. If this issue still exists in a supported
series, please file a new bug.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Thanks for testing and confirming against the latest Jaunty released.
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-image-2.6.28-11-generic 376363
** Tags added: needs-kernel-logs
** Tags added: needs-upstream-testing
--
soft lockup - CPU#1 stuck for 61s! [cron:3954]
https://bugs.launchpad.net/bugs/376363
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
uploaded the requested info. Will try to reproduce the issue with the
latest upstream kernel over the weekend. Right now running with kernel
2.6.28-13 and haven't run into the problem for the past week (tho I try
to avoid stressing the load on network connection which brought that
issue in most
** Tags removed: needs-kernel-logs
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
soft lockup - CPU#1 stuck for 61s! [cron:3954]
https://bugs.launchpad.net/bugs/376363
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hey Moritz,
thanks for suggestion, but it is not really an option.
I tried backports already and with that i have same issue as before (when i was
using intrepid) - the network keeps disconnecting frequently, specially under
the load (e.g. when transfering data files bigger then 1GB) and since I
** Package changed: evolution (Ubuntu) = linux (Ubuntu)
--
soft lockup - CPU#1 stuck for 61s! [cron:3954]
https://bugs.launchpad.net/bugs/376363
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
On a wild guess, this can be related to a firmware (microcode) issue in
iwlagn. I suggest installing linux-backports-modules-jaunty which will
cause an updated (and apparently less problematic) firmware to be
installed.
--
soft lockup - CPU#1 stuck for 61s! [cron:3954]
I should provide references to explain what makes me think this can be
related to the iwlagn module, as well as other Intel wireless modules:
* I just reviewed a syslog
(https://bugs.launchpad.net/linux/+bug/200509) of a user who had this
issue and also had iwlagn: Microcode SW error detected.
