Re: msk Marvell Yukon 88E8038 hangs

On Sun, Jan 18, 2009 at 05:10:02AM -0500, Kim Culhan wrote:
 > On Sun, Jan 11, 2009 at 1:31 AM, Pyun YongHyeon <pyunyh_at_gmail.com> wrote:
 > > On Sat, Jan 10, 2009 at 08:19:50AM -0500, Kim Culhan wrote:
 > >  > On Fri, Jan 9, 2009 at 10:18 PM, Pyun YongHyeon <pyunyh_at_gmail.com> wrote:
 > >  > > On Fri, Jan 09, 2009 at 03:43:38PM -0500, Kim Culhan wrote:
 > >  > >  > On Fri, Jan 9, 2009 at 1:10 AM, Pyun YongHyeon <pyunyh_at_gmail.com> wrote:
 > >  > >  > > On Thu, Jan 08, 2009 at 11:35:28AM -0500, Kim Culhan wrote:
 > >  > >  > >  > On Thu, Jan 8, 2009 at 2:51 AM, Pyun YongHyeon <pyunyh_at_gmail.com> wrote:
 > >  >
 > >  > >  > > Ok, then how about disabling TSO/Tx checksum offload?
 > >  > >  > > (eg. ifconfig msk0 -tso -txcsum)
 > >  > >  >
 > >  > >  > This stops the messages: in_cksum_skip: out of data by 56952
 > >  > >
 > >  > > Ok, would you try attached patch?
 > >  >
 > >  > With the patch there are no in_cksum_skip messages
 > >  >
 > >
 > > Thanks for testing!
 > >
 > >  > a cvsup session still has:
 > >  > Network write failure: Connection timed out
 > >  >
 > >
 > > That's odd, I can't reproduce this on my box. If you disable Tx
 > > checksum offload of msk(4), cvsup session completes without
 > > problems?
 > > When cvsup plains network errors, can you still send/receive
 > > packets with msk(4)?
 > 
 > Sorry for the noise re: Network write failure
 > 
 > This was caused by an unrelated network problem.
 > 

Thanks for feedback.

 > Thanks for the patch, this fixes the complaints: in_cksum_skip: out of data
 > 
 > The present dmesg is:
 > 
 > Jan 17 18:11:01 lapster kernel: mskc0: <Marvell Yukon 88E8038 Gigabit
 > Ethernet> port 0x2000-0x20ff mem 0xd0100000-0xd0103fff irq 16 at
 > device 0.0 on pci2
 > Jan 17 18:11:01 lapster kernel: msk0: <Marvell Technology Group Ltd.
 > Yukon FE Id 0xb7 Rev 0x01> on mskc0
 > Jan 17 18:11:01 lapster kernel: can't re-use a leaf (jabbers)!
 > Jan 17 18:11:01 lapster kernel: msk0: disabling jumbo frame support
 > Jan 17 18:11:01 lapster kernel: msk0: Ethernet address: 00:1b:24:59:5b:7a
 > Jan 17 18:11:01 lapster kernel: miibus0: <MII bus> on msk0
 > Jan 17 18:11:01 lapster kernel: e1000phy0: <Marvell 88E3082 10/100
 > Fast Ethernet PHY> PHY 0 on miibus0
 > Jan 17 18:11:01 lapster kernel: e1000phy0:  10baseT, 10baseT-FDX,
 > 100baseTX, 100baseTX-FDX, auto
 > Jan 17 18:11:01 lapster kernel: mskc0: [FILTER]
 > 
 > The problem with msk not working with ACPI enabled is well known, is
 > there anything
 > I can do to get this working?
 > 

Sorry, I have no idea. freebsd-acpi_at_ would be more appropriate
list.

-- 
Regards,
Pyun YongHyeon