Re: em(4) hardware error after ACPI suspend

[Matthias Schmidt <matthias@xxxxxxxxxxxxxxxx>]

Hi

* Sepherosa Ziehau wrote:
> On Jan 27, 2008 6:26 PM, Matthias Schmidt <matthias@dragonflybsd.org> wrote:
> > * Sepherosa Ziehau wrote:
> > > On Jan 27, 2008 5:13 PM, Matthias Schmidt <matthias@dragonflybsd.org> wrote:
> > >
> > > Don't have much idea about how ACPI suspend/resume works.  But it
> > > looks like it calls device attach routine.  And the above debug log is
> > > benign.  Does it mean you will have to manually ifconfig em0 up again
> > > after resuming?
> >
> > ifconfig after a resume will not help.  The device is completely
> > unusable after the resume.  I don't even see an em0 device after a
> > resume.
> 
> Try the following one:
> http://leaf.dragonflybsd.org/~sephe/em_d0.diff

Doesn't solve the EEPROM checksum problem, but printing the status
output works:

Before suspend:

em0: <Intel(R) PRO/1000 Network Connection, Version - 6.2.9> port
0x8000-0x803f mem 0xc0200000-0xc020ffff,0xc0240000-0xc025ffff
irq 11 at device 1.0 on pci2
STATUS 0xc380

After resume:

em0: <Intel(R) PRO/1000 Network Connection, Version - 6.2.9> port
0x8000-0x803f mem 0xc0200000-0xc020ffff,0xc0240000-0xc025ffff irq 11 at
device 1.0 on pci2
STATUS 0xffffffff
em0: The EEPROM Checksum Is Not Valid
em0: Unable to initialize the hardwar

Is assume that's bad :)

Regards

	Matthias