** Changed in: linux
Importance: Unknown => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/83009
Title:
sky2 transmit timeout and soft lockup detected on CPU#0!
--
ubuntu-bugs mailing list
According to the last comment about updating the firmware solving the
problem, I am closing this bug.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
sky2 transmit timeout and soft lockup detected on CPU#0!
https://bugs.launchpad.net/bugs/83009
You received this bug notifi
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
I found the 'transmit timed out' issue solved totally by moving from
firmware 1.9 to 2.2 on my 88E8053; others have reported success with
firmware updates to their 8056 NICs also. Contact your motherboard
vendor for the update.
You can find the current firmware version using:
http://www.marvell.co
Hello, I'm experiencing a similar problem with my 88E8053
I read there's a fix released. How do I apply the patch? I have Ubuntu
Feisty up to date and using the linux kernel 2.6.20-16-generic.
I never notice this problem until lately that I've been trying to
transmit big files over samba or using
** Changed in: linux (upstream)
Status: Invalid => Fix Released
--
sky2 transmit timeout and soft lockup detected on CPU#0!
https://bugs.launchpad.net/bugs/83009
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bu
At least the sky2-tx-kick.patch applies fine to the 2.6.20 kernel. But I
can't test it, because currently I don't have access to a sky2 network
controller.
--
sky2 transmit timeout and soft lockup detected on CPU#0!
https://bugs.launchpad.net/bugs/83009
You received this bug notification because
The upstream bug report is now being shown as Resolved Code_Fix. Is
this something we can see backported to 2.6.20 or do we need to wait
until Gutsy to get the fix in?
Thanks!
--
sky2 transmit timeout and soft lockup detected on CPU#0!
https://bugs.launchpad.net/bugs/83009
You received this bu
** Changed in: linux (upstream)
Status: In Progress => Invalid
--
sky2 transmit timeout and soft lockup detected on CPU#0!
https://bugs.launchpad.net/bugs/83009
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bug
I am experiencing similar problems. I downloaded Marvell's sk98lin
driver, compiled and installed without problems besides those already
mentioned (headers symbolic link and #!/bin/bash).
Perhaps related is my inability to resume from S3 via wake on lan using
other ethernet card - nvidia gige on m
Hello, i had the same Problem with a Marvell ethernet controller.
Bevore reading this bug-thread i made a upgrade from edgy to feisty but the
problem still occurs every few hours.
I installed the driver from
http://www.marvell.com/drivers/driverDisplay.do?dId=153&pId=36 as by Andreas
Simon descr
** Changed in: linux-source-2.6.20 (Ubuntu)
Assignee: Tim Gardner => Ubuntu Kernel Team
Target: None => later
--
sky2 transmit timeout and soft lockup detected on CPU#0!
https://bugs.launchpad.net/bugs/83009
You received this bug notification because you are a member of Ubuntu
Bugs,
Tim, thank you for your work. Sadly, like Darren, I too encountered
soft-lockups with that sky2.ko.2.6.20-14 (as with a complete vanilla
2.6.21-rc6 kernel). It's slightly better with this version. Removing the
module and reloading it again makes the network work again. With earlier
versions of the
It would be weird if it was related to network equipment behind the NIC.
Before Feisty (i.e. Edgy) network connectivity would work basically
flawless.
I am usually able to get connectivity back after unplugging and
replugging the physical connection. The network-manager will detect this
and will r
I can take a look at grabbing a new switch gig switch tomorrow, the NIC
is on a MAC Mini but the unit itself is well ventilated.
--
sky2 transmit timeout and soft lockup detected on CPU#0!
https://bugs.launchpad.net/bugs/83009
You received this bug notification because you are a member of Ubuntu
I would be interesting to change switches, though a 100Mbit switch is
much less stressful. Also make sure your network adapter is well
ventilated.
--
sky2 transmit timeout and soft lockup detected on CPU#0!
https://bugs.launchpad.net/bugs/83009
You received this bug notification because you are
Unfortunately it still seemed to crash, after copying about 9 gigs back
and forth I lost all network connectivity. Removing the sky2 driver
and adding it back brought it back to life.
Is there a chance it is related to the cheap switch I am using? I have
an off the shelf D-link gig switch. I c
I just grabbed it, I can generally trigger it with 4-5 gigs back and
forth over smb or SSH so I will try that now.
Thank you!
--
sky2 transmit timeout and soft lockup detected on CPU#0!
https://bugs.launchpad.net/bugs/83009
You received this bug notification because you are a member of Ubuntu
B
** Changed in: linux-source-2.6.20 (Ubuntu)
Assignee: Ubuntu Kernel Team => Tim Gardner
--
sky2 transmit timeout and soft lockup detected on CPU#0!
https://bugs.launchpad.net/bugs/83009
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Uh, be sure to save your original sky2.ko before running 'wget'.
--
sky2 transmit timeout and soft lockup detected on CPU#0!
https://bugs.launchpad.net/bugs/83009
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mai
I back ported sky2 from 2.6.21-rc6. Lets see if it helps:
cd /lib/modules/2.6.20-14-generic/kernel/drivers/net
sudo wget -O sky2.ko http://people.ubuntu.com/~rtg/sky2.ko.2.6.20-14
sudo modprobe -r sky2
sudo modprobe sky2
Please attach dmesg output if you continue to have failures.
--
sky2 trans
In the meantime I encountered several soft lockups with linux image
2.6.20-14.22 too. It seems this bug is not fixed with tha latest sky2
upstream changes.
Currently I test the Yukon driver (sk98lin) from Marvell, which can be
downloaded from http://www.marvell.com/drivers/driverDisplay.do?dId=1
I was copying around 4 gigs of files over SMB and experienced the sky2
hang today. I am running 2.6.20-14
--
sky2 transmit timeout and soft lockup detected on CPU#0!
https://bugs.launchpad.net/bugs/83009
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bu
Sky2 upstream updates will appear in the 2.6.20-14 kernel. Check the
daily ISO at http://cdimage.ubuntu.com/daily-live/current on April 2.
--
sky2 transmit timeout and soft lockup detected on CPU#0!
https://launchpad.net/bugs/83009
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https
Lauri, it could also be that your problem is a different one. At least
some lockups seems to be highly related to sky2 and network traffic.
Anyway, since the 3 days I run linux-image-2.6.20-13-generic version
2.6.20-13.21 I haven't encountered any new lockups. Maybe the problem is
already fixed in
Doesn't seem to be exclusively a sky2 issue since as far as I can tell,
I've never run that specific driver (in fact, I suspect the culprit to
be the rt61(pci) driver in my case).
--
sky2 transmit timeout and soft lockup detected on CPU#0!
https://launchpad.net/bugs/83009
--
ubuntu-bugs mailin
** Summary changed:
- BUG: soft lockup detected on CPU#0!
+ sky2 transmit timeout and soft lockup detected on CPU#0!
--
sky2 transmit timeout and soft lockup detected on CPU#0!
https://launchpad.net/bugs/83009
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/
27 matches
Mail list logo
