Hardware Initialization Failed with Intel I219-V

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Hardware Initialization Failed with Intel I219-V

Daniel Jakots-3
>Synopsis:
>Category:
>Environment:
        System      : OpenBSD 6.0
        Details     : OpenBSD 6.0-current (GENERIC.MP) #0: Wed Nov 30 09:19:28 MST 2016
                         [hidden email]:/usr/src/sys/arch/amd64/compile/GENERIC.MP

        Architecture: OpenBSD.amd64
        Machine     : amd64
>Description:
        I received a few days ago a thinkpad x260. Sometimes em0 won't show up and in
dmesg it says:
em0 at pci0 dev 31 function 6 "Intel I219-V" rev 0x21: msi
em0: Hardware Initialization Failed
em0: Unable to initialize the hardware

On other reboots, it works fine.


dmesg:
OpenBSD 6.0-current (GENERIC.MP) #0: Wed Nov 30 09:19:28 MST 2016
    [hidden email]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8451014656 (8059MB)
avail mem = 8190332928 (7810MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xd7bfb000 (65 entries)
bios0: vendor LENOVO version "R02ET50W (1.23 )" date 09/20/2016
bios0: LENOVO 20F6CTO1WW
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP UEFI SSDT SSDT ECDT HPET APIC MCFG SSDT SSDT DBGP DBG2 BOOT BATB SLIC SSDT SSDT MSDM ASF! FPDT UEFI
acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP8(S4) XHCI(S3)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpiec0 at acpi0
acpihpet0 at acpi0: 23999999 Hz
acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2195.78 MHz
cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 24MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2194.90 MHz
cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 1 (application processor)
cpu2: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2194.90 MHz
cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 1, core 0, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2194.90 MHz
cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec00000, version 20, 120 pins
acpimcfg0 at acpi0 addr 0xf8000000, bus 0-63
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PEG0)
acpiprt2 at acpi0: bus -1 (PEG1)
acpiprt3 at acpi0: bus -1 (PEG2)
acpiprt4 at acpi0: bus 2 (EXP1)
acpiprt5 at acpi0: bus 4 (EXP3)
acpiprt6 at acpi0: bus -1 (EXP4)
acpiprt7 at acpi0: bus -1 (EXP5)
acpiprt8 at acpi0: bus -1 (EXP8)
acpicpu0 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33), C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33), C1(1000@1 mwait.1), PSS
acpicpu2 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33), C1(1000@1 mwait.1), PSS
acpicpu3 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151 mwait.1@0x33), C1(1000@1 mwait.1), PSS
acpipwrres0 at acpi0: PUBS, resource for XHCI
acpipwrres1 at acpi0: PG00, resource for PEG0
acpipwrres2 at acpi0: PG01, resource for PEG1
acpipwrres3 at acpi0: PG02, resource for PEG2
acpipwrres4 at acpi0: WRST
acpipwrres5 at acpi0: WRST
acpitz0 at acpi0: critical temperature is 128 degC
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
"LEN0071" at acpi0 not configured
"LEN2014" at acpi0 not configured
"INT3F0D" at acpi0 not configured
acpibat0 at acpi0: BAT0 model "45N1111" serial 10768 type LiP oem "SONY"
acpibat1 at acpi0: BAT1 model "45N1767" serial  3754 type LION oem "SANYO"
acpiac0 at acpi0: AC unit online
acpithinkpad0 at acpi0
"PNP0C14" at acpi0 not configured
"PNP0C14" at acpi0 not configured
"PNP0C14" at acpi0 not configured
"INT3394" at acpi0 not configured
acpivideo0 at acpi0: GFX0
acpivout at acpivideo0 not configured
cpu0: Enhanced SpeedStep 2195 MHz: speeds: 2301, 2300, 2200, 2100, 2000, 1800, 1700, 1500, 1400, 1300, 1100, 1000, 800, 700, 500, 400 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel Core 6G Host" rev 0x08
"Intel HD Graphics 520" rev 0x07 at pci0 dev 2 function 0 not configured
xhci0 at pci0 dev 20 function 0 "Intel 100 Series xHCI" rev 0x21: msi
usb0 at xhci0: USB revision 3.0
uhub0 at usb0 configuration 1 interface 0 "Intel xHCI root hub" rev 3.00/1.00 addr 1
pchtemp0 at pci0 dev 20 function 2 "Intel 100 Series Thermal" rev 0x21
"Intel 100 Series MEI" rev 0x21 at pci0 dev 22 function 0 not configured
ahci0 at pci0 dev 23 function 0 "Intel 100 Series AHCI" rev 0x21: msi, AHCI 1.3.1
ahci0: port 1: 6.0Gb/s
scsibus1 at ahci0: 32 targets
sd0 at scsibus1 targ 1 lun 0: <ATA, SanDisk SD8TB8U2, X412> SCSI3 0/direct fixed naa.5001b444a6823dff
sd0: 244198MB, 512 bytes/sector, 500118192 sectors, thin
ppb0 at pci0 dev 28 function 0 "Intel 100 Series PCIE" rev 0xf1: msi
pci1 at ppb0 bus 2
rtsx0 at pci1 dev 0 function 0 "Realtek RTS522A Card Reader" rev 0x01: msi
sdmmc0 at rtsx0: 4-bit
ppb1 at pci0 dev 28 function 2 "Intel 100 Series PCIE" rev 0xf1: msi
pci2 at ppb1 bus 4
iwm0 at pci2 dev 0 function 0 "Intel Dual Band Wireless AC 8260" rev 0x3a, msi
pcib0 at pci0 dev 31 function 0 "Intel 100 Series LPC" rev 0x21
"Intel 100 Series PMC" rev 0x21 at pci0 dev 31 function 2 not configured
azalia0 at pci0 dev 31 function 3 "Intel 100 Series HD Audio" rev 0x21: msi
azalia0: codecs: Realtek/0x0293, Intel/0x2809, using Realtek/0x0293
audio0 at azalia0
ichiic0 at pci0 dev 31 function 4 "Intel 100 Series SMBus" rev 0x21: apic 2 int 16
iic0 at ichiic0
em0 at pci0 dev 31 function 6 "Intel I219-V" rev 0x21: msi
em0: Hardware Initialization Failed
em0: Unable to initialize the hardware
isa0 at pcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard
pms0 at pckbc0 (aux slot)
wsmouse0 at pms0 mux 0
wsmouse1 at pms0 mux 0
pms0: Synaptics clickpad, firmware 8.1
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
vmm disabled by firmware
vmm at mainbus0 not configured
efifb0 at mainbus0: 1920x1080, 32bpp
wsdisplay0 at efifb0 mux 1: console (std, vt100 emulation), using wskbd0
wsdisplay0: screen 1-5 added (std, vt100 emulation)
uhidev0 at uhub0 port 2 configuration 1 interface 0 "Logitech USB Optical Mouse" rev 2.00/72.00 addr 2
uhidev0: iclass 3/1
ums0 at uhidev0: 3 buttons, Z dir
wsmouse2 at ums0 mux 0
ugen0 at uhub0 port 7 "Intel product 0x0a2b" rev 2.00/0.01 addr 3
uvideo0 at uhub0 port 8 configuration 1 interface 0 "Chicony Electronics Co.,Ltd. Integrated Camera" rev 2.00/0.29 addr 4
video0 at uvideo0
vscsi0 at root
scsibus2 at vscsi0: 256 targets
softraid0 at root
scsibus3 at softraid0: 256 targets
sd1 at scsibus3 targ 1 lun 0: <OPENBSD, SR CRYPTO, 006> SCSI2 0/direct fixed
sd1: 149999MB, 512 bytes/sector, 307199472 sectors
root on sd1a (1554353ea1ae25b4.a) swap on sd1b dump on sd1b
iwm0: hw rev 0x200, fw ver 16.242414.0, address f0:d5:bf:7f:1b:9c

usbdevs:
Controller /dev/usb0:
addr 1: super speed, self powered, config 1, xHCI root hub(0x0000), Intel(0x8086), rev 1.00
 port 1 disabled
 port 2 addr 2: low speed, power 100 mA, config 1, USB Optical Mouse(0xc077), Logitech(0x046d), rev 72.00
 port 3 disabled
 port 4 disabled
 port 5 disabled
 port 6 disabled
 port 7 addr 3: full speed, self powered, config 1, product 0x0a2b(0x0a2b), Intel(0x8087), rev 0.01
 port 8 addr 4: high speed, power 500 mA, config 1, Integrated Camera(0xb52c), Chicony Electronics Co.,Ltd.(0x04f2), rev 0.29, iSerialNumber 0001
 port 9 disabled
 port 10 disabled
 port 11 disabled
 port 12 disabled
 port 13 disabled
 port 14 disabled
 port 15 disabled
 port 16 disabled

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Hardware Initialization Failed with Intel I219-V

Mike Belopuhov-5
On 5 December 2016 at 11:16,  <[hidden email]> wrote:

>>Synopsis:
>>Category:
>>Environment:
>         System      : OpenBSD 6.0
>         Details     : OpenBSD 6.0-current (GENERIC.MP) #0: Wed Nov 30 09:19:28 MST 2016
>                          [hidden email]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
>
>         Architecture: OpenBSD.amd64
>         Machine     : amd64
>>Description:
>         I received a few days ago a thinkpad x260. Sometimes em0 won't show up and in
> dmesg it says:
> em0 at pci0 dev 31 function 6 "Intel I219-V" rev 0x21: msi
> em0: Hardware Initialization Failed
> em0: Unable to initialize the hardware
>
> On other reboots, it works fine.
>

Most likely related to the PHY power being turned off.  X540
got a fix for that.  You might want to look through FreeBSD's
e1000 driver looking for the phy power bits relevant to your
model (determine MAC and PHY ids and chip family and then
follow the code).  I've looked briefly some time ago but
nothing has immediately popped at me.

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Hardware Initialization Failed with Intel I219-V

Paul Irofti-4
On 20.12.2016 17:45, Mike Belopuhov wrote:

> On 5 December 2016 at 11:16,  <[hidden email]> wrote:
>>> Synopsis:
>>> Category:
>>> Environment:
>>         System      : OpenBSD 6.0
>>         Details     : OpenBSD 6.0-current (GENERIC.MP) #0: Wed Nov 30 09:19:28 MST 2016
>>                          [hidden email]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
>>
>>         Architecture: OpenBSD.amd64
>>         Machine     : amd64
>>> Description:
>>         I received a few days ago a thinkpad x260. Sometimes em0 won't show up and in
>> dmesg it says:
>> em0 at pci0 dev 31 function 6 "Intel I219-V" rev 0x21: msi
>> em0: Hardware Initialization Failed
>> em0: Unable to initialize the hardware
>>
>> On other reboots, it works fine.
>>
>
> Most likely related to the PHY power being turned off.  X540
> got a fix for that.  You might want to look through FreeBSD's
> e1000 driver looking for the phy power bits relevant to your
> model (determine MAC and PHY ids and chip family and then
> follow the code).  I've looked briefly some time ago but
> nothing has immediately popped at me.
>

I think we need at least

     e1000_power_up_phy_copper
     e1000_power_down_phy_copper

from FreeBSD's dev/e1000/e1000_phy.c.

Speaking of i219 hardware, any idea where the code from if_em.c r1.330
came from? The commit is rather succinct.

I will try to adapt the FreeBSD bits and send a diff today or tomorrow.

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Hardware Initialization Failed with Intel I219-V

Theo Buehler
On Thu, Dec 22, 2016 at 11:37:05AM +0200, Paul Irofti wrote:

> On 20.12.2016 17:45, Mike Belopuhov wrote:
> > On 5 December 2016 at 11:16,  <[hidden email]> wrote:
> > > > Synopsis:
> > > > Category:
> > > > Environment:
> > >         System      : OpenBSD 6.0
> > >         Details     : OpenBSD 6.0-current (GENERIC.MP) #0: Wed Nov 30 09:19:28 MST 2016
> > >                          [hidden email]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> > >
> > >         Architecture: OpenBSD.amd64
> > >         Machine     : amd64
> > > > Description:
> > >         I received a few days ago a thinkpad x260. Sometimes em0 won't show up and in
> > > dmesg it says:
> > > em0 at pci0 dev 31 function 6 "Intel I219-V" rev 0x21: msi
> > > em0: Hardware Initialization Failed
> > > em0: Unable to initialize the hardware
> > >
> > > On other reboots, it works fine.
> > >
> >
> > Most likely related to the PHY power being turned off.  X540
> > got a fix for that.  You might want to look through FreeBSD's
> > e1000 driver looking for the phy power bits relevant to your
> > model (determine MAC and PHY ids and chip family and then
> > follow the code).  I've looked briefly some time ago but
> > nothing has immediately popped at me.
> >
>
> I think we need at least
>
>     e1000_power_up_phy_copper
>     e1000_power_down_phy_copper
>
> from FreeBSD's dev/e1000/e1000_phy.c.
>
> Speaking of i219 hardware, any idea where the code from if_em.c r1.330 came
> from? The commit is rather succinct.

The diff appears to be based on FreeBSD's code. It's discussed here:

