Koozali.org: home of the SME Server

Waking up of SME 9.1 using WoL (SME server used for Affa)

Offline turandot

  • *
  • 82
  • +0/-0
Waking up of SME 9.1 using WoL (SME server used for Affa)
« on: December 31, 2016, 04:51:18 PM »
I am currently still running SME 8.2 on my SME backup server. This backup machine is regularly waked up using WoL by a magic packet from my productive SME server. A while after the wakeup, Affa is started, hence my productive machine is backuped. Using a cron job, the machine will halt once the Affa backup job is done. This works perfectly since a long time.

I am aware that SME 8.2 will become obsolete soon due to the obsolescence of CentOS 5. Therefore I was preparing to update my backup machine to SME 9.1. Unfortunately WoL does not work for the SME 9.1 test installation.

The ethtool on the SME 9.1 backup server (test installation) produces the following output:
Code: [Select]
[root@smebackup ~]# ethtool eth0
Settings for eth0:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
        Supported pause frame use: No
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
        Advertised pause frame use: Symmetric Receive-only
        Advertised auto-negotiation: Yes
        Link partner advertised link modes:  10baseT/Half 10baseT/Full
                                             100baseT/Half 100baseT/Full
        Link partner advertised pause frame use: Symmetric
        Link partner advertised auto-negotiation: Yes
        Speed: 100Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: on
        Supports Wake-on: pumbg
        Wake-on: g
        Current message level: 0x00000033 (51)
                               drv probe ifdown ifup
        Link detected: yes
[root@smebackup ~]#
Doing the same on my productive SME 8.2 backup server, the output is the following:
Code: [Select]
[root@smebackup ~]# ethtool eth0
Settings for eth0:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
        Advertised auto-negotiation: Yes
        Speed: 100Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: on
        Supports Wake-on: pumbg
        Wake-on: g
        Current message level: 0x00000033 (51)
        Link detected: yes
[root@smebackup ~]#
The output is more or less identical except
Code: [Select]
                              drv probe ifdown ifupAny ideas what I can do? I have seen this bug report https://bugs.contribs.org/show_bug.cgi?id=7928 , but it relates to SME 8 (which works for me) and it seems to be fixed anyway...

Regards, turandot
« Last Edit: December 31, 2016, 04:53:55 PM by turandot »

Offline Stefano

  • *
  • 10,836
  • +2/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #1 on: December 31, 2016, 04:55:58 PM »
are 2 nics the same?

Offline turandot

  • *
  • 82
  • +0/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #2 on: December 31, 2016, 04:59:18 PM »
I should have stated that it is the identical hardware, except the HDD... To test all this, I just used a spare HDD which I swapped into my backup server for testing purposes.

So yes: same machine, identical NIC, same MAC address...

BTW: the SME 9.1 installation is completely updated.

Thanks, turandot
« Last Edit: December 31, 2016, 05:06:44 PM by turandot »

Offline Jean-Philippe Pialasse

  • *
  • 2,747
  • +11/-0
  • aka Unnilennium
    • http://smeserver.pialasse.com
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #3 on: December 31, 2016, 05:06:26 PM »
You can not have two identical mac address on same network from what i know, this will cause conflict. Even with same model, two nics should have two unique mac address.

Your issue is not sme related but hardware related. Check that wake on lan is enabled on bios setting and double check your mac address

Offline turandot

  • *
  • 82
  • +0/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #4 on: December 31, 2016, 05:09:43 PM »
Stefano,

sorry, this is a misunderstanding. I don't have two identical machines with identical MAC address in my network. I am using the same machine, alternatively with a 8.2 installation (productive server) or (exclusive or!) with the 9.1 test installation. (Just the HDD is different carrying the SME installations.)

Thanks, turandot

Offline Jean-Philippe Pialasse

  • *
  • 2,747
  • +11/-0
  • aka Unnilennium
    • http://smeserver.pialasse.com
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #5 on: December 31, 2016, 05:17:34 PM »
Ok my bad, same hardware except for hdd.

So bios should be set to the same.
The bug linked seemed stranged to me as the wake is related to the hardware not the os.

However i have seen some linux module not handling correctly some nics leaving them disabled.

One way to test this hypothesis.
1 Switch on your sme9 version, then halt it.
2 Try to wake it... works? Fails?
3 swap disk to sme8, do not power on, just try to wake up.
4. If previous failed, switch on and halt, then try to wake. And halt if success
5. Swap back to sme9, do not switch on, just try to wake

If both 2 and 3 failed and 4 and 5 succeed then this is a driver issue and need to be reported to redhat, and maybe buy a new nics (different brand) waiting for a fix

Or keep your server running, or use the bios hour programmed wake up. Carrefull for summer time not handled by bios.

Offline turandot

  • *
  • 82
  • +0/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #6 on: December 31, 2016, 05:21:58 PM »
OK, my fault as well: Jean-Philippe (and not Stefano)!

The BIOS settings are indeed unchanged.

I now need a bit of testing time, I will probably come back tomorrow. New year eve is coming!

Have a good time,

turandot

Offline turandot

  • *
  • 82
  • +0/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #7 on: January 01, 2017, 10:50:51 AM »
Here are my test results.

Test conditions:
  • SME 8.2 32 Bit fully patched (noted as "SME 8.2" below)
  • SME 9.1 64 Bit fully patched (noted as "SME 9.1" below)
  • always use Putty for console commands, even though local console and monitor are available as well
  • always use WoL to wake up server, just use power button in case of WoL Fail
  • always 3x WoL (if Fail) in order to avoid "single events"
  • always 1x WoL (if OK), first time works perfectly
  • "Detach power" means: a) pull off main power cord, b) wait 30 seconds, c) plug in power cord. (BIOS Power up on AC power loss is disabled.)
  • "Start, Stop" means: a) let the SME server boot completely, b) logon to remote console, c) apply console command signal-event halt

Test sequence and test results:
  • Start test sequence with SME 8.2 HDD
  • Detach power, reattach power, WoL --> OK
  • Start, stop, WoL --> OK
  • Start, stop, swap SME 8.2 HDD to SME 9.1 HDD without detaching main power, WoL --> OK
  • Start, stop, WoL --> Fail
  • Start, stop, detach power, reattach power, WoL --> OK
  • Start, stop, WoL --> Fail
  • Start, stop, swap SME 9.1 HDD to SME 8.2 HDD without detaching main power, WoL --> Fail
  • Detach power, reattach power, WoL --> OK

My main conclusion is: once SME 9.1 was running and server was halted, WoL fails. This faulty situation is "healed" by cycling the main power.

The used system is a MSI Wind 2713 NetTop, the used hardware can be seen here:
Code: [Select]
[root@smebackup ~]# lspci
00:00.0 Host bridge: Intel Corporation 82945G/GZ/P/PL Memory Controller Hub (rev 02)
00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02)
00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition Audio Controller (rev 01)
00:1c.0 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 1 (rev 01)
00:1c.1 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 2 (rev 01)
00:1c.2 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 3 (rev 01)
00:1c.3 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 4 (rev 01)
00:1d.0 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #1 (rev 01)
00:1d.1 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #2 (rev 01)
00:1d.2 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #3 (rev 01)
00:1d.3 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #4 (rev 01)
00:1d.7 USB controller: Intel Corporation NM10/ICH7 Family USB2 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev e1)
00:1f.0 ISA bridge: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge (rev 01)
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 01)
00:1f.2 IDE interface: Intel Corporation NM10/ICH7 Family SATA Controller [IDE mode] (rev 01)
00:1f.3 SMBus: Intel Corporation NM10/ICH7 Family SMBus Controller (rev 01)
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 02)
[root@smebackup ~]#

Any ideas?

Thanks, turandot
« Last Edit: January 01, 2017, 10:56:32 AM by turandot »

Offline Jean-Philippe Pialasse

  • *
  • 2,747
  • +11/-0
  • aka Unnilennium
    • http://smeserver.pialasse.com
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #8 on: January 01, 2017, 08:16:09 PM »
Wow, excellent testing!

Happy new year  !

So you have your confirmation, this is indeed driver related, something went bad on rhel6 version, hence you should report this to red hat bugzilla for rhel6 as sme9 is based on this.

This might take a while to fix, if you are urged by time, i advise to buy a different network card from different manifacturer capable of wol. Considering the cost of your time this might be a savvy solution, however i still strongly suggest you to report it to red hat. As you have the hardware in hand you are more suited than us to report it.

Offline Jean-Philippe Pialasse

  • *
  • 2,747
  • +11/-0
  • aka Unnilennium
    • http://smeserver.pialasse.com
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #9 on: January 01, 2017, 08:22:40 PM »
Two other thoughts:
- check for mother board firmware update
- is this a uefi or bios board? This could be related to some os security check to deactivate if this is an uefi

Offline turandot

  • *
  • 82
  • +0/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #10 on: January 01, 2017, 11:32:39 PM »
Happy new year as well!

Wow, excellent testing!
Thanks 8)

...this is indeed driver related, something went bad on rhel6 version, hence you should report this to red hat bugzilla for rhel6 as sme9 is based on this.
Here I need a little help. You are suggesting, that I should raise a bug report here: https://bugzilla.redhat.com/index.cgi? Do I need to report what component is affected? How to differentiate between SME and Red Hat components?

...i advise to buy a different network card from different manifacturer capable of wol.
You are probably right.

check for mother board firmware update
Hmm, could do this, but the latest available Bios is from 2008-12-11...

is this a uefi or bios board? This could be related to some os security check to deactivate if this is an uefi
The machine has a classical Bios, nothing else.

I need to think now, because the affected machine is quite old, probably nine or ten years. May be I should sent the machine to the happy hunting grounds?

Whatever: some advice how to submit a bug at Red Hat would be very much appreciated anyhow.

Thanks, turandot

Offline ReetP

  • *
  • 3,722
  • +5/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #11 on: January 01, 2017, 11:57:14 PM »
https://bugzilla.redhat.com/

You could then open one in bugs.contribs.org and reference the redhat one.

B. Rgds
John
...
1. Read the Manual
2. Read the Wiki
3. Don't ask for support on Unsupported versions of software
4. I have a job, wife, and kids and do this in my spare time. If you want something fixed, please help.

Bugs are easier than you think: http://wiki.contribs.org/Bugzilla_Help

If you love SME and don't want to lose it, join in: http://wiki.contribs.org/Koozali_Foundation

Offline TerryF

  • grumpy old man
  • *
  • 1,821
  • +6/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #12 on: January 02, 2017, 02:18:35 PM »
Not a soluti8on but some reading and path for further investigation:

https://www.centos.org/forums/viewtopic.php?t=46364
https://www.centos.org/forums/viewtopic.php?t=3259


--
qui scribit bis legit

Offline Jean-Philippe Pialasse

  • *
  • 2,747
  • +11/-0
  • aka Unnilennium
    • http://smeserver.pialasse.com
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #13 on: January 03, 2017, 04:27:26 AM »
TerryF links could be promising.
at least the part where you see :
Code: [Select]
cat /proc/acpi/wakeup

You could indeed check at the message log about the time the machine is powering off to catch some errors on closing network.
also you could try to catch them on the screen connected to the server.

For the bugs, should be against rhel6. As we base sme9 on centos6 which is based on rhel6,

In term of hardware this is your call. As long as the disks have been replaced regularly ( 5 years) your machine could still go on. Maybe a check to the power supply and inspect the mother board for visually bad capacitors
« Last Edit: January 03, 2017, 04:31:18 AM by Jean-Philippe Pialasse »

Offline TerryF

  • grumpy old man
  • *
  • 1,821
  • +6/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #14 on: January 03, 2017, 04:56:34 AM »
Although an old 8.2 bug it does highlight issues that can arise with driver/module updates upstream
https://bugs.contribs.org/show_bug.cgi?id=7928

Seems to be a bit of discussion around CentOS and that RealTek chip
eg https://www.unixteacher.org/blog/linux/ethernet-rtl-8168-driver-on-centos/

added: interesting although Ubuntu https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/981461
« Last Edit: January 03, 2017, 05:34:47 AM by TerryF »
--
qui scribit bis legit

Offline TerryF

  • grumpy old man
  • *
  • 1,821
  • +6/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #15 on: January 04, 2017, 01:31:23 AM »
OK definitely SME related, confirm behaviour on a HP Microserver..very very similar to old SME 8 bug as quoted above.

I will also look at using an older kernel and see if its an update to a module as with the olds SME 8 bug

If it is then a bug needs to be raised, in CentOS and RH

--
qui scribit bis legit

Offline TerryF

  • grumpy old man
  • *
  • 1,821
  • +6/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #16 on: January 04, 2017, 01:38:39 AM »
Nope..going back three updates still evident..bug please
--
qui scribit bis legit

Offline TerryF

  • grumpy old man
  • *
  • 1,821
  • +6/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #17 on: January 04, 2017, 01:50:24 AM »
See comment 45 in the sme8 bug https://bugs.contribs.org/show_bug.cgi?id=7928

WOL was working in SME9b2 note driver versions then
[root@sme9b2 ~]# modinfo tg3 | grep -i version
version:        3.124
srcversion:     849BDFC1D60C5393F1EC438
vermagic:       2.6.32-358.23.2.el6.x86_64 SMP mod_unload modversions

SME 9.1 driver version
[root@fagehome ~]# modinfo tg3 | grep -i version
version:        3.137
srcversion:     1E40B98DF422DE93879F7FF
vermagic:       2.6.32-642.11.1.el6.x86_64 SMP mod_unload modversions
--
qui scribit bis legit

Offline TerryF

  • grumpy old man
  • *
  • 1,821
  • +6/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #18 on: January 04, 2017, 07:20:29 PM »
My observations, On a HP Microserver, server/gateway, using a Intel® Gigabit CT Desktop Adapter (Intel® 82574L Gigabit Ethernet Controller) issuing a magic packet from a windows 10 pc wakes the server up from a power down after using console to shutdown. So appears to be a driver issue.

Are you setup as server only or server/gateway.

If server/gateway are you issuing the wol directive to the right nic?

Swapping of nics has been observed when installing sme9 in the past

Did you try issuing # ethtool -s eth0 wol g and then shutdown and try the wol directive again?
--
qui scribit bis legit

Offline turandot

  • *
  • 82
  • +0/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #19 on: January 05, 2017, 10:56:59 PM »
My server hardware has just a single NIC, so confusion between various NICs is not possible. Consequently I am running the server in the "server only" mode.

Applying the command...
Code: [Select]
ethtool -s eth0 wol g...just before shutdown does not make any difference: WoL is not working with SME 9.1.

I also experimented with nested commands
Code: [Select]
ifconfig eth0 down; signal-event haltno difference: WoL is not working with SME 9.1

I also checked /var/log/messages for errors during shutdown, and I did not find any error message at all. Same on the local console during shutdown: no error message is displayed.

This is the output of /proc/acpi/wakeup under SME 9.1:
Code: [Select]
[root@smebackup ~]# cat /proc/acpi/wakeup
Device  S-state   Status   Sysfs node
P0P2      S4     disabled
P0P1      S4     disabled  pci:0000:00:1e.0
EUSB      S4     disabled  pci:0000:00:1d.7
MC97      S4     disabled
P0P4      S4     disabled  pci:0000:00:1c.0
P0P5      S4     disabled  pci:0000:00:1c.1
P0P6      S4     disabled  pci:0000:00:1c.2
P0P7      S4     disabled  pci:0000:00:1c.3
P0P8      S4     disabled
P0P9      S4     disabled
USB0      S3     disabled  pci:0000:00:1d.0
USB1      S3     disabled  pci:0000:00:1d.1
USB2      S3     disabled  pci:0000:00:1d.2
USB3      S3     disabled  pci:0000:00:1d.3
[root@smebackup ~]#
Situation under SME 8.2:
Code: [Select]
[root@smebackup ~]# cat /proc/acpi/wakeup
Device  Sleep state     Status
P0P2       4            disabled
P0P1       4            disabled
EUSB       4            disabled
MC97       4            disabled
P0P4       4            disabled
P0P5       4            disabled
P0P6       4            disabled
P0P7       4            disabled
P0P8       4            disabled
P0P9       4            disabled
USB0       3            disabled
USB1       3            disabled
USB2       3            disabled
USB3       3            disabled
[root@smebackup ~]#
It is interesting to note that the LAN device is neither listed under SME 8.2 nor under 9.1. Despite of that, WoL is working under SME 8.2.
« Last Edit: January 05, 2017, 11:08:31 PM by turandot »

Offline TerryF

  • grumpy old man
  • *
  • 1,821
  • +6/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #20 on: January 05, 2017, 11:54:59 PM »
So it looks to be a specific driver issue..

Just to confirm you have a Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet card?

Althought not SME/CentOS/RH, still worth a read
https://bbs.archlinux.org/viewtopic.php?id=192514
https://wiki.archlinux.org/index.php/Wake-on-LAN#Realtek
Plenty of other refs from Mr Google to do with issues

--
qui scribit bis legit

Offline TerryF

  • grumpy old man
  • *
  • 1,821
  • +6/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #21 on: January 06, 2017, 01:46:31 AM »
SME9.1 fully updated shows following

[root@fagehome ~]# modinfo r8168 | grep -i version
ERROR: modinfo: could not find module r8168
[root@fagehome ~]# modinfo r8169 | grep -i version
version:        2.3LK-NAPI
srcversion:     3587FAC210AABB4E2A8CB0F
vermagic:       2.6.32-642.11.1.el6.x86_64 SMP mod_unload modversions

Perhaps try an updated driver.. http://rpm.pbone.net/index.php3/stat/4/idpl/30514405/dir/redhat_el_6/com/#provides

Test box only, a bit dodgy on a prod box...good luck
--
qui scribit bis legit

Offline turandot

  • *
  • 82
  • +0/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #22 on: January 06, 2017, 11:55:46 AM »
On SME 8.2:
Code: [Select]
[root@smebackup ~]# lspci -nn | grep Realtek
01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 02)
[root@smebackup ~]#

On SME 9.1:
Code: [Select]
[root@smebackup ~]# lspci -nn | grep Realtek
01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 02)
[root@smebackup ~]#

On SME 8.2:
Code: [Select]
[root@smebackup ~]# modinfo r8168 | grep -i version
modinfo: could not find module r8168
[root@smebackup ~]# modinfo r8169 | grep -i version
version:        2.3LK-1-NAPI
srcversion:     2F438BE7BC0FF431B08F6F4
[root@smebackup ~]#

On SME 9.1:
Code: [Select]
[root@smebackup ~]# modinfo r8168 | grep -i version
ERROR: modinfo: could not find module r8168
[root@smebackup ~]# modinfo r8169 | grep -i version
version:        2.3LK-NAPI
srcversion:     3587FAC210AABB4E2A8CB0F
vermagic:       2.6.32-642.11.1.el6.x86_64 SMP mod_unload modversions
[root@smebackup ~]#

The NIC is integrated on the motherboard of the system MSI Wind 2713 NetTop, which does not come with any expansion slot. So I don't have any chance to test whatsoever other NIC. I checked the Bios version: it is the latest version available in the Internet. The link LED stays on, when the system is powered down. I am a bit reluctant to make any conclusion, but my gut feeling is pointing to a driver issue as well.

a bit dodgy on a prod box...
This is the point :-( And I don't have too much experience to fumble with kernel modules...

To test this, I downloaded the kernel module as given here: http://rpm.pbone.net/index.php3/stat/4/idpl/30514405/dir/redhat_el_6/com/#provides and pushed it to SME 9.1 to the directory /root . Then I installed it using yum install /root/kmod-r8168-8.040.00-1.el6.elrepo.x86_64.rpm I was surprised, because this took quite a while, but it worked successfully.

Following that, I applied modprobe -r r8169 and modprobe r8168 . This worked as well. Please remember that I don't have too much experience, I tried to step back applying modprobe -r r8168 , which works. However when then applying modprobe r8169 , a kernel panic results, and the system crashes. I can reproduce this: when I reboot and repeat modprobe -r r8168 and modprobe r8169 , I will get another kernel panic.

Booting up again (without applying the manual modprobe commands), everything seems to work fine again. However I am struggling to understand, which kernel module is currently operational:
Code: [Select]
[root@smebackup ~]# modprobe -l r8168
weak-updates/r8168/r8168.ko
[root@smebackup ~]# modprobe -l r8169
kernel/drivers/net/r8169.ko
[root@smebackup ~]#
[root@smebackup ~]# modinfo r8168 | grep -i version
version:        8.040.00-NAPI
srcversion:     BC1CAF8ECC36006913B85E5
vermagic:       2.6.32-279.el6.x86_64 SMP mod_unload modversions
[root@smebackup ~]# modinfo r8169 | grep -i version
version:        2.3LK-NAPI
srcversion:     3587FAC210AABB4E2A8CB0F
vermagic:       2.6.32-642.11.1.el6.x86_64 SMP mod_unload modversions
[root@smebackup ~]#

Interestingly: WoL now works in this configuration!!!  :???: :-o

Do you have any recommendation what I should do? Most important questions I have:
  • Which kernel module is currently working: r8168, or r8169?
  • Should I operate a productive system with this manually added kernel module?

Offline TerryF

  • grumpy old man
  • *
  • 1,821
  • +6/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #23 on: January 06, 2017, 12:27:48 PM »
Cheers all round :-) good result, confirms its the driver module, well to me it does.

What next? file a bug with the results of your testing and the outcome with the newer driver module, this also needs to be done at CentOS and Red Hat, all good fun :-)

From my understanding of discussions in other forums etc the nic is now using the r8168 driver.

As I understand it, a kernel upgrade will revert to whatever is in that kernel, "I think :-)" I am sure someone will correct me if that is otherwise.

There is also a newer driver than the one you used:  http://syd.mirror.rackspace.com/elrepo/elrepo/el6/x86_64/RPMS/ I also presume if you enable the elrepo repo you will benefit from updates using yum, again I stand to be corrected..

Fun isn't it :-)
--
qui scribit bis legit

Offline turandot

  • *
  • 82
  • +0/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #24 on: January 06, 2017, 01:17:25 PM »
Fun isn't it :-)
For sure: you always stumble across stuff you don't know up to now, and an interesting journey what you see and learn 8)

Sorry to be a bit niggling: would you recommend to run this setup on a productive machine?

And you are really recommending to open a bug on https://bugzilla.redhat.com/ ? Against RHEL 6 and kmod r8169? :o Seems (at least to me) honorable...

Offline ReetP

  • *
  • 3,722
  • +5/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #25 on: January 06, 2017, 02:19:17 PM »
However I am struggling to understand, which kernel module is currently operational:

Try this to see what is loaded :

Code: [Select]
lsmod |grep r816
You could try blacklisting either module for testing

Have a look in /etc/modprobe.d/blacklist.conf

blacklist nameOfYourModule

Or prevent it loading in /etc/modprobe.d/dist.conf with

alias nameOfYourModule off

Oddly you seem to have a 8168 based card but v8.2 was using the 8189 driver (check it with lsmod and look at your output above "modinfo: could not find module r8168")

Perhaps they updated the 8169 driver in CentOS 6 and made it more specific so you really need the 8168 driver.

Suggest checking which module gets loaded in v8 first and work from there.

B. Rgds
John
...
1. Read the Manual
2. Read the Wiki
3. Don't ask for support on Unsupported versions of software
4. I have a job, wife, and kids and do this in my spare time. If you want something fixed, please help.

Bugs are easier than you think: http://wiki.contribs.org/Bugzilla_Help

If you love SME and don't want to lose it, join in: http://wiki.contribs.org/Koozali_Foundation

Offline turandot

  • *
  • 82
  • +0/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #26 on: January 06, 2017, 03:00:26 PM »
Output from SME 8.2 (out of the box):
Code: [Select]
[root@smebackup ~]# lsmod | grep r816
r8169                  43077  0
mii                     9409  1 r8169
[root@smebackup ~]#

And from SME 9.1 (patched with kmod r8168):
Code: [Select]
[root@smebackup ~]# lsmod | grep r816
r8168                 324411  0
[root@smebackup ~]#

Why the heck does SME 9.1 crash with a kernel panic, if I now try to load r8169!? I see only a single explanation: the installation of r8168 changed something, which is not compliant with r8169. Isn't this one more indication, that something is wrong with r8169!?

Offline TerryF

  • grumpy old man
  • *
  • 1,821
  • +6/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #27 on: January 06, 2017, 03:12:40 PM »
Oddly you seem to have a 8168 based card but v8.2 was using the 8189 driver (check it with lsmod and look at your output above "modinfo: could not find module r8168")

Perhaps they updated the 8169 driver in CentOS 6 and made it more specific so you really need the 8168 driver.
B. Rgds
John

That's what the discussion revolves around in the CentOS, arch and Ubuntu forums re r8169 is being hence issues arising other than just wol. Resolved by changing to the r8168 driver.  In our case it seems as thought the version of the r8169 driver ion 8.2 was still working regarding wol but the later version in 9.1 is not.

If wol is required on the production box then yes, elrepo is reputable and a trusted source. Also if no bug is lodged with RH etc then when a kernel update is released you will have to update the kmod elrepo module when they produce an updated rpm.

re opening a bug in RH and CentOS, yes, its how the 8.2 wol bug in the tg3 driver was resolved by RH updating the kernel with the updated  one, just took a couple of months :-) just register on both bugzillas and away you go. There is a Red Hat bug for the 8.2 wol bug, unfortunately kernel bugs are private so I cannot show it to you.
--
qui scribit bis legit

Offline turandot

  • *
  • 82
  • +0/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #28 on: January 07, 2017, 12:03:31 PM »
I opened bug report 1410994 "WoL does not work with r8169 on RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 02)" on bugzilla.redhat.com . I have dropped in information, which summarizes the testing as follows:



Description of problem: Wake on LAN (WoL) does not work


Version-Release number of selected component (if applicable):

On RHEL 6.7:

modinfo r8169 | grep -i version
version:        2.3LK-NAPI
srcversion:     3587FAC210AABB4E2A8CB0F
vermagic:       2.6.32-642.11.1.el6.x86_64 SMP mod_unload modversions


How reproducible: 100%


Steps to Reproduce:

1. Install RHEL 5 on a system using HDD1 --> WoL works

On RHEL 5:

modinfo r8169 | grep -i version
version:        2.3LK-1-NAPI
srcversion:     2F438BE7BC0FF431B08F6F4


2. Take out HDD1, swap in HDD2, do fresh install of RHEL 6.7

Actual results: WoL does not work


Expected results: WoL should work


Additional info:

WoL works again with RHEL 6.7, if the main power line was cycled, and the NIC did a cold start. So the NIC "only" refuses the WoL magic packet, if the main power was kept switched on all the time. (Together with the RHEL 5 results, hardware issues can consequently be excluded.)


The r8168 driver for RHEL as supplied here http://rpm.pbone.net/index.php3/stat/4/idpl/30514405/dir/redhat_el_6/com/#provides works i.e. supports WoL.

Steps to achieve that:
a) download driver package kmod-r8168-8.040.00-1.el6.elrepo.x86_64.rpm
b) drop to e.g. /root/kmod-r8168-8.040.00-1.el6.elrepo.x86_64.rpm
c) install by yum install /root/kmod-r8168-8.040.00-1.el6.elrepo.x86_64.rpm
d) modprobe -r r8169
e) modprobe r8168

modinfo r8168 | grep -i version
version:        8.040.00-NAPI
srcversion:     BC1CAF8ECC36006913B85E5
vermagic:       2.6.32-279.el6.x86_64 SMP mod_unload modversions

Having that WoL supporting configuration, I cannot revert to r8169 anymore. Step a) of the following procedure works, but step b)...

a) modprobe -r r8168
b) modprobe r8169

...causes a kernel panic and hence a system crash. After reboot (loading r8168) everything is fine again.



Happy waiting ;-)

Offline TerryF

  • grumpy old man
  • *
  • 1,821
  • +6/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #29 on: January 08, 2017, 01:56:08 AM »
Nice :-) If you want to tie it all up neatly you could also raise a bug here and add a link to the RH bug there, at worst the forum posts here and the bug will tell any SME user whats what and how to  get a solution that works while RH get on it.

Great bit of sleuthing, if the last time this occurred is any indication it will be a couple of months before a resolution and a updated kernel appears. RH will list in the kernels changelog the fix when they do it.

Hope you don't mind me to have kept after you to do the triage :-) its just once you go through the process you learn something, get a bit of a kick :-) and show others it is relatively straightforward..

Good Job, nothing better than a bit of global collaboration :-)
--
qui scribit bis legit

Offline ReetP

  • *
  • 3,722
  • +5/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #30 on: January 08, 2017, 02:02:58 AM »
Hope you don't mind me to have kept after you to do the triage :-) its just once you go through the process you learn something, get a bit of a kick :-) and show others it is relatively straightforward..

Bloody slave driver....

;-)
...
1. Read the Manual
2. Read the Wiki
3. Don't ask for support on Unsupported versions of software
4. I have a job, wife, and kids and do this in my spare time. If you want something fixed, please help.

Bugs are easier than you think: http://wiki.contribs.org/Bugzilla_Help

If you love SME and don't want to lose it, join in: http://wiki.contribs.org/Koozali_Foundation

Offline TerryF

  • grumpy old man
  • *
  • 1,821
  • +6/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #31 on: January 08, 2017, 02:11:50 AM »
Why the heck does SME 9.1 crash with a kernel panic, if I now try to load r8169!? I see only a single explanation: the installation of r8168 changed something, which is not compliant with r8169. Isn't this one more indication, that something is wrong with r8169!?

and lots of refs in google to r8169 causing a crash..

and ReetP knows what my response is :-)
--
qui scribit bis legit

Offline ReetP

  • *
  • 3,722
  • +5/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #32 on: January 08, 2017, 02:14:21 AM »
Chortle :-)
...
1. Read the Manual
2. Read the Wiki
3. Don't ask for support on Unsupported versions of software
4. I have a job, wife, and kids and do this in my spare time. If you want something fixed, please help.

Bugs are easier than you think: http://wiki.contribs.org/Bugzilla_Help

If you love SME and don't want to lose it, join in: http://wiki.contribs.org/Koozali_Foundation

Offline TerryF

  • grumpy old man
  • *
  • 1,821
  • +6/-0
--
qui scribit bis legit

Offline turandot

  • *
  • 82
  • +0/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #34 on: January 08, 2017, 09:43:20 PM »
Thanks for all your help  8-)

I have now tested the r8168 driver from ELRepo.org, it works perfectly  :grin:  :grin:  :grin: Here are the detailed steps, how made this happen.

First make a clean install of SME 9.1 e.g. from CDROM. After that apply all available updates.

Next enable ELRepo.org repository, details see here: https://wiki.contribs.org/ELRepo#tab=For_SME_9

Check that the repository has been added:
Code: [Select]
[root@smebackup ~]# /sbin/e-smith/audittools/repositories
base: enabled
centosplus: disabled
contrib: disabled
elrepo: disabled            <--- see here
extras: disabled
fasttrack: disabled
smeaddons: enabled
smecontribs: disabled
smedev: disabled
smeextras: enabled
smeos: enabled
smetest: disabled
smeupdates: enabled
smeupdates-testing: disabled
updates: enabled
[root@smebackup ~]#

Check driver status:
Code: [Select]
[root@smebackup ~]# lsmod |grep r816
r8169                  74333  0            <--- see here: r8169 is loaded
mii                     5376  1 r8169
[root@smebackup ~]# modprobe -l r8168            <--- see here: r8168 is not present
[root@smebackup ~]# modprobe -l r8169
kernel/drivers/net/r8169.ko            <--- but r8169 is present
[root@smebackup ~]#

Update ELRepo repository:
Code: [Select]
[root@smebackup ~]# yum update --enablerepo=elrepo
Geladene Plugins: fastestmirror, smeserver
Einrichten des Aktualisierungsprozess
Loading mirror speeds from cached hostfile
 * base: mirror.23media.de
 * smeaddons: mirrors.rbx.opencare.nl
 * smeextras: mirrors.rbx.opencare.nl
 * smeos: mirrors.rbx.opencare.nl
 * smeupdates: mirrors.rbx.opencare.nl
 * updates: repo.de.bigstepcloud.com
elrepo                                                   | 2.9 kB     00:00 ...
elrepo/primary_db                                        | 727 kB     00:02
Keine Pakete für die Aktualisierung markiert
[root@smebackup ~]#

No driver is installed without explicit loading from ELRepo:
Code: [Select]
[root@smebackup ~]# yum install kmod-r8168
Geladene Plugins: fastestmirror, smeserver
Einrichten des Installationsprozess
Loading mirror speeds from cached hostfile
 * base: mirror.23media.de
 * smeaddons: mirrors.rbx.opencare.nl
 * smeextras: mirrors.rbx.opencare.nl
 * smeos: mirrors.rbx.opencare.nl
 * smeupdates: mirrors.rbx.opencare.nl
 * updates: repo.de.bigstepcloud.com
Kein Paket kmod-r8168 verfügbar.            <--- r8168 is not downloaded, because ELRepo repository is disabled
Fehler: Nichts zu tun
[root@smebackup ~]#

However when enabling ELRepo, the driver is downloaded and installed, and the GPG key is added:
Code: [Select]
[root@smebackup ~]# yum install --enablerepo=elrepo kmod-r8168
Geladene Plugins: fastestmirror, smeserver
Einrichten des Installationsprozess
Loading mirror speeds from cached hostfile
 * base: mirror.23media.de
 * smeaddons: mirrors.rbx.opencare.nl
 * smeextras: mirrors.rbx.opencare.nl
 * smeos: mirrors.rbx.opencare.nl
 * smeupdates: mirrors.rbx.opencare.nl
 * updates: repo.de.bigstepcloud.com
Löse Abhängigkeiten auf
--> Führe Transaktionsprüfung aus
---> Package kmod-r8168.x86_64 0:8.043.01-1.el6.elrepo will be installiert
--> Abhängigkeitsauflösung beendet

Abhängigkeiten aufgelöst

================================================================================
 Paket            Arch         Version                       Repository   Grösse
================================================================================
Installieren:
 kmod-r8168       x86_64       8.043.01-1.el6.elrepo         elrepo        95 k

Vorgangsübersicht
================================================================================
Install       1 Package(s)

Gesamte Downloadgrösse: 95 k
Installed size: 728 k
Ist dies in Ordnung? [j/N] :j
Lade Pakete herunter:
kmod-r8168-8.043.01-1.el6.elrepo.x86_64.rpm              |  95 kB     00:00
Warnung: rpmts_HdrFromFdno: Header V4 DSA/SHA1 Signature, Schlüssel-ID baadae52: NOKEY
Retrieving key from http://elrepo.org/RPM-GPG-KEY-elrepo.org
Importing GPG key 0xBAADAE52:
 Userid: "elrepo.org (RPM Signing Key for elrepo.org) <secure@elrepo.org>"
 From  : http://elrepo.org/RPM-GPG-KEY-elrepo.org
Ist dies in Ordnung? [j/N] :j            <--- GPG key is added:
Führe rpm_check_debug durch
Führe Verarbeitungstest durch
Verarbeitungstest erfolgreich
Führe Verarbeitung durch
  Installieren : kmod-r8168-8.043.01-1.el6.elrepo.x86_64                    1/1
Working. This may take some time ...
Done.
  Verifying    : kmod-r8168-8.043.01-1.el6.elrepo.x86_64                    1/1

Installiert:
  kmod-r8168.x86_64 0:8.043.01-1.el6.elrepo

Komplett!
[root@smebackup ~]#

Now the r8168 driver is present, but not yet loaded:
Code: [Select]
[root@smebackup ~]# lsmod |grep r816
r8169                  74333  0
mii                     5376  1 r8169
[root@smebackup ~]# modprobe -l r8168
weak-updates/r8168/r8168.ko
[root@smebackup ~]# modprobe -l r8169
kernel/drivers/net/r8169.ko
[root@smebackup ~]#

Now unload r8169, and load r8168:
Code: [Select]
[root@smebackup ~]# modprobe -r r8169
[root@smebackup ~]# modprobe r8168

Last check on driver status, r8168 is now loaded:
Code: [Select]
[root@smebackup ~]# lsmod | grep r816
r8168                 329880  0
[root@smebackup ~]# modprobe -l r8168
weak-updates/r8168/r8168.ko
[root@smebackup ~]# modprobe -l r8169
kernel/drivers/net/r8169.ko
[root@smebackup ~]#

Now do a reboot (for testing), and check driver status again, that r8168 loading survives a reboot:
Code: [Select]
[root@smebackup ~]# signal-event reboot

[root@smebackup ~]# lsmod | grep r816
r8168                 329880  0
[root@smebackup ~]#

Now halt the server:
Code: [Select]
[root@smebackup ~]# signal-event halt

And bingo: WoL now works in this configuration  :grin: :grin: :grin:

Background information:

https://wiki.hetzner.de/index.php/Installation_des_r8168-Treibers/en
http://elrepo.org/tiki/tiki-index.php

turandot
« Last Edit: January 08, 2017, 09:54:04 PM by turandot »

Offline TerryF

  • grumpy old man
  • *
  • 1,821
  • +6/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #35 on: January 09, 2017, 12:19:11 AM »
Mate...I like your work :-)

Excellent triage, testing and outcome, pats on the back..

Now I am off to do the same to a white box server I have running for a community group that has worked but always been slow, the investigation etc of this driver issue has given me a possible solution..

Now need to wait for RH to look to adding an updated driver..

Also have read what seems to be conflicting advise re driver reverting with a Kernel update, can someone confirm if the elrepo kmod driver will still be active on a kernel update. 

Would be a pleasure to buy you a coffee if you are ever in Melbourne Oz.. :-)
« Last Edit: January 09, 2017, 12:22:19 AM by TerryF »
--
qui scribit bis legit

Offline turandot

  • *
  • 82
  • +0/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #36 on: January 09, 2017, 07:43:55 PM »
Mate...I like your work :-)
Thanks for your compliments  8)

Excellent triage, testing and outcome
I am working in the space business. Here you learn it the hard way how to prepare and run tests :grin:

...the investigation etc of this driver issue has given me a possible solution..
This is what I like most: one successful collaboration inspires ideas for the next task :)

Would be a pleasure to buy you a coffee if you are ever in Melbourne Oz.. :-)
Just for the coffee would be probably a bit too expensive, since it would require a flight around half the globe! But you never know...

Redhat has at least assigned the bug report to dedicated persons.

Offline TerryF

  • grumpy old man
  • *
  • 1,821
  • +6/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #37 on: January 09, 2017, 07:55:05 PM »
Just for the coffee would be probably a bit too expensive, since it would require a flight around half the globe! But you never know...

You never ever know :-) Formula 1 in March :-)

Redhat has at least assigned the bug report to dedicated persons.

Yes, just a waiting game now, if they aren't told then it would definitely never get looked at.
--
qui scribit bis legit

Offline turandot

  • *
  • 82
  • +0/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #38 on: January 12, 2017, 08:26:22 PM »
I reported that I had opened bug report https://bugzilla.redhat.com/show_bug.cgi?id=1410994

Things started to move. The bug is assigned, I was requested to provide more info (output of dmesg and ethtool under various conditions), I provided that information.

https://bugs.contribs.org/show_bug.cgi?id=7928 reports a comparable bug which was managed through https://bugzilla.redhat.com/show_bug.cgi?id=996331 . I gave the hint to Redhat to cross check that bug / bug fix in RHEL 5.

turandot

Offline TerryF

  • grumpy old man
  • *
  • 1,821
  • +6/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #39 on: January 12, 2017, 11:14:43 PM »
Love it when a plan bears fruit :-)

If you add me as a CC contact in your Red Hat bug I will be able to read it, kernel bugs are made private and only accessible by registered users etc, which I am.

--
qui scribit bis legit

Offline turandot

  • *
  • 82
  • +0/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #40 on: January 13, 2017, 10:52:50 PM »
If you add me as a CC contact in your Red Hat bug
Easier said than done... I need to know your bugzilla contact email address for this, right? I would have sent a private message to request that, but I am not allowed to post private messages  :???:

Redhat has worked on the bug on a test system, but they could not reproduce it. They asked me to use RHEL 6.8 instead of 6.7, I used centOS 6.8. And bingo: I reproduced the faulty behaviour. First I thought about using CentOS 6.7, but with duplication under 6.8 I don't think that it makes much sense. Terry, do you think that I should give CentOS 7 a try?

turandot

Offline TerryF

  • grumpy old man
  • *
  • 1,821
  • +6/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #41 on: January 13, 2017, 11:45:38 PM »
tfage at yahoo dot com dot au will find me..

CentOS 7 is a very different animal :-) I don't think it would server any useful purpose just now, personal curiosity not withstanding.

Have to question whether Red Hat used the same Ethernet card/motherboard Realtek chipset version in their testing.
« Last Edit: January 14, 2017, 08:47:14 AM by TerryF »
--
qui scribit bis legit

Offline turandot

  • *
  • 82
  • +0/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #42 on: January 14, 2017, 10:03:06 AM »
I have added you to the CC list.

Offline TerryF

  • grumpy old man
  • *
  • 1,821
  • +6/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #43 on: January 14, 2017, 01:20:25 PM »
I have added you to the CC list.

Sweet, looking at the comments etc, there may very well be differences between the stand alone nic they used to test with and the, I would think, older spec of an on board system. The proof is in the testing :-)
--
qui scribit bis legit

Offline turandot

  • *
  • 82
  • +0/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #44 on: January 14, 2017, 04:43:33 PM »
Yes, the mainboard with onboard NIC is from 2007 or 2008.

I tried to install CentOS 7 on the machine, but I failed (unknown error). Looking into https://wiki.centos.org/About/Product , I suspect that there is not enough memory installed (1GB for 2 logical cores) versus required (1GB per logical CPU).

I will now wait for Redhat's actions.

Offline turandot

  • *
  • 82
  • +0/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #45 on: January 15, 2017, 08:15:12 PM »
I am not too surprised: the installation of SME 10 Alpha2 fails with identical symptoms as the CentOS 7 installation.

Now I am a bit concerned with regard to my current machine. Is it worth to invest much more work? What are the minimum hardware requirements for SME 10? Identical to CentOS 7?

Offline TerryF

  • grumpy old man
  • *
  • 1,821
  • +6/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #46 on: January 15, 2017, 10:23:51 PM »
Yes..although memory is cheap..

I have used an old IBM thinkcentre desktop that chugs away happily in a local community house computer room as a file/media/print  server currently using SME9.1, more than adequate for what it does, been doing its stuff for 3 years now.  They have limited financial resources, I think it cost something like $30 used.

By the time SME9 goes EOL and hopefully Koozali is still active with SME10 I think it will be time then to retire the thinkcentre and get another cheap used box that is compatable. :-)
--
qui scribit bis legit

Offline TerryF

  • grumpy old man
  • *
  • 1,821
  • +6/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #47 on: January 20, 2017, 03:57:47 PM »
May be of use

Red Hat Knowledgebase article - 13 Jan 2016

https://access.redhat.com/solutions/1595533
--
qui scribit bis legit

Offline turandot

  • *
  • 82
  • +0/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #48 on: January 26, 2017, 10:18:02 PM »
Thanks for this additional hint. I will check with SME 9.1 the other day.

This evening I have upgraded my machine to 2 GByte RAM (RAM on Ebay is indeed cheap), but this did not solve my installation problem with SME 10 Alpha 2 as well as CentOS 7. So I made some further tests.

Obviously both distros did not like the HDD partion (created by SME 9.1). After wiping the partion table and the first cylinders with dd if=/dev/zero of=/dev/sda bs=4M count=200, I at least was able to initiate the installation of both distros. However both distros obviously have problems with the graphical user interface on my machine. The GUI gets chopped: seems to be a VGA driver issue. Appending the boot option text  I now have to fiddle with text mode installation. This is currently running. Strange problems with my machine...

I will report more in the next days.

Offline Stefano

  • *
  • 10,836
  • +2/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #49 on: January 26, 2017, 10:19:52 PM »
please report in bugzilla, thank you

Offline turandot

  • *
  • 82
  • +0/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #50 on: February 14, 2017, 07:15:50 PM »
In the meantime I was able to duplicate the problem on CentOS 7.3, and I logged a second bug on buzilla @RedHat. They were now closed by RedHat, both for RHEL 6 as well as RHEL 7:
Quote
We got hold of a 8168c (21) model just as yours.  However, even after a couple of days testing we can't get it to honor WoL requests at all, independently of using the Linux in-tree 8169 driver, or the Realtek-provided 8168 driver.  We tested this in different hardware setups as well as in different network setups, known to WoL well using a Realtek 8168f.

To top it off, the 8168c we got for testing can't WoL after a power cycle, because it switches itself to 'WoL off' on a cold start.

Other than that, the NIC works as desired.  Our conclusion is that the devices differ in some cases even when using seemingly identical hardware, and the devices are apparently prone to BIOS or hardware differences.

Given that we're unable to reproduce this problem with reasonable effort, I'll close this issue (as well as BZ 1410994) as CANTFIX.

So I think, this is it :sad: Probably I have to send my machine to the Happy Hunting Grounds in the mid term.

Thanks for your advice and help!

turandot

Offline TerryF

  • grumpy old man
  • *
  • 1,821
  • +6/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #51 on: February 14, 2017, 11:52:24 PM »
ah, bummer...not unexpected actually..

You could stay with the kmod driver and keep the old girl going :-)

Great triage and investigation, not such a good outcome but still an outcome that is understood and can be worked with.
--
qui scribit bis legit

Offline TerryF

  • grumpy old man
  • *
  • 1,821
  • +6/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #52 on: February 14, 2017, 11:54:13 PM »
If you did want to keep the old hardware in service this is worth a read re using the kmod packages

https://elrepo.org/tiki/wl-kmod
--
qui scribit bis legit

Offline TerryF

  • grumpy old man
  • *
  • 1,821
  • +6/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #53 on: January 23, 2018, 02:20:44 AM »
Even if it is an old thread :-)

Looks like the end of the road :  https://bugzilla.redhat.com/show_bug.cgi?id=1417367#c14

RH private bug, need to be logged in to RH Bugzilla to see.
« Last Edit: January 23, 2018, 02:23:32 AM by TerryF »
--
qui scribit bis legit

Offline Jean-Philippe Pialasse

  • *
  • 2,747
  • +11/-0
  • aka Unnilennium
    • http://smeserver.pialasse.com
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #54 on: January 23, 2018, 05:32:04 AM »
even logged:

You are not authorized to access bug #1417367.

Most likely the bug has been restricted for internal development processes and we cannot grant access.

Offline TerryF

  • grumpy old man
  • *
  • 1,821
  • +6/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #55 on: January 23, 2018, 07:08:32 AM »
Added you, JP, to the RH bugs CC list
--
qui scribit bis legit

Offline TerryF

  • grumpy old man
  • *
  • 1,821
  • +6/-0
Re: Waking up of SME 9.1 using WoL (SME server used for Affa)
« Reply #56 on: January 23, 2018, 07:12:20 AM »
These are last couple of comment from the RH rep re the bug ie wont fix, move on :-)

Corinna Vinschen 2017-02-03 04:54:03 EST
(In reply to turandot from comment #9)
> Hi Corinna,
>
> is there a r8168 available within RHEL 7.x? I don't think so...

No, there isn't, of course, since the r8168 driver is covered by
patents incompatible with the Linux source tree.

I refered to it as an alternative since you were already using it
per https://bugzilla.redhat.com/show_bug.cgi?id=1410994

> Therefore I installed the r8168 from elrepo.org and did the following:
> [...]
> Then I once again did the WoL test, now with r6168 loaded:
>
> - init 0
> - Test WoL: FAIL
> - switch off main line
> - wait 10 seconds
> - switch on main line (system does not start automatically)
> - Test WoL: OK
>
> So this driver does not support WoL as well. (The elrepo r8168 for RHEL 6
> does support WoL.)

This isn't quite correct.  Both drivers, r8168 from Realtek and r8169
from the Linux source tree support WoL.  The problem are some of the NICs
which just don't always work as desired, sometimes even dependent on the
machine they are plugged into.  WoL is a delicate issue, susceptible to
all kinds of hardware differences.

Please note that the 8168c model is quite old and EOLed since 2009 as far
as I know.  It has been long since replaced by more modern chpsets like
8168evl or 8168f used on many third-party PCIe NICs, the latest of which
is the 8168h.

As I outlined in my replies, I have no trouble with WoL at all with the
8168f NIC I have available in my test setup, neither with RHEL 6.8, nor with
RHEL 7.3.  It may be a feasible option to upgrade the NIC to a later version,
especially given the low cost of the device.

> Then I searched the dmesg output for the requested line:
>
>    "Realtek PCIe GBE Family Controller mcfg = 1234"
>
> Unfortunately I did not find any output like this. I just see the following:

My bad.  I realised belatedly that the above line is only printed if
the driver is running in debug mode.  If you want to see the version of
your 8168c model, you have to download the r8168 driver from Realtek,
apply the newly attached patch (8168.diff) and build and install it.

But...

> Did I miss something? Should I compile the kernel with the provided
> patch as per comment 8?

...yes, this would be the better option.


Regards,
Corinna


Corinna Vinschen 2017-02-14 10:16:29 EST
Hi turandot,

We got hold of a 8168c (21) model just as yours.  However, even after a
couple of days testing we can't get it to honor WoL requests at all,
independently of using the Linux in-tree 8169 driver, or the
Realtek-provided 8168 driver.  We tested this in different hardware
setups as well as in different network setups, known to WoL well using
a Realtek 8168f.

To top it off, the 8168c we got for testing can't WoL after a power
cycle, because it switches itself to 'WoL off' on a cold start.

Other than that, the NIC works as desired.  Our conclusion is that the
devices differ in some cases even when using seemingly identical
hardware, and the devices are apparently prone to BIOS or hardware
differences.

Given that we're unable to reproduce this problem with reasonable
effort, I'll close this issue (as well as BZ 1410994) as CANTFIX.


Corinna
Status: ASSIGNED → CLOSED
Resolution: --- → CANTFIX
Last Closed: 2017-02-14 10:16:29
--
qui scribit bis legit