panic doing remote buildworld w/nve

From: Joel Diaz (joeldiaz_at_nc.rr.com)
Date: 05/30/05

  • Next message: Ed Maste: "SMP, DEVICE_POLLING and fxp LOR" 
    To: freebsd-current@freebsd.org
Date: Mon, 30 May 2005 09:22:32 -0400

    I'm consistently getting a panic doing a buildworld through SSH.
    This is using CURRENT from maybe 10 hours ago (built on the
    console). For the past few days I've been using the onboard nve
    network card on my nForce(2?) board. Previously I used a card that
    used the rl driver and I never ran into any problems. Here's the trace:

    cpuid = 0
    KDB: enter: panic
    [thread pid 721 tid 100076 ]
    Stopped at kdb_enter+0x2b: nop
    db> trace
    Tracing pid 721 tid 100076 td 0xc2328e10
    kdb_enter(c0651992) at kdb_enter+0x2b
    panic(c064619d,c0639f38,c23460fc,2,e8cc0114) at panic+0x127
    nve_ifstart(c2346000) at nve_ifstart+0x366
    if_start(c2346000) at if_start+0x7b
    ether_output_frame(c2346000,c25f0b00,0,0,0) at ether_output_frame+0x1d9
    ether_output(c2346000,c25f0b00,e8cb5ab4,c26d8c60,c260e200) at
    ether_output+0x370
    ip_output(c25f0b00,0,e8cb5ab0,0,0) at ip_output+0x6fc
    tcp_output(c26ff000,1,c26fd9d8,0,40) at tcp_output+0xdf8
    tcp_usr_send(c26d567c,0,c25f2600,0,0) at tcp_usr_send+0x177
    sosend(c26d567c,0,e8cb5c78,c25f2600,0) at sosend+0x5e7
    soo_write(c264c4c8,e8cb5c78,c26bba00,0,c2328e10) at soo_write+0x46
    dofilewrite(c2328e10,c264c4c8,3,807e000,40) at dofilewrite+0xa8
    write(c2328e10,e8cb5d04,3,ca,206) at write+0x39
    syscall(3b,3b,3b,bfbfde78,806edc8) at syscall+0x22b
    Xint0x80_syscall() at Xint0x80_syscall+0x1f
    --- syscall (4, FreeBSD ELF32, write), eip = 0x282b875b, esp =
    0xbfbfdddc, ebp = 0xbfbfddf8 ---db>

    Joel
    _______________________________________________
    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: Ed Maste: "SMP, DEVICE_POLLING and fxp LOR"

    Relevant Pages

    • Re: "Invalid Connection Data" Message XBOX 360 acting as an MCE
      ... This can be caused by the router or network card. ... Once these are set please connect the PC to the Xbox, start a netcap trace ... The capture using netcap has been sent. ... Install the Windows XP Service Pack 2 Support Tools from the ...
      (microsoft.public.windows.mediacenter)
    • Re: "Invalid Connection Data" Message XBOX 360 acting as an MCE
      ... I sent a second trace that I took with the XBOX and MCE PC direct connected. ... I figured you would want to eliminate the router. ... This can be caused by the router or network card. ...
      (microsoft.public.windows.mediacenter)
    • Re: "Invalid Connection Data" Message XBOX 360 acting as an MCE
      ... The network trace is reporting TCP checksum issues when attempting to ... This can be caused by the router or network card. ... Once these are set please connect the PC to the Xbox, start a netcap trace ... Install the Windows XP Service Pack 2 Support Tools from the ...
      (microsoft.public.windows.mediacenter)
    • rtmutex assert failure (was [Patch] restore the RCU callback...)
      ... just a single line reported to the machine's console (and not on the ... I'll come up with a patch tomorrow to try and get a clean stack trace. ... so I'll be around for a little while longer, hopefully longer. ...
      (Linux-Kernel)
    • Problem after removing old kernel packages
      ... modules, network card etc, except a few of them, like ext3, ext2, ... but mount /dev/fd0 complains that /dev/fd0 isn't a block ... So I have no way of attaching a dmesg to this message, ... screen and console view a few times, then I'm able to log in normally ...
      (Debian-User)