https://marc.info/?t=145493623800004&r=1&w=2

>
> I will try to adapt the FreeBSD bits and send a diff today or tomorrow.
>

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Hardware Initialization Failed with Intel I219-V

Paul Irofti-4
>>> Most likely related to the PHY power being turned off.  X540
>>> got a fix for that.  You might want to look through FreeBSD's
>>> e1000 driver looking for the phy power bits relevant to your
>>> model (determine MAC and PHY ids and chip family and then
>>> follow the code).  I've looked briefly some time ago but
>>> nothing has immediately popped at me.
>>>
>>
>> I think we need at least
>>
>>     e1000_power_up_phy_copper
>>     e1000_power_down_phy_copper
>>
>> from FreeBSD's dev/e1000/e1000_phy.c.
>>
>> Speaking of i219 hardware, any idea where the code from if_em.c r1.330 came
>> from? The commit is rather succinct.
>
> The diff appears to be based on FreeBSD's code. It's discussed here:
>
> https://marc.info/?t=145493623800004&r=1&w=2

 From that thread

> - e1000_check_for_copper_link_ich8lan has been ignored.
> - e1000_suspend_workaroudns_ich8lan has been ignored. Suspend does
>   seem to work on my I219_V chip, though.

these might also be worth looking into.

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Hardware Initialization Failed with Intel I219-V

Paul Irofti-4
In reply to this post by Daniel Jakots-3
On 12/5/2016 12:16 PM, [hidden email] wrote:

>> Synopsis:
>> Category:
>> Environment:
> System      : OpenBSD 6.0
> Details     : OpenBSD 6.0-current (GENERIC.MP) #0: Wed Nov 30 09:19:28 MST 2016
> [hidden email]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
>
> Architecture: OpenBSD.amd64
> Machine     : amd64
>> Description:
> I received a few days ago a thinkpad x260. Sometimes em0 won't show up and in
> dmesg it says:
> em0 at pci0 dev 31 function 6 "Intel I219-V" rev 0x21: msi
> em0: Hardware Initialization Failed
> em0: Unable to initialize the hardware
>
> On other reboots, it works fine.

Do you happen to be multi-booting on this machine? I think I found a
reliable way to reproduce this...

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Hardware Initialization Failed with Intel I219-V

Daniel Jakots-3
On Tue, 14 Mar 2017 16:01:16 +0200, Paul Irofti <[hidden email]> wrote:

> On 12/5/2016 12:16 PM, [hidden email] wrote:
> >> Synopsis:
> >> Category:
> >> Environment:  
> > System      : OpenBSD 6.0
> > Details     : OpenBSD 6.0-current (GENERIC.MP) #0: Wed Nov
> > 30 09:19:28 MST 2016
> > [hidden email]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> >
> > Architecture: OpenBSD.amd64
> > Machine     : amd64  
> >> Description:  
> > I received a few days ago a thinkpad x260. Sometimes em0
> > won't show up and in dmesg it says:
> > em0 at pci0 dev 31 function 6 "Intel I219-V" rev 0x21: msi
> > em0: Hardware Initialization Failed
> > em0: Unable to initialize the hardware
> >
> > On other reboots, it works fine.  
>
> Do you happen to be multi-booting on this machine? I think I found a
> reliable way to reproduce this...
>

Yes I guess it's related because I stopped cheating on^W^W multi-booting
and I've never had the problem again.

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Hardware Initialization Failed with Intel I219-V

Paul Irofti-4
>> Do you happen to be multi-booting on this machine? I think I found a
>> reliable way to reproduce this...
>>
>
> Yes I guess it's related because I stopped cheating on^W^W multi-booting
> and I've never had the problem again.
>


I am pretty sure the bug has to do with power management and Wake on Lan
(WoL) settings according to this thread[0].

The em attachement trace I am seeing is

em_read_phy_reg
em_access_phy_reg_hv
em_swfw_sync_acquire
em_get_software_flag
em_read_phy_reg_ex
MDI Error
em_swfw_sync_release
em_release_software_flag
em_set_mdio_slow_mode_hv
em_read_phy_reg
em_access_phy_reg_hv
em_swfw_sync_acquire
em_get_software_flag
em_write_phy_reg_ex
em_read_phy_reg_ex
MDI Error


and adding the phy_power_up_copper() method from the Intel driver is not
enough. I am currently trying to put together the WoL bits to whack the
phy with it.

[0] -- https://bbs.archlinux.org/viewtopic.php?id=191981

Loading...