Re: ale(4) cannot negotiate as GigE

2014-05-09 Thread Alexey Dokuchaev
On Fri, May 09, 2014 at 02:38:16PM +0900, Yonghyeon PYUN wrote: On Thu, May 08, 2014 at 05:23:32PM +, Alexey Dokuchaev wrote: I just had a chance to plug the Ethernet cable directly into my laptop's bge(4) port, and it immediately negotiated at 1000baseT; but with the switch, it can

Re: ale(4) cannot negotiate as GigE

2014-05-08 Thread Alexey Dokuchaev
On Tue, Mar 05, 2013 at 09:14:11AM +, Alexey Dokuchaev wrote: On Tue, Mar 05, 2013 at 05:57:03PM +0900, YongHyeon PYUN wrote: Hmm, Does the switch support EEE feature? If yes, would you try disabling it? I do not think it [1] does; plus I cannot do much about this switch, as I'm

Re: ale(4) cannot negotiate as GigE

2014-05-08 Thread Yonghyeon PYUN
On Thu, May 08, 2014 at 05:23:32PM +, Alexey Dokuchaev wrote: On Tue, Mar 05, 2013 at 09:14:11AM +, Alexey Dokuchaev wrote: On Tue, Mar 05, 2013 at 05:57:03PM +0900, YongHyeon PYUN wrote: Hmm, Does the switch support EEE feature? If yes, would you try disabling it? I do not

Re: ale(4) cannot negotiate as GigE

2013-03-05 Thread Alexey Dokuchaev
On Tue, Mar 05, 2013 at 04:43:15PM +0900, YongHyeon PYUN wrote: Could you disable WOL before rebooting your box? # ifconfig ale0 -wol # reboot It came up as 100baseTX. :( You don't use any manual link configuration, right? Right, everything is auto (that is, the defaults).

Re: ale(4) cannot negotiate as GigE

2013-03-05 Thread YongHyeon PYUN
On Tue, Mar 05, 2013 at 08:06:20AM +, Alexey Dokuchaev wrote: On Tue, Mar 05, 2013 at 04:43:15PM +0900, YongHyeon PYUN wrote: Could you disable WOL before rebooting your box? # ifconfig ale0 -wol # reboot It came up as 100baseTX. :( You don't use any manual link

Re: ale(4) cannot negotiate as GigE

2013-03-05 Thread Alexey Dokuchaev
On Tue, Mar 05, 2013 at 05:57:03PM +0900, YongHyeon PYUN wrote: Hmm, Does the switch support EEE feature? If yes, would you try disabling it? I do not think it [1] does; plus I cannot do much about this switch, as I'm pretty far away from it right now. ./danfe [1]

Re: ale(4) cannot negotiate as GigE

2013-03-04 Thread Alexey Dokuchaev
On Mon, Mar 04, 2013 at 04:06:32PM +0900, YongHyeon PYUN wrote: On Mon, Mar 04, 2013 at 06:59:40AM +, Alexey Dokuchaev wrote: Better this time, I'm having 1000baseT again! :-) Thanks a lot for testing and patience! Could you reboot multiple times and check whether you reliably get a

Re: ale(4) cannot negotiate as GigE

2013-03-04 Thread YongHyeon PYUN
On Mon, Mar 04, 2013 at 08:18:58AM +, Alexey Dokuchaev wrote: On Mon, Mar 04, 2013 at 04:06:32PM +0900, YongHyeon PYUN wrote: On Mon, Mar 04, 2013 at 06:59:40AM +, Alexey Dokuchaev wrote: Better this time, I'm having 1000baseT again! :-) Thanks a lot for testing and patience!

Re: ale(4) cannot negotiate as GigE

2013-03-04 Thread Alexey Dokuchaev
On Tue, Mar 05, 2013 at 02:49:20PM +0900, YongHyeon PYUN wrote: On Mon, Mar 04, 2013 at 08:18:58AM +, Alexey Dokuchaev wrote: Yes, multiple reboots was a good idea, it's not very stable: [...] I've tried various combinations of just reboot, shutdown -r +1m and pinging some host while

Re: ale(4) cannot negotiate as GigE

2013-03-04 Thread YongHyeon PYUN
On Tue, Mar 05, 2013 at 06:59:10AM +, Alexey Dokuchaev wrote: On Tue, Mar 05, 2013 at 02:49:20PM +0900, YongHyeon PYUN wrote: On Mon, Mar 04, 2013 at 08:18:58AM +, Alexey Dokuchaev wrote: Yes, multiple reboots was a good idea, it's not very stable: [...] I've tried various

