Bug 238411 - [igb] wake on lan not working with Intel I210
Summary: [igb] wake on lan not working with Intel I210
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 12.0-RELEASE
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-net (Nobody)
URL:
Keywords: IntelNetworking, needs-qa, regression
Depends on:
Blocks:
 
Reported: 2019-06-08 03:34 UTC by Nikita Druba
Modified: 2020-10-31 11:36 UTC (History)
1 user (show)

See Also:

Attachments
dmesg.boot (12.77 KB, text/plain)
2019-06-11 09:39 UTC, Nikita Druba 		no flags Details
pciconf -lv (4.69 KB, text/plain)
2019-06-11 09:39 UTC, Nikita Druba 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nikita Druba 2019-06-08 03:34:02 UTC 
Hi to all! 

After updating to 12.0-RELEASE wake on lan function stoped working in my configuration.
I have Intel I210 Gigabit Network Connection, driver igb.
rc.conf at server that need to wake up:

ifconfig_igb0="-wol_ucast -wol_mcast wol_magic"

powered on at another server by:

wake igb0 11:22:33:44:55:66;

I tryed to change sysctl by
dev.igb.0.wake=0 -> 1
but no result.

Can anybody confirm this bug?
Comment 1 Kubilay Kocak freebsd_committer freebsd_triage 2019-06-11 05:18:41 UTC 
@NIkita Could you please provide additional information, including:

- Exact version (uname -a) the update was 'from'
- Exact system versions now (uname -a)
- /var/run/dmesg.boot output (as an attachment)
- pciconf -lv output (as an attachment
Comment 2 Nikita Druba 2019-06-11 09:39:04 UTC 
Created attachment 204981 [details]
dmesg.boot
Comment 3 Nikita Druba 2019-06-11 09:39:49 UTC 
Created attachment 204982 [details]
pciconf -lv
Comment 4 Nikita Druba 2019-06-11 09:40:27 UTC 
(In reply to Kubilay Kocak from comment #1)
updated from 11.1-RELEASE r318763
to FreeBSD SERVERBAK 12.0-RELEASEp5 FreeBSD 12.0-RELEASE-p5 r348792 MYKERNEL amd64
Comment 5 Yuran 2020-10-31 11:36:07 UTC 
A similar problem is reproduced on 12.2-release with Intel I210 hardware