Re: 12.1 weirdness

2019-10-17 Thread Eugene Grosbein
17.10.2019 12:37, Daniel Braniss wrote:

> just trying out 12,1 on a DELL PowerEdge R710, and I see:
> ...
> Oct 16 22:52:12 store-08 kernel: bce3: bce_pulse(): Warning: bootcode thinks 
> driver is absent! (bc_state = 0x0023600E)
> Oct 16 22:52:13 store-08 kernel: Limiting icmp unreach response from 3244 to 
> 200 packets/sec
> Oct 16 22:52:13 store-08 kernel: bce3: bce_pulse(): Bootcode found the driver 
> pulse! (bc_state = 0x0003610E)
> Oct 17 06:04:29 store-08 kernel: Limiting icmp unreach response from 564 to 
> 200 packets/sec
> 
> there is nothing connected to bce3, only bce0, 
> rev is r353486, and it’s diskless.

Does it experience some disruption? If not, you may just ignore those.

> BTW: is there a way of knowing which port is being reported as unreachable? 

So many packets should be easily seen with net/trafshow or just tcpdump.

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


12.1 weirdness

2019-10-16 Thread Daniel Braniss
hi,
just trying out 12,1 on a DELL PowerEdge R710, and I see:
...
Oct 16 22:52:12 store-08 kernel: bce3: bce_pulse(): Warning: bootcode thinks 
driver is absent! (bc_state = 0x0023600E)
Oct 16 22:52:13 store-08 kernel: Limiting icmp unreach response from 3244 to 
200 packets/sec
Oct 16 22:52:13 store-08 kernel: bce3: bce_pulse(): Bootcode found the driver 
pulse! (bc_state = 0x0003610E)
Oct 17 06:04:29 store-08 kernel: Limiting icmp unreach response from 564 to 200 
packets/sec

there is nothing connected to bce3, only bce0, 
rev is r353486, and it’s diskless.

BTW: is there a way of knowing which port is being reported as unreachable? 

any ideas?

thanks,
danny
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"