Re: msk watchdog timeout - FreeBSD

This is a discussion on Re: msk watchdog timeout - FreeBSD ; -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, Oct 15, 2008 at 09:34:40PM +0900, Pyun YongHyeon wrote: > On Wed, Oct 15, 2008 at 02:22:34PM +0200, Koen Martens wrote: > > The problem occurs under load (rsyncing tens of gigabytes ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Re: msk watchdog timeout

  1. Re: msk watchdog timeout

    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA1

    On Wed, Oct 15, 2008 at 09:34:40PM +0900, Pyun YongHyeon wrote:
    > On Wed, Oct 15, 2008 at 02:22:34PM +0200, Koen Martens wrote:
    > > The problem occurs under load (rsyncing tens of gigabytes over
    > > gigabit link for example). I tried configuring the switch port
    > > down to 100MB, in the hopes that msk0 would be more stable. It
    > > is, but it still goes down after a while with watchdog timeouts.
    > >
    > > I am now running it with msi disabled, it appears it lasts longer
    > > than before now. But judging by what others said on this subject
    > > already, it might still go wrong after as much as a month.
    > >
    > > Also, I've never had these problems when the machine was still
    > > on 6.x with the myk driver. Only after I upgraded it this tuesday
    > > to RELENG_7, trouble started.
    > >
    > > This is a server that I need to put back into production. I could
    > > give you some time on it before I do that, but that'd have to be
    > > *right now* so i guess that won't work out really.
    > >
    > > I'll probably install a nic to be used instead of the built-in
    > > yukon interface, to get back the required stability.
    > >

    >
    > I'm not sure whether 88E8050 also has RAM buffer. Youkon
    > controllers seems to have silicon bugs for hardwares with RAM
    > buffer. msk(4) in HEAD has workaround code for the silicon bug.
    > Would you try latest msk(4) from HEAD?(Just copy
    > if_msk.c/if_mskreg.h from HEAD to your box and rebuild kernel.)
    > Also show me verbosed boot message(msk(4) related one would be
    > enough).


    No dice, compile bails out:

    o-pointer-sign -fformat-extensions -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror /usr/src/sys/dev/msk/if_msk.c
    /usr/src/sys/dev/msk/if_msk.c:845:50: error: macro "MEXTADD" passed 8 arguments, but takes just 7
    /usr/src/sys/dev/msk/if_msk.c: In function 'msk_jumbo_newbuf':
    /usr/src/sys/dev/msk/if_msk.c:844: error: 'MEXTADD' undeclared (first use in this function)
    /usr/src/sys/dev/msk/if_msk.c:844: error: (Each undeclared identifier is reported only once
    /usr/src/sys/dev/msk/if_msk.c:844: error: for each function it appears in.)
    *** Error code 1

    Stop in /usr/obj/usr/src/sys/GENERIC.
    *** Error code 1

    Stop in /usr/src.
    *** Error code 1

    Stop in /usr/src.
    postel#

    I'll have to get back to you about the verbose boot, as i have no remote
    console on that machine.

    Thanks,

    Koen

    - --
    K.F.J. Martens, Sonologic, http://www.sonologic.nl/
    Databases, wiki-expertise, hosting, server- en infrabeheer.
    Public PGP key: http://www.metro.cx/pubkey-gmc.asc
    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.7 (GNU/Linux)

    iD8DBQFI9fajktDgRrkFPpYRAhMPAJ9SRqS3R0/YSErjSaiS0hc+m5HBOwCbBaTk
    HgSPcihKuvvLTMJtlL6LrIg=
    =5Au9
    -----END PGP SIGNATURE-----
    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/lis...reebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"


  2. Re: msk watchdog timeout

    On Wed, Oct 15, 2008 at 03:56:52PM +0200, Koen Martens wrote:
    > -----BEGIN PGP SIGNED MESSAGE-----
    > Hash: SHA1
    >
    > On Wed, Oct 15, 2008 at 09:34:40PM +0900, Pyun YongHyeon wrote:
    > > On Wed, Oct 15, 2008 at 02:22:34PM +0200, Koen Martens wrote:
    > > > The problem occurs under load (rsyncing tens of gigabytes over
    > > > gigabit link for example). I tried configuring the switch port
    > > > down to 100MB, in the hopes that msk0 would be more stable. It
    > > > is, but it still goes down after a while with watchdog timeouts.
    > > >
    > > > I am now running it with msi disabled, it appears it lasts longer
    > > > than before now. But judging by what others said on this subject
    > > > already, it might still go wrong after as much as a month.
    > > >
    > > > Also, I've never had these problems when the machine was still
    > > > on 6.x with the myk driver. Only after I upgraded it this tuesday
    > > > to RELENG_7, trouble started.
    > > >
    > > > This is a server that I need to put back into production. I could
    > > > give you some time on it before I do that, but that'd have to be
    > > > *right now* so i guess that won't work out really.
    > > >
    > > > I'll probably install a nic to be used instead of the built-in
    > > > yukon interface, to get back the required stability.
    > > >

    > >
    > > I'm not sure whether 88E8050 also has RAM buffer. Youkon
    > > controllers seems to have silicon bugs for hardwares with RAM
    > > buffer. msk(4) in HEAD has workaround code for the silicon bug.
    > > Would you try latest msk(4) from HEAD?(Just copy
    > > if_msk.c/if_mskreg.h from HEAD to your box and rebuild kernel.)
    > > Also show me verbosed boot message(msk(4) related one would be
    > > enough).

    >
    > No dice, compile bails out:
    >
    > o-pointer-sign -fformat-extensions -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror /usr/src/sys/dev/msk/if_msk.c
    > /usr/src/sys/dev/msk/if_msk.c:845:50: error: macro "MEXTADD" passed 8 arguments, but takes just 7
    > /usr/src/sys/dev/msk/if_msk.c: In function 'msk_jumbo_newbuf':
    > /usr/src/sys/dev/msk/if_msk.c:844: error: 'MEXTADD' undeclared (first use in this function)
    > /usr/src/sys/dev/msk/if_msk.c:844: error: (Each undeclared identifier is reported only once
    > /usr/src/sys/dev/msk/if_msk.c:844: error: for each function it appears in.)
    > *** Error code 1
    >
    > Stop in /usr/obj/usr/src/sys/GENERIC.
    > *** Error code 1
    >
    > Stop in /usr/src.
    > *** Error code 1
    >
    > Stop in /usr/src.
    > postel#
    >
    > I'll have to get back to you about the verbose boot, as i have no remote
    > console on that machine.
    >


    Oops! Sorry, I forgot there is difference in jumbo frame buffer
    handling. Try attached patch and show me verbosed boot message.

    --
    Regards,
    Pyun YongHyeon

    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/lis...reebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

+ Reply to Thread