em/amd64 on 6.0-RC1

From: Danny Braniss (danny_at_cs.huji.ac.il)
Date: 10/24/05

  • Next message: Peter Holm: "inodes and soft update [FIXED]" 
    To: freebsd-current@freebsd.org
Date: Mon, 24 Oct 2005 12:26:02 +0200

    I have been running this box (an Intel SR1435VP2/Xeon-NOCOMA), of which
    we have 6, under several different configurations to try and pin down
    some problems, initialy I suspected am-utils, but now it's almost certain
    the if_em. The problem is sometimes on i386, but always on amd64.

    it seems that the problem starts right after the em is re-initialized, after
    it was used via PXE to boot. Sniffing shows that the kernel sends
    a GETATTR, the server responds, but the client does not see it, and
    after some time it will resend, and so on ...

    pinging from the server to the client works.

    btw, booting off the local disk (not diskless/PXE) em works fine, though
    the logs seems a bit baffling:

            ...
            em0: no link ... got link
            DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 3
            DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 8
            DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 9
            DHCPOFFER from 132.65.16.10
            unknown dhcp option value 0xfc
            DHCPREQUEST on em0 to 255.255.255.255 port 67
            DHCPACK from 132.65.16.10
            unknown dhcp option value 0xfc
            bound to 132.65.16.104 -- renewal in 7200 seconds.

            lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
                    inet6 ::1 prefixlen 128
                    inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2

            em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
                    options=b<RXCSUM,TXCSUM,VLAN_MTU>
                    inet6 fe80::20e:cff:fe6a:8973%em0 prefixlen 64 scopeid 0x1
                    inet 132.65.16.104 netmask 0xfffff000 broadcast 132.65.31.255
                    ether 00:0e:0c:6a:89:73
                    media: Ethernet autoselect
                    status: no carrier
            **************** HU? *************

    later on, ifconfig em0 shows that all is ok.

    danny

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

  • Next message: Peter Holm: "inodes and soft update [FIXED]"

    Relevant Pages

    • Windows Server 2003 - Shared Fax - Long Distance Dialing Rules
      ... I have installed Faxing on a Server 2003 for inbound faxing...all worked great. ... Now I am trying to get an XP Pro client to send faxes via the shared fax. ... Then came dialing rules. ... to the calling card stuff for PIN. ...
      (microsoft.public.windowsxp.print_fax)
    • Re: Joining client to domain
      ... I was checking messages and came across this post, because I have ran MS virtual PC on many occasions to test for configurations or beta testing (just recently server 2008) and I was wondering if I could add my 2 cents. ... However when you try to join the workstation (assuming that is what you are calling your client pc), have you tried just entering the domain controller name only. ... Click More to change the primary Domain Name System (DNS) suffix. ...
      (microsoft.public.cert.exam.mcsa)
    • RE: 802.1X configuration for IAS and Cisco WLC 4402
      ... these docs are describing several configurations and when you start ... addition to the server authenticating the client/user, ... server must have a server certificate that meets the minimum server ... client computers must be configured to ...
      (microsoft.public.internet.radius)
    • Re: Win XP FAX SERVICE MISSING CONTACTS
      ... > server, for security reasons the final destination number wont be displayed. ... >> Now I am trying to get an XP Pro client to send faxes via the shared fax. ... Then came dialing rules. ... >> to the calling card stuff for PIN. ...
      (microsoft.public.windowsxp.print_fax)
    • Re: Windows Server 2003 - Shared Fax - Long Distance Dialing Rules
      ... When you fax through Remote Server, ... > Now I am trying to get an XP Pro client to send faxes via the shared fax. ... Then came dialing rules. ... > to the calling card stuff for PIN. ...
      (microsoft.public.windowsxp.print_fax)