[sky2] Marvell ethernet interface doesn' t work after reboot

This is also true for Toshiba Tecra A4, which has pretty much identical network card.

Just noticed this in my dmesg output:

sky2 0000:02:00.0: No interrupt was generated using MSI, switching t o INTx mode. Please report this failure to the PCI maintainer and include system chipset information.

Additional info: When installing, I get no error messages but am unable to pull an IP from my Marvell ethernet interface (eth0).

Sky2 version 1.1 is broken because MSI (Message Signaled Interrupt) support was enable by default and it was causing weird behaviour.
Ben Collins has backported the sky2 driver 0.15 from 2.6.16.13. It will be in the next kernel upload. it should fix this bug.
Please test when it is available and let us know.

Do you need to be fixed also in Breezy?

Wonderful, when is the next Dapper daily image going to be pushed out?

Or rather, is this fix in the current dapper Daily Image for May 15 or do we need to wait another day?

Angelo Lisco wrote:
> Do you need to be fixed also in Breezy?
>
> ** Changed in: linux-source-2.6.15 (Ubuntu Breezy)
> Status: Unconfirmed => Needs Info
>

Personally, no.

This has not resolved the issue for my Toshiba Tecra A4 with a Marvell Yukon Gigabite network card. I am still unable to pull an IP at install. Dmesg looks good, but I just can't get an IP. This is not a network issue, I can immediately grab an IP on my other Dapper daily test setup.

sky2 eth0: enabling interface
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control none

But I did find this earlier in the output:

sky2 v1.1 addr 0xbc000000 irq 11 Yukon-EC (0xb6) rev 1
sky 2 eth0: addr <my MAC address>
sky2 0000:02:00.0: No interrupt was generated using MSI, switching to INTx mode. Please report this failure to th PCI maintainer and include system chipset information.

This has not been fixed in Dapper yet. Is there any reason why it was marked as Fixed?

Ensure you're using kernel 2.6.15-23 which include the new driver (version 0.15)...

I am using the most recent dapper daily build with no luck.

Greg, can you attach the output of 'uname -r' and 'modinfo sky2 | grep version', please?

> uname -r
2.6.15-23-386

> modinfo sky2 | grep version
/bin/sh: modinfo: not found

Never got far enough into the installer to get modinfo it appears.

Also of note, I'm now getting a ton of errors that look like this before the output I mentioned a few replies ago:

[4294879.9870000] ACPI-0517: *** Error: Method parse/execution failed [\_SB_.RDEC] (Node dfff22e0), AE_AML_MUTEX_NOT_ACQUIRED
[4294879.0470000] ACPI-0240: *** Error: Cannot release Mutex [MUT1], not acquired

It looks like the interface went down before this happened. The interface came back up, and I get another round of the MUTEX errors, but no notification that the interface is down again.

When I say the interface came up, I do not mean pull an IP. I still can't pull an IP at all and never have been able to.

This isn't fixed, see reply.

I confirm it's not fixed.

$ uname -r

2.6.15-23-686

$ modinfo sky2 | grep version
version: 0.15
srcversion: 93714536D12639FF916A2AA

I'm not seeing the ACPI messages Greg reports above.

Windows XP hangs a few seconds into a warm boot.

Setting back to unconfirmed because there are no outstanding requests for reporter information.

This really needs attention, the existing is still outstanding and doesn't appear to be even be acknowledged. I'd get some dmesg output to you, but it seems like my USB controller is bugged too. Filing another report for that.

Is there anything further I can provide to help debug this?

I have a Toshiba Tecra laptop and have no network connectivity with the Marvell NIC running sky2 driver version 0.15.

I installed Kubuntu 6.06 (kernel 2.6.15-23-686 (system is dual boot with WinXP). I can't get it to work even with a cold boot. I don't see the ACPI error messages either.

Ethtool reports no link even though I am connected to my router.

Everything works fine in Windows.

Out of curiousity, what kind of Tecra do you have, Ayaz?

I have the same NIC in an AOpen XC Cube. I have been unable to use the latest Dapper kernel for a few weeks now ever since the last kernel update (booting into 2.6.15-22-k7 works OK for a few days and then dies). I presume if I ever try installing Dapper directly on this system networking will be unavailable as this bug was introduced with the last update before release as far as I can tell. If there is any info I can provide to help resolve this, let me know.

Greg,
I have a Toshiba Tecra M3 system.

I resolved this by doing the following:

#1) Boot with pci=noacpi and irqpoll
#2) This will make your ethernet and USB drives work. You can then apt-get update and dist-upgrade to get the latest kernel.
#3) Restart, upgrade your BIOS to 1.70. This gets around a measure that forces pci=noacpi for BIOS version 1.60 which actually appears to make things worse.
#4) Restart, enjoy ethernet and USB.

I will post this on the Toshiba Tecra A4 page at http://wiki.ubuntu.com/LaptopTestingTeam/ToshibaTecraA4

The original problem I reported is half-resolved with kernel 2.6.15-25 (386 and 686) and sky2 driver version 1.4. After rebooting Ubuntu, the interface works fine.

However, the interface doesn't work with a warm boot of Windows XP after shutting down Ubuntu. Of course, it could be argued this is a problem with Windows, but fair's fair: the problem doesn't happen in reverse, i.e., the interface works with a wam boot of Ubuntu after shutting down Windows.

Can you attach the output of sudo dmidecode to this bug? Thanks

chuck

dmidecode output for Tecra M3

Greg,

I updated the kernel and now my ethernet is working fine from cold boot. I have not yet updated my BIOS.

Thanks!

I upgraded to Dapper and both ethhernet cards stopped working (one integrated and one d-links card), with linux-image-2.6.12-9-386 and sk98lin module they work. I tried removing the sky2 module and insmodding sk98lin but that didn't help either, I tried removing the second card and with disabling the integrated card from the BIOS. I also tried with pci=noacpi and irqpoll.

The motherboard is ASUS A8V-E SE and it has this card integrated;
0000:05:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8053 Gigabit Ethernet Controller (rev 19)
the D-Link is DGE-530T, I'm attaching the dmidecode output.

I hope that this gets fixed since I have to use the older kernel now to get any work done and the sound card stopped working with the old kernel after the upgrade (it works with the new kernel)

as promiced earlier

Using Marvell's driver will probably fix the problem. You can take a look at this bug: https://launchpad.net/distros/ubuntu/+source/linux-source-2.6.15/+bug/38865 It explains how to install the driver.

I have a Toshiba Tecra A3 and since I re-installed the sk98lin driver from Marvell, my connection works perfectly. Because I must install the driver manually, I don't shut my laptop down and it's been 1 week now and everything is still fine.

I hope it helps.

Etienne:

Somewhat strangely the sound card started working with the older kernel when I used modprobe to install the snd_via82xx module, insmod gave error about unknown symbol in the module (some kind of a problem with new module-init-tools?) ... and then used alsamixer to remove the mutes from Master and PCM.

Here is a dmesg, it seems that one of the cards (the one integrated to the motherboar) uses skge and the one in PCI-slot sk98lin, go figure ...

[4294774.165000] sk98lin: Network Device Driver v8.23.1.3
[4294774.165000] (C)Copyright 1999-2005 Marvell(R).
[4294774.182000] ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 36 (level, low) -> IRQ 36
[4294774.199000] PCI: Setting latency timer of device 0000:05:00.0 to 64
[4294774.263000] eth1: Marvell Yukon 88E8053 Gigabit Ethernet Controller
[4294774.272000] PrefPort:A RlmtMode:Check Link State
[4294785.683000] eth1: network connection up using port A
[4294785.683000] speed: 1000
[4294785.683000] autonegotiation: yes
[4294785.683000] duplex mode: full
[4294785.683000] flowctrl: symmetric
[4294785.683000] role: slave
[4294785.683000] irq moderation: disabled
[4294785.683000] tcp offload: enabled
[4294785.683000] scatter-gather: enabled
[4294785.683000] tx-checksum: enabled
[4294785.683000] rx-checksum: enabled
[4294785.683000] rx-polling: enabled
[4294794.297000] eth1: no IPv6 routers present
[4294814.398000] skge eth0: enabling interface
[4294816.828000] skge eth0: Link is up at 1000 Mbps, full duplex, flow control tx and rx
[4294824.555000] eth0: no IPv6 routers present

I'll try the driver next week (important deadline on Friday and weekend for the last fixes :-).

2.6.15-26.47 has fixed the problem. After booting from Linux to Windows and from Linux to Linux, the interface works fine. Thanks!

2.6.15-27-686 has reverted to earlier behaviour. Warm booting to Linux from Linux works fine, but when warm booting to Windows, the interface isn't detected.

Everything looks fine in Edgy.

[Expired for linux-source-2.6.15 (Ubuntu) because there has been no activity for 60 days.]