** Changed in: linux (upstream)
Status: Unknown => In Progress
--
BUG: soft lockup detected on CPU#0!
https://launchpad.net/bugs/83009
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I reported similar behaviour in Bug #87320.
I have a Gigabyte GA-965P-DS3 motherboard with a gigabit network
interface - using the sky2 driver.
--
BUG: soft lockup detected on CPU#0!
https://launchpad.net/bugs/83009
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu
** Changed in: linux-source-2.6.20 (Ubuntu)
Importance: Undecided => Medium
Assignee: Kyle McMartin => Ubuntu Kernel Team
--
BUG: soft lockup detected on CPU#0!
https://launchpad.net/bugs/83009
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/li
I remove the "needs info" status because the last request was answered.
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: Needs Info => Confirmed
--
BUG: soft lockup detected on CPU#0!
https://launchpad.net/bugs/83009
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://l
This seems to be a bug in the sky2 network driver.
I have the same on a Gigabyte P695-DS4 rev3.3 motherboard with a Marvel
8056 chip. The higher the network traffic, the higher the probability
for the crash.
** Bug watch added: Linux Kernel Bug Tracker #7546
http://bugzilla.kernel.org/show_bug
OK, so here goes. I've been futzing around with my wireless NIC
recently, and looks to me like the rt61(pci) module might have something
to do with the hang (I'm just guesstimating but the presence of the
driver seems to correlate with the hangs).
The lsmod is taken some fifteen minutes prior to t
Yes, lsmod before the hang should be okay.
Also have you observed any pattern to the hangs? Does it always occur
at roughly the same time after booting? Are you doing a lot of network
I/O just before or whilst the hang takes place? Any information along
those lines would be helpful.
--
BUG: s
I'll see what I can do about it after work today, but I think that it's
going to be a wee bit difficult, since the lockup literally locks my
system up.
I don't think that any new modules are loaded when the bug manifests, so
I could save the lsmod output and then try to reproduce it?
--
BUG: sof
Could you also attach the output of "lsmod" after you see this problem?
Thanks!
Kyle
** Changed in: linux-source-2.6.20 (Ubuntu)
Assignee: (unassigned) => Kyle McMartin
Status: Confirmed => Needs Info
--
BUG: soft lockup detected on CPU#0!
https://launchpad.net/bugs/83009
--
ubu
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: Unconfirmed => Confirmed
--
BUG: soft lockup detected on CPU#0!
https://launchpad.net/bugs/83009
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Attachment added: "lspci -vv"
http://librarian.launchpad.net/6456295/lspci.txt
--
BUG: soft lockup detected on CPU#0!
https://launchpad.net/bugs/83009
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Attachment added: "cat /proc/cpuinfo"
http://librarian.launchpad.net/6456296/cpuinfo.txt
--
BUG: soft lockup detected on CPU#0!
https://launchpad.net/bugs/83009
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Happens to me on 2.6.20-8.
Feb 16 07:25:58 reactor kernel: [ 628.004000] BUG: soft lockup detected on
CPU#0!
Feb 16 07:25:58 reactor kernel: [ 628.004000] [softlockup_tick+156/240]
softlockup_tick+0x9c/0xf0
Feb 16 07:25:58 reactor kernel: [ 628.004000] [update_process_times+51/128]
update_
** Changed in: linux-restricted-modules-2.6.20 (Ubuntu)
Sourcepackagename: linux-restricted-modules-2.6.20 => linux-source-2.6.20
--
BUG: soft lockup detected on CPU#0!
https://launchpad.net/bugs/83009
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/li
14 matches
Mail list logo