Re: ale(4) cannot negotiate as GigE

2013-03-03 Thread Alexey Dokuchaev
On Mon, Feb 25, 2013 at 05:23:44PM +0900, YongHyeon PYUN wrote: Then have no idea at this moment. Can you try other OS and check whether it can establish a gigabit link? I did not have a chance to try other OS, because machine paniced during tinderbuilding of a large port. Unfortunately I

Re: ale(4) cannot negotiate as GigE

2013-03-03 Thread Alexey Dokuchaev
On Sun, Mar 03, 2013 at 09:53:30AM +, Alexey Dokuchaev wrote: However, after reboot ale0 come up at 1000baseT full-duplex, with patched driver (longer delays in ale_phy_reset()). I've reverted this change and rebooted again, but it again come up as GigE. Alas, after make kernel, link come

Re: ale(4) cannot negotiate as GigE

2013-03-03 Thread YongHyeon PYUN
On Sun, Mar 03, 2013 at 12:00:10PM +, Alexey Dokuchaev wrote: On Sun, Mar 03, 2013 at 09:53:30AM +, Alexey Dokuchaev wrote: However, after reboot ale0 come up at 1000baseT full-duplex, with patched driver (longer delays in ale_phy_reset()). I've reverted this change and rebooted

Re: ale(4) cannot negotiate as GigE

2013-03-03 Thread Alexey Dokuchaev
On Mon, Mar 04, 2013 at 09:50:44AM +0900, YongHyeon PYUN wrote: On Sun, Mar 03, 2013 at 12:00:10PM +, Alexey Dokuchaev wrote: Alas, after make kernel, link come up as 100mbps again, playing with delays and rebooting (several times) did not make it GigE. I'm not sure what's actually

Re: ale(4) cannot negotiate as GigE

2013-03-03 Thread YongHyeon PYUN
On Mon, Mar 04, 2013 at 01:53:44AM +, Alexey Dokuchaev wrote: On Mon, Mar 04, 2013 at 09:50:44AM +0900, YongHyeon PYUN wrote: On Sun, Mar 03, 2013 at 12:00:10PM +, Alexey Dokuchaev wrote: Alas, after make kernel, link come up as 100mbps again, playing with delays and rebooting

Re: ale(4) cannot negotiate as GigE

2013-03-03 Thread Alexey Dokuchaev
On Mon, Mar 04, 2013 at 11:10:59AM +0900, YongHyeon PYUN wrote: On Mon, Mar 04, 2013 at 01:53:44AM +, Alexey Dokuchaev wrote: Yes, it did help. With 2000us delays (I didn't revert them [...] Great! But it seems 2ms delays is too much. Could you revert the change (2000us delays) and

Re: ale(4) cannot negotiate as GigE

2013-03-03 Thread YongHyeon PYUN
On Mon, Mar 04, 2013 at 02:46:31AM +, Alexey Dokuchaev wrote: On Mon, Mar 04, 2013 at 11:10:59AM +0900, YongHyeon PYUN wrote: On Mon, Mar 04, 2013 at 01:53:44AM +, Alexey Dokuchaev wrote: Yes, it did help. With 2000us delays (I didn't revert them [...] Great! But it seems 2ms

Re: ale(4) cannot negotiate as GigE

2013-03-03 Thread Alexey Dokuchaev
On Mon, Mar 04, 2013 at 02:23:28PM +0900, YongHyeon PYUN wrote: Ok, here is final diff which combines two things you've tested. So revert any changes before applying it. Let me know how it goes on your box. Hmm, apparently something went wrong, as I'm back to 100baseTX after make kernel and

Re: ale(4) cannot negotiate as GigE

2013-03-03 Thread YongHyeon PYUN
On Mon, Mar 04, 2013 at 05:59:48AM +, Alexey Dokuchaev wrote: On Mon, Mar 04, 2013 at 02:23:28PM +0900, YongHyeon PYUN wrote: Ok, here is final diff which combines two things you've tested. So revert any changes before applying it. Let me know how it goes on your box. Hmm, apparently

Re: ale(4) cannot negotiate as GigE

2013-03-03 Thread Alexey Dokuchaev
On Mon, Mar 04, 2013 at 03:29:44PM +0900, YongHyeon PYUN wrote: On Mon, Mar 04, 2013 at 05:59:48AM +, Alexey Dokuchaev wrote: On Mon, Mar 04, 2013 at 02:23:28PM +0900, YongHyeon PYUN wrote: Ok, here is final diff which combines two things you've tested. So revert any changes before

Re: ale(4) cannot negotiate as GigE

2013-03-03 Thread YongHyeon PYUN
On Mon, Mar 04, 2013 at 06:59:40AM +, Alexey Dokuchaev wrote: On Mon, Mar 04, 2013 at 03:29:44PM +0900, YongHyeon PYUN wrote: On Mon, Mar 04, 2013 at 05:59:48AM +, Alexey Dokuchaev wrote: On Mon, Mar 04, 2013 at 02:23:28PM +0900, YongHyeon PYUN wrote: Ok, here is final diff which

Re: ale(4) cannot negotiate as GigE

2013-02-25 Thread YongHyeon PYUN
On Fri, Feb 22, 2013 at 01:56:07AM +, Alexey Dokuchaev wrote: On Fri, Feb 22, 2013 at 10:13:08AM +0900, YongHyeon PYUN wrote: On Thu, Feb 21, 2013 at 12:43:44PM +, Alexey Dokuchaev wrote: ale_flags = 0x0040 Thanks for the info. Indeed, your controller is AR8121 Gigabit

Re: ale(4) cannot negotiate as GigE

2013-02-21 Thread YongHyeon PYUN
On Wed, Feb 20, 2013 at 06:08:53AM +, Alexey Dokuchaev wrote: On Wed, Feb 20, 2013 at 01:37:39PM +0900, YongHyeon PYUN wrote: On Tue, Feb 19, 2013 at 08:23:02AM +, Alexey Dokuchaev wrote: ale0@pci0:2:0:0:class=0x02 card=0x82261043 chip=0x10261969 rev=0xb0 hdr=0x00

Re: ale(4) cannot negotiate as GigE

2013-02-21 Thread Alexey Dokuchaev
On Thu, Feb 21, 2013 at 05:33:35PM +0900, YongHyeon PYUN wrote: On Wed, Feb 20, 2013 at 06:08:53AM +, Alexey Dokuchaev wrote: $ dmesg | egrep ale\|atphy ale0: Atheros AR8121/AR8113/AR8114 PCIe Ethernet port 0xcc00-0xcc7f mem 0xfe9c-0xfe9f irq 17 at device 0.0 on pci2 ale0:

Re: ale(4) cannot negotiate as GigE

2013-02-21 Thread YongHyeon PYUN
On Thu, Feb 21, 2013 at 12:43:44PM +, Alexey Dokuchaev wrote: On Thu, Feb 21, 2013 at 05:33:35PM +0900, YongHyeon PYUN wrote: On Wed, Feb 20, 2013 at 06:08:53AM +, Alexey Dokuchaev wrote: $ dmesg | egrep ale\|atphy ale0: Atheros AR8121/AR8113/AR8114 PCIe Ethernet port

Re: ale(4) cannot negotiate as GigE

2013-02-21 Thread Alexey Dokuchaev
On Fri, Feb 22, 2013 at 10:13:08AM +0900, YongHyeon PYUN wrote: On Thu, Feb 21, 2013 at 12:43:44PM +, Alexey Dokuchaev wrote: ale_flags = 0x0040 Thanks for the info. Indeed, your controller is AR8121 Gigabit etherent(L1E). I guess the PHY initialization is not complete. Would you

ale(4) cannot negotiate as GigE

2013-02-19 Thread Alexey Dokuchaev
Hi there, I've recently put back online one of my home servers, updated to the latest -CURRENT code. All went fine, but one thing bothers me. This box bears Asus P5Q Pro mobo, with the following onboard NIC: ale0@pci0:2:0:0:class=0x02 card=0x82261043 chip=0x10261969 rev=0xb0

Re: ale(4) cannot negotiate as GigE

2013-02-19 Thread YongHyeon PYUN
On Tue, Feb 19, 2013 at 08:23:02AM +, Alexey Dokuchaev wrote: Hi there, I've recently put back online one of my home servers, updated to the latest -CURRENT code. All went fine, but one thing bothers me. This box bears Asus P5Q Pro mobo, with the following onboard NIC:

Re: ale(4) cannot negotiate as GigE

2013-02-19 Thread Alexey Dokuchaev
On Wed, Feb 20, 2013 at 01:37:39PM +0900, YongHyeon PYUN wrote: On Tue, Feb 19, 2013 at 08:23:02AM +, Alexey Dokuchaev wrote: ale0@pci0:2:0:0:class=0x02 card=0x82261043 chip=0x10261969 rev=0xb0 hdr=0x00 vendor = 'Atheros Communications Inc.' device =