Date: Wed, 13 May 2009 19:18:52 +0200 From: Guy Brand <gb@unistra.fr> To: freebsd-current@FreeBSD.org Subject: Re: [Fwd: Re: amd64 suspend/resume broken on current] Message-ID: <20090513171851.GA2582@unistra.fr> In-Reply-To: <200905111602.20462.jkim@FreeBSD.org> References: <4A058B5C.3010707@FreeBSD.org> <200905111529.12808.jkim@FreeBSD.org> <200905111602.20462.jkim@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Jung-uk Kim (jkim@FreeBSD.org) on 11/05/2009 at 16:02 wrote: Hello > Can you try the attached patch? I may be wrong cause I am not a > firewire guru, though. I can, but I updated (csup) my sources yesterday and resuming works fine again without your patch applied. I now have: FreeBSD 8.0-CURRENT #12: Wed May 13 11:22:30 CEST 2009 ... acpi_lid0: Lid closed fwohci0: fwohci_pci_suspend acpi_ec0: warning: EC done before starting event wait stray irq0 ugen0.2: <STMicroelectronics> at usbus0 (disconnected) ugen4.2: <Sierra Wireless, Incorporated> at usbus4 (disconnected) wpi0: could not lock memory wpi0: could not lock memory wpi0: could not lock memory wpi0: could not lock memory wpi0: could not lock memory wpi0: could not lock memory wpi0: could not lock memory wpi0: could not lock memory wpi0: timeout waiting for master fwohci0: device physically ejected? uhci_interrupt: resume detect fwohci0: device physically ejected? fwohci0: device physically ejected? fwohci0: device physically ejected? fwohci0: device physically ejected? fwohci0: device physically ejected? fwohci0: device physically ejected? fwohci0: device physically ejected? fwohci0: device physically ejected? fwohci0: device physically ejected? wlan0: link state changed to DOWN fwohci0: device physically ejected? fwohci0: device physically ejected? fwohci0: device physically ejected? fwohci0: device physically ejected? fwohci0: device physically ejected? fwohci0: device physically ejected? fwohci0: device physically ejected? ugen0.2: <STMicroelectronics> at usbus0 fwohci0: device physically ejected? fwohci0: device physically ejected? fwohci0: device physically ejected? fwohci0: device physically ejected? fwohci0: device physically ejected? fwohci0: device physically ejected? fwohci0: device physically ejected? fwohci0: device physically ejected? fwohci0: device physically ejected? fwohci0: device physically ejected? fwohci0: device physically ejected? fwohci0: device physically ejected? fwohci0: device physically ejected? fwohci0: device physically ejected? fwohci0: device physically ejected? fwohci0: device physically ejected? fwohci0: device physically ejected? fwohci0: device physically ejected? fwohci0: device physically ejected? fwohci0: device physically ejected? fwohci0: device physically ejected? fwohci0: device physically ejected? fwohci0: device physically ejected? fwohci0: device physically ejected? fwohci0: device physically ejected? fwohci0: device physically ejected? fwohci0: device physically ejected? fwohci0: device physically ejected? fwohci0: device physically ejected? fwohci0: Phy 1394a available S400, 1 ports. fwohci0: Link S400, max_rec 2048 bytes. fwohci0: Initiate bus reset fwohci0: fwohci_intr_core: BUS reset fwohci0: fwohci_intr_core: node_id=0x00000000, SelfID Count=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0 cable IRM irm(0) (me) firewire0: bus manager 0 fwohci0: unrecoverable error so the repeating fwohci0 stops and the system is working fine. I only had to apply you two line patch to fix sys/netinet/in.c to get network devices working properly, but that's another issue. All the best -- bug
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090513171851.GA2582>