https://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082008-01-27T11:46:02ZDragonFlyBSD bugtrackerDragonFlyBSD - Bug #933: em(4) hardware error after ACPI suspendhttps://bugs.dragonflybsd.org/issues/933?journal_id=42262008-01-27T11:46:02Zsepherosa
<ul></ul><p>Intel does only one eeprom checksum upon em_attach() in their new<br />driver, but I don't think that will solve your problem; I suspect all<br />of the devices' BAR is complete trashed after suspend/resume. Could<br />you apply following patch and post the debug prints?<br /><a class="external" href="http://leaf.dragonflybsd.org/~sephe/em_test.diff">http://leaf.dragonflybsd.org/~sephe/em_test.diff</a></p>
<p>The read back value should not be 0xffffffff</p> DragonFlyBSD - Bug #933: em(4) hardware error after ACPI suspendhttps://bugs.dragonflybsd.org/issues/933?journal_id=42272008-01-27T17:17:01Zmatthias
<ul></ul><p>He sephe,</p>
<p>I've applied the patch, but I don't see any status output. The only<br />change is the following additional line after resume:</p>
<p>Jan 27 10:07:57 jupiter kernel: em0: Memory Access and/or Bus Master<br />bits were not set</p>
<p>Cheers</p>
<pre><code>Matthias</code></pre> DragonFlyBSD - Bug #933: em(4) hardware error after ACPI suspendhttps://bugs.dragonflybsd.org/issues/933?journal_id=42282008-01-27T18:07:01Zsepherosa
<ul></ul><p>Don't have much idea about how ACPI suspend/resume works. But it<br />looks like it calls device attach routine. And the above debug log is<br />benign. Does it mean you will have to manually ifconfig em0 up again<br />after resuming?</p>
<p>Best Regards,<br />sephe</p> DragonFlyBSD - Bug #933: em(4) hardware error after ACPI suspendhttps://bugs.dragonflybsd.org/issues/933?journal_id=42292008-01-27T18:30:01Zmatthias
<ul></ul><p>ifconfig after a resume will not help. The device is completely<br />unusable after the resume. I don't even see an em0 device after a<br />resume.</p>
<p>Regards</p>
<pre><code>Matthias</code></pre> DragonFlyBSD - Bug #933: em(4) hardware error after ACPI suspendhttps://bugs.dragonflybsd.org/issues/933?journal_id=42302008-01-27T18:53:03ZJohannes.Hofmann
<ul></ul><p>Hi,</p>
<p>don't want to discourage you, but I've given up on suspend/resume on<br />my T42p. And I don't even miss it :-)<br />It basically works, but then there are tons of minor issues.</p>
<p>Now I use hw.acpi.lid_switch_state=S5 to shutdown when I close the lid<br />and booting is pretty fast anyway.</p>
<pre><code>Johannes</code></pre> DragonFlyBSD - Bug #933: em(4) hardware error after ACPI suspendhttps://bugs.dragonflybsd.org/issues/933?journal_id=42312008-01-27T21:37:01Zmatthias
<ul></ul><p>Heho,</p>
<p>Yeah, thats right, but I'll continue to use it anyway. Unloading ath(4)<br />and usb works find and due to the fact that I use wireless LAN most of<br />the time I can live with that em(4) issue. And how knows, maybe someone<br />fixes it someday :)</p>
<p>That would be my second choice :)</p>
<p>regards</p>
<pre><code>Matthias</code></pre> DragonFlyBSD - Bug #933: em(4) hardware error after ACPI suspendhttps://bugs.dragonflybsd.org/issues/933?journal_id=42322008-01-28T01:38:00Zsepherosa
<ul></ul><p>Try the following one:<br /><a class="external" href="http://leaf.dragonflybsd.org/~sephe/em_d0.diff">http://leaf.dragonflybsd.org/~sephe/em_d0.diff</a></p>
<p>Best Regards,<br />sephe</p> DragonFlyBSD - Bug #933: em(4) hardware error after ACPI suspendhttps://bugs.dragonflybsd.org/issues/933?journal_id=42442008-01-29T03:02:01Zmatthias
<ul></ul><p>Hi</p>
<p>Doesn't solve the EEPROM checksum problem, but printing the status<br />output works:</p>
<p>Before suspend:</p>
<p>em0: <Intel(R) PRO/1000 Network Connection, Version - 6.2.9> port<br />0x8000-0x803f mem 0xc0200000-0xc020ffff,0xc0240000-0xc025ffff<br />irq 11 at device 1.0 on pci2<br />STATUS 0xc380</p>
<p>After resume:</p>
<p>em0: <Intel(R) PRO/1000 Network Connection, Version - 6.2.9> port<br />0x8000-0x803f mem 0xc0200000-0xc020ffff,0xc0240000-0xc025ffff irq 11 at<br />device 1.0 on pci2<br />STATUS 0xffffffff<br />em0: The EEPROM Checksum Is Not Valid<br />em0: Unable to initialize the hardwar</p>
<p>Is assume that's bad :)</p>
<p>Regards</p>
<pre><code>Matthias</code></pre> DragonFlyBSD - Bug #933: em(4) hardware error after ACPI suspendhttps://bugs.dragonflybsd.org/issues/933?journal_id=53072008-08-20T19:08:09Zsepherosa
<ul></ul><p>hand over to myself</p> DragonFlyBSD - Bug #933: em(4) hardware error after ACPI suspendhttps://bugs.dragonflybsd.org/issues/933?journal_id=113402013-03-09T21:15:59Ztuxillo
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/11340/diff?detail_id=864">diff</a>)</li><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li><li><strong>Assignee</strong> set to <i>sepherosa</i></li></ul><p>Hi Sephe,</p>
<p>I've assigned it to you (as per your last comment).<br />I would suppose this is not relevant anymore since em(4) has been updated several times in the last 4 years.</p>
<p>Cheers,<br />Antonio Huete</p> DragonFlyBSD - Bug #933: em(4) hardware error after ACPI suspendhttps://bugs.dragonflybsd.org/issues/933?journal_id=143572022-06-04T12:30:49Ztuxillo
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/14357/diff?detail_id=4045">diff</a>)</li><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Closed</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>Although it may have worked at some point for some specific hardware, we don't support suspend/resume.</p>