Re: Problem with re(4) Ethernet driver has resurfaced in 11-STABLE and HEAD

2017-05-22 Thread Thomas Mueller 
from O. Hartmann:

> Just for my curiosity: do you have "options FLOWTABLE" defined in your kernel 
> config?

I was not even aware of "options FLOWTABLE", having not seen it in GENERIC 
kernel config.

I had to look in $SRCDIR/sys/conf/NOTES to find it.

What would I get by adding "options FLOWTABLE" to my kernel config?

Tom

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

Re: Problem with re(4) Ethernet driver has resurfaced in 11-STABLE and HEAD

2017-05-21 Thread O. Hartmann 
On Mon, 22 May 2017 10:55:46 +0900
YongHyeon PYUN  wrote:


Just for my curiosity: do you have "options FLOWTABLE" defined in your kernel
config?

> On Sun, May 21, 2017 at 09:29:42AM +, Thomas Mueller wrote:
> > from YongHyeon PYUN:
> >   
> > > [removed stable@ from CC]  
> >   
> > > > I recently updated my 10.1-STABLE to 11.0-STABLE and find I can no
> > > > longer connect with the Ethernet.  
> >   
> > > > dhclient re0 produces  
> >   
> > > > DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 4
> > > > DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 11
> > > > DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 19
> > > > DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 7
> > > > DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 14
> > > > DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 5
> > > > No DHCPOFFERS received.
> > > > No working leases in persistent database - sleeping.  
> > 
> >   
> > > If you assign an static IPv4 address to re(4) are you able to use
> > > the network interface?  
> >   
> > > AFAIK there was no significant re(4) changes for a long time. Could
> > > you show us back trace information?  
> > 
> > Problem with re(4) reappeared in both 11.0-STABLE and HEAD, but OK to trim
> > stable@ since changes/fixes would go to HEAD first.
> > 
> > No connection with static IPv4 address. 
> > 
> > Where do I get back trace information?
> >   
> 
> https://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html
> 
> > Problem was more severe with HEAD in that OS immediately crashed into
> > debugger, while in 11.0-STABLE, only the connection failed but may have
> > left memory unstable. 
> 
> I guess you have two issues. No connection with static IPv4 address
> and kernel crash.  Couldn't you obtain a kernel crash dump when you
> encounter kernel panic? If this is no crash dump you probably have
> some missing kernel configuration.
> 
> > I can still connect on that computer with Hiro H50191 USB wireless adapter,
> > driver rsu.
> > 
> > Tom
> >   
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

Re: Problem with re(4) Ethernet driver has resurfaced in 11-STABLE and HEAD

2017-05-21 Thread YongHyeon PYUN 
On Sun, May 21, 2017 at 09:29:42AM +, Thomas Mueller wrote:
> from YongHyeon PYUN:
> 
> > [removed stable@ from CC]
> 
> > > I recently updated my 10.1-STABLE to 11.0-STABLE and find I can no longer 
> > > connect with the Ethernet.
> 
> > > dhclient re0 produces
> 
> > > DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 4
> > > DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 11
> > > DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 19
> > > DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 7
> > > DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 14
> > > DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 5
> > > No DHCPOFFERS received.
> > > No working leases in persistent database - sleeping.
> 
> 
> > If you assign an static IPv4 address to re(4) are you able to use
> > the network interface?
> 
> > AFAIK there was no significant re(4) changes for a long time. Could
> > you show us back trace information?
> 
> Problem with re(4) reappeared in both 11.0-STABLE and HEAD, but OK to trim 
> stable@ since changes/fixes would go to HEAD first.
> 
> No connection with static IPv4 address. 
> 
> Where do I get back trace information?
> 

https://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html

> Problem was more severe with HEAD in that OS immediately crashed into 
> debugger, while in 11.0-STABLE, only the connection failed but may have left 
> memory unstable.
> 

I guess you have two issues. No connection with static IPv4 address
and kernel crash.  Couldn't you obtain a kernel crash dump when you
encounter kernel panic? If this is no crash dump you probably have
some missing kernel configuration.

> I can still connect on that computer with Hiro H50191 USB wireless adapter, 
> driver rsu.
> 
> Tom
> 
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Problem with re(4) Ethernet driver has resurfaced in 11-STABLE and HEAD

2017-05-21 Thread Baho Utot 



On 05/21/17 05:29, Thomas Mueller wrote:

from YongHyeon PYUN:


[removed stable@ from CC]



I recently updated my 10.1-STABLE to 11.0-STABLE and find I can no longer 
connect with the Ethernet.



dhclient re0 produces



DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 19
DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 5
No DHCPOFFERS received.
No working leases in persistent database - sleeping.




If you assign an static IPv4 address to re(4) are you able to use
the network interface?



AFAIK there was no significant re(4) changes for a long time. Could
you show us back trace information?


Problem with re(4) reappeared in both 11.0-STABLE and HEAD, but OK to trim 
stable@ since changes/fixes would go to HEAD first.

No connection with static IPv4 address.

Where do I get back trace information?

Problem was more severe with HEAD in that OS immediately crashed into debugger, 
while in 11.0-STABLE, only the connection failed but may have left memory 
unstable.

I can still connect on that computer with Hiro H50191 USB wireless adapter, 
driver rsu.

Tom

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


I have the same problem with this driver:

 urtwn - Realtek RTL8188CU/RTL8188RU/RTL8188EU/RTL8192CU USB IEEE
 802.11b/g/n wireless network device

On this platform:

FreeBSD desktop.example.com 11.0-RELEASE-p9 FreeBSD 11.0-RELEASE-p9 #0 
r316958: Sat Apr 15 09:25:18 EDT 2017 
r...@desktop.example.com:/usr/obj/usr/src/sys/GENERIC  amd64


Had to quit using it under FreeBSD works fine in Win7.

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

Re: Problem with re(4) Ethernet driver has resurfaced in 11-STABLE and HEAD

2017-05-21 Thread Thomas Mueller 
from YongHyeon PYUN:

> [removed stable@ from CC]

> > I recently updated my 10.1-STABLE to 11.0-STABLE and find I can no longer 
> > connect with the Ethernet.

> > dhclient re0 produces

> > DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 4
> > DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 11
> > DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 19
> > DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 7
> > DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 14
> > DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 5
> > No DHCPOFFERS received.
> > No working leases in persistent database - sleeping.


> If you assign an static IPv4 address to re(4) are you able to use
> the network interface?

> AFAIK there was no significant re(4) changes for a long time. Could
> you show us back trace information?

Problem with re(4) reappeared in both 11.0-STABLE and HEAD, but OK to trim 
stable@ since changes/fixes would go to HEAD first.

No connection with static IPv4 address. 

Where do I get back trace information?

Problem was more severe with HEAD in that OS immediately crashed into debugger, 
while in 11.0-STABLE, only the connection failed but may have left memory 
unstable.

I can still connect on that computer with Hiro H50191 USB wireless adapter, 
driver rsu.

Tom

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

Re: Problem with re(4) Ethernet driver has resurfaced in 11-STABLE and HEAD

2017-05-20 Thread YongHyeon PYUN 
On Thu, May 18, 2017 at 07:04:51AM +, Thomas Mueller wrote:

[removed stable@ from CC]

> I recently updated my 10.1-STABLE to 11.0-STABLE and find I can no longer 
> connect with the Ethernet.
> 
> dhclient re0 produces
> 
> DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 4
> DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 11
> DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 19
> DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 7
> DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 14
> DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 5
> No DHCPOFFERS received.
> No working leases in persistent database - sleeping.
> 

If you assign an static IPv4 address to re(4) are you able to use
the network interface?

> uname -a shows
> 
> FreeBSD amelia2 11.0-STABLE FreeBSD 11.0-STABLE #1 r317932: Mon May  8 
> 23:23:37 UTC 2017 root@amelia2:/usr/obj/usr/src11/sys/SANDY11NC  amd64
> 
> Relevant lines from /var/run/dmesg.boot are
> 
> re0:  port 
> 0xe000-0xe0ff mem 0xf7d04000-0xf7d04fff,0xf7d0-0xf7d03fff irq 17 at 
> device 0.0 on pci2
> re0: Using 1 MSI-X message
> re0: Chip rev. 0x2c80
> re0: MAC rev. 0x0010
> miibus0:  on re0
> rgephy0:  PHY 1 on miibus0
> rgephy0:  none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 
> 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 
> 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 
> 1000baseT-FDX-flow-master, auto, auto-flow
> re0: Using defaults for TSO: 65518/35/2048
> re0: Ethernet address: d4:3d:7e:97:17:e2
> re0: netmap queues/slots: TX 1/256, RX 1/256
> 
> Problem shows much quicker in my recent build of HEAD (12-current), where 
> dhclient re0
> gives just a couple lines screen output before crashing into debugger 
> db> prompt
> 

AFAIK there was no significant re(4) changes for a long time. Could
you show us back trace information?

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

Problem with re(4) Ethernet driver has resurfaced in 11-STABLE and HEAD

2017-05-18 Thread Thomas Mueller 
I recently updated my 10.1-STABLE to 11.0-STABLE and find I can no longer 
connect with the Ethernet.

dhclient re0 produces

DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 19
DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 5
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

uname -a shows

FreeBSD amelia2 11.0-STABLE FreeBSD 11.0-STABLE #1 r317932: Mon May  8 23:23:37 
UTC 2017 root@amelia2:/usr/obj/usr/src11/sys/SANDY11NC  amd64

Relevant lines from /var/run/dmesg.boot are

re0:  port 
0xe000-0xe0ff mem 0xf7d04000-0xf7d04fff,0xf7d0-0xf7d03fff irq 17 at device 
0.0 on pci2
re0: Using 1 MSI-X message
re0: Chip rev. 0x2c80
re0: MAC rev. 0x0010
miibus0:  on re0
rgephy0:  PHY 1 on miibus0
rgephy0:  none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 
100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 
1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, 
auto-flow
re0: Using defaults for TSO: 65518/35/2048
re0: Ethernet address: d4:3d:7e:97:17:e2
re0: netmap queues/slots: TX 1/256, RX 1/256

Problem shows much quicker in my recent build of HEAD (12-current), where 
dhclient re0
gives just a couple lines screen output before crashing into debugger 
db> prompt

Build host for 12-current installation was the recent build of 11.0-STABLE 
amd64.

Kernel strings there show

__page_fault.read
__page_fault.write
amd64
@(#)FreeBSD 12.0-CURRENT #1 r318262: Sun May 14 09:37:30 UTC 2017
FreeBSD 12.0-CURRENT #1 r318262: Sun May 14 09:37:30 UTC 2017
root@amelia4:/BETA1/usr/obj/BETA1/usr/src/sys/SANDY12NC
FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on LLVM 
4.0.0)
FreeBSD
12.0-CURRENT
SANDY11NC

It looks like I can connect to Internet with Hiro H50191 USB wireless adapter, 
driver rsu, but I am not sure of its stability on 11.0-STABLE and 12.0-current..

Tom

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