Project

General

Profile

Actions

Bug #1445

closed

Trouble with interface msk0 (Marvell Yukon 88E8057 Gigabit Ethernet)

Added by Malte Stretz over 13 years ago. Updated almost 5 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Interfaces
Target version:
-
Start date:
04/17/2011
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.0
Affected Architecture:

Description

This is a follow-up to bug 1444. Installed via pfSense-memstick-2.0-RC1-i386-20110417-0359.img.gz.

As described in bug 1444 after the first boot I wasn't able to get a DHCP lease from the LAN interface which I set to the on-board interface (see attached dmesg.txt). After battling bug 1444 and a reboot, I was able to access the WebUI without problems. I set up msk0 as OPT1 with the IP 192.168.2.1, a DHCP server and pass-all firewall rules. And again, I could neither get a lease from there nor ping the machine.

It is a Gigabit interface which is connected to a cheap 100 MBit switch; auto-negotiation looks fine (see attached ifconfig.txt), dhcp server is running (see attached ps-axfu.txt). Looks like there are some driver trouble with this chipset?

The system is a Lenovo ThinkCentre A58 (7515-79G).


Files

ifconfig.txt (1.45 KB) ifconfig.txt Malte Stretz, 04/17/2011 11:26 AM
dmesg.txt (37.5 KB) dmesg.txt Malte Stretz, 04/17/2011 11:26 AM
ps-axfu.txt (5.31 KB) ps-axfu.txt Malte Stretz, 04/17/2011 11:26 AM
config-pfSense.localdomain-20110417181349.xml (14.5 KB) config-pfSense.localdomain-20110417181349.xml Malte Stretz, 04/17/2011 11:26 AM
Actions #1

Updated by Chris Buechler over 13 years ago

  • Status changed from New to Rejected

not convinced that's a driver problem, sounds like it may be config related, but if it is, not something we can fix. We don't control or write drivers.

Actions #2

Updated by Per Møller Olsen over 13 years ago

I am having problems too with the msk0 Marvell Yukon Gigabit on an iMac.

I will get a watchdog timeout on that interface. When the interface was configured as LAN it would drop the connection once or twice a day. To day I tried to reconfigure the msk0 to be WAN and now it drops the connection once or twice an hour.

WHEN the msk0 works, everything is running perfectly.
Rebooting the system helps right away - until the problem reoccurs.

The other interface works perfect in both LAN and WAN (Apple USB-Ethernet adaptor).

Actions #3

Updated by Warren Baker over 13 years ago

There is a driver bug logged, have a look at http://www.freebsd.org/cgi/query-pr.cgi?pr=156493 - otherwise one person recommends forcing it to 100M and disabling auto-negotiation which seems to have worked for them. So you can try that.

Actions #4

Updated by George M over 13 years ago

I have the problem too with the RC3 version of pfsense, according to

http://freebsd.1045724.n5.nabble.com/msk0-interface-stops-working-when-downloading-td3910881.html

the msk driver works in the FreeBSD version 8.2 but not in 8.1.

Actions #5

Updated by Chris Buechler over 9 years ago

  • Target version deleted (2.0)
Actions

Also available in: Atom PDF