From: Larry Finger <larry.finger@lwfinger.net>
To: roucaries bastien <roucaries.bastien@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
bcm43xx devel <Bcm43xx-dev@lists.berlios.de>
Subject: Re: Bcm43xx oops after suspend to disk
Date: Fri, 26 Jan 2007 09:55:23 -0600 [thread overview]
Message-ID: <45BA246B.6030505@lwfinger.net> (raw)
In-Reply-To: <195c7a900701251530m409878a8id301c7cada76f342@mail.gmail.com>
roucaries bastien wrote:
>> Do you have the log stuff that precedes this part? In particular, was
>> there a assertion that failed?
>>
> It is oops on resume and no asseertion failled this boot. However I
> have usually a lot of
> bcm43xx: ASSERTION FAILED (radio_attenuation < 10) at:
> drivers/net/wireless/bcm43xx/bcm43xx_phy.c:1496:bcm43xx_find_lopair()
Those are well known and do not affect this problem.
> Moreover after the first oops I have a second oops (Surelly a
> consequence of the first).
I think that is right.
Unfortunately, I cannot test for this problem on my system as it doesn't suspend at all.
Does this oops happen every time, or is it intermittent? I'm looking at the code to find places to
insert debugging statements. At present, I don't understand how it gets to the shutdown code while
resuming!
Larry
next prev parent reply other threads:[~2007-01-26 15:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <45B92488.6090908@lwfinger.net>
2007-01-25 21:46 ` Bcm43xx oops after suspend to disk Larry Finger
2007-01-25 23:30 ` roucaries bastien
2007-01-26 15:55 ` Larry Finger [this message]
2007-01-29 11:58 ` Pavel Machek
2007-01-29 12:55 ` roucaries bastien
2007-01-29 14:04 ` Matthew Garrett
2007-01-29 15:43 ` Larry Finger
2007-02-04 17:07 ` roucaries bastien
2007-02-04 17:42 ` Larry Finger
2007-02-05 1:10 ` Rafael J. Wysocki
2007-02-05 3:19 ` Larry Finger
2007-01-25 19:18 roucaries bastien
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=45BA246B.6030505@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=Bcm43xx-dev@lists.berlios.de \
--cc=linux-kernel@vger.kernel.org \
--cc=roucaries.bastien@gmail.com \
/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