Re: b44 -- Re: No network after S3

Peter Meier
2004-02-26T15:48:45Z

Hi,

that fix didnt work for me. Here is what I did:
I downloaded the broadcom driver 3.0.7 and installed the modules. I
rebootet, put the machine to sleep, and got follwing error message after
wake-up:

ASSERT failed: b44_LM_sb_coreid(pDevice) == SB_PCI
ASSERT failed: b44_LM_sb_coreid(pDevice) == SB_PCI
SBTMH_SERR; clearing...
ASSERT failed: 0
ASSERT failed: 0

Then, I rebootet, rmmod the driver before going to sleep, and modprobed
it after wake-up. Leads to follwing error message:

Broadcom 4401 Ethernet Driver bcm4400 ver. 3.0.7 (10/31/03)
PCI: Enabling device 0000:02:02.0 (0000 -> 0002)
PCI: Setting latency timer of device 0000:02:02.0 to 64
Get Adapter info failed

I then changed the line 417 in b44lm.c as suggested in bug id 2030.
Still, nothing changed. After playing around, I finally decied to get
back to my "normal" b44 - and had that bug described. Booting into XP
didnt help, and your "fix" described didnt work, too. Only thing that
solved the problem was disconnecting power and shutdown the system.

On Tue, 2004-02-24 at 23:34, Pekka Pietikainen wrote:
> I was recently able to reproduce a bug that sounds related,
> http://bugme.osdl.org/show_bug.cgi?id=2030 has the details.
> Would be interesting to know whether the "fix" I found (running
> _only_ the initialization part of the bcm4400 driver) helps in this case too.
>
> Broadcoms changelog provides some clues about what kind of access patters
> make the chip break.
>
> Current guesses are ssb_* (maybe ssb_is_core_up returning 1
> even when it isn't leading to ssb_pci_setup not getting called)
> and b44_setup_phy (where the register access pattern differs slightly).
> It didn't work even after altering the register access patterns to be ~=
> identical, making sure ssb_pci_setup gets run etc., alas, but I
> probably missed something.
>
> Anyway, I'm working on it, but no guarantees on when I'll find the time to
> nail it down.