Re: "no toe capability on..."

2008-08-02 Thread Nejc Škoberne 

Hey,


no toe capability on 0xc2e66400


Looks like this is was fixed 7/31/2008:

http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netinet/tcp_offload.c.diff?r1=text&tr1=1.4.2.1&r2=text&tr2=1.4.2.2

That was fast!

Bye,
Nejc
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: "no toe capability on..."

2008-08-01 Thread Ewald Jenisch 
On Thu, Jul 31, 2008 at 09:13:29AM -0600, Warren Block wrote:
>
> Looks like it.  They're debug messages that shouldn't still be in there.  
> They were removed in version 1.2 but then reappeared in 1.4.2.1:
>
> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netinet/tcp_offload.c
> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netinet/tcp_offload.c.diff?r1=1.1;r2=1.2
> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netinet/tcp_offload.c.diff?r1=1.4;r2=1.4.2.1
>
> Thanks for locating the source of the problem.  I entered a PR (#126138)  
> but forgot to put in a pointer to your message--and now can't, since the  
> PR database claims #126138 doesn't exist.  I'll try again later.
>


Hi Warren,

Wow that was really fast - thanks much for filing a PR! 

...good to know that this message is just for debug and relatively
harmless...

Kind regards,
-ewald

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: "no toe capability on..."

2008-07-31 Thread Norberto Meijome 
On Thu, 31 Jul 2008 14:09:21 +0200
Ewald Jenisch <[EMAIL PROTECTED]> wrote:

> Hi,
> 
> Today I updated kernel & system on one of my machines (FreeBSD
> 7.0). After the update which ran absolutely smooth I'm seeing spurious
> messages both on the console and in /var/log/messages like the
> following:
> 
> no toe capability on 0xc2e66400

+1 , different address:

no toe capability on 0xc48e3800

bge0:  mem 
0xb020-0xb020 irq 16 at device 0.0 on pci2

 
> 
> Grep-ing through the sources I found the above message to come from
> /usr/src/sys/netinet/tcp_offload.c. As far as I understand this has
> something to do with TcpOffloadEngine.

yup

> 
> Please note that this is a box several years old (2GHz P4) with three
> Intel FXP FastEthernet-cards.
> 
> So here are my questions:
> 
> o) Has anybody else seen the above messages? 
> 
> o) Can they safely be ignored?
> 
> o) If not - what can I do to get rid of them?
> 

they seem harmless enough.

B

_
{Beto|Norberto|Numard} Meijome

Unix is user friendly. However, it isn't idiot friendly.

I speak for myself, not my employer. Contents may be hot. Slippery when wet. 
Reading disclaimers makes you go blind. Writing them is worse. You have been 
Warned.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: "no toe capability on..."

2008-07-31 Thread Warren Block 

On Thu, 31 Jul 2008, Ewald Jenisch wrote:


Today I updated kernel & system on one of my machines (FreeBSD
7.0). After the update which ran absolutely smooth I'm seeing spurious
messages both on the console and in /var/log/messages like the
following:

no toe capability on 0xc2e66400


Grep-ing through the sources I found the above message to come from
/usr/src/sys/netinet/tcp_offload.c. As far as I understand this has
something to do with TcpOffloadEngine.

Please note that this is a box several years old (2GHz P4) with three
Intel FXP FastEthernet-cards.

So here are my questions:

o) Has anybody else seen the above messages?


Yes, same here on a VIA motherboard with a vr interface.


o) Can they safely be ignored?


Looks like it.  They're debug messages that shouldn't still be in there. 
They were removed in version 1.2 but then reappeared in 1.4.2.1:


http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netinet/tcp_offload.c
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netinet/tcp_offload.c.diff?r1=1.1;r2=1.2
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netinet/tcp_offload.c.diff?r1=1.4;r2=1.4.2.1

Thanks for locating the source of the problem.  I entered a PR (#126138) 
but forgot to put in a pointer to your message--and now can't, since the 
PR database claims #126138 doesn't exist.  I'll try again later.


-Warren Block * Rapid City, South Dakota USA
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

"no toe capability on..."

2008-07-31 Thread Ewald Jenisch 
Hi,

Today I updated kernel & system on one of my machines (FreeBSD
7.0). After the update which ran absolutely smooth I'm seeing spurious
messages both on the console and in /var/log/messages like the
following:

no toe capability on 0xc2e66400


Grep-ing through the sources I found the above message to come from
/usr/src/sys/netinet/tcp_offload.c. As far as I understand this has
something to do with TcpOffloadEngine.

Please note that this is a box several years old (2GHz P4) with three
Intel FXP FastEthernet-cards.

So here are my questions:

o) Has anybody else seen the above messages? 

o) Can they safely be ignored?

o) If not - what can I do to get rid of them?

Thanks much in advance for any clue,
-ewald

