Bug 136946 - [fwohci] [suspend/resume] fwohci throws an "unrecoverable error" upon resume from suspend
Summary: [fwohci] [suspend/resume] fwohci throws an "unrecoverable error" upon resume ...
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 8.0-BETA2
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-21 02:00 UTC by Gonzalo Nemmi
Modified: 2017-12-31 22:23 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gonzalo Nemmi 2009-07-21 02:00:16 UTC
Running a fresh 8.0-BETA2 install (i386), everytime I resume my laptop from suspend I get the following output:

Jul 20 17:53:51 gargoyle acpi: suspend at 20090720 17:53:51
Jul 20 17:53:56 gargoyle kernel: fwohci0: fwohci_pci_suspend
Jul 20 17:54:25 gargoyle kernel: bge0: PHY write timed out (phy 1, reg 0, val 32768)
Jul 20 17:54:25 gargoyle kernel: bge0: PHY read timed out (phy 1, reg 0, val 0xffffffff)
Jul 20 17:54:25 gargoyle kernel: bge0: PHY read timed out (phy 1, reg 24, val 0xffffffff)
Jul 20 17:54:25 gargoyle kernel: bge0: PHY read timed out (phy 1, reg 16, val 0xffffffff)
Jul 20 17:54:25 gargoyle kernel: bge0: PHY write timed out (phy 1, reg 16, val 0)
Jul 20 17:54:25 gargoyle kernel: bge0: PHY read timed out (phy 1, reg 16, val 0xffffffff)
Jul 20 17:54:25 gargoyle kernel: bge0: PHY write timed out (phy 1, reg 16, val 0)
Jul 20 17:54:25 gargoyle kernel: bge0: PHY write timed out (phy 1, reg 23, val 18)
Jul 20 17:54:25 gargoyle kernel: bge0: flow-through queue init failed
Jul 20 17:54:25 gargoyle kernel: bge0: initialization failure
Jul 20 17:54:25 gargoyle kernel: fwohci0: Phy 1394a available S400, 1 ports.
Jul 20 17:54:25 gargoyle kernel: fwohci0: Link S400, max_rec 2048 bytes.
Jul 20 17:54:25 gargoyle kernel: fwohci0: Initiate bus reset
Jul 20 17:54:25 gargoyle kernel: fwohci0: fwohci_intr_core: BUS reset
Jul 20 17:54:25 gargoyle kernel: fwohci0: fwohci_intr_core: node_id=0x00000000, SelfID Count=1, CYCLEMASTER mode
Jul 20 17:54:25 gargoyle kernel: firewire0: 1 nodes, maxhop <= 0 cable IRM irm(0)  (me) 
Jul 20 17:54:25 gargoyle kernel: firewire0: bus manager 0 
Jul 20 17:54:25 gargoyle kernel: fwohci0: unrecoverable error
Jul 20 17:54:25 gargoyle kernel: wakeup from sleeping state (slept 00:00:29)
Jul 20 17:54:25 gargoyle acpi: resumed at 20090720 17:54:25

As you can see from the messages, bge never gets back (PR 136876)

Full boot-v can be foun in here: http://pastebin.com/f32612f89

This happens on a Dell 1318 laptop and it's also present on FreeBSD 7.2-RELEASE and 8.0-BETA1.

more info:

How-To-Repeat: I just need to issue a "acpiconf -s 3" and, upon resume, I will always get the same output on:

7.2-RELEASE
8.0-BETA1
8.0-BETA2
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2009-07-21 02:03:56 UTC
Responsible Changed
From-To: freebsd-bugs->freebsd-net

Over to maintainer(s).
Comment 2 Mark Linimon freebsd_committer freebsd_triage 2009-07-21 05:51:09 UTC
Responsible Changed
From-To: freebsd-net->freebsd-firewire

fix assignment.
Comment 3 sean.bruno 2009-07-22 17:40:06 UTC
Thanks.  This is perfect.

I seem to remember looking at suspend/resume at BSDCan and realizing
that it's pretty broken.  I forgot to submit a PR at the time, thanks
for putting this in.

Since the firewire stack is in multiple parts, I'll have to think about
how each module needs to save it's respective state and what to do on
resume.

Thoughts?

Sean
Comment 4 Gonzalo Nemmi 2009-07-22 20:55:52 UTC
Thanks a lot for you interest !

Not much I can do to help on the coding side of things but I'm willing 
to try any patch you need me to, give you root acces via ssh to this 
machine should you need it and to look for a firewire appliance in 
order to run any possible test.

Basically .. I can't code, but Im really willing to do everything I can 
to pitch in to solve this problem :)

Best regards
Gonzalo
Comment 5 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 08:00:51 UTC
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped