Re: Panic with nve

From: Martin MATO <martin.mato_at_wanadoo.fr>
Date: Tue, 14 Jun 2005 09:46:16 +0200
>
> I'm seeing the same thing here on my NForce 2 board.  It used to be  
> that I couldn't do a buildworld through SSH, but now I can trigger  
> the panic by simply loading up a remote X session.  After using X for  
> about a minute, I get the following:
>
> %panic: nve_ifstart: attempted use of a free mbuf!
> cpuid = 0
> KDB: enter: panic
> [thread pid 571 tid 100087 ]
> Stopped at      kdb_enter+0x2b: nop
> db> trace
> Tracing pid 571 tid 100087 td 0xc2735000
> kdb_enter(c084ebd5) at kdb_enter+0x2b
> panic(c08237f7,c080dffc,c2395100,350,e8cbaa98) at panic+0x127
> nve_ifstart(c2395000) at nve_ifstart+0x35a
> if_start(c2395000) at if_start+0x7b
> ether_output_frame(c2395000,c239ec00,0,0,0) at ether_output_frame+0x1d9
> ether_output(c2395000,c239ec00,eb12cad8,c273cbdc,c2732100) at  
> ether_output+0x3b4
> ip_output(c239ec00,0,eb12cad4,0,0) at ip_output+0x6fc
> tcp_output(c274eac8) at tcp_output+0xfb2
> tcp_usr_rcvd(c2728a60,0,c2728ac8,0,c0855428) at tcp_usr_rcvd+0x82
> soreceive(c2728a60,0,eb12cc78,0,0) at soreceive+0xc63
> soo_read(c2690ab0,eb12cc78,c2691a00,0,c2735000) at soo_read+0x41
> dofileread(c2735000,c2690ab0,3,bfbf9e40,4000) at dofileread+0xad
> read(c2735000,eb12cd04,3,2b,202) at read+0x3b
> syscall(3b,3b,3b,bfbf9e40,8078b40) at syscall+0x22f
> Xint0x80_syscall() at Xint0x80_syscall+0x1f
> --- syscall (3, FreeBSD ELF32, read), eip = 0x282bc753, esp =  
> 0xbfbf9e2c, ebp = 0xbfbfde58 ---
> db>
>
> Thanks,
> Joel Diaz
>
>
i have the same problem:
i got a panic systematically if i try  to transfert a file from an sftp 
session; from any host
i  have an abit nfs7 2.0 (Nforce2 ultra).
Received on Tue Jun 14 2005 - 05:46:28 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:36 UTC