PS: I'm enclosing the output of dmesg below

-- < Cut here > --

Copyright (c) 1992-2008 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 7.0-STABLE #5: Thu Jul 31 12:49:30 CEST 2008
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/OeKB-SNIFF
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Pentium(R) 4 CPU 2.00GHz (1994.12-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0xf27  Stepping = 7
  
Features=0xbfebfbff
  Features2=0x4400
real memory  = 528416768 (503 MB)
avail memory = 50318 (479 MB)
ACPI APIC Table: 
ioapic0: Changing APIC ID to 8
ioapic0  irqs 0-23 on motherboard
kbd1 at kbdmux0
ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
acpi0:  on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
acpi0: reservation of 0, a (3) failed
acpi0: reservation of 10, 1f70 (3) failed
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0xf808-0xf80b on acpi0
pcib0:  port 0xcf8-0xcff on acpi0
pci0:  on pcib0
vgapci0:  mem 
0xf000-0xf7ff,0xfc70-0xfc77 irq 16 at device 2.0 on pci0
agp0:  on vgapci0
agp0: detected 8060k stolen memory
agp0: aperture size is 128M
uhci0:  port 0x2440-0x245f irq 16 at 
device 29.0 on pci0
uhci0: [GIANT-LOCKED]
uhci0: [ITHREAD]
usb0:  on uhci0
usb0: USB revision 1.0
uhub0:  on usb0
uhub0: 2 ports with 2 removable, self powered
uhci1:  port 0x2460-0x247f irq 19 at 
device 29.1 on pci0
uhci1: [GIANT-LOCKED]
uhci1: [ITHREAD]
usb1:  on uhci1
usb1: USB revision 1.0
uhub1:  on usb1
uhub1: 2 ports with 2 removable, self powered
ehci0:  mem 0xfc78-0xfc7803ff 
irq 23 at device 29.7 on pci0
ehci0: [GIANT-LOCKED]
ehci0: [ITHREAD]
usb2: EHCI version 1.0
usb2: wrong number of companions (3 != 2)
usb2: companion controllers, 2 ports each: usb0 usb1
usb2:  on ehci0
usb2: USB revision 2.0
uhub2:  on usb2
uhub2: 6 ports with 6 removable, self powered
pcib1:  at device 30.0 on pci0
pci5:  on pcib1
fxp0:  port 0x1040-0x105f mem 
0xfcc0-0xfcc00fff,0xfc40-0xfc4f irq 16 at device 4.0 on pci5
miibus0:  on fxp0
inphy0:  PHY 1 on miibus0
inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp0: Ethernet address: 00:a0:c9:9f:20:57
fxp0: [ITHREAD]
fxp1:  port 0x1000-0x103f mem 
0xfc60-0xfc600fff irq 20 at device 8.0 on pci5
miibus1:  on fxp1
inphy1:  PHY 1 on miibus1
inphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp1: Ethernet address: 00:0b:cd:21:c6:c7
fxp1: [ITHREAD]
fxp2:  port 0x1060-0x107f mem 
0xfcc01000-0xfcc01fff,0xfc50-0xfc5f irq 18 at device 9.0 on pci5
miibus2:  on fxp2
inphy2:  PHY 1 on miibus2
inphy2:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp2: Ethernet address: 00:a0:c9:b2:e9:bc
fxp2: [ITHREAD]
isab0:  at device 31.0 on pci0
isa0:  on isab0
atapci0:  port 
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x24a0-0x24af irq 18 at device 31.1 on pci0
ata0:  on atapci0
ata0: [ITHREAD]
ata1:  on atapci0
ata1: [ITHREAD]
pcm0:  port 0x2000-0x20ff,0x2400-0x243f mem 
0xfc780400-0xfc7805ff,0xfc780600-0xfc7806ff irq 17 at device 31.5 on pci0
pcm0: [ITHREAD]
pcm0: 
cpu0:  on acpi0
p4tcc0:  on cpu0
acpi_button0:  on acpi0
atkbdc0:  port 0x60,0x64 irq 1 on acpi0
atkbd0:  irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
psm0:  irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: [ITHREAD]
psm0: model IntelliMouse, device ID 3
sio0:  port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
sio0: type 16550A, console
sio0: [FILTER]
sio1:  port 0x2f8-0x2ff irq 3 on acpi0
sio1: type 16550A
sio1: [FILTER]
fdc0:  port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0
fdc0: [FILTER]
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
pmtimer0 on isa0
ppc0:  at port 0x378-0x37f irq 7 on isa0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/13 bytes threshold
ppbus0:  on ppc0
ppbus0: [ITHREAD]
ppi0:  on ppbus0
plip0:  on ppbus0
plip0: WARNING: using obsoleted IFF_NEEDSGIANT flag
lpt0:  on ppbus0
lpt0: Interr