On Wednesday, 23 of January 2008, Celejar wrote:
> On Wed, 23 Jan 2008 16:00:15 +0100
> "Rafael J. Wysocki" <[EMAIL PROTECTED]> wrote:
>
> > On Wednesday, 23 of January 2008, Celejar wrote:
> > > Hi,
> >
> > Hi,
> >
> > > I know there's an ongoing long thread about suspend in b43, but
> > > the technical level has been above me, and I don't know if anything
> > > there is relevant to me.
> > >
> > > When I suspend to disk ('s2disk' from uswsusp), the resume fails if b43
> > > is loaded. The screen stays blank, although I see a cursor flashing.
> > > 'modprobe -r b43' before suspending makes the resume work fine, but if I
> > > subsequently load b43 after the resume the machine freezes.
> >
> > Hm, I use b43 w/ s2disk on a regular basis and it works, but openSUSE has a
> > userland suspend hook that disables NetworkManager before a suspend.
> >
> > > I am using Debian Sid, b43 from vanilla kernels from kernel.org (2.6.24
> > > isn't in Debian yet). I have had this problem with -rc4 and -rc8. the
> > > only two I've tried. HW is a 4318 Air Force One, in an Acer Aspire
> > > 3690-2672. Is there any debugging info I can provide? Is this a known
> > > problem? Is there anything I should try?
> >
> > Please try to switch off the interface before suspend without unloading the
> > module.
>
> I did 'ifdown eth0' followed by 'ifconfig eth0 down'; I assume that's
> what you meant. I do have some sort of HW switch, but I never touch it.
>
> The machine came up okay. 'ifconfig -a' shows eth0 (unconfigured), but
> 'ifup eth0' and even 'ifconfig eth0 up' returns 'SIOCSIFFLAGS: no such
> device. lsmod shows that b43 is still there. When I then did
> 'modprobe -r b43' followed by 'modprobe b43', the machine froze - no
> screen output after the module insertion.
When 2.6.24 is out, please test it, but make sure you don't set
USB_OHCI_HCD_SSB.
> > Also, does s2ram work on your box?
>
> I've never gotten it to resume correctly. I tried at one time
> many / most of the s2ram option suggestions from the
> README.s2ram-whitelist, but nothing worked, and I eventually ran out of
> patience for the sort of experimenting that required constant hard
> power offs and reboots.
There are some suspend debug patches scheduled for 2.6.25 time frame. If they
get merged, we'll be able to check what's going wrong here.
Thanks,
Rafael
_______________________________________________
Bcm43xx-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
