From: Larry Finger <Larry.Finger@lwfinger.net>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Michael Buesch <mb@bu3sch.de>,
b43-dev@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [RFC/RFT] ssb: Avoid system hang when SPROM read fails
Date: Mon, 26 Apr 2010 13:04:33 -0500 [thread overview]
Message-ID: <4BD5D5B1.6020906@lwfinger.net> (raw)
In-Reply-To: <20100426171505.GC2387@tuxdriver.com>
On 04/26/2010 12:15 PM, John W. Linville wrote:
>
> Well, the "good" news is that I hit the "Unable to read SPROM" case.
> The bad news is that the box still hangs after the -ENODEV. I have
> not yet tracked-down the exact location of the current hang.
>
> John
>
> P.S. Sorry about the 'radio silence' -- I've been distracted with
> some other things. Also, the box in question originally belonged
> to someone else who had configured it in a way that was less than
> friendly to kernel development. I finally reinstalled it...
That box is certainly resistant!
I certainly understand your distractions. That has to be a major
understatement.
As the patch makes some improvement in both your system and the one in
Bug #15825, I'll push it as a real patch.
Would your box be available to me as a loaner? I have considered buying
a netbook for debugging purposes, but I cannot quite justify the cost.
In addition, Murphy's law would make whatever one I bought work without
any problems.
Larry
next prev parent reply other threads:[~2010-04-26 18:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-25 22:30 [RFC/RFT] ssb: Avoid system hang when SPROM read fails Larry Finger
2010-04-26 17:15 ` John W. Linville
2010-04-26 18:04 ` Larry Finger [this message]
2010-04-26 18:32 ` John W. Linville
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=4BD5D5B1.6020906@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
/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;
as well as URLs for NNTP newsgroup(s).