From: Peter Meier <crazy-b-Mmb7MZpHnFY@public.gmane.org>
To: Pekka Pietikainen <pp-YuCZbdju05vHOG6cAo2yLw@public.gmane.org>
Cc: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
davem-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Subject: Re: b44 -- Re: No network after S3
Date: Thu, 26 Feb 2004 16:48:45 +0100 [thread overview]
Message-ID: <1077810525.5332.51.camel@homer> (raw)
In-Reply-To: <20040224223421.GA6225-YuCZbdju05vHOG6cAo2yLw@public.gmane.org>
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.
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
next prev parent reply other threads:[~2004-02-26 15:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-16 6:10 No network after S3 Brown, Len
[not found] ` <BF1FE1855350A0479097B3A0D2A80EE0025A6344-N2PTB0HCzHJF3Yvz3xaN/VDQ4js95KgL@public.gmane.org>
2004-02-16 11:02 ` Peter.Zeipelt-zqRNUXuvxA0b1SvskN2V4Q
2004-02-16 13:17 ` Thorsten Zachmann
[not found] ` <200402161417.42755.t.zachmann-c61pB8mzqkY@public.gmane.org>
2004-02-17 6:53 ` Len Brown
[not found] ` <1077000806.2515.46.camel-D2Zvc0uNKG8@public.gmane.org>
2004-02-17 7:56 ` Thorsten Zachmann
[not found] ` <200402170856.42059.t.zachmann-c61pB8mzqkY@public.gmane.org>
2004-02-24 6:41 ` Thorsten Zachmann
[not found] ` <200402240741.30530.t.zachmann-c61pB8mzqkY@public.gmane.org>
2004-02-24 16:41 ` Peter Meier
[not found] ` <1077640877.5369.12.camel-0dCjsm2Eg2I@public.gmane.org>
2004-02-24 22:00 ` b44 -- " Len Brown
[not found] ` <1077660024.3036.56.camel-D2Zvc0uNKG8@public.gmane.org>
2004-02-24 22:34 ` Pekka Pietikainen
[not found] ` <20040224223421.GA6225-YuCZbdju05vHOG6cAo2yLw@public.gmane.org>
2004-02-26 15:48 ` Peter Meier [this message]
2004-02-26 15:50 ` Peter Meier
2004-02-17 21:49 ` Peter.Zeipelt-zqRNUXuvxA0b1SvskN2V4Q
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1077810525.5332.51.camel@homer \
--to=crazy-b-mmb7mzphnfy@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=davem-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=pp-YuCZbdju05vHOG6cAo2yLw@